I agree, I tell everyone who will listen that no country, not Russia, China, Japan, France, USA etc has ever made nuclear power profitable. And you can't blame it on the environmentalists in China and Russia.
That being said, many countries consider it a national security issue not to be held hostage to foreign oil.
Buried at the end of the article the author linked a library of different art styles applied to the same poster content. Found some new cool art styles to try out in the future.
https://john.hartnup.uk/poster-prompts/
This is the reason I never made a mobile version and all mobile users use it in a browser.
The biggest problem (bug) with this approach is that iOS limits the RAM usage to 2 GB per website. I have to tell many of my users to ditch their $1000 iPads and get a used $150 Macbook for better experience.
Lossless JPEG XL is in the DNG spec since three years (v1.7). So, you can convert your proprietary camera raw files to smaller ISO standard compliant JPEG XL compressed DNG raw files (mosaiced, not linearized).
Yeah, in essence. This is actually a pretty cool part of working in Lean. It's a somewhat normal convention to write something in a human readable way and then write a second optimized implementation with some kindness of correctness theorem connecting them. There was a whole open "competition" for writing a faster Lean kernel/proof checker that didn't sacrifice on soundness called Lean Kernel Arena. Fun reference point: https://kim-em.github.io/blog/2026-7-24-why-lean-is-faster-t...
Velocity raptor is a free game that accurately simulates the effects of special relativity. It slows down the speed of light to 3m/s and you solve puzzles as a cute dinosaur. https://www.testtubegames.com/velocityraptor.html
There is also a helpful FAQ which explains all the strange things happening, such as length contraction, time dilation, and color shifting: https://testtubegames.com/srel101.html
My favorite levels are #18 (which demonstrates time dilation), #26 (which demonstrates space warping), and #42 (which demonstrates retarded time https://en.wikipedia.org/wiki/Retarded_time ). All the levels are unlocked and you can skip to any level.
I love this line of thinking but the framing comes across to me as a bit inflammatory and uncharitable. Just about anything involved in the exchanged of ideas can be viewed as a virus! That is because, when viewed from an evolutionary biology perspective, ideas are the cognitive equivalent of genes (in fact, this is where the term meme comes from).
There's a whole field, evolutionary memetics, dedicated to this. Cultural values, marketing, religion, social media, education, propaganda, etc. can all be viewed quite naturally through this lense. Even the terms we use in every day language (eg, going "viral") seem to intuitively grasp this.
Is my friend a virus for recommending me their favorite book? Well, yes I guess, but that's kind of just how ideas work. Just my two cents
I worked on a 20-ish team of good-but-not-brilliant engineers. Our secret weapon was liking each other and having very low turnover over the course of 10 years.
As a principal engineer at Meta and LinkedIn, it’s still the most productive team I’ve ever been on
China's nuclear production is only growing in an absolute sense. As a share of production, it's dropping, from a very low level of 4%. China is building other power types far faster than nuclear.
I’ve tested at least 20 STT models in a benchmark I’ve set up with German, Italian and English voices from meetings in my company.
The voices contained very industry specific words, the languages changed from one sentence to another, sometimes words in a language were mentioned while a discussion was in another.
The only local model that satisfies me is Voxtral Mini 3b, the only paid API that is slightly better is eleven labs. Yes, Voxtral might not reach the best score in the benchmarks, but to me, it just solves a problem. It might not be the best in terms of speed... but that’s not a problem for me.
Happy to test this new model from Google but I’m not sure I’d go with that instead of something that can run so easily in my machine.
Though this article concentrates on the SSRIs, other meds like the SNRIs can have a similar or even worse withdrawal effect. We didn't call it "Side Effexor" for nothing.
People legitimately need these drugs, including in the short term. The problem for acute stressors once they resolve is how to get them back off.
I’m a big fan of how C# handles this. The standard library is versioned like any other library. Your program is explicit about the major version of the standard library you’re pulling in. And all major versions of the standard library continue to work.
For rust, this would mean something like adding std = 1.0.6 to your cargo.toml. The advantage is it means the standard library can deprecate and replace features. Upgrading std is an explicit step by the developer. Annoying, but in the age of LLMs it should be pretty easy.
The one big question I can’t answer is what happens if your dependencies use a different version of std? Are std v1 Strings compatible with std v2 strings? Oof.
Tao's Rule of Thumb (which applies very well to software):
> My own suggested rule of thumb: if the authors cannot convincingly demonstrate that they are able to give a clear, expert-level talk on their results, one that is correct and properly attributed, then the result should not be published. A proof that no human can properly explain should be viewed as incomplete, even if it has been formally verified.
I think in this case it doesn't help that there are multiple watermarking schemes, and the easiest for people to understand is the red/green scheme by Kirchenbauer et al. (https://arxiv.org/pdf/2301.10226), which does technically distort the logits (but I'd argue only in cases where you wouldn't notice it anyway).
I wasn't aware of this gumbel softmax scheme, it seems you're referring to https://simons.berkeley.edu/talks/scott-aaronson-ut-austin-o... ? That's really clever as it doesn't even distort the logits, basically cryptographically indistinguishable from a "real" random sample unless you have the key.
The actual scheme Claude uses seems to be neither of those two though, they say it is SynthId-text which seems to be tournament sampling based.
Nice graphs, but these numbers are not reflecting the reality. As both count heat deaths differently. Europe does calculate it based on excess mortality studies and US only counts them if it is listed as contributing cause on the death certificate. With similar statistics, US numbers are several times higher. And as Europe has an older population, rates are likely higher, but the real difference is much smaller.
The EU told them they can not by default prefer their own maps product when linking from their search product, they have to allow the user to choose.
They could have simply added a selector when a user first clicks on the maps preview in the search result, and then remembered it on device or across that user's account.
But of course, then the user could choose a competitor's product and Google would have to honor it. That would be horrible, so instead they just made the user experience worse for everyone and elegantly made people blame the EU.
I'm not sure how this interacts with open source principles. I think they are free to do whatever they want with their own website and indeed with open source tooling, but as a host for open source it could conceivably conflict with those principles.
A much debated aspect of open source is that it may be used for any purpose. The JSON licence sparked much of this debate.
More recently there has been suggestions for an ethical source movement, which advocate that source may only be used for ethical uses. I presume they must mean Good old christian, pro family, anti-terrorism, traditional values etc. the usual ten commandments stuff. Or perhaps they had something else in mind, it's unclear, but what ever it is that's the stuff that's allowed and the other stuff isn't.
It's just part of what I call the config pendulum.
Simple config -> (Need to do more complicated things) -> Add override levels -> (Need even more flexibility) -> Add a Turing complete language -> (Things get ridiculous, lots of spaghetti code outside of version control. Time for a reset) -> goto "Simple config"
It's fine. I am not saying it's wrong or right. I've gone through the cycle a few times in some projects. On the other hand, think of it as your project is lucky to be used long enough to have these problems. To feel better about it think of it as a spiral. The next "Simple config" is a slightly better version of the first.
The surprising (and possibly untrue) thing is the high price of canned vulnerabilities. WordPress is known as the remote root shell with a blogging feature.
This is a rare instance where feeding this groundbreaking information into an LLM gives _them_ psychosis. I fed this to claude code and watched it verify the result in 7 different ways to be 100% certain, and it was just flabbergasted. Quite remarkable.
Absolutely true. But China’s industrial dominance is also the government immiserating its people, just in a different way. Domestic consumption in China is famously low, work culture is famously bad (996,etc). And this is because of what their government, not the people of China, have chosen to do.
This reads an awful lot like the prompter had a semi-confusing time with some async, and had their favourite model write an upset blog post about it.
I don't think these systems are perfect, nor are they fit for every use-case, but some of the complaints ring a bit hollow.
> fetching a database record over the network, then immediately crunching the data. But what happens when that data crunching involves parsing a 10MB JSON payload
Mixing IO-sensitive code and blocking code causes issues, who knew? I'm not quite sure how these libraries are supposed to magically _save_ you from this?
> When these latency spikes occur, the answer is always the same: separate your runtimes.
Well yeah. "Why doesn't my daily-driver cut sick lap times around the Nurburgring?" If you want to run blocking, non-interleaved code, don't do it in an executor expecting small, interleaved, non-blocking tasks. The docs for Tokio even mention this, and provide a number of worked examples of integrating/bridging sync and async code.
> If a developer must manually partition I/O and compute, strictly police the boundaries to prevent deadlocks, and ferry data between two different runtimes with two different mental models, the async abstraction has failed.
Not necessarily. If I'm chasing a performance target, and the tool gets me 80-90% of the way there, to the point where my next task is optimising layout and caching, I call that a win. That's performance ground we'd have to address at some point if we want to go faster, so getting there easily means:
- those people who don't need to go faster because their perf requirements are met are happy
- those people who need to go further get to skip the intervening work, and go straight to these optimisations.
Edit: also wanted to make a point about the "memory blowup" the author mentions. It's entirely possible to do the _same_ load-shedding the author wants in Rust/Tokio/Monoio/etc, this is again, just a matter of building your application in a way that uses, and communicates back-pressure. I gather that they appear to want something which is a bit more opinionated and "batteries included" as far as functionality goes, which is totally fine-and-cool, but calling Tokio + Rayon _bad_ because they explicitly don't do this is a bit of a miss.
That being said, many countries consider it a national security issue not to be held hostage to foreign oil.