3 ms·

> you have to deep-dive into different frameworks, different tools that all do the same thing in the end you aren't forced to use these frameworks and tools. Y

by chii 3y ago

> you have to deep-dive into different frameworks, different tools that all do the same thing in the end you aren't forced to use these frameworks and tools. You can chuck a NIH syndrome, and just write everything from scratch. The only reason you wouldn't is because you aren't interested in programming as a craft in itself, but is only interested in the output and productivity.

kragen 3y ago
maybe what you need to practice is figuring out how to locate, evaluate, and use new libraries and tools? if not, then that means those libraries and tools save you less time than it would appear, and you might as well write your own code
karmakaze 3y ago
It also depends on the language and ecosystem. I've found that with Go or F#, they typically use smaller task oriented libraries, the largest of which might be an http router, client, config reader, and db driver. There may also be larger more framework style libraries but tend to be less often used.
- klabb3 3y ago
  Yes. When people ask why I prefer Go over Rust (as a solo dev in web-adjacent space) it’s mainly two things: - std lib that does some really heavy lifting. (Dep tree is maybe 10 libs total, 2-3 layers deep for mid-sized projects). - concurrency is simpler and less boilerplate. Data races is a non-issue with good hygiene + race detector I would normally throw in the Go toolchain as a plus but I think Rusts tooling is very good as well, in some cases maybe even better. It’s much more of a problem with other languages.
jodrellblank 3y ago
> "The only reason you wouldn't is because you aren't interested in programming" Niklaus Wirth said writing an RDBMS was too hard for him.[1] Where does that fit into your "only" reason? [1] in the Questions/Answers section at the end of this presentation https://www.youtube.com/watch?v=EXY78gPMvl0 https://www.youtube.com/watch?v=EXY78gPMvl0

by chii 3y ago

kragen 3y ago

maybe what you need to practice is figuring out how to locate, evaluate, and use new libraries and tools? if not, then that means those libraries and tools save you less time than it would appear, and you might as well write your own code

karmakaze 3y ago

It also depends on the language and ecosystem. I've found that with Go or F#, they typically use smaller task oriented libraries, the largest of which might be an http router, client, config reader, and db driver. There may also be larger more framework style libraries but tend to be less often used.

klabb3 3y ago
Yes. When people ask why I prefer Go over Rust (as a solo dev in web-adjacent space) it’s mainly two things: - std lib that does some really heavy lifting. (Dep tree is maybe 10 libs total, 2-3 layers deep for mid-sized projects). - concurrency is simpler and less boilerplate. Data races is a non-issue with good hygiene + race detector I would normally throw in the Go toolchain as a plus but I think Rusts tooling is very good as well, in some cases maybe even better. It’s much more of a problem with other languages.

jodrellblank 3y ago

> "The only reason you wouldn't is because you aren't interested in programming" Niklaus Wirth said writing an RDBMS was too hard for him.[1] Where does that fit into your "only" reason? [1] in the Questions/Answers section at the end of this presentation https://www.youtube.com/watch?v=EXY78gPMvl0 https://www.youtube.com/watch?v=EXY78gPMvl0