A work from home full time and don’t want to go back to the office, but the periodic need for unscheduled ad-hoc communication is absolutely the most exhausting part of it.
134 karma · joined May 25, 2023
A work from home full time and don’t want to go back to the office, but the periodic need for unscheduled ad-hoc communication is absolutely the most exhausting part of it.
That said, having dabled in rust there’s a temptation to name breaking changes to improve ergonomics because the type system is so expressive. I almost wonder if this is an argument for simpler type systems to reduce churn.
I don’t care if things look native, however I am actively repulsed by modern web design trends.
Some of the “compliance managers as a service” push you in this direction as well.
So, one of the big problems with chevron deference is that when the laws says XYZ to be determined by agency ABC and agency ABC determines Q, but an election happens, the president gets up and makes a big populist speech, issues an executive order and now agency ABC determines R instead. This is a problem because under chevron + APA, the agency determination of both Q and R which may be contradictory both have the force of law and the courts were bound to simply defer to the interpretation.
You have agency making rules which have the force of law but the "law" is changing without the authorizing statute having changed and the courts' hands were tied by chevron. This is especially problematic when the rulemaking has associated criminal penalties.
Now, just because chevron deference no longer exists doesn't mean that agencies cannot make rules, but it does mean that if an agency makes a wild swing in rulemaking without a change in the underlying statute then its much easier to challenge that action. Ultimately, we want these things in the hands of the representative branch of the legislature anyway. One can dream anyway...
If I’m in psql I can tab complete columns in the where clause but not in the select because I haven’t actually given any information about what I’m selecting from yet.
They already know what region an account is in. If they just said “Ok, EU account, turn on the flags” that would be less engineering effort. Even if they increased verification of things like where you actually are relative your account at signup. But this is them engineering this solution to make sure the secret sauce doesn’t leak out of the EU. Everyone knows it’s malicious because it’s easy to intuitively grasp that they’ve gone through all this extra effort to make absolutely sure everyone outside of the EU has a worse experience no matter what
The US government is unlikely to carpet bomb its own territory even after hypothetically sliding into tyranny because it would presumably want territory to rule afterwards. What is left is intense urban fighting which we’ve seen in Iraq or wilderness fighting in poor terrain like Afghanistan. It doesn’t end quickly so the cost is a deterrent.
Although it is periodically useful to be able to copy a binary to some random Linux server and know it will work.
While the multi-tenant with zero shared ui elements is a monstrosity, I think they do a really good job at discoverability. One of the things application level menus aren’t great at is connecting what element must be focused to take the action. In something like word, it’s all a document so most things are applicable most of the time, but that breaks down in chat like slack where there is a notion of chats, files, links, users, etc and the localized contextual controls while not always great aren’t terrible either.
Consider Files.createFile. It throws if the target already exists. That method has no way of knowing what the recovery is, however, the caller might.
It could be that the caller wants to explode, but maybe its part of some kind of singleton launch where the recovery is to pass some piece of data off to whoever created the file originally.
Maybe this is a bad example since there’s not much interesting in the return of Files. But it’s exceptional in that it’s an abort rather than a success.
That said, checked exceptions are still trash because they don’t work across thread boundaries or with futures. ExecutionException is the catch all baked into the design because they needed something. The idea could have been good though because naming error handling visible is useful. Java just has the misfortune of designing early before the kinks had been worked out and now we get nice stuff like Rust has.
I’m curious how successful they will be.