Yes, you should write unit tests to cover this in interpreted languages with weak or no types, but this depends on the developer a) doing it, and b) not missing any cases - PRs/code reviews are not a catch-all. Especially in the case of factoring common logic out or some other form of refactoring, a strongly typed language is my best friend.
Ask HN: When has switching the language/framework made an important difference?
51–60 of 152 posts
Re: Ask HN: When has switching the language/framework made an important difference?
#52A few years ago, I rewrote an `R` script into Fortran, for better than order-of-magnitude speed increase. The script optimized the placement of samplers in a building, in order to maximize the probability of detecting airborne pollutants, or to minimize the expected time required to detect. The rewrite cut the runtime down from 2-3 days to sub-hour. Some of the speedup was intrinsic to the interpreted/compiled divide…
Re: Ask HN: When has switching the language/framework made an important difference?
#53A few years ago, I rewrote an `R` script into Fortran, for better than order-of-magnitude speed increase. The script optimized the placement of samplers in a building, in order to maximize the probability of detecting airborne pollutants, or to minimize the expected time required to detect. The rewrite cut the runtime down from 2-3 days to sub-hour. Some of the speedup was intrinsic to the interpreted/compiled divide…
This is the first time that I have ever encountered someone who used Fortran for something other than earth sciences related modeling. Thank you, now I have a second example the nest time someone claims "nobody used fortran anymore".
Most of this and related applications engage in data shuffling rather than number crunching, but FORTRAN used to be one way of creating code that ran at nearly assembly language speed and size in (historically) memory constrained environments.
That said, the application (and I) are nearing retirement.
Re: Ask HN: When has switching the language/framework made an important difference?
#54Re: Ask HN: When has switching the language/framework made an important difference?
#55We're starting to develop greenfield APIs in Scala (with Play) rather than PHP (with Laravel) and we've noticed new developers without experience in either language have a surprisingly similar time-to-productivity. Here are some major factors: PHP's dynamic typing combined with Laravel's magical approach makes discoverability hard. A developer can't trace through a request by starting from a controller method and nav…
Re: Ask HN: When has switching the language/framework made an important difference?
#56Developer ergonomics is underrated. Having an easy to understand system that has no magic, and in 90% of the work has no dependency chains that you have to hold in your head can really help people avoid bugs by being able to focus on the intent and execution rather than the framework quirks.
Re: Ask HN: When has switching the language/framework made an important difference?
#57Re: Ask HN: When has switching the language/framework made an important difference?
#58Re: Ask HN: When has switching the language/framework made an important difference?
#59Re: Ask HN: When has switching the language/framework made an important difference?
#60This until I discovered Vue.js which changed my life. This and lodash made me actually like JS and front-end programming.
So this is an example what a framework did not help to improve code but actually made me choose in something else than the language I was using so far (coming from a background in C, then Perl)