Joseph MItzen

It all depends on the implementation. I believe JetBrains is offering their own LLM service in their IDEs now, but they've also added a completely local LLM that can perform whole-line auto completion. If hypothetically Embarcadero was offering their own LLM service, it could be turned on by default and people might not be happy about that. But I agree, as an excuse it seems a bit flimsy. I'm not sure why waiting longer would somehow lead to anything being more secure by design.

Apparently not. After just checking out their SQL Server update policies, I'm flabbergasted. This... this is not right. It's a nightmare. I remember when Oracle had a vulnerability where someone could log into a certain Oracle account without a password. I had an Internet-facing system set up at the time (fortunately not running Oracle). I checked the log the same day the Oracle vulnerability was revealed and there were at least 15 attempts to log in via that Oracle user account. THAT'S why you don't mix new features and updates. No one should have to choose between potentially introducing new bugs, vulnerabilities or incompatibilities and leaving a system vulnerable while a patch is tested. I remember a Delphi user (David Erbas-White?) running into this problem with Delphi. A new Delphi release came out that fixed a show-stopping bug he was experiencing. However, code that used to compile no longer did. Barry used to say that "If it compiles, it's valid Delphi". Marco said to David "This never should have compiled in the first place". Now David was faced with the choice of either getting his bug fixed at the price of breaking his code and requiring some redesign and rewriting, or having his current code compile but still be buggy. That's not a choice anyone should have to make. It's especially bad if the bug fixes are bundled with changes that break compatibility. As for the Windows OS, there's a reason the professional server space belongs to Linux of various flavors. Windows still hasn't figured out updating while Linux is moving to "atomic" updating for secure servers. In this setup, the file system is a read-only copy-on-write file system. This makes the system secure against malware. The update process is applied to a new file system snapshot. If it is successful, the OS is told to use the new snapshot on its next reboot (which will then be read-only as well). If for some reason this doesn't work right the system can always boot back into the previous snapshot. Security and ease of updating with minimal downtime (all the updating can be done while the system is still running). In this design the applications are installed via a container system, allowing installation without reboot, enhanced security, isolation of the application from the OS, atomic updating, etc.

That's what the word "amnesty" is supposed to mean in this instance - a waving of penalties. I'm very surprised to discover it was just another sale. They're out and out telling you something that's not so to get you to call up a sales representative. A former 20-year employee of Borland/Embarcadero's Delphi support once shared that they start having these sales whenever the sales team isn't making its target sales numbers for the quarter. It seems like that's a constant state now.

This isn't correct. Microsoft's tools division is not a loss leader (it currently supplies 23% of MS' revenue). Jetbrains doesn't charge for bug fixes and they're not Microsoft. They're also not a random assemblage of different software products glued together into one company. Embarcadero struggles to make a profit on Delphi because the user numbers are so much smaller and an accumulation of missteps that long predate their purchasing the product. Embarcadero can't attract new users so they have to find more and more ways to squeeze money from the existing ones. It's also hard to upsell to existing customers since most of its products aren't for developers. That's the honest truth no one likes to say out loud. I can't find more current numbers right now, but from 2013: "Microsoft also today announced that Visual Studio 2013 has sold over 3.7 million copies since its release less than five months ago." Prices then ranged from $1,000 to $13,000. They're obviously making a lot of money on Visual Studio! A publicly traded company doesn't choose to continue divisions that lose money (otherwise there would still be Windows phones and Zunes).

OK, first, this reminds me of an observation Jolyon Duranko-Smith once made. He observed that if anyone complained about something Embarcadero did as opposed to another major company, a defender would say it's not fair to compare them to Microsoft/whomever because those companies are much bigger. And if you counter by observing that a company like RemObjects does something that Embarcadero doesn't, the reply will be that that's because RemObjects is a much smaller company and can be more nimble. Every company ever compared to Embarcadero is always bigger or smaller; none of them are ever considered a fair comparison. 🙂 We learned during the sale to Idera that Embarcadero's bottom line is NOT based on the success of its development tools and Interbase. It paid only $30M or so for those, but was purchased by Idera for about $425 million a few years later. The bulk of Embarcadero's value is based on its database tools, not its development tools and especially not Interbase, whose market share is negligible (Enlyft estimates it at 0.13%). So Embarcadero could afford to give away Delphi... oh wait, it actually DOES give away a community version of Delphi, just as Microsoft gives away a version of Visual Studio (although MS' terms are more generous). I guess the comparison is apt after all. Finally, here's the terms from JetBrains, which only sells development tools, most of them being IDEs (but unlike Embarcadero, they've expanded to cover everything a developer could need, such as continuous integration software, bug tracking software, etc.): So Jetbrains doesn't charge you for bug fixes and IDEs are their core business. It's not normal to charge people for bug fixes. In fact, it's not normal to mix bug fixes and new features in the same update, something I argued with David Millington about in vain. Bug fixes need to be separate so they don't need extensive testing before application. This is how all major enterprise software works.

This is absolutely the case. A while back before the Idera acquisition I was using the GlassDoor website which lets people rate their employers. I decided while there to see what Embarcadero employees were saying. There was a very unhappy Delphi sales employee talking about the unrealistic target numbers and that the CEO was willing to do anything to hit target numbers because even they could lose their job if they didn't (this was when the previous owner was trying to pump up numbers so they could sell it for a profit). They said that management had told them they were setting up webinars to generate sales leads for them, but the salesperson complained that the only people who signed up for them were existing customers so they were useless for lead generation.

Just spam? You're lucky. A while back they made a big deal about giving away a 32-bit, command line-only version of their C++ compiler. I was curious what other restrictions were in place, given anyone could just download clang for free without any significant restrictions. There was no way to read the license without first installing the product, so I filled out a form to be able to download the compiler, supplying name, address, phone number, etc. A few days later I got a phone call from an unrecognized number and as I was busy I didn't answer. There was a voice mail message left - from an Embarcadero salesperson! They were trying to sell me a full C++ compiler (I don't code in C++ and don't code on Windows anymore, and already had GCC on my system anyway). They kept calling me back for about two weeks to the point I would never answer the phone if I didn't know who it was. They were emailing me, too, weird personalized messages wanting to talk to me and get to now my needs rather than forwarding me generic marketing department emails. I joked at the time I wasn't sure if they were trying to sell me something or ask me out. Finally almost three weeks in they gave up.

It's a privately held company; they don't have to answer to shareholders. By saying it didn't work out for them, that really means that most current users would be happy with having less features for a lower price, but this would not attract sufficient new users to make up the difference. So current users have to spend more than they want for things they don't use. There's a difference between a change and a bug fix. A bug means you paid for something that actually wasn't delivered as promised. In no circumstances should someone be able to deliver a product that doesn't work correctly and then offer to fix it for an additional fee.

If the only motivation was saving some money they could use an open source alternative, such as https://www.openproject.org/blog/open-source-jira-alternative/ or the brand new https://plane.so/

I would think delivering software and information to customers would be mission-critical infrastructure. Honestly, if you're in charge of a data center, redundancy and failover are basic elements of the job, like making sure a bank account isn't overdrawn is to accounting. Netflix periodically shuts down 10% of its infrastructure to be sure their system is resistant to failure! Just like the old forum used to be made of custom code held together with wire and chewing gum and managed by a volunteer employee in their spare time, it sounds like Embarcadero has one on-premises server for all the Delphi stuff with no failover, geographically-separated redundancy, etc. Given the rock-bottom price of hardware today in addition to the ready availability of cloud virtualization, there's no excuse for not having a physical or virtual standby. On top of that, server problems aren't a sudden development like your severed cable example. Drawing upon what Uwe said, it seems reasonable to conclude they just kept ignoring recurring problems or beating it with a stick until a component failed completely, at which point they ordered a replacement.

Like a lot of stuff at this company, things are probably done a certain way just because they've always been done a certain way by the same people who have worked there since the 80s or 90s.

Don't worry; I figured out where they can get a replacement server!

If they're not going to have any internal redundancy then they should just move to cloud servers.

They did, and Larry Ellison said to try turning the servers off and back on again.

Well, some of us like to feel fancy when we code!