4 ms·
I would very much love to read a prequel article that defines "bad". I define a "good" programming language and framework as having as many of the following pro
by anticristi 7y ago
I would very much love to read a prequel article that defines "bad". I define a "good" programming language and framework as having as many of the following properties:
* It can quickly solve a problem, e.g., build a webapp that uploads cat pictures.
* It is here to stay, i.e., my investment in using and learning that tool won't be subject to hyperinflation.
* It has a good enough base, i.e., I can quickly recruit someone to scale-up my problem solving.
According to my definition JS is good, or, at the very least, is good in 2019.
- johnisgood 7y agoIt really depends on the type of problem. In many cases, C was really great to use to quickly solve a problem. It is here to stay, and has a good enough base.
- anticristi 7y agoWe seem to a agree. C is also good (according to my definition) to solve problems in the area of system tooling. I tend to see programming languages as DSLs for a specific problem domain. C has become the DSL of software that lies close to the hardware, whereas JS has become the DSL of webapps.
- johnisgood 7y agoYes, I agree. I do not stick to one "ultimate" programming language. I pick one (or two!) based on the problem at hand. I once used FastCGI + C because it made more sense and was quick to implement. :D