When I write JavaScript, I make as many things immutable as I can. Sometimes it adds verbosity and leads to less efficient computational patterns, but overall I believe I run into far fewer bugs that are hard to make sense of. There are things about the design of Temporal I don't really like, but immutability was a solid move.
What I don't understand is why they had to make string formatting so rigid. Maybe it has to do with internationalization? I'd have liked if it included a sort of templating system to make the construction of rendered date-time strings much easier.
> What I don't understand is why they had to make string formatting so rigid. Maybe it has to do with internationalization? I'd have liked if it included a sort of templating system to make the construction of rendered date-time strings much easier.
I think Temporal takes the right approach: toString() is the (mostly) round-trippable ISO format (or close to it) and every other format is accessible by toLocaleString(). In Python terms, it is a bit like formally separating __repl__ and __str__ implementations, respectively. Date's toString() being locale-dependent made it a lot harder to round-trip Date in places like JSON documents if you forgot or missed toISOString().
Temporal's various toLocaleString() functions all take the same Intl.DateTimeFormat constructor parameters, especially its powerful options [1] argument, as Date's own toLocaleString() has had for a long while and has been the preferred approach to locale-aware string formatting.
A lesson I've picked up from what little localization work I've done is to avoid "specific formats" as much as possible. Some user's locale is never going to fit your "specific format" and the more you try to (micro-)manage the output format of your dates the more you are likely to make that user upset or show them a very broken experience. The short/medium/long formats you can get out of Intl.DateTimeFormat/toLocaleString aren't perfect, they are compromises, but they work and users can generally trust them.
(If you are using a specific format for something other than display to a user, maybe consider the standardized ISO format instead. Machine-to-machine communications could definitely use a whole lot fewer "specific formats" and explicit Date parsing. Very few backend languages don't have out-of-the-box support or easy found library support for ISO format today.)
The formatting decision is intentional and documented in the proposal: toString() is meant to be the round-trippable ISO representation, not a display string. For locale-aware output, toLocaleString() accepts the full Intl.DateTimeFormat options bag, which covers most real-world display needs.
For non-locale custom formats ("YYYY-MM-DD" style), there is a gap - Temporal deliberately does not ship a strftime-style templating system. The design rationale was that custom format strings are a source of i18n bugs (hard-coded separators, month/day order assumptions, etc). The idea was to push display formatting toward Intl so locale handling is correct by default.
In practice you can cover most cases with something like:
const d = Temporal.PlainDate.from('2026-03-11')
const parts = d.toLocaleString('en-CA', {year:'numeric',month:'2-digit',day:'2-digit'})
for YYYY-MM-DD (Canadian locale uses that order). Fragile, but workable.
The V2 issue Dragory linked is exactly tracking this - custom format pattern support is on the backlog. For now, date-fns or luxon work fine alongside Temporal if you need templated strings.
I have a GMRS license, which isn't "amateur radio" per se, but can be used in much the same way. The main differences are that you're limited to a narrow band of "channels", and repeaters are not allowed to form networks. The tradeoff is that the license is basically just a fee and requires no test or advanced knowledge.
This is why I disable automatic updates. Not just for browser extensions but everything. This whole "you gotta update immediately or you're gonna get hacked" thing is a charade. If anything, if you update you'll be hacked at this point.
Could the BMI thing be simply explained by the treated children expending less kinetic energy? In other words, they are less hyperactive, so it seems logical that they might actually be prone to some weight gain.
Methylphenidate is also prescribed for ADHD-PI (inattentive). My son took this medication and for him it served as an appetite suppressant. He's also 6'5" now as an adult. So individual experiences will vary.
I take methylphenidate, actually. I experienced the appetite suppressing effect, but I would say that after ~3 to 5 months on the drug that basically went away. There's still a noticeable benefit for attention, but otherwise I eat just about as much as ever. But yeah, different experiences for different folks.
Haven't cared about Discord in a long time. In fact I'm glad they're continuing to shoot themselves in the foot.
During the pandemic, I was on a Discord server for folks to socialize and blow off steam about the whole situation. Yes, there were some anti-vaxx wackos, but overall the place was civil and balanced, and I met some interesting people through it. We cracked jokes and it was a little bit of fun in a tough time.
One day I came to discover that Discord had banned the server for allegedly violating... something. I wish I had written down everyone's emails because I permanently lost contact with a bunch of friends in an instant.
I never signed in to Discord again, in spite of times where some other social group wanted to use it. I vowed never to use Discord again. Fuck those guys and the Teslas they rode in on. I hope this ID verification thing is another big step towards their irrelevancy.
The difference with Reddit is it has way more persistent value. Everything on Discord is throwaway, but valuable posts on Reddit from years past are easily retrievable. The two aren't so comparable.
One of the unspoken reasons many people have for using Discord is they don't want what they say to easily be associated with them in perpetuity. Requiring ID really chips away at that, in spite of what Discord has to say about privacy around ID.
By no means am I saying that Discord will go extinct. I just haven't observed anything about it that's irreplaceable. Reddit, on the other hand, has a wealth of discussion dating back to the mid-to-late 00's.
> valuable posts on Reddit from years past are easily retrievable.
Rant: Several years ago, everything I'd ever written for over a decade on Reddit vanished one morning for no discernible reason, including all nested replies from other people. I appealed, my appeal was "granted", and nothing changed, except the appeals page refused to work because it said my account was already in good standing.
I dug up an ancient account I had used for resume feedback, asked around in the help subreddits, and it too was killed the same way.
It's wild that this nonsense is still floating around by people pushing "credentialed doctors", whatever the fuck they think that means. No one with any vague degree of credibility would now or ever has supported "very large number" and all of the "externalities" (are you sure you're using the right words) have been vastly outweighed by the things the vaccine provably did.
What is a "credentialed doctor"? What are your qualifications for having an opinion in the first place? Why do you think a minority org full of quacks with little relevant background has any standing at all? Aside, of course, from the fact that it confirmed your priors (that became your priors after, presumably, some intense research on Facebook and OAN). Perhaps we should let Dr. Oz chime in, too, on things he's not qualified in.
Nah, it's because you know you have no idea what you're talking about, and you know you're utterly out of your depth, just like every other Facebook researcher, so instead, you'll play "you're mean and that makes me feel bad" games.
It's so boring and predictable. You're happy to shitpost across the internet, but the instant you're called on it, you take your imaginary ball and go home.
I suggest you take another angle than "Facebook researcher". I've seen enough to know how much we were lied to. All the stories coming out of Children's Health Defense, VAERS, doctors like McCullough and Cole and Malone (but I'm sure you don't care, they're all discredited to you)
I really think most of the criticism towards embedded Browser engines would be moot if there was an engine where anything unrelated to layout and rendering had to be imported piece by piece. Most of the time, we just desire what HTML and CSS give us (layout and styling) and an element node API in the DOM, or something like that. So many other things get wrapped into even the most stripped down browser engines that don't really have to do with layout and styling which increases the bloat. I don't really see why we can't have a GUI toolkit that just renders HTML and CSS and only be in the dozens of megabytes. I don't care that lots of existing Node modules wouldn't work out of the box. Give me HTML rendering without the kitchen sink. It seems we aren't capable of this. From what I can tell, this can't even be done easily enough with Servo.
That's what Sciter does - https://sciter.com/ - it just gives you a lightweight HTML / CSS / Javascript "webview" engine for layout and rendering. Like you pointed out, that should be enough. But corporates want a "webview" that is an OS so that they can do everything with Javascript on it (hence why embedded Chrome with NodeJS is so popular).
What I don't understand is why they had to make string formatting so rigid. Maybe it has to do with internationalization? I'd have liked if it included a sort of templating system to make the construction of rendered date-time strings much easier.
reply