Re:“No, we’re telling everyone we are using Java”
by myth2018 on Saturday March 09, 2019 @07:55PM
(#19349549)
If they faced issues in a one-week project, I ask myself what would have happened in a project big enough to speak to something
Re:“No, we’re telling everyone we are using Java”
by myth2018 on Saturday March 09, 2019 @07:52PM
(#19349535)
The link exposes some underlying reasons which I think applies to bigger projects as well. Like the lack of libraries.
Re:“No, we’re telling everyone we are using Java”
by kazinator on Saturday March 09, 2019 @09:48PM
(#19349865)
Lack of libraries applies to tiny projects, because the "activation potential" has to be small. Developers are reluctant to write 1000 lines of library wrappage for the sake of 700 LOC of payload, but they might well do it for something that can be expected to be 25 kLOC, and much more likely if they're going to have 250 kLOC riding on it before the product reaches 1.0.
Re:“No, we’re telling everyone we are using Java”
by myth2018 on Saturday March 09, 2019 @10:47PM
(#19350057)
It definitely applies to large projects as well. It's not just a matter of what developers think about writing more code. It's a bit more complicated economic decision involving how a significant amount of resources is going to be spent on writing code, testing it, whether the team is actually capable of writing the needed libraries, security risks introduced by bugs etc etc, just to begin with.
Things that can be rewritten in one weekend are trivial; they don't speak to anything.
A Lisp site that can be rewritten in Python in one weekend can be probably be rewritten in shell + awk + CGI in two weekends.