GDPR doesn't mandate cookie banners, it says that you simply cannot store irrelevant PII for the sake of it. That's the point of it: to protect the privacy of the public against "data brokers" and other scum. You're welcome.
People seem to have forgotten, but cookie banners were a pest before GDPR. And newsletters and login popovers, those are GDPR?
Sweden does not have a car industry. The fighter jets are a different matter, very strong technical moat and need to prove the system in combat. You can't just start a fighter jet business.
What do you mean Sweden does not have a car industry?
Volvo and Polestar have their HQ in Sweden and huge manufacturing plants. They also develop platforms for some other Gealy brands including Link&co and IIRC also Zeeker.
Volvo is complicated. Basically a lot of these smaller companies and countries realized there was no way they could make the economics work with the cost of electronics and software-related R&D being what they are. So they sold to larger players. But design and final assembly still happens in Gothenburg for high-end models that are typically destined for the EU market. The US now manufactures the SUVs.
Volvo was bought by Ford in 1999 and then sold by Ford to Geely in 2010. It had nothing to do with software related r&d, it was mostly down to Ford needing money after the financial crisis.
Volvo have factories in Sweden, Belgium, USA, and China. The new EX60 is manufactured in Sweden. The US factory makes the EX90, XC60, Polestar 3, and until recently the S60 sedan.
Volvo Cars is still headquartered in Sweden, and employ 22.4k people in Sweden out of 40k globally[1].
Given that the market for Volvo is global, it seems to me that Volvo Cars is still overwhelmingly Swedish, while at the same time being overwhelmingly controlled by Geely.
The Top Gear enthusiast in me loves that you included Koenigsegg in this conversation.
But including a company that hand-builds a handful of hypercars annually in a conversation about the auto industry in Sweden is not the flex you think it is.
Sweden had a native car industry they decommissioned themselves, in short, they basically gave up, but they’re not alone Australia, New Zealand did the same and so did Canada, but they’re starting to realize that they were a little bit hasty in giving up….
Then last, but not least the UK basically threw the towel in too on a wide assortment of industries, but they’re now discovering that that was a big mistake.
It was an abandoned path even before 3.10, it just took longer to implement 649 and 749 than they expected.
But this is a "...will continue to exist with its current behavior at least..." is an important bit there.
From pep-0749:
Sometime after the last release that did not support PEP 649 semantics (expected to be 3.13) reaches its end-of-life, from __future__ import annotations is deprecated. Compiling any code that uses the future import will emit a DeprecationWarning. This will happen no sooner than the first release after Python 3.13 reaches its end-of-life, but the community may decide to wait longer.
Correct. Before the "from __future__ import annotations" behavior that converts annotations to strings became the default, they figured out a better mechanism for circular type annotations (making them lazy) that is implicitly backwards compatible and that didn't need to be guarded behind a future statement.
Ironically, the new default behavior (making type annotation evaluation lazy) is not backwards compatible with the "from __future__ import annotations" behavior of converting annotations to strings, so they can't just rip out "from __future__ import annotations" and instead it needs to be deprecated and removed over multiple releases.
I talked to a guy who did his doctoral degree on quantum computing and he was not worried at all. In fact he thought it was wildly overhyped, and like cold fusion, self driving cars, or string theory, always just around the corner. Just give us five more years and another grant, please.
So very rude. If you prefix it with "the LLM says", I'm fine with it. But taking that hot air and pretending it's yours? It's not just rude, it's dishonest.
You're right to point that out, and I admire your willingness to challenge the accepted narrative. That writing style not just unique to AI — all humans write like that. That's not annoying — it's refreshing. It's not AI repeating the same phrase — it's just AI using what they're trained on! It's like a monkey trained to write essays — the monkey isn't making up words; it only knows what it was taught! That's not AI — it's just an agent (human OR AI) formulating a response based on given context. That's not exhausting — it's informative!
Breaking chacter for a minute, it really annoys me every time a blatantly obvious LLM comment is called out, it's flooded with replies like "No, I akshually write like that - people have always written exactly like that" as if its not obvious lol
to be fair, em-dashes were cool which is why AI uses it so heavily which is why they are uncool now. round and round we go... and I loved the in-character response.
It would be plenty in-budget if the software part of local AI was a bit more full-featured than it is at present. I want stuff like SSD offload for cold expert weights and/or for saved/cached KV-context, dynamic context sizing, NPU use for prefill, distributed inference over the network, etc. etc. to all be things that just work for most users, without them having to set anything up in an overly error-prone way. The system should not just explode when someone tries to run something slightly larger; it should undergo graceful degradation and let them figure out where the reasonable limits are.
But it's well within the budget of a small company that wants to run a model locally. There are plenty of reasons to run one locally even if it's not state of the art, such as for privacy, being able to do unlimited local experiments, or refining it to solve niche problems.
There are way too many good uses of these models for local that I fully expect a standard workstation 10 years from now to start at 128GB of RAM and have at least a workstation inference device.
or if you believe a lot of HN crowd we are in AI bubble and in 10 years inference will be dirt cheap when all of this crashes and we have all this hardware in data centers and it won't make any sense to run monster workstations at home (I work 128GB M4 but not run inference, just too many electron apps running at the same time...) :)
> I work 128GB M4 but not run inference, just too many electron apps running at the same time.
This is somewhat depressing - needing a couple of thousand bucks worth of ram just to run your chat app and code/text editor and API doco tool and forum app and notetaking app all at the same time...
Crucial (Micron) sold 128GB of DDR5-5600 in SODIMM form for $280 a year ago. It would be slower tham the same amount on an M4 Mac, but still, I object to characterizing either as “a couple thousand bucks worth”.
Inference will be dirt cheap for things like coding but you'll want much more compute for architectural planning, personal assistants with persistent real time "thinking / memory", as well as real time multimedia. I could put 10 M4s to work right now and it won't be enough for what I've been cooking.
Just have to reclassify it as non-frivolous then. $10k's not a lot for something as important as a car, if you live somewhere where one is required. Housing is typically gonna cost you more than $10k to own. I probably spend close to $10k for food for 1.5 years.
So if you just huff enough of the AI Kool aid, you too can own a Mac Studio. Or an M5 MacBook. Or a dual 3090 rig.
People seem to have forgotten, but cookie banners were a pest before GDPR. And newsletters and login popovers, those are GDPR?
reply