2 ms·
That's not really the argument that I'm making. I am a deployment engineer. Deployment is actually really easy. I'd argue that it's not far off from FTPing y
by busterarm 6y ago
That's not really the argument that I'm making.
I am a deployment engineer.
Deployment is actually really easy.
I'd argue that it's not far off from FTPing your code changes over in terms of difficulty.
No, my argument is that more engineers today do not know how computers work. I'd even argue that many engineers would find FTPing over code changes to be too difficult (or they'd screw it up). My argument is that homebrew makes some amount of contribution (not 100% the reason for) engineers remaining ignorant about computers.
- mercer 6y agoDo you know how to directly 'talk' to the CPU or GPU? Do you build everything from source? Are you comfortable writing assembly? Have you recently soldered shit or built a PC from scratch?
- busterarm 6y agoYes, when it makes sense to, yes and yes. I'd be happy to work with people who know system calls & exit codes though. And basic network protocols. And how to read an RFC.
- vetinari 6y agoWhile I sympathize, I think that train left long time ago. I had that aha moment, when during early 2000s I found myself explaining to C++ developer what linker is and what exactly it does. Until then, it was just the thing that VC++ did as the last step after clicking the Build menu item. It certainly didn't improve since then.
- gurkendoktor 6y agoHomebrew was the first package manager where I actually looked under the covers because everything was pretty easy to follow. I regularly use 'brew edit <formula>' just to see how something is built. I don't see how brew obscures the internals of my computer at all.