The punchline, I suppose, is that we did switch from MSSQL to Mogile and, eventually, S3. But we still had the code to sometimes store attachments in the DB because that’s how we shipped complete backups to customers!
We still had about a dozen developers combined on FogBugz+Kiln at the very end.
The plug-in API was very bad for performance and security, especially in a multitenant cloud application. That led a team to experimentally reimplement the entire frontend as a single-page app (code named Project Ocelot, whose shirt I am wearing today). Webhooks and a well-designed web API would have been a much tidier solution than the plug-in API.
FogBugz For Your Server had constant support costs, like Ben said, but also the application started growing all sorts of supporting services (a QueueService, an ElasticSearch cluster, Redis…) that made the existing InstallerShieid installer a huge cost to maintain.
Later, I wrote an “autosetup” script in PowerShell to help developers and support engineers onboard faster, which later became the new installer for FogBugz On-Site / Manuscript On Premises. It was designed for a single edition of Windows (Server 2012 iirc?) and SQL Server. We sold a million bucks worth of licenses for that.
I was at the strategic offsite where we decided to go with .NET. Java wasn’t installed on Windows by default.
The original version of Wasabi, known as Thistle, was written in Java, by the intern in the class before Aardvark’d. It transpiled ASP to PHP.
Every intern class was named after an animal with the next consecutive letter. I don’t remember any of them except Aardvark, and I was a “B????” intern!
Nintendo partnered with Ricoh to put a Z80 in the NES, like Coleco and Sega, but Ricoh didn’t have the license to produce Z80s and didn’t think they would be able to reverse engineer it quickly enough. But they did have a reverse-engineered 6502 clone with the patented bits removed, and US copyright law didn’t cover IC lithography yet, and would they be interested in that instead?
> that heat is being generated less efficiently than a purpose-built device.
“efficiency” is meaningless when heat is desired. if you pump 100W into a device, and it “wastes” all that power, you have successfully generated 100W of heat. only heat pumps can be more efficient.
The Chalk Talk was not invented after the IBM System/360. This entire article is clearly a joke.