251–260 of 363 posts
2000. VB6. Manufacturing workflow / management system, BOM..... I did some consulting work at the same company a year ago and that system was still chugging along. They had pretty much rewritten / replaced everything else around the place but apparently didn't see a need to change my module. I was amused to have a couple of guys come and ask me questions/advice, and all I could do was sympathize.
2012 for me. Also VB6 though...
My "personal" website that I made when I was a kid at 2001. I think that I uploaded it to the Geocities free hosting and soon forgot about it. Then a few years back when I googled my name I stumbled upon it haha It is still up after more than 15 years on god know which free hosting and server, it was so funny. And of course it is used as a joke now by my friends :) And of course I have forgot my credentials long long…
I wrote a fax->email gateway in 2002 that's still in very active use.. wouldn't be that remarkable, except most of the servers are still running original equipment with original hard drives! Anyone have servers running 24x7 with hard drives older that that?
A system information app I originally wrote for Windows 98, but subsequently added support for NT-class Windows client, still runs and works almost perfectly today (with graceful feature degredation) on Windows 10. I do a tiny amount of work for every new Windows that's released, to support it. Sometimes no work at all. The codebase was originally written in 1998. Nobody uses it now apart from me, but I still maintai…
Would be very interested in this. Might even use it over winver/dxdiag ;)
Several VB6 based tools from 1999 are still in use. They still work just fine in Win 7 64-bit. (VB6 was the best RAD tool from Microsoft, great integration with Windows and was part of the "information at your fingertip" vision. Then Java happend and Microsoft frantically tried to create something similar. 15 lost years, nowadays compiled languages and on the otherside dynamic languages like Javascript succeeded. And…
Every once in a while it would miss some files in its directory listings. Took me forever to figure out that it only occurred when the new SAN was under heavy load and took longer than half a second to return a directory listing.
I laughed when I came across this:
Problems Using Intrinsic File System Controls https://support.microsoft.com/EN-US/kb/196141
SYMPTOMS: When you are using the intrinsic Visual Basic file system controls (for example, DriveListBox, DirListBox, FileListBox), some or all of your files are not listed. This usually occurs when you are trying to access files on a network server, but can occur locally under some circumstances.
CAUSE: ... These controls are old technology. They were not designed for, nor tested with, some of the new operating and network system software. ...
I just made it sleep for a second and then refresh its directory listings, sigh.. not gonna rewrite this thing now..
I wrote the Oracle driver for the AOLserver web server in 1997. Last year I met a guy who worked at Zipcar who said they were still using it.
I released the first content management system for websites back in about 1995. It was a fully database driven system with different post types, much like WordPress in design, and editable page content.
About 15 years ago, I wrote an entire web-based system for managing an online grocery delivery company. The whole site runs off of version 2 of that content management system, which had lots of the version 1 code in it, which is now 21 years old.
And yes, they are still running their whole business off of that unmodified system today! I should have put them onto a monthly maintenance plan. ;-)
Sadly, I hear that they will be finally replacing it soon, putting an end to that legacy code.
There's an entire community of video game hackers (smwcentral.net) using a cross-assembler I wrote in 2001 named xkas. I added a few minor patches and by early 2004 I had released the final version, v06. I never really intended for anyone to use it seriously. I made it for myself, but went ahead and posted it online anyway. It is a 1500-line single-file, nearly-commentless, nearly-spaceless abomination of code with n…
I like this: http://www.romhacking.net/utilities/269/ "Newer versions have been released, however contain poor documentation, and removal of features that can be found in v0.06. Version 0.06 is still considered the best version available by most ROM hackers until the author addresses the shortcomings of subsequent versions."
The newer versions are called bass, and you can compare yourself here: http://byuu.org/tool/bass/
There is full documentation of every possible command, the code is readable by human beings (eg variables are named words instead of single letter abbreviations, C++ is used for more than just the class keyword, there's more than one source code file, I learned how to use the spacebar key in my code, etc), it has a real recursive descent parser that builds a proper abstract syntax tree for evaluations, it has a macro system that supports recursion and conditional evaluation, supports multiple architectures instead of just one, allows the user to dynamically add/change the actual opcode mnemonics used by the assembler (useful as the SNES has games using several strange coprocessors), has no known bugs (as opposed to xkas' that allow native code execution), etc. xkas was written when I had about a years' worth of real programming experience, bass was after over a decade's worth of experience; including experience using assemblers to create code.
If you want to know why RHDN users threw a fit about it; it's because I used // as a comment delimiter instead of ; and decided to add a closing marker to defines so you could say "lda {macro}_b", which was impossible with the old "lda !macro_b" because it'd look for "macro_b" instead of "macro".
That's really it. That's the whole of why many people there say they'll never use it. The syntax is 99% compatible otherwise. I could link you to posts saying as much, but I really don't feel like browsing their site any more than I have to.
SMWC's case is very different: they're all hacking the same game, so they require 100% backward-compatibility with a decade's worth of game patches; and they only make the problem worse as time goes on. This constraint would not apply to new games started on from scratch.