5 ms·
Our main product is in Delphi, a B2B CRUD-ish application, with a 60% market share in our niche. We're crucial to daily operations of many local branches of wel
by magicalhippo 4y ago
Our main product is in Delphi, a B2B CRUD-ish application, with a 60% market share in our niche. We're crucial to daily operations of many local branches of well-known global businesses.
These days it's obvious the years of lost momentum is taking a toll. The language hasn't evolved much and is showing its age in many areas. The IDE is far behind Visual Studio in terms of code completion and similar help. It's also been difficult hiring developers.
We've looked at moving to the web, but none of the front-end frameworks and tools we've seen so far get anywhere close to the ease of Delphi when it comes to making decent looking user interfaces with nontrivial functionality that doesn't silently break in random weird ways from one day to the next.
Also, if you want something in between a full CRM and "assembly level" database access, Delphi has some powerful libraries and components.
To give some perspective, we've got hundreds of businesses with many thousands of users, many large modules which constantly evolve, we have tons of custom integrations per customer, including custom data entry windows/screens. The largest customer has 25 integrations, 20 of them entirely custom including non-trivial new user interfaces, and got onboarded in less than a year from signing the contract. This with a team of 7 devs total and zero hired manpower. I'm not sure we could have gotten this far with such few developers with any other tool/platform.
But as I said, things are changing. So far we're moving the "backend" stuff to .Net/C#. Via RPC and message queues we can implement pieces in .Net while keeping the frontend in Delphi for now. We'll probably move the front end at some point once we find something suitable.
- s1k3s 4y agoTo download Delphi "Community Edition" I need to provide: name, email address, country, phone number and a company name. I can also use it only if I agree with their terms (understandable-ish, every license is like this). So how can anyone expect people to use it when even if you just want to try it out you have to register somewhere.
- magicalhippo 4y agoYeah that's another side, Delphi's never been good at entry-level stuff. Back in the days the only way to get a cheap copy was to be a student. Now there's the "Community Edition" but as you say, compared to other options it's pretty high-friction. This combined with the years of subpar evolution due to poor management certainly did not help Delphi.
- nurettin 4y agoCommunity edition was 32-bit, was missing design-time and had strange constraints for compiling. It is essentially and unusable, stripped down version of Delphi that you can look at, but not use.
- thewrinklyninja 4y agoCheck out FreePascal with the Lazarus IDE. It's all free and the same language essentially. https://www.lazarus-ide.org/ https://www.lazarus-ide.org/
- Aloha 4y agoYa, we're in a similar boat - lots of custom versions for customers, we're a large payer in our market too however. We ship our application as a binary with some premade Delphi form files and a tool we wrote to build DFM files for the customer specific application that limits access to the functions and objects built into the application. I'm part of the group that consumes the application as built and develops customer implementations. We're slowly transitioning from Delphi to C#, because the language is creaky, and mostly, its become impossible to hire dev's and when we do its months before they can be productive (but boy are they once they are). I think the move away from Delphi is going to hurt a bunch in the short term, but will probably get us long term benefits. For me the biggest issue I'm dealing with, is Windows is a treadmill of changes, and its hard-to-impossible to keep up with it.
- cxr 4y agoThese stories about not being able to hire developers sound like the software industry's version of "No one wants to work [here] anymore." I have real difficulty believing that these positions are as hard to fill they are made to sound. Comments about how it takes "months before [new hires] can be productive" certainly don't help in that regard.
- Renaud 4y agoHow many people do you know who are fluent in Delphi? Would they relocate to fill a job in a small company that mostly use Delphi? We're talking about a programming language mostly targetting software for small businesses. A language that has basically no future. Nothing's impossible, but I'm ready to believe that finding people for these types of job is probably not easy. Not impossible, just not as easy as finding a Python developer.
- Aloha 4y agoI think there are lots of laudable things to say about Delphi, but like.. developer availability is not one of those things ;-)
- magicalhippo 4y ago> CRM ORM of course, not sure what my brain was doing at that moment.
- cynwoody 4y ago> But as I said, things are changing. So far we're moving the "backend" stuff to .Net/C#. Delphi and C# share a chief architect, Anders Hejlsberg, who left Borland for Microsoft in 1996[0]. [0]https://en.wikipedia.org/wiki/Anders_Hejlsberg https://en.wikipedia.org/wiki/Anders_Hejlsberg
- miohtama 4y agoLater he went to develop TypeScript
- EFreethought 4y agoNot a Delphi/Pascal person, but: Did you look at Lazarus and Free Pascal? Why not go with them over .NET? Since Delphi and FP are both variants of Pascal, it seems like it would be easier.
- Aloha 4y agoI commented in a parallel comment, but likely for the same reason we are - Developer pool for .NET is much larger.
- magicalhippo 4y agoThe issue isn't licensing cost, but developer productivity and being able to hire people. Like I said, we've struggled big-time to fill our open dev positions. Also, the .Net community is just that much bigger, and the tools get more attention. For example, a customer recently required us to fetch messages from Azure Service Bus to get an ID for a file in Azure Blob Storage. Sure the REST calls for the Azure API's could have been written fairly easily, but they used that pre-shared key authorization scheme which required signing certain HTTP headers[1]. None of our libraries easily supported integrating that, as they all generated those headers on the fly while making the HTTP call. In .Net there was already official libraries for this and it took me a couple of hours to write the integration, including testing. Even without the authorization blocker, it'd taken way more time than that to implement the necessary REST calls and properly test them in either Delphi or Free Pascal. In another example, we've adding JSON support for our "public" API, in addition to our XML. We're quite used to customers feeding us with crap data, so validating against schema on the way in is a must to keep support requests down. In .Net there was already a nice JSON Schema library waiting for us[2], so only took me a couple of minutes to integrate that. The only Delphi/FPC library I could find was years old and didn't support the JSON Schema version we required. [1]: https://learn.microsoft.com/en-us/rest/api/storageservices/authorize-with-shared-key https://learn.microsoft.com/en-us/rest/api/storageservices/a... [2]: https://www.newtonsoft.com/jsonschema https://www.newtonsoft.com/jsonschema
- vfclists 4y agoHave you evaluated RemObjects Oxygene? The blurb says it integrates with .NET well.
- RcouF1uZ4gsC 4y ago> We've looked at moving to the web, but none of the front-end frameworks and tools we've seen so far get anywhere close to the ease of Delphi when it comes to making decent looking user interfaces with nontrivial functionality that doesn't silently break in random weird ways from one day to the next. That has been my experience as well. For stamping out these CRUD apps with custom forms, nothing I have come across has been able to match the productivity and simplicity of Delphi and Visual Basic from the mid 1990's.
- abraxas 4y agoSame here. Younger developers often don't realize how unproductive they are with their JS based frameworks. The one thing that I found that makes knocking out a simple web app fast is Streamlit in the Python ecosystem. Setting up Python is a bit of a nightmare but once out of the way, using Stramlit is quite nice. Although no visual designer is a bit of a let down.
- shrubble 4y agoDo you feel that the strict type-checking that Delphi/Pascal do, has helped you in any way? I have done some stuff in TypeScript but what happens in our group is that they just use ":any" which defeats the checks, if they can't get it working right away (stack is Java on one side, Angular on the JS side). Wondering if the strictness has helped you avoid errors or not.
- magicalhippo 4y agoOh absolutely. While I every now and then feel a bit restricted by it, overall it's just such a mental relief not to have to think about those things because the compiler will catch me if I mess up. For example, when we upgrade a dependency and suddenly we get 30 compiler errors because the signature of a call-back function in the new version of the dependency differs. Without strong typing and strict checking that could be 30 support cases (or more) as we don't have full integration test suites for all the various customer integrations for various reasons. Strong typing helps a lot with readability, as it can make the code a lot more self-documenting. Very often I don't need any separate documentation. Just by looking at a function signature I can see what types it expect, I can thus find code for those types to see what they look like and that way gain a good understanding of what I need to do to call that function and, just as importantly, what I get back. Strict checking means I don't have to worry about silly bugs all over. Want to assign a string to an integer variable? Well then you better say so. In fact the areas that annoy me the most is those where the strict checking fails. For example the TDateTime type, which holds a time and a date unsurprisingly, is defined as a type alias for a double-precision float. Thus "myDateTime := Pi;" compiles just fine. This is mainly for historical reasons, as records (structs) were more limited and clunky back in the days, however the type is so ingrained in library code all over it's hard to avoid.
- presentation 4y agoSounds like an organizational problem, if people are passing code reviews with any littered all over the place then your engineering culture is flawed. At least at my company, you need to have a discussion explaining why any use of the any type is justified or else it will be by default rejected.
- tlear 4y agoIsn't it incredible that now in 2023 web is still this bad? One of the biggest online outdoor retailer websites breaks catastrophically in fully updated Safari on Mac.. been going on for month. By catastrophically I mean you get a blank white screen with ui flashing in out. And this is normal, I find something like that regularly, stopped bothering sending bug reports years ago. It blows my mind.. really it does, how did we not fix this shitshow? We have automated test on top of automated test on top of automated tests but web is so messed up we still can't have shit working reliably.
- emodendroket 4y agoI mean it can. Some Web sites are done well, some aren't. What else is new? People wrote terrible desktop applications too.
- magicalhippo 4y agoClearly there are some good applications running on the web out there. How many are a) highly nontrivial with hundreds of windows/screens, many with with multiple searchable grids, custom lookups, per-screen user-definable tab-stop order etc etc b) reliable enough that the users can enter all the data they need without looking at the application (ie no missed keypresses or focus changes etc) c) being developed, maintained and operated by a team of <10 devs? Honest question, if you know then do tell! I'd love to hear how they're doing it. Like, this year changes to gov't systems means we'll have to implement about a dozen new complex windows/screens, along with all the backend logic. We get the specs about 6-9 months before go-live, so it's not like we have a full year either.
- emodendroket 4y agoI think where people get into trouble is trying to get too custom. It's been quite a while since I did any frontend stuff, but I was able to do work I was very proud of just sticking to default Angular 1 and Bootstrap and it worked great with a team fluctuating between 1-3 people. I was even able to write some code that could use reflection to generate forms based on the view models used by REST controllers in .NET, which was neat. But overall I'd rather work with Web tools than most desktop options out there. Clearly a lot of others feel the same or stuff like Electron wouldn't exist.
- kylecordes 4y agoWhile I moved away from Delphi over a decade ago, it is still reasonably popular in niche vertical market software and internal systems. It is probably still a practical choice for both of those. Certainly I've seen sprawling internal systems developed with web technology at a multiple of what it would cost to deliver the functionality with Delphi. Recruiting top talent will be tough though - those with the most choice often (rationally) choose to work on growing-adoption technologies.
- tiffanyh 4y ago> B2B CRUD-ish application, with a 60% market share > we've got hundreds of [customers] Lesson for anyone wanting to start their own business, go after small niches like this company where the entire customer base is < 1,000. There’s lots of money to be made in these pockets. Then expand into adjacent segments.
- nurettin 4y agoI went from a pure Delphi shop to a web/python/c++ shop and felt the same frustration with frontend development. DevExtreme (DevExpress for web) comes very close to the frontend development experience of Delphi, because it was created by the shop which created the best Delphi component suite. Currently, we are using DevExtreme with React. All of the components are tied to DataSource which you can map your insert, update, delete calls in order to cause the updates to be rendered, just like it did in Delphi with Data Modules and Data Sources. Of course you don't get the benefit of data sources working at design-time while working on the web. Delphi was and still is a few decades ahead of whatever we have on the web.
- magicalhippo 4y agoThanks for the feedback. Yeah we're already using DevExpress for Delphi, so obviously their web solutions are looking very tempting. Do you do the form layouts by hand then, or are there other tools to assist with that which work well?
- nurettin 4y agoWe use bootstrap for layouts. I think you're going to need to write some special tooling if you want to migrate hundreds of forms to the web. Maybe load a form, generate a component tree, dump to json and then try to generate devextreme forms with that information?
- magicalhippo 4y agoThat's indeed an interesting idea, will have to do some serious investigation to see if that is possible. If nothing else, it might give us a GUI editor to drive the new forms.
- ssdspoimdsjvv 4y agoThis reads like a perfect description of the place I work - only difference is that we're using Smalltalk instead of Delphi. We are gradually trying to move to the web, but the reality is that the complexity of the web makes it a lot harder and slower to develop useful applications. I am not sure if this added complexity is inherent to the web, or if we just decided it should be that way.
- Gemlotodk 4y agoYour company sounds like a company who just connects companies with code which does exactly what the company needs. No product, no product strategy just pure company integration. I bet the train is gone for years already. And instead of creating a real product and forcing companies in a clean workflow and driving it you are being driven. The message queue thing you mentione sounds exactly like other companies I have seen with the exact same issue were suddenly some random tech is used to add things to that pile 'easier' just digging the grave deeper. But I can be wrong.
- magicalhippo 4y ago> No product, no product strategy just pure company integration. Oh we definitely have a product. Almost none of our customers have all the data they need in the other systems, but they almost always have much of it. They're just lacking the domain specific stuff, unsurprisingly. So our product has a lot of domain-specific logic that greatly assists customers in enriching the data as required by law, before submitting it. However part of what got us to dominate the niche is that we were willing to be driven, as you say, or solve our customers problems as we see it, when it comes to integrating with those other systems. Now that we've grown we're trying to be more strict. Custom screen/windows is not something we do readily anymore for example. However, oh so many new customers ask for our standard XSDs etc, and once we hand them our XSDs they turn around and go "hmmkay, but how about you just use the files we already got?" and hand us some other XML, CVS or whatever.