isp-localhost

> ... "bunch of random hobbyists" ...

That beat Microsoft dead in the server market. In academic and scientific computing. How about the embedded market?

From my perspective the random hobbyists have Microsoft backed into a corner, with only their hold on a narrowing desktop market share remaining.

How many 0-days has Microsoft left hanging open for the better part of a decade while trying to figure out how to defeat open source software?

I think that if Microsoft focused on being the best of something they'd not have a problem right now. I think they focused on being the only of something, trying to make sure no one else could enter the market. I think now they're trying to use money to make themselves an asset in that market.

Go's error type is something declared as being returned from a function, there's no try-catch with an exception being handed up a call stack. That's like saying ASM has exceptions because you can leave an error code in one of the registers.

The VM bit doesn't make sense to me at all. By that logic any language which implements a GC or has a native support for threads constitutes a VM?

There's no difference between a runtime and a VM? As an embedded developer I would argue that there's quite a difference between the two.

edit: Clarification on error type being "always" returned from a function.

I hear these sorts of arguments often, as someone who likes both Go and C I do have some responses: I would hardly call exceptions in C++ a "feature" but more of a "liability." Enumerated types (probably referring to sum types here) have trade offs that are not necessarily clear from simply reading the code. Generics often lead to code which is (IMO) difficult to follow, debug, and reason about. The point about assembly is jest? Or dishonest? I would argue that C, C++, Go, Haskell, etc etc are "simpler" than assembly, if they weren't we probably would be writing assembly, and I suppose following that logic maybe we'd be hand constructing opcodes with a two key keyboard.