Hacker News new | ask | show | jobs
by IshKebab 1307 days ago
I sort of agree wrt quoting. Most people's solution is just "well don't use spaces or dollars or whatever in your filenames!" which is obviously shit.

But on the other hand I think the ultimate blame lies with Bash for being so shitily designed that you can make basic quoting mistakes and it works most of the time. Real programming languages don't have that issue.

2 comments

Yes, the convention is shit.

Alas, the things that force it are also shit. Overall, it is an improvement.

Want real fun. touch -- --help # or similar. :)

It's not a real programming language tho
Yeah! REAL programmers program only in the REAL programming languages like ${MY_FAVORITE_LANG}. Bash? More like - Bah!.
It's not a real programming language in the same way Brainfuck isn't a real programming language, because it makes life too hard.
So does Java, yet it is still considered a real programming language...
I always have to share this video on threads like these: https://youtu.be/kdMG40wUCm4. Maybe you’ve seen it - interview with a senior Java developer in 2022.
> It has clean code and a clear architecture which makes it perfect for serious business

I love how vague and meaningless this is, yet I still feel like I've heard this sentence said unironically a hundred times.

Let me summarize. Java, the good parts:

> We don't actually use Java. We use Scala.

true, but nothing (besides how entrenched sh is) prevents replacing it with a real language. you don't need to use a posix shell in your terminal, any REPL that can launch executables will do. i used tclsh as my shell for a while, for instance.
So why do people write real production code in it?