You should think of Monad as basically giving you a way to provide your own implementation of the semicolon operator so that you can dictate what it means to sequence computations of a given type.

You misspelled Haskell.

As someone who owns a System76 desktop, which I really love, I would have preferred that they spend more time on getting Pop!_OS 24.04 first, and then finish COSMIC.

When more of my day-to-day job involved reviewing long PRs, I also got grumpy over this kind of thing, so I am very sympathetic.

Thank you for the correction!

The web did not exist until the 90’s.

No you sudon’t.

WHAT HAVE I DONE!!! 😮

What is this, potential for a circle tool?

Just in time for version 3.1.4!

They are making a funny facial expression while wearing Nim on top of a tall hat.

I have found that conda proves to be

. . .

a fairly good

. . .

alternative to pip as well.

I am really looking forward to using this next year!

(Off-topic, but your username is fantastic!)

Saying that the problem of formatting goes away if you have a carefully configured IDE is an excuse, not a reason.

I work with Python on a daily basis as well and this has never been a big deal for me. So in short: speak for yourself.

A text editor that indents a block when you press “tab” is not hard to find and takes all of 30 seconds to set up.

Interesting… so in the end, if the whitespace is not telling you what the code is doing, you reformat it so that it does?

Imagine if there were languages that just let you skip that step entirely!

More like everyone whose text editor is apparently Notepad…

Lisp syntax would not even necessarily be that bad if in practice people did not lump all of the closing parentheses in a place where it is really hard to visually match them with their respective opening parentheses so that it is hard to immediately see what is going on. (I have been told that the trick is to read the whitespace instead of the parentheses, but that does not actually help because the whitespace is not significant in Lisp!)

A more fundamental difference between Rust and Python is essentially that the former is expression-based whereas the latter is statement-based, so arguably you need delimiters for code blocks in Rust because an expression can contain a block that itself has statements in it, whereas there is (sadly) no equivalent in Python. (Having said that, even if this weren’t the case, it would probably still have used curly braces for delimiters because it wants to look a bit like C++ to make it more palatable for that group, not because deep wisdom was involved.)

There are lots of things to not like about Python, but the lack of curly brackets that would just be redundant anyway is not one of them. You hardly alone in your opinion, but you are not speaking for “everyone” either.