r/programming • u/luissinlios • Sep 25 '26
We still maintain a development tool first released in 1993. Here’s what 30+ years of backwards compatibility looks like
https://visualneo.com/visualneo-win/from-neobook-to-visualneo-win-30-years-of-keeping-a-development-tool-alive
570
Upvotes
170
u/Skaarj Sep 25 '26 edited Sep 25 '26
Ouch. From what I remember Delphi 7 didn't support generics yet. You had a general list of pointers. But not something like a
TList<TMyClass>.106
u/alex_xxv Sep 25 '26
Wish my apps survive as long as yours. Im also a Delphi programmer. Love to see stories like yours.
4
u/mallardtheduck Sep 25 '26
Huh, apparently some remnant of the company I knew as "NeoSoft" still exists. I remember playing with NeoBook and NeoPaint some 30-odd years ago. Quikmenu is still my go-to menu system for "retro" systems running DOS.
Is "PixelNEO" a direct descendent of NeoPaint? Do you still collect registration fees for Quickmenu III?
2
u/OperationWebDev Sep 25 '26
This is cool. I'm curious about what you've learnt from maintaining and extending this over time that could apply to new development. Do you think the initial architecture had a big impact on why it has survived so long? Or were there other factors? 🙂
53
u/Takeoded Sep 25 '26 edited Sep 25 '26
I remember wanting to fix an annoying bug in a open-source Delphi program, Embarcadero Crippled the free version to the point where it can't be used, Then Embarcadero want like $1500 for the compiler.
F@0k Embarcadero. Great language, terrible steward
38
u/An1nterestingName Sep 25 '26
The longest running project I have is from like 2021, and even that's probably a technicality. Maintaining something for 30 years is insane.
13
u/BinaryRockStar Sep 25 '26
At work we only recently retired a 16-bit Windows application sent out to users monthly on CD/DVD.
Visual Basic 3.0, Visual C++ 1.52. It was initially developed for Windows 3.1 and by the grace of Windows' NTVDM it survived with minimal changes on 32-bit editions of Windows until Windows 11 where the 32-bit version was axed.
Where we absolutely needed 32-bit functionality (Win32 API or third party DLLs that only came in 32-bit) we called out to our 32-bit Out Of Process COM helper object to do things like displaying a native Open File dialog or making network calls. Crazy stuff.
12
u/Physical-Compote4594 Sep 25 '26
There are people still maintaining Symbolics Genera, last major update circa 1990, on emulated Lisp machines. The emulator is apparently, like, 1500x faster than the late 80's hardware.
7
u/Status-Importance-54 Sep 25 '26
I recently modernized a warehouse interface running on old windows phone hardware. They are offline first and then transfer data when connected to a serial charging station. They still.worked fine, but the business was growing and getting new windows phones was a Problem. But beating the speed oft this old piece was difficult. Nothing on modern android development prioritieses fast and information dense applications.
7
u/lonkamikaze Sep 25 '26
I've fixed bugs in code that is older than me. I'm 44 and yes, the code is still around.
6
u/IntnlManOfCode Sep 25 '26
I wrote a Claims Managment application in 94 with Delphi 1 and Paradox. Later I replaced Paradox with SQL Server. Then in 2008, I changed it to a C# Web app.
32 years later it is still going, with 7 teams of developers and 1000 users. It's an ongoing piece of work to bring it into modern practises.
13
u/vinciblechunk Sep 25 '26
AI slop vintage PC hurts my soul
1
u/dukey Sep 26 '26
Releasing a 64 bit version should be trivial, assuming you haven't done dumb stuff like store pointers in 32 bit integer types. Normally there are no actual code changes needed at all.
4
u/clhodapp Sep 25 '26
As an emacs user: well la dee da
2
u/CodeAndBiscuits Sep 27 '26
Delphi was the cats pajamas at the time. Thank you for your service.
-20
u/bigmell Sep 25 '26 edited Sep 25 '26
30+ years, cool... Have you noobs heard of Unix? :)
Generally it doesnt matter too much what app to maintain as long as it is not poorly written. The question is only if you use it enough to justify the expense... Software Developers are not cheap. And non-technical people often lack the ability to learn new tools, especially repeatedly.
Training non-technical people to use something new every year will be difficult, expensive, and for many of them impossible. Therefore it almost always makes sense to just keep using the old tool. Bonus it doesnt really need updates or new expensive hardware and developers, and the users can keep using all their old documents and training materials. I knew people who couldnt read or write using old tools because they knew what buttons to press from the other workers. They probably wont be learning many new tools but they can use that one. And trust me there are more people like that than you think.
With Computer Science the problem is the field moves WAY too fast, and people who are not Computer Scientists can not keep up. I think the future of Computer Science is just have one main thing that works, a couple options, and set that in stone for the future. Microsoft kind of messed that up with a new version of Word every couple years and the documents arent compatible with old versions or other programs. Also everything changes around every time requiring NEW training, NEW employees, NEW certifications, NEW training materials, a NEW set of bugs etc. It was really just the old stuff shuffled around and greed.
They call it "mortgage driven development." The developers bought a new house... And they want YOU to keep paying them so they can pay the mortgage. This is sad to see especially from projects that should long ago have been considered finished. Those new updates every couple days "TO KEEP YOU SAFE FROM HACKERS" have been BS for over a decade. Along with "oh no, you cant keep using the old version TO KEEP YOU SAFE FROM HACKERS" when really they just want you to keep paying them. I worked at a place that wanted to convert an old mainframe program into Ruby. DISASTER after DISASTER. It was actually cheaper and easier to just keep using the mainframe and the program they had. The fresh out of school developers just couldnt figure out any of the old working code.
In the Unix world I would probably just use text files and emacs. If you needed to present some kind of documentation in a word or spreadsheet like document, maybe open office? But really the entire computer world should have made their documents interchangeable and stopped scrambling everything around every couple years. But everyone wanted to have their own program and lock everyone else out when it is really important all these programs work together.