HN user

0dmethz

87 karma
Posts0
Comments17
View on HN
No posts found.

As a typical end user you probably won't understand what that "via" means. All you see is that your e-mail was sent "via" some unknown thing you don't recognize.

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"

Unless I'm misunderstanding something the system did not perform as documented. It should have scaled, it didn't.

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.

I mean, when the hammer manufacturer sells managed, auto scaling thumb-avoiding services you might rely on that.

If I understand correctly they didn't initially hit a TGW quota, it just didn't scale up fast enough.

Working from Bed 6 years ago

This article kind of feels like people are working really hard to rationalize working from bed?

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.

1. You can create throwaway PGP keys, it's not like they can definitively identify you 2. You can encrypt messages for target PGP public key(s) without actually signing them

It's a good way to prevent people from snooping on your messages. Why do you think it's a bad idea?

I don't really understand this point of view.

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.

No Free Features 6 years ago

100% agree. "Sorry, but I don't work for free, consider sponsoring the project" should be a perfectly legitimate reason to reject a request on an open source project.

Performance First 6 years ago

Of course you should consider performance when you start a project - if your language, framework or core design is slow it seems unlikely you'll be able to do much to improve it later. You need to at least think about 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.