[NTLK] What to do next

[NewtonTalk]

Just my very personal opinion. But since you asked...

> 1: AI: feed a local AI with all documentation we can find a see if we can get a specialized LLM running for Newton questions.

I think there are more important issues. And the Newton Glossary is coming along nicely.

> 2: Einstein: the emulator still works fine, but it could use a general overhaul to modern C++ and maybe new minor features.

That would mostly help those who are working on Einstein. The people using it would hardly notice the difference.

> 3: Einstein on Android: the old Android apk works, but it is no longer maintainable or upgradable.

Funny that you mention this. I've recently contemplated that I don't know enough about writing Amazon Apps and should install the latest version of Android Studio on my new Windows 11 computer to change this. My intention was starting with a Hello World App, but why not start with Einstein...

> 4: NCX: NCX mostly works. We have access to the source code and I managed to recompile it on modern macOS. Question is, is current NTX good enough for everyone?

It would be cool if it ran on Windows or Linux, but I don't think it's strictly necessary. I've always been able to figure out a way to run the Newton Connection Utilities in a Virtual Machine. Provided there's a sufficient amount of slowdown.exe instances around. When I started writing Newton software, one instance was sufficient. On my 14 year old Windows 7 computer I need between 5 and 6. I haven't even tried how many I would need on my Windows 11 computer, which is a decade younger and significantly faster. If there's one thing I would consider an incredibly helpful development, it would be removing the necessity for slowdown.exe under Windows.

> 5: E-Paper display retrofit: I did find an e-Paper touch display that could work with existing MP2x00 and eMates.
> Not sure if there is anyone ready to modify their machines, or if using a modern e-Paper device with Einstein ist better.

To a certain degree, of course, this is a philosophical question. A modern E-Reader might be faster and more modern, but in my humble opinion nothing beats a REAL Newton. If the display would physically fit in a 2x00 case, this would be really cool. Missing backlight might be a drawback, but considering how tiny SMD LEDs have become, it would probably be possible to put some of those in, too. Rest assured that there's at least one person who would be willing to modify one or more machines. And he's living not so far away from you :-)

> 6: Wifi Modem Card: Based on Jake Bordens awesome ESP32 board, we could create an internalboard for the
> modem port that combines the USB dongle functionality with modern Wifi and possibly even bluetooth.

In my opinion this is cool, but a version working decently on Android would be cooler.

== Newton apps development ==

> 7: Despite adding a compiler to Einstein, I have not seen new apps for NewtonOS.
> Not complaining, since I have not written one myself either, but the question is,
> does it make any sense to invest time into a: improving the Einstein Toolkit, or b:
> documenting NTK with BasiliskII and Einstein

I think most people are, and have been for decades, more or less satisfied with the software that already exists. Most of what people would like to see wouldn't be possible due to the Newton's limited resources and speed. If I were to write a new Newton App, I would ALWAYS use the Newton Toolkit in a Windows Virtual Machine. There are heaps of documentation for NewtonScript and the NTK out there.

> 10. Write an interface (similar to WINE that runs Windows apps on macOS and Linux).

I'd not spend any time on that. The Newton is a synthesis of the arts. It would be most helpful to keep it that way, but spend time on making using it more easy.

Be aware, though, that whatever you decide on will use an additional amount of your time for getting willing helpers on their way. Provided there are any.

Regards

Frank

-- Newton software and hardware at http://www.pda-soft.de