Perl is the only language that looks just as incomprehensible before and after a rot13 transformation.
Python on the other hand is the only language that will cause your application to stop working because you mixed up tabs and spaces, even though it looks perfectly fine on your scr.
It is absolutely fine to mix tabs and spaces in Python, as long as you are consistent about it. It’s not recommended though, as it’s easy to mess up if you’re not paying attention. Most IDE’s will convert tabs to spaces anyway so it’s a bit of a non-issue.
…is it truly that bad? npm is the reason I don’t even install software based on node on my machines… python doesn’t seem nearly as bad by comparison? (I run it, just don’t like to write it) Maybe it’s worse than I realize
I haven’t used npm. But pip is horrible. Some times I’ve used a well-known library that only works on linux, but there is no mention of it whatsoever, and it installs without problem. The error only happens at run-time (not even when importing!) and says nothing about platform-dependency. I only learned that it was a linux-only library because I happened to try running it on a Linux machine to see if it worked.
Many times you have to set up your environment a specific way (environment variables, PATH, install dependencies outside of pip) for it to work, and there’s no mention of it anywhere. Sometimes you install the library with pip, sometimes with apt, and there is no way to know which one. And sometimes the library is both in apt and pip, but the pip one does nothing.
Furthermore, good luck importing a library. You might have installed it with “pip install my-library” but to import it you have to do “import MyAwesomeLibrary3”. And pip won’t tell you about that.
Wow that sounds like a headache, even though I’ve avoided python for other reasons that sounds like an additional reason to do so. Also the reason I avoid npm isn’t for a technical reason like you’ve outlined here. It’s because even installing npm requires me to install an entire other Linux distros worth of packages. Why do I need to install like 100+ new packages just to use a freaking package manager???
I’ve had very few issues with whitespace in my decade or so of using python, especially since git and IDEs do a lot to standardize it. I’m a Python simp, tho
You can make embarrassing mistakes in virtually any programming language that’s not too esoteric.
When I still used Python for prototyping (today, I usually use Go for that), it happened much too often that I did this:
if foo:
bar()
foobar() # syntax error
In Lisp, however, both errors are much harder to make (not even considering GNU Emacs’s superb auto-indentation - which is what most Lispers use these days, as far as I know):
(when foo) ;; <- obvious!
(bar))
(when foo
(bar)
(foobar) ;; <- still valid
(quux)) ;; <- also still valid
For all of those, Lisp is the more logical choice. Plus, whitespace as syntax is the worst possible design decision.
Ok, but what if an entire programming language is made of whitespace?
https://en.wikipedia.org/wiki/Whitespace_(programming_language)
Still easier to refactor than Python. ;-)
Relevant XKCD. Python has replaced Perl, but things have otherwise changed quite little.
Perl is the only language that looks just as incomprehensible before and after a rot13 transformation.
Python on the other hand is the only language that will cause your application to stop working because you mixed up tabs and spaces, even though it looks perfectly fine on your scr.
And lisp is hard to say if you have one.
Edit: aa -> after a
It is absolutely fine to mix tabs and spaces in Python, as long as you are consistent about it. It’s not recommended though, as it’s easy to mess up if you’re not paying attention. Most IDE’s will convert tabs to spaces anyway so it’s a bit of a non-issue.
APL would like a word, though I imagine ROT13 on APL source code might actually be horrific.
Lol. You’re not wrong.
I still write more Perl than Python these days.
I’m kinda jealous. I don’t miss maintaining production Perl code, but Perl was more fun to code in.
Feel free, it’s still out there!
That syntax decision is single handedly why I avoid python if possible
For me it’s dependency hell. Almost as bad as npm.
…is it truly that bad? npm is the reason I don’t even install software based on node on my machines… python doesn’t seem nearly as bad by comparison? (I run it, just don’t like to write it) Maybe it’s worse than I realize
I haven’t used npm. But pip is horrible. Some times I’ve used a well-known library that only works on linux, but there is no mention of it whatsoever, and it installs without problem. The error only happens at run-time (not even when importing!) and says nothing about platform-dependency. I only learned that it was a linux-only library because I happened to try running it on a Linux machine to see if it worked.
Many times you have to set up your environment a specific way (environment variables, PATH, install dependencies outside of pip) for it to work, and there’s no mention of it anywhere. Sometimes you install the library with pip, sometimes with apt, and there is no way to know which one. And sometimes the library is both in apt and pip, but the pip one does nothing.
Furthermore, good luck importing a library. You might have installed it with “pip install my-library” but to import it you have to do “import MyAwesomeLibrary3”. And pip won’t tell you about that.
Wow that sounds like a headache, even though I’ve avoided python for other reasons that sounds like an additional reason to do so. Also the reason I avoid npm isn’t for a technical reason like you’ve outlined here. It’s because even installing npm requires me to install an entire other Linux distros worth of packages. Why do I need to install like 100+ new packages just to use a freaking package manager???
Not as bad. But if a bigger tool like Paperplane doesn’t run after an update, it’s likely some changed dependency in python.
I’ve had very few issues with whitespace in my decade or so of using python, especially since git and IDEs do a lot to standardize it. I’m a Python simp, tho
You say that, then use a language that allows you to do this (it’s not lisp)
if (foo); { bar(); }You can make embarrassing mistakes in virtually any programming language that’s not too esoteric.
When I still used Python for prototyping (today, I usually use Go for that), it happened much too often that I did this:
if foo: bar() foobar() # syntax errorIn Lisp, however, both errors are much harder to make (not even considering GNU Emacs’s superb auto-indentation - which is what most Lispers use these days, as far as I know):
(when foo) ;; <- obvious! (bar))(when foo (bar) (foobar) ;; <- still valid (quux)) ;; <- also still validI mean, their goal was readability, and at least they’re trying new things.