jmull

38 ms·

601.
by jmull 2y ago
Confirmation bias in action: accepting as true information that confirms your preexisting beliefs while ignoring information that contradicts them. E.g. this article has information in it that refutes the idea that the voting process in CO
602.
by jmull 2y ago
Apparently, you forgot to click the "don't hallucinate as much" checkbox. How silly of you.
603.
by jmull 2y ago
> are not to be prescribed for cosmetic weight loss We don't really know the coworker's medical conditions. Also, I'm not sure that achieving a positive self-image isn't worthwhile. With any drug you take, you balance
604.
by jmull 2y ago
Wanting food is a built-in fundament of life. It's hardly comparable, and I doubt dealing with it philosophically leads anywhere.
605.
by jmull 2y ago
> it also makes it easier for compilers/query planners to understand what you're trying to do Hopefully that's not true. SQL's a declarative language, where you describe what you want and the system figures out how to
606.
by jmull 2y ago
It feels like VR is the future of work that benefits from lots of display space.
607.
by jmull 2y ago
I think a big problem is that Flutter's approach is very labor intensive. It takes over responsibility for the UI, which is tough when you want to be cross-platform. You need to keep up with the native UI across all the platforms. (Or,
608.
by jmull 2y ago
No 5K iMacs had target display mode, I think. If the EU had mandated it, the 5K iMac may not have existed, would have been delayed if it did (to wait for display port 1.3 to be viable), and would have been more expensive. Just understand wh
609.
by jmull 2y ago
It also means nothing in English, though that's somewhat obscure from my perspective. (Looking it up, it sounds like English borrowed it from German a while back.) In English I think it's most often used as a verb that means basic
610.
by jmull 2y ago
Don't forget the comment above proposes another alternative, "rewrite it in Rust". The problem with such a proposal is that the cost is impossibly high for many, many cases. Effectively, across the entire existing C++ code ba
611.
by jmull 2y ago
> It seems to me like we already have a lower-overhead approach ... Rust Rewriting all the existing C++ code in Rust is extremely high-cost. Practically speaking, that means it won't happen in many, many cases. I think we want to fi
612.
by jmull 2y ago
I recently canceled T-mobile home internet. Cancelling the service was easy. Cancelling the recurring payments has turned out to be an entirely different matter.
613.
by jmull 2y ago
I thought it was quite good; an entirely approachable explanation that nonetheless gets across the essential limitations of the current approach to AI: When working well, they provide existing answers to questions, rather than thinking up n
614.
by jmull 2y ago
I think we can understand syntactic sugar as an alternative (hopefully more convenient, elegant, or pleasing) syntax for expressing something that can already be expressed. That is, something that works the same but looks better (hopefully)
615.
by jmull 2y ago
> Wait, you're proposing... No. Some significant differences between those examples and the new proposal: (1) (most important) Those are all implemented and released. The time to debate how those things might best be handled is long
616.
by jmull 2y ago
That’s part of what C does, but it’s not the only thing. Assembly adds mnemonics and a logical structure to machine code. C largely does the same, but adds a cross-platform abstraction, mechanisms for organizing and sharing source code, a
617.
by jmull 2y ago
It looks like the proposal is to build a little single purpose reactive UI engine into <select><button><selectedcontent>, and we're talking over the details. To me it's a bad idea from the top. Either leave react
618.
by jmull 2y ago
All I’m seeing here is alternative syntax for what’s already there. I like some of it, but that’s hardly worth the increase in complexity. In fact, having fewer aesthetic syntax choices is probably more of an improvement — cuts down on poin
619.
by jmull 2y ago
> Apple suddenly listens to the world. If Apple wants to listen to everything everyone says, they already are. (And where they go, and with whom they communicate, etc.)
620.
by jmull 2y ago
> And the main tradeoff with the AirPods Pro 2 is battery life: they can last for around six hours with the hearing aid engaged, which doesn’t match what you’ll get from many OTC and prescription hearing aids. Since they are comparing to
621.
by jmull 2y ago
Don't bother telling me you're rewriting something for performance if you haven't profiled the existing solution and optimized based on that.
622.
by jmull 2y ago
"node1", "node2", and "storage" are three separate things in the distributed environment. Only storage accepts changes, and it's what verifies the incoming token matches the current token. So node2 doesn&#
623.
by jmull 2y ago
> and a reliable one for correctness To be clear, my point is don't use distributed locking for correctness. There are much better options. Now, the atomicity I mention implies some kind of internal synchronization mechanism for mul
624.
by jmull 2y ago
Sure, that's why I said you might introduce "locks" (reservations is a much better term) for other reasons. Efficiency is one, as you say. The other main one that comes to mind is to implement other "business rules"
625.
by jmull 2y ago
This overcomplicates things... * If you have something like what the article calls a fencing token, you don't need any locks. * The token doesn't need to be monotonically increasing, just a passive unique value that both the clien
626.
by jmull 2y ago
I just mean a mechanism for specifying metadata, and a little metadata. Off the top of my head, an optional header like "MergeMetadataObjectPropertyName: @mergeMetadata" Which would cause objects in the merge containing the proper
627.
by jmull 2y ago
json merge patch is pretty good. I think it just needs an optional extension to specify an alternative magical value for “delete”. null is a pretty good default, and comports well with typical database patterns, but is outright bad for some
628.
by jmull 2y ago
Meh. I get it. It’s just so bassackwards to use an imperative, indirect form to describe state, even if it’s just state changes. Maybe simply specify the new state?
629.
by jmull 2y ago
Yes, it looks like it has been removed. A good edit, IMO.
630.
by jmull 2y ago
That's OK, but there's still a lot of unnecessary/undesirable wrapping.

More ›