87 karma · joined December 27, 2014
Even if you do understand - isn't the "via" specifically designed to reduce trust? "Hey, head's up, this message actually came in through this third-party"
When a critical piece of infrastructure fails under massive load I'm not sure it it'll help much when you politely tell your engineers they fucked up for not anticipating it.
You learn lessons. Both Slack and AWS seem to have learnt lessons here.
If I understand correctly they didn't initially hit a TGW quota, it just didn't scale up fast enough.
Personally I just find it extremely uncomfortable, and I just can't be productive that way. Plus you have to wonder what the long term effects are, it doesn't seem very ergonomic.
It's a good way to prevent people from snooping on your messages. Why do you think it's a bad idea?
WSL2 is faster and works better in almost every way. As a developer I absolutely love it and it has changed my workflow completely.
I haven't run into any limitations that kept me from doing what I wanted to do with it, and some minor adjustments like using wsl2host helps bridge any gaps.
What did we sacrifice along the way? Well, apparently we can't change our Windows network config or see Windows processes through Linux tools that weren't designed for it anyway.
And we want that sort of thing because, it's, uhh, "cool"? Those priorities don't make sense to me, but maybe I don't fully understand what people want to do with it.
But I don't think "Premature optimization" is synonymous with "performance". Optimizing or perfecting every detail of a feature that might still go through significant changes over time seems risky and wasteful.
Remember: ABP = Shit. AB = Good.