If you were a betting TI'er

[Omega-TI]

If you were a betting TI'er, do you think there will ever be a Lynx type browser (in 512K cartridge form) for the TIPI/Rpi/F18A?

Yes, no? If yes, when do you think the earliest something like this would or could arrive on the scene?

[Omega-TI]

Based upon participation levels (so far) and the results (so far), I can arrive at only one conclusion (so far)...

 

 

[Omega-TI]

Here they found a 'workaround' to get a 64K IMSAI 8080 on the Internet...

https://www.youtube.com/watch?v=nq4g6SLC8NM

Seems to me using the TELNET program in TIPI...

[Casey]

I was about to suggest it would be easily possible just to telnet into the pi from the TI and install Lynx inside the raspberry pi. It's not as simple as having it directly available on the TI, but it'd be close.

[iKarith]

Stuart's browser doesn't actually use "proper" HTML for what it supports. That could be fixed I suppose. The issue is that Lynx is not small and a lot of web browsers REQUIRE encryption today the TI is going to have a hard time doing quickly. It could be done I suppose, but you'd want a proxy to handle HTTPS. The question's really going to be ultimately how much do you want to do on the TI and how much off of it?

[Omega-TI]

The question's really going to be ultimately how much do you want to do on the TI and how much off of it?

 

That is one loaded question!

 

Depending on the hobbyist, some people don't want anything that requires any processing off the TI.

 

Some hobbyists don't mind if an attachment simply emulates current TI hardware... but don't want any 'extra features' that a normal TI could not run.

 

There are also hobbyists that don't want specific hardware items that add new capabilities to new hardware items... even if the item in question already does stuff a normal TI could never do.

 

BITD much third party hardware added extra abilities or capabilities not normally found on original TI hardware, but again, for some, there appears to be an arbitrary cut-off date for new hardware adding new capabilities.

 

It all gets so confusing to me.

[RXB]

If the SAMS and a cart to load that SAMS is available it should be possible to make a Linux cut down version.

 

On 14 March 1994, Linux kernel 1.00 was released, with 176,250 lines of code.

 

RXB uses 26405 lines of code (GROM & Assembly) and does not put any into the SAMS as of yet to function.

 

One Meg SAMS is 1000000 bytes and a 4 Meg SAMS would be 4000000 bytes, so 4 bytes per line of code would be 705000 used (average).

 

This would leave over 3200000 bytes of SAMS available for programs.

Edited June 20, 2018 by RXB

[Omega-TI]

If the SAMS and a cart to load that SAMS is available it should be possible to make a Linux cut down version.

 

On 14 March 1994, Linux kernel 1.00 was released, with 176,250 lines of code.

 

RXB uses 26405 lines of code (GROM & Assembly) and does not put any into the SAMS as of yet to function.

 

One Meg SAMS is 1000000 bytes and a 4 Meg SAMS would be 4000000 bytes, so 4 bytes per line of code would be 705000 used (average).

 

This would leave over 3200000 bytes of SAMS available for programs.

 

While technically possible, the sheer amount of coding involved forces me in the column of the majority.

Who the heck would ever have the time to do that!?! I'd love to see it, but can't imagine anyone tackling it.

 

Speaking of the SAMS... with some of the new hardware permutations, there are things possible that I doubt anyone has considered yet, so there may be some new development yet for it. Future still looks bright!

 

https://www.youtube.com/watch?v=8qrriKcwvlY