3 ms·

It sort of makes sense. If things can still change. Have you never been at a company where the above list was: Our web apps get written in Perl (later added: w

It sort of makes sense. If things can still change. Have you never been at a company where the above list was: Our web apps get written in Perl (later added: with jQuery for FE interactivity) Our data science gets written in Oracle stored procedures Our core business logic is written in Oracle stored procedures! Fat clients are written in Smalltalk These were arguably even sort of well chosen at the time. (I won't say which company this was as that would identify me and I changed some details but this is a real life example)

HelloNurse 5y ago
In such an environment, there is usually next generation after next generation of these software types, with upgraded (or at least updated) basic technological choices. Some of these choices are recent and possibly bleeding edge, some are old and possibly only good at that time, some prove misguided immediately or in hindsight. For example I've seen: - COM and ASP.Net to Java and JSF (general web apps) - Forté 4GL (look it up, it was very interesting) to J2EE (general enterprise software) - MIDP Java to React Native, following mobile phone evolution (mobile app front ends of general enterprise software) - HTML frame messes to Java applets to JavaScript interactivity (high profile public web site) - ColdFusion, or something of the sort, to Sharepoint (another high profile public web site) - SharePoint to a BPEL workflow engine (important workflow-oriented application)
- pjmlp 5y ago
  People keep dismissing COM, unaware that all major Windows APIs since Vista are COM based, even WinRT. Not using COM for native programming on Windows is being stuck with Windows XP.
  - HelloNurse 5y ago
    In my case there were true believers using their own COM components to complicate the architecture of web apps and web services, without the slightest interest for Windows APIs beyond "we are stuck with a fun server OS".

HelloNurse 5y ago

In such an environment, there is usually next generation after next generation of these software types, with upgraded (or at least updated) basic technological choices. Some of these choices are recent and possibly bleeding edge, some are old and possibly only good at that time, some prove misguided immediately or in hindsight. For example I've seen: - COM and ASP.Net to Java and JSF (general web apps) - Forté 4GL (look it up, it was very interesting) to J2EE (general enterprise software) - MIDP Java to React Native, following mobile phone evolution (mobile app front ends of general enterprise software) - HTML frame messes to Java applets to JavaScript interactivity (high profile public web site) - ColdFusion, or something of the sort, to Sharepoint (another high profile public web site) - SharePoint to a BPEL workflow engine (important workflow-oriented application)

pjmlp 5y ago
People keep dismissing COM, unaware that all major Windows APIs since Vista are COM based, even WinRT. Not using COM for native programming on Windows is being stuck with Windows XP.
- HelloNurse 5y ago
  In my case there were true believers using their own COM components to complicate the architecture of web apps and web services, without the slightest interest for Windows APIs beyond "we are stuck with a fun server OS".