I can certainly understand how Python became fairly broadly popular given its niche (hard 'ch'), but personally feels like it just introduces its own uniquely idiosyncratic syntax at the expense of runtime efficiency, and some of the narrative around it more generally as a language seems like it borders on propaganda to me. I'm sure it's useful in a lot of ways. I just don't really want to use it, if I can help it.
MrPopo wrote: ↑Tue Jul 29, 2025 11:48 am Trying to extend it to larger and larger stuff you run into problems like the lack of strong typing and the hatred you will develop for "we dislike curly braces so here you go, whitespace". It's especially bad when you refactor and cut and paste something to a different block with different scoping; with curly braces your indentation is fucked but it all compiles, whereas with Python now you've fucked the logic.
Yeah, this is the type of thing I was thinking of when referencing the whole, 'We got rid of your semicolon dependency for you, aren't you happy,' but if the interpreter still relies on whitespace, what have you really gained? A sense that it looks a little prettier in code review, I guess. Like your example, I'd kind of rather have something with truly hideous formatting that compiles.
Also, I kind of skimmed through the Linux section on boot.dev, and in some ways it was useful in just sort of explicitly outlining the building blocks of a bash script, but there's also a fair amount of time spent on stuff like, 'What is a file system?', 'What are permissions?', 'Man? Man.' So, aside from pointing out some things I wasn't really clear about, like piping, and grep, I don't really feel like I unlocked my third-eye in Linux, or anything. Still probably worth the couple hours of poking at, though. (Considering it was free to me. I would have been a little more annoyed if this was something I'd paid for.)
Git I know very little about actually using, though, so that will probably be more educational for me.
