Oh, no, I actually misunderstood cobby's complaint: the field names, yes, those still have to be unique. Which is also a bit annoying, though I've seen discussions about changing it.
That's fine, but saying this doesn't engage with the problems that have been raised at all.
It's like saying "but it's the most delicious thing I've ever eaten" in response to someone telling you a double-bacon cheeseburger with extra sauce is bad for your heart.
Interesting angle. This kind of robotic tracking has also helped me with personal aspirations (exercise a key one). I suppose it is all in how you use it. In fact, I even stopped using it at one point for another activity because it was making it feel like a chore. For that one it is more satisfying to allow myself to skip it.
"then use a loud angle grinder in a very enclosed space" They don't need to cut the lockbar:
> What we knew was that the Club is a hardened steel device that attaches to the steering wheel and the brake pedal to prevent steering and/or braking. What we found out was that a pro thief would carry a short piece of a hacksaw blade to cut through the plastic steering wheel in a couple seconds. They were then able to release The Club and use it to apply a huge amount of torque to the steering wheel and break the lock on the steering column (which most cars were already equipped with). The pro thieves actually sought out cars with The Club on them because they didn’t want to carry a long pry bar that was too hard to conceal.
We had a brilliant, visionary solution to this whole problem. It was called Stack Overflow. Real questions with actual answers, no faffing about. Tragically it has been dying a slow death for seven or eight years and as of now looks like it will just be milled into LLM food.
> The thing is, this is something no one is really incentivized to lie about
I don't think it's lying in the sense of trying to make someone else actually believe it. It's just a form of creative fiction writing. It can be a lot of fun to write in this mode; when well done it's a pleasant kind of erudite humor because to produce it (and get it) you have to be somewhat knowledgeable in the topic. Mockumentaries might be the film/TV equivalent. Unfortunately (especially for certain subjects) it also confuses and causes strife if readers take it too seriously.
Inference for static types requires more from the compiler in two key ways that impact the developer experience. First, it's just plain more work to do when compiling, so compile times are longer than they might otherwise be. Second, error handling and messaging needs to be written very carefully to avoid dense and unhelpful output when inference fails. It's positive in many ways, but it's not a free lunch.
Mapo tofu doesn't seem like a good counterexample since the pork component is as important as the tofu to the dish. Granted there are veg versions using mushrooms as an alternative.
If you do squash merges, how does the queue handle the creation of the final commit message? We already have a problem with trash-filled message bodies with GitHub, and I don't want this to make it worse.
There's a huge gap between sharing a post and having that be replicated and consumed or archived elsewhere by other users/hosts, and having that same post processed against a giant pile of other data specifically to de-anonymize it. The first one is, yes, just normal use of public information. The second is more like spying, and since we know Facebook does stuff like that, being apprehensive specifically about them is justified.
OP is about sending the photos over an unencrypted channel, not that OneDrive unencrypted access to them. Normally when talking to a cloud storage service, the data will be encrypted in transit (and then again when at rest).
I don't follow. Macros are literally just vectors of input events; if keyboard navigation works, then so will a macro that replays that navigation. (It is also already possible to record a macro that includes mouse events.)
There's no reason keyboard navigation can't work in a GUI context. In fact it might be easier to define things like "up" or "forward" since widgets will often have a natural hierarchy with direct references to each other, so there's no need to parse anything to figure out what the "sexp" is.
Isn't the necessity of skip meetings itself a pathological sign? The only thing you legitimately need to talk to your manager's manager about is things your manager can't handle -- i.e. mostly problems with and/or praise for your manager. Everything else should go through your manager, or what are they there for?
The thing is, for people who want a small phone, the 13 mini still has a pretty hefty feel. Compared to the 5s/orig SE body it's massive and it's only a tiny bit shorter and narrower than the 8/new SE, while feeling thicker.
You're ignoring that Kagi runs on subscriptions, so this funding is not all there is. If the subscription covers basic user costs (which it should, because they just adjusted the pricing) or at least covers most of them then the 670K can be used for growth.
iCloud storage was never E2EE; the iMessage system was, but not iCloud. As of late last year iCloud can optionally be E2EE, with the "Advanced Data Protection" feature, which is off by default (https://support.apple.com/en-us/HT212520).
It's an interesting thought but GitHub specifically has absolutely no reason to want this; doubly so after the Microsoft acquisition. Sourcehut, Gitea.io, and Codeberg would be the places to start.
Any sane business decisionmaker would want legal cover for something like this in case it draws a lawsuit. Regardless of whether they themselves think it's okay, doing it entirely on the sly makes it more likely an opposing lawyer can convince a judge/jury that it's not okay. If they have an agreement that the client "accepted" that strengthens their position quite a lot.
Designers should be very familiar with the standard widgets, idioms, and interactions of the platforms they're designing for, but I don't think performance is rightfully something they should have to worry about.