BatmanAoD

Probably moreso for expressing the opinion so strongly without actually knowing any of the three languages.

Edit: I'm just guessing why a different comment got downvotes. Why am I getting downvotes?

Doesn't the first edition use K&R style parameter lists and other no-longer-correct syntax?

If you mean the box at the top, with "Larger Text", "Default", and "More Space", mouse-over shows a resolution spec. Is it actually just scaling "as if" the screen had the given resolution?

Even so, I can understand how a Mac user would be confused by this and expect the equivalent feature in a different OS to be called "resolution".

Based on the headline, they've probably maladapted to Mac OS, which doesn't actually have a scaling setting.

(This is somewhat baffling to me, since Apple clearly cares a lot about their display hardware and about having good screen resolution.)

You don't have to imagine it; you can browse the Linux Kernel mailing list!

That's called a mailing list

/s

I think generally C compilers prefer to keep the stack intact for debugging and such.

Okay, yeah, I was indeed reading your original reply as a criticism of one of the people involved (presumably the security researcher), rather than as a criticism of the post title. Sorry for misunderstanding.

Apparently GCC does indeed do tail-call optimization at -O2: https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html#index-foptimize-sibling-calls

But in that case, I'm not sure why the solution to the denial of service vulnerability isn't just "compile with -foptimize-sibling-calls."

...what is your point? Some software (in a language that doesn't have tail-recursion optimization) used recursion to handle user-provided input, and indeed it broke. Someone wrote to explain that that's a potential vulnerability, the author agreed, and fixed it. Who here is misunderstanding how computers implement recursion?

TypeScript is a language, and traditionally languages are considered separate from their implementations. When I first saw the headline I hoped maybe it meant a non-JS runtime for compiled TS, and I'm well aware of the difference. Yes, that would be a much larger undertaking than porting the compiler to a new language, but the headline doesn't indicate how large a project this is, and Microsoft certainly has the resources to write a new backend (even a native-code one) for the TS compiler.

I really like concave keyboards, and maybe someday I'll invest in one (I previously used a Kinesis 2 but the company kept it when I left).

But besides the brief Kinesis foray, I have used the MS Ergo Sculpt since...2014, I think. It's honestly pretty nice, especially since I don't really care about mechanical keycaps and I value portability. (The only portability downside is that I need to manually put something in the battery compartment to keep it powered off while traveling, because for some reason it has no off-switch.)

What about Julia?