(no title)
cianuro_ | 1 year ago
With the setup you described I just felt I had to write more, even if it was in the same language.
cianuro_ | 1 year ago
With the setup you described I just felt I had to write more, even if it was in the same language.
hn_throwaway_99|1 year ago
More importantly, though, you seem to be commenting from the perspective of an individual developer. The biggest productivity gains I've seen is that it makes it much easier for people on different areas of the team to understand and fix/modify parts of the code that they're least familiar. E.g. if I'm a developer that spends 99% of my time on the front end, but then I need some extra field that's not being returned by the backend, instead of having to do a full context switch, get an environment up and building that I may not have compiled in a long time, get my brain "switched over" to a different language, or worse, file a ticket and wait for the backend team to fix it, it's much easier if I can just go in quickly and add the field I need.
I've seen this in spades on small/medium teams - it really "lowers the barrier to entry" for people being able to submit PRs in parts of the codebase that is not their primary day-to-day work.
re-thc|1 year ago
This assumes that just because it's the "same language" it's all the same.
It's especially true in Javascript land where the React setup is vastly different than the Node backend framework setup.
You get bundler differences, ESM/CJS, different versions of Node (or even Bun / Deno), linters or things like decorators, etc... You can be doing "functions" with React and then head to classes and modules with NestJs all of a sudden.
It pretends to be much easier. I've seen lots of real world assume-there's-a-shortcut method that just makes it worse.
mplewis|1 year ago