ledauphin

the tables agree that microseconds are supported by both standards, but for some reason the Venn Diagram only displays 6-digit fractional seconds under ISO8601. This led me to do some head-scratching until I referenced the table, which seems a lot more comprehensive.

This is extremely cool and useful overall, but unfortunately the Venn Diagram seems to be slightly misleading.

i, too, wish that there were an actual way to pay per view on things like this.

i read a lot, but i read widely, and I have absolutely no desire to pay for the entirety of what tNYT is into (nor do i want to deal with their dark patterns around canceling).

Everyone keeps telling me there's no market for this, etc etc, and I suppose that must be true, but I can't help but think that there must be _dozens_ of us who want a different approach here...

thanks for doing this. I could see this becoming a part of my workflow long term.

yeah, this struck me as strange too. the ongoing maintenance on long-lasting industrially-manufactured drones might well cost more than rebuilding a cardboard one every few weeks.

in Python, dicts are actually definitionally ordered, since 3.7, so this objection doesn't carry much weight.

additionally, you might be interested to know that the implementation of dicts as ordered was found to be more performant than its predecessor.

Finally, even if they were unordered, there would be no need for ordering in this proposal, which depends on unique integer keys starting at 0.

100%.

as an organization, there's value in _limiting_ the number of tools you adopt. But you'll nearly always want to adopt a few right-sized tools rather than using the same sledgehammer for every single thing that looks remotely like a nail.

agreed, but there's still differentiation in syntax, and I was responding to someone asking for no differentiation.

I disagree - allowing for type inference on the closures will make for a much more pleasant language, whereas requiring type annotations on top level functions makes sense for lots of reasons.

there will be any number of design issues for them to solve and this will certainly be one of them. it doesn't seem insurmountable, though.

this was a common problem with the older tail-mounted engines. ice would come off the wings during takeoff and go straight back into them.

"Moonbit makes programming easier with its automatic memory management" isn't absolutely nothing.

they apparently have their own GC and intend to use the one that comes with WASM 2.0.

The most obvious performance win for free threading in Python is where you have large read-only, immortal data that is referenced by all threads. The "memory traffic" you mention is a major issue for multiprocessing approaches, and sub-interpreters don't provide access to shared memory in this way, either.

The no-gil project has already been benchmarked to scale basically linearly in this scenario, so your hand-waving predictions are already known to be inaccurate. https://www.backblaze.com/blog/python-gil-vs-nogil-boost-i-o...

you're actually blurring some of these images, huh? :D

I appreciate this note - I have no exposure to the original games, but Dragon Age: Origins was one of the best games I've ever played.

I looked up some basic numbers on the death toll of World War II in the Pacific theater. It seems to be in the ballpark of 30 _million_ people that died.

I think it would be fair to say that bombing a civilian city into oblivion is immoral. Unfortunately, Hiroshima and Nagasaki were not the only cases where this happened. And at the end of the day, it's killing people that's immoral, and vaporizing them with different types of bombs... well, it feels like we're starting to split hairs here, right?

It's odd to me how bad we are at sensible discourse wherever the word "nuclear" is concerned.

it's not going to stop, and those who complain about it without curiosity about why it's such a valued language feature are doomed to suffer until the end of their careers.

at the same time, I'm somewhat interested to hear a further defense of this idea that newlines and spaces are "invisible". Is this invisible in the sense of neutrinos, or in the sense of wind blowing in the trees, or in the sense of the vacuum of space, or what?

For my part, I seem to have no trouble "seeing" line breaks, spaces between words, etc.

how do eSIMs enable locking arbitrary devices to a network?

this downplays the possibility of having competitors. if your idea either already exists or can be cloned quickly, being stuck on one platform while somebody else hoovers up the broader userbase can absolutely kill you.

wow.

i think this is a strong point, and it's underscored by how little anyone is willing to center the discussion on something quite fundamental: is the behavior from the individuals in question acceptable even if it were legal? My answer to that is no, it is not and could not be acceptable human activity even if the laws protected it.

We've largely lost the ability to talk about the things themselves, preferring instead to look at things through the tremendously artificial lens of "what do the lawyers say?"

We've outsourced morality to a technocracy.

yes, I use obsidian and I have several vaults, and each is its own directory that is synced independently using Syncthing to whichever devices need to be able to access each vault.

great to hear that it works, but it is hilariously expensive for what it does.

When the price comes down to $3/month, I'll start paying for it. Until then, I'll use Syncthing for free.

it'll be very good. it won't resolve conflicts for you, though - just like Dropbox or Google Drive also wouldn't. It's last-write-wins, so you either need to keep your devices connected and syncing at all times, or you need to be careful when you edit the same files on different devices.

I use Syncthing for all kinds of things and it's excellent, but it's not really a silver for bullet for mutable data like text files.

I appreciate the correction and reference!

in practice, they just make you sign a notice and consent form in order to receive care. if all the local hospitals do this (and they do) then you no longer have any option but to sign the form.

we really need to eliminate this absolutely ludicrous distinction legislatively.

EDIT: i stand corrected with regard to anesthesiologists. I maintain that hospitals and providers are quickly learning how to maneuver patients into scenarios where they will be subjected to surprise billing anyway. I also maintain that the concept of out-of-network services is mostly ridiculous, since the median patient is very rarely in a position to make actual choices about most of the care they receive.

this is exactly the software that came to mind for me.

a fraction of the billions in wealth that had magically appeared during covid, largely because of government policy.

i want something like this for lots of reasons, but the headliner is structual typing.

It should be possible to get simple attribute access while not creating a new nominal type and not going outside the Python stdlib.

I'm constantly using NamedTuples when what i really want is an anonymous struct.

yes, from reading the docs, there's a websocket.

Making a 'server call' on each interaction is also what web apps used to do before SPAs were a thing. And in many cases it's what SPAs do as well.

Of course, it depends what counts as an 'interaction', but that's been the case since JavaScript existed.

this is very light on details. I would be thrilled to see an actual economic analysis showing that this is working, though.