Hard to integrate in what way? XSLT is a language focused on several things that it’s very good at but it’s not intended to replace Python or be a general purpose language. Yet there are many common data related tasks where a messy and hard to maintain pile of imperative code can be replaced with a simple XSLT.
Isn’t this standard competitive practice ? Charge what the market will bear.
I don’t know if I’d call that “exploitation”. If there’s one gas station 90 miles from every other gas station in the Nevada desert, they’re gonna charge more, aren’t they?
https://arstechnica.com/tech-policy/2025/06/stung-by-custome...
A comcast customer always had the option to pay for unlimited data. I get that part. What is the 2nd part? “Started offering it as standard” means what?
How, where? In 2013 I was still working a lot with XSLT and 1.0 was completely dead everywhere one looked. Saxon was free for XSLT 2 and was excellent.
I used to do transformation of both huge documents, and large number of small documents, with zero performance problems.
In the early days the xsl was all interpreted. And was slow. From ~2004 or so, all the xslt engines came to be jit compiled. XSL benchmarks used to be a thing, but rapidly declined in value from then onward because the perf differences just stopped mattering.
Then there's the fact that heat is very difficult to get rid of when in space. The ISS's radiators are much bigger than its solar panels. If you wanted to have a very-long eva spacesuit you'd have to have radiators much bigger than your body hanging off of it. Short evas are handled by starting the eva with cold liquids in the suit and letting them heat up.
All of the mockups of starships going to Mars mostly fail to represent where they're going to put the radiators to get rid of all the excess heat.
I think you’re missing the key point - heat transfer. The reason we feel hot at the beach is not solely because of heat we absorb directly from solar energy. Some of the heat we feel is the lack of cooling because the surrounding air is warm, and our bodies cannot reject heat into it as easily as we can into air that is cool. And some is from heat reflecting up from the sand.
Theres a heat wave across much of the US right now. Even when the sun goes down it will still be hot. People will still be sweating , doing nothing, sitting on their porches. Because the air and the surrounding environment has absorbed the sun’s heat all day and is storing it.
That’s what you’re neglecting in your analysis of space.
Kudos
and it’s easy to do keypair generation in the browser using subtle crypto. That API doesn’t provide jwk generation, but seems like it would be relatively easy to do even without the jose module. And the browser cab “download” (really just save) the keypair using the Blob API. Keys need not leave the browser.
An api developer portal could just offer - generate a new keypair? - upload your existing public key?
…As a choice. Either way the public key gets registered for your account.
The end. Easy.