4 ms·
I'm not dismissing it. Doing stuff certain way because it makes them fun for you is OK. Myself I'm not far from Drew with my dotfiles, doing everything in CLI a
by globalreset 4y ago
I'm not dismissing it. Doing stuff certain way because it makes them fun for you is OK. Myself I'm not far from Drew with my dotfiles, doing everything in CLI and being a die-hard Vimer. And I love embedded, low-powered devices too. But I'm not going to pretend there's some big practical reason to do things this way. My VSCode-using mouse-clicking friends are as productive as I am, and produce similar software.
The idea that using underpowered computer makes you write some faster or better software etc. is just silly. Especially that all the really fast and well known projects in last few years tend to come from Rust people, with their super heavy compiler that has no respect for RAM and storage usage.
It's by definition always better to have a faster box than slower one. You want to see how it works on much slower boxes? Run it with a CPU quota or in a VM. People don't do it, not because they can't, or because they have too fast computers, but because they have other priorities.
- LeFantome 4y agoI did not take his point to be that low powered hardware was superior. Rather, he states that older hardware is fine and good enough. That has been my experience as well. You state something similar above.
- globalreset 4y agoHaving no hardware at all is also fine and good enough if you make it so and are willing to go without possibilities it gives you, duh.
- A4ET8a8uTh0 4y ago<< The idea that using underpowered computer makes you write some faster or better software etc. is just silly. I will admit that I would rather someone with more experience commented on this rather than me. That said, I disagree on general principle. When you are restrained ( sometimes severely restrained ) by the environment, the net result is that you use resources a lot more efficiently. I absolutely get that we are kinda spoiled now with crazy hardware that is basically a supercomputer from not so long ago and it is hard to let that convenience and power go, but that lends to the bloated software landscape we have today that manages to overuse just about every resource available. With limited power, you are effectively forced to write better. It is not completely unlike training with weights. It is not silly. It produces real results.