<story><title>Delphi still exists and is actively developed</title><url>https://www.embarcadero.com/products/delphi</url></story><parent_chain><item><author>magicalhippo</author><text>We use Delphi at work. We&amp;#x27;ve gotten a lot of pressure from customers to move to the web.&lt;p&gt;However the lack of ways to design non-trivial UIs quickly does not make it seen feasible at the moment.&lt;p&gt;Then there&amp;#x27;s the fact that Win32 is like bedrock in terms of stability. We&amp;#x27;ve got forms that&amp;#x27;s been designed and coded over 15 years ago which still works just as fine as they did back then.&lt;p&gt;We&amp;#x27;ve got input-heavy UIs, the one I&amp;#x27;m working on right now is a single window with &amp;gt;150 input fields including multiple child tables up to levels 3 deep with their own grids. Getting the UI layout done and components connected to the DB will take me a day tops, it&amp;#x27;ll look great and based on history should work for the next 10+ years. The web seems like such a step back whenever I try it.</text></item></parent_chain><comment><author>shrubble</author><text>What no one in the responses is talking about ...is &lt;i&gt;speed&lt;/i&gt; of using the UI during day to day operations.&lt;p&gt;Web interfaces are extremely clunky to use when trying to do things via only-keyboard (which is the only way to have muscle-memory help you zip through forms) methods.&lt;p&gt;They are slow to update and in some cases, the Web browser&amp;#x27;s UI is fighting with you, such as offering to replace your input with the previous data you put in a form field of the same name, etc.  In certain cases the tab method of navigation between fields gets broken or something else that interrupts the person&amp;#x27;s flow happens.&lt;p&gt;Having worked in a case where the ticketing system and related interfaces were half-Web and half-Java-application-on-Windows - even the Java application was better to use via the keyboard.&lt;p&gt;If you are paying people on a regular basis, whether hourly or per-shift, and the UI slows people down by 5% , what is the cost over the (perhaps) 3 years of that application&amp;#x27;s life?&lt;p&gt;Even 4 users at $50k&amp;#x2F;year each in the USA (with healthcare and other business expenses etc. that means a $20&amp;#x2F;hour full time job) means $10K&amp;#x2F;year (5% * 200K salaries) in extra expense.</text></comment>
<story><title>Delphi still exists and is actively developed</title><url>https://www.embarcadero.com/products/delphi</url></story><parent_chain><item><author>magicalhippo</author><text>We use Delphi at work. We&amp;#x27;ve gotten a lot of pressure from customers to move to the web.&lt;p&gt;However the lack of ways to design non-trivial UIs quickly does not make it seen feasible at the moment.&lt;p&gt;Then there&amp;#x27;s the fact that Win32 is like bedrock in terms of stability. We&amp;#x27;ve got forms that&amp;#x27;s been designed and coded over 15 years ago which still works just as fine as they did back then.&lt;p&gt;We&amp;#x27;ve got input-heavy UIs, the one I&amp;#x27;m working on right now is a single window with &amp;gt;150 input fields including multiple child tables up to levels 3 deep with their own grids. Getting the UI layout done and components connected to the DB will take me a day tops, it&amp;#x27;ll look great and based on history should work for the next 10+ years. The web seems like such a step back whenever I try it.</text></item></parent_chain><comment><author>yrgulation</author><text>“ &amp;gt;150 input fields including multiple child tables up to levels 3 deep with their own grids”&lt;p&gt;Yeah i’ve built single page apps with more input fields than this and grid tables all in a single view. Are you sure this cant be easily done?&lt;p&gt;Coincidentally that was first 15 years ago with extjs, second time with react 3 years ago - the latter being a slower process but still pretty much doable.</text></comment>