Leaderboard

I'm porting to various environments, depending on the need of the application. I am almost finished with a port of a Mac application to Swift (using Xcode). Granted this was more of a rewrite but since our customer requires 64 bit support (so they can deploy to the Mac App Store) and refuses to pay us without 64 bit support so I had no choice. Since from a customers perspective the application is exactly the same I cannot charge for porting, especially since I was the one that convinced the customer to go with Delphi when we started this project two years ago.... I feel like an idiot for having defended Emba/Delphi and now I am paying the price... Other tools (mainly data analysis) I've ported to Python. This was also more of a rewrite and required a completely different mindset. My reservations "Python is just a script language" and "not type safe?" turned out to be completely unfounded; Properly written ("Pythonic") code is beautiful! Third party (open source) availability is simply amazing (micro-service architecture using ZeroMQ). I did briefly consider Lazarus but decided against it. I could not afford to take any risks (swift on Mac OS is basically a given w.r.t. support) and Python runs anywhere. Stubbornly staying with object pascal also "felt" wrong; if the tool/language I trusted and relied upon for 20 years betrayed me I might as well take a deep dive and go in a completely different direction. As a side-note: having seen what modern IDE's can do (Xcode/PyCharm) and what a joy they are to work with I highly doubt Emba will be able to catch up even if they start treating their customers as customers again. I'm not ruling out ever taking a subscription again but it is going to take some really impressive releases and flawless ethical behaviour for Emba to regain my trust.

Clarity is certainly not one of his strong points.

I am using a Delphi beta under an Embarcadero NDA, so I suppose I cannot reveal what 64 bit target it is 😉

Embarcadero can't fire him; Idera purchased EMBT and he was the person Idera picked to oversee Delphi. I'm not sure this was his idea either. I heard it was Michael Swindell who came up with the Delphi Pro EULA change (as well as the bogus 3 million users figure) and he's not only still there, he's listed as "Senior Vice President of Marketing and Product Management". Let's not rule him out as a suspect.

No, you just use TDatastore.Data1 whereever you need the value stored in that field. Basically the class vars of the TDatastore class are your global variables, they are just neatly packaged and hidden in the class.

Yes, but nontheless I like the idea of a self-service portal. Given that this will really allow me to use my perpetual licenses without any further troubles. (I am clearly not intending to re-install twice per day but about every 12-20 months I clear my VMs to have a fresh system.)

I stumbled upon AES problems a month ago (using a two decades old code which worked ok) when it suddenly appeared that SizeOf(LongWord)=8 on Linux. I solved my problem by explicitly replacing LongWord -> UInt32, PLongWord -> PUInt32, array -> packed array and probably AnsiString -> RawByteString and something like this (I don't have the code at hand). At least these changes in the code helped to produce equal results in both Win32 and Linux64 versions. I do not know the internals of the Eidos implementation but probably the required changes are also minimal.

It also doesn't address the fact that Embarcadero service reps are simply outright refusing to do the bumps for those who aren't on current subscription. His "clarification" doesn't address what Embarcadero is actually doing. I'm starting to suspect that this is going to be like the resolution of the Delphi Pro EULA incident, where Embarcadero tried to convince everyone that they never actually made any change. In this case, his clarification is actually a policy reversal and now he's going to tell sales to stop refusing to do the bumps. Then we'll all be told it was never the policy and we just misunderstood. It'll be just like this:

History will show that not firing him was the worst move by EMBT after this total betrayal of loyal customers..

Atanas just posted an update on his blog post. Policy Update: We still receive occasional comments on this and want to make sure we are clear on our Policy. Registration limits were introduced a long time ago with very valid use cases, but many of these are now outdated. We still do them, just now they get approved by Account Management (Sales/Renewals) vs. Support. Further, we have done several auto-bumps for everyone that should limit these issues altogether (and will do more as needed). As communicated, over the summer, we will work on a more automated way to increase registration limits through the self-service portal. It looks like there was an issue with the auto bump. I can manually process your registration bump if you private message me on here or email me: firstname dot lastname at embarcadero.com