duaneb

We should really require commenting while downvoting unreplied comments. The community has gotten lazy.

I'll be the devils advocate. Why? I can understand calculus perfectly fine without understanding how people got there. In fact, I'd argue much of what you learn before call--in the order of discovery--actively hinders understanding.

If anyone has a clue why this was downvoted, please clue me in. It was on topic and indicating missing information.

Edit: I really don't care how much I get downvoted, I'm going to highlight its uselessness until someone cares to justify it.

Well, it's basically duck typed, but without type values you can assign. Doesn't surprise me much.

...yet.

Fix for some value of fix. Go's lack of generics make the data structure offerings pitiful. Just look at heap: it's worse than c.

There is a role for a language like that, but calling it fixing c++ ignores 90% of the reasons people use c++ in the first place. In fact, id say that go reminds me most of the version of c++ that operated as a preprocessor. It's almost exactly the same template implementation!

Sure. It's also why the internet is super vulnerable to 0-days.

> The actual decision needed could be done in a couple of Slack messages between two programmers

In my experience, those two programmers rarely have a good enough understanding of existing codebase and momentum to make good decisions. Without meetings, there is little way to avoid these problems.

Programmers are good at implementation, not (necessarily) decision making.

Also, meetings only make sense if everyone is focused on decision making; this is a company culture issue more than anything.

Wow, I never realized operators couldn't push fixes to their routers without permission. The internet is indeed a tragedy of the commons: trivial to ruin, but a Sisyphean task to fix.

In many jobs that's totally worth it—chances are very low a stranger will need something high priority from you, and people who work with you will know how to communicate.

Email is good for a lot of things, but not for expecting processing quickly.