61–70 of 70 posts
IT is changing fast and a stream of fresh converts is required to implement & update new libraries and features and protocols.
Earlier quoted context omitted.
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.
In principle, if stuck on a desert island, we all could recreate our tools, right? (stuck, w/plenty of hardware and electricity, that is)
Anyways. Could we re-create our programming tools? Eventually. So long as we have a computer and a whole lot of time. Bootstrapping a programming language to create an operating system's going to be a real bear though.
Now then, making those tools efficient (namely optimizing compilers) and safe is going to take a whole lot of time and brainpower.
Yet another website where the text is 3x the size of all the rest of the text on my screen. Did everyone forget that desktop browsers exist?
This is biggest lie. Tools matter a lot.
You can do everything with just ’ed’, but you can nor argue that you wouldn’t be more productive with pretty much anything else.
Earlier quoted context omitted.
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.
Bad tools make it hard for good developers to do good things, and good tools make it easy for good developers to to good things. Why do you care about bad developers? They won't do good things either way.
Most people, in my experience, are both good and bad developers in different measures. Tools that help the bad developer therefore help all developers in those moments when we make mistakes.
> It is rather simple: The tools don't matter. This is biggest lie. Tools matter a lot. You can do everything with just ’ed’, but you can nor argue that you wouldn’t be more productive with pretty much anything else.
> If you work on your own, pick the tool that works best for you. If you work in a team, pick the tool that works best for the team.
And why shouldn’t they be - What other proof is there of our wisdom’s worth? Tools are the most of our humanity; the all of it, for what is not a tool? A shirt, a city: all not animal is the animus of tools. All we are which we are not is holy tooling; it is then the wisest worship!
They're not a religion in any sense of the word. A culture, maybe. A religion? Nay, never. OK, I'll make an exception for Emacs users. And Lisp users, them as well seeing how as both sort of fit in the same pews. Apple also has attracted a pious crowd so they also get an exception, especially given the sacrifices which its followers make, the regular pilgrimages to the Holy Store where the latest sacrament is purchas…
Forgive me father, for I have used tabs to indent my code.
Thy sin is forgiven.
Earlier quoted context omitted.
Forgive me father, for I have used tabs to indent my code.
In a Commodore 64 emulator, write a BASIC program to output 10 Hail Marys. Thy sin is forgiven.
10 FOR I = 1 TO 10
20 PRINT "Hail Mary"
30 NEXT I
Alternatively, you can also use the following single line of code to achieve the same result:
10 PRINT "Hail Mary";:FOR I = 1 TO 9:PRINT "Hail Mary";:NEXT I
I don't think this bot understands the term "Hail Mary". I told it to spit out the whole thing and it did, followed by a one-line program which could never be entered on a real C64 (hardware or emulated) given that the maximum line length in the BASIC screen editor is 255 characters. Also, what's up with that silly extra "Hail Mary" in the single-line version and why are those colons there? I'm afraid salvation is far away...