4 ms·
Okay, but we're talking about an application, a piece of software who's primary intention is to run for a short period of time, parse a text file and transform
by jpitz 6y ago
Okay, but we're talking about an application, a piece of software who's primary intention is to run for a short period of time, parse a text file and transform it. It will be ran many many many times a day by developers whose time is expensive. Language servers are a very new concept in terms of being part of the day-to-day tool chains for most developers. Trading garbage collection for compile time was absolutely a winning strategy for compiler writers. It made them money.
- viraptor 6y ago"We made dodgy choices to be competitive" is a valid explanation. They don't start being dodgy when new use cases come around and technical debt bites you in the butt. I see not freeing as a clever bug/workaround with nice positive side effects. Not as a clever solution.
- pjmlp 6y agoLanguage servers go back all the way to Xerox PARC workstations and Lisp machines. C++ had its very first language servers via Lucid's Energize C++ and Visual Age for C++ v4. Here is the 1993 video and related paper from Lucid. https://www.youtube.com/watch?v=pQQTScuApWk https://www.youtube.com/watch?v=pQQTScuApWk http://www.dreamsongs.com/Cadillac.html http://www.dreamsongs.com/Cadillac.html And some information regarding VA, unfortunately most is missing from online world. https://www.ecomstation.it/pido2/home/esterni/vac40os2.pdf https://www.ecomstation.it/pido2/home/esterni/vac40os2.pdf (codestore) http://www.edm2.com/index.php/VisualAge_C%2B%2B_4.0_Review http://www.edm2.com/index.php/VisualAge_C%2B%2B_4.0_Review It is also why Delphi, VB and C++ Builder were already such a pleasure to use versus the Makefile and vi world of UNIX.