BatmanAoD

Hopefully you only chmod'd your own systems. Early in my career, I worked on a project wherein we gave a contracting company root access to a computer they could use to test the software they were writing for us. One morning, they sent us a message saying they couldn't log in. We looked at the computer and discovered it wouldn't boot. Turned out someone on the remote team had chmod 777'd the entire filesystem. Of course we locked down their access after that.

Yeah, I commented elsewhere on the misinformation regarding emacs in the article.

Sure. But the author cites that as a disadvantage of emacs and links to an article about the person who invented ctrl-c and ctrl-v for copy and paste.

The author also makes some incorrect or misleading claims, specifically about emacs. I acknowledge there's a high bar for entry there and don't personally like emacs, but it's not modal, and it does have the ability to display images and markdown previews.

I know several world class programmers, and interestingly, the commonality among them is that they all seem to use Vim as their code editor. Many people I know who think of themselves as world class programmers use Emacs.

What a burn!

Wow, that was not at all clear. I was shocked that 50% of respondants identify as LGBTQ; 7% is a much less surprising figure.

How is that easier? It doesn't look like it provides a list of which modules have a __name__ == "__main__" block.

...yeah, that's really unfortunate. Part of why I said "in principle".

Minor point of clarification: it can't have runtime reflection, but in principle it could have compile time reflection.

Yeah, Boats' point there is definitely about semantic correctness rather than performance. Goroutines do indeed have good performance.

Ah. No, keep reading:

In a less than optimal world, you might decide to do something less inspired. You might take that break from the C runtime and then just implement threads again, with basically the same semantics, except that they are scheduled in userspace. Your users would be required to implement concurrency in terms of threads, locks and channels, just like they had always been in the past. You might also decide your language should have other classic features like null pointers, default constructors, data races and GOTO, for reasons known only to you. Maybe you would also drag your feet for years on adding generics, despite frequent user requests. You might go do that, in a less than optimal world.

(Emphasis on "go" is in the original.)

It doesn't mention him by name, but he's the "language designer of some renown" alluded to here:

If you were a language designer of some renown, you might convince a large and wealthy technology company to fund your work on a new language which isn’t so beholden to C runtime...