Earlier quoted context omitted.
No it isn't. The Romans were every bit as smart as we are today. The biggest difference between us and them is our tools. Similarly, compare the computers of the 60's (or even the 80's) to the computers of today. The difference in outcomes reflects the difference in capabilities.
The Romans were not as smart as us because they did not have the tools to understand the neurological effect of lead poisoning.
When did our tools become our religion?
31–40 of 70 posts
Re: When did our tools become our religion?
#32FTA: > Otherwise, the only thing that matters is that the tool works. Every tool comes with its own upsides and downsides, but most of them are increasingly the same. They mostly differ in workflow. But I can promise you: they all draw rectangles equally as well. If you can accomplish your work with the tool, then it serves its purpose. Eevee dismissed with that argument succinctly when they wrote in their "PHP: a fr…
I've heard it differently, but is a corollary: bad tools make it easy for bad developers to do bad things. Good tools make it easy for bad developers to do good things.
Who get to say if it's good or bad?
We need more "software things".
Users can decide what's good.
A few billion people have decided FB (done in php) is good.
Re: When did our tools become our religion?
#33Re: When did our tools become our religion?
#34FTA: > Otherwise, the only thing that matters is that the tool works. Every tool comes with its own upsides and downsides, but most of them are increasingly the same. They mostly differ in workflow. But I can promise you: they all draw rectangles equally as well. If you can accomplish your work with the tool, then it serves its purpose. Eevee dismissed with that argument succinctly when they wrote in their "PHP: a fr…
I've heard it differently, but is a corollary: bad tools make it easy for bad developers to do bad things. Good tools make it easy for bad developers to do good things.
Why do you care about bad developers? They won't do good things either way.
Re: When did our tools become our religion?
#35(Forming of a ) Religion is always a 4 step process. i) Use a Framework/Tool/Process/Guideline rules to better your life. ii) Feeling of elation/enlightenment when it provides that dopamine hit because it does provide benefits compared to before. iii) The innate human nature to share the Framework/Tool/Process/Guidelines with others (and forming an opinion of them being idiots for not seeing the obvious benefits) iv)…
Where humanity goes, evil [1] follows. [1] https://github.com/emacs-evil/evil
Editors lead to fresh code
Fresh code leads to bugs
Bugs lead to sufferingRe: When did our tools become our religion?
#36The OP is right: the interesting stuff in computing has always been what a new app/tool/library can DO, how it's being USED, but never HOW it was made.
This revelation first came home for me when the team of contractors I was on proposed to our customer that our mission for the next year should be to convert our prototype R&D air traffic control simulation from Pascal into C++. We were (stupidly) surprised when the customer declined, observing that the product's capabilities wouldn't advance at all but merely become a little more modern under the hood, where nobody but us contractors would ever look.
Re: When did our tools become our religion?
#37Re: When did our tools become our religion?
#38> It is rather simple: The tools don't matter. Its hard to read past nonsense like this.
People can - do, and always have done - work around tool deficiencies. Once you're familiar with a tool, the simple act of moving to another tool will be what slows you down, but you'll get back up to speed soon enough. The only place tool choice really matters is when you're part of a team who has to pass their work around. If you're not using the same tool - whichever tool it may be - it adds needless friction.
(stuck, w/plenty of hardware and electricity, that is)
Re: When did our tools become our religion?
#39Re: When did our tools become our religion?
#40Nobody looks at a house and asks, "What kind of hammer and nails did they use?" The OP is right: the interesting stuff in computing has always been what a new app/tool/library can DO, how it's being USED, but never HOW it was made. This revelation first came home for me when the team of contractors I was on proposed to our customer that our mission for the next year should be to convert our prototype R&D air traffic…
Some tools feel better in your hands.