3 ms·
The actual productivity improvements are things like * distributed version control, * open source culture and infrastructure (GitHub, GPL and Apache licenses.
by jimbokun 9y ago
The actual productivity improvements are things like
* distributed version control,
* open source culture and infrastructure (GitHub, GPL and Apache licenses...),
* dependency management and build tools (pull in many man years of effort into your project with a single declaration),
* HTTP and REST APIs (accidentally taught developers the importance of idempotency, statelessness, uniform interfaces, etc.),
* cloud infrastructure (no more need to purchase, install, configure, and secure expensive workstations before starting your project and business).
As for programming languages, there have been very few actual productivity gains since the standardization of Common Lisp.
- flavio81 9y ago>As for programming languages, there have been very few actual productivity gains since the standardization of Common Lisp. Although this is mostly true, I think you forgot to mention that the latest trend of repositories with tens of thousands of libraries are a boost in productivity as well. Even the Common Lisp world received a big boost in productivity when the Quicklisp library/system repository was created and consolidated.
- hinkley 9y ago* Decades of coherent thought on code robustness and maintainability.
- bsder 9y ago> As for programming languages, there have been very few actual productivity gains since the standardization of Common Lisp. This isn't true. Common Lisp had more than a few problems which later languages fixed: 1) Module system/encapsulation Common Lisp has a notoriously fickle and opaque system for importing other code into your space. 2) Sequences as sequences rather than linked lists terminated by null. Dealing with the fact that a list is a null-terminated linked list instead of an actual sequence/vector/tree is a big deal. Try implementing a printer for dotted pairs at some point. Talk about annoying and it costs you enormous performance. I could keep going, but there are far better qualified people to talk about the many shortcoming of Common Lisp.
- flavio81 9y ago>Dealing with the fact that a list is a null-terminated linked list instead of an actual sequence/vector/tree is a big deal. If you need a vector, just use a vector, don't use a list. Common Lisp has very flexible vectors and arrays. Lists are the way they are because they're the fundamental block for manipulating/constructing lisp code itself. >Common Lisp has a notoriously fickle and opaque system for importing other code into your space. Care to elaborate? You just load it; everything is in its own, separate namespace.