oneoverten

Yes. This is true for JS too, object-wrapping parameters just to make them named will add runtime overhead.

Variable names is just documentation. Having types that can assert some condition on the underlying value is not even comparable to "having a named return variable". (just document? just name variables?) You don't care about what the name of the returned value is, you care about what *it is*.

Just figma apparently, it's disclosed in the FAQ.

Those animations wont "peg" any relevant CPU, and they clearly had a purpose that was not about wasting cycles or battery.

What does this solve? Genuine question. You still have to manage connectivity, and synchronization. Also not so sure that stream reading will necessarily be quantized chunks of your updates sent from the server.

That seems very unlikely, why would you think that will be a requirement?

So.. For which company? The sentence "there are scam profiles all around the IT world" would not be on any real company of scale guidelines, and no company would put that much liability in one "slide" even if they had them.

Thank you for expanding on it!

Pretty fun, but how can you tell the content you link to is from "real people"?

How is the feed ordered, I saw a pretty wide timerange?

Is it supposed to be used as a search engine, feed, or more like "stumble!"?

Congrats, but why not just share code as usual, like via libs and so on?

Yes, many companies will cap out on the advancement ladder so that at that point there's no requirement to advance further formally. Any company doing up or out indefinitely will obviously just drop valuable resources. You can still advance in pay etc.

If you respond like that to a basic question you don't work at Tesla, and you are acting out for no reason.

Yes indeed, I think you are completely right on that

Thanks, I hope so, best of luck!