I think the point is that jury members have to be objective at all times. So you would do him a favour by being not objective, since the ruling may be overturned and dismissed. So, stay objective.
Then again the whole court system is so skewed in favour of who has more money.
So far all these fines have been "ugh that's one day of net profits only",
be it at Google, Apple, Microsoft, Facebook - you name it. Are there kickbacks
involved to keep the fines at a minimum?
Yeah, fully agree. Fines for companies bigger than a certain threshold should be percentages of their global annual income and potentially include jail time for the decision makers that enabled them.
As long as these are the incentives companies/execs will continue to do this shit
This is much more important than the fines. But really it should be widened to include not only those who made the decision but also those who implemented it (software developers, designers, project managers) and those who benefited from it (executive officers, shareholders).
Anyone involved with the company who knew what was going on and did nothing to hinder it is culpable to some degree.
With the rank and file I am not 100% sure. I mean, they get paid a fraction of execs and potentially don't have the whole picture.
Additionally, it is really hard to draw a line. For instance, I can develop some logic that could take a screenshot of your phone. It is perfectly fine for debug builds or with explicit user consent while using an app to provide some additional context on some issue. The same logic used to spy on users is not.
I "enable" them, but I won't consider myself responsible or even remotely involved.
It would have been kind of great to see an OOP language with Alan's design, but with a better syntax. I dislike smalltalk syntax. Barely anyone uses smalltalk today.
Even then, we'd also have an OOP language to be really really fast. Otherwise people will just use C.
Java itself is too verbose and has a rather boring OOP model.
You are in luck: Alan Kay's original Smalltalk, also known as Smalltalk-72, doesn't have a syntax but instead allows you to define your own. Each class includes a single method that parses incoming messages however it wants.
The two problems with this were a lack of performance and the difficulty of understanding other people's code.
Dan Ingalls looked at the most popular styles people had created in Smalltalk-72 and defined a fixed syntax for Smalltalk-76 with the same flavor. This allowed him to "compile" -76 into bytecodes which would then be executed much faster by an interpreted virtual machine (and years later a JIT compiled one).
The analogy is putting grass everywhere in a new university campus and after a while seeing where the grass has been trampled and putting concrete sidewalks there.
For Smalltalk-80 they wanted people to be able to use it on their own computers and not only on the special Xerox PARC ones so the patched the syntax to use ASCII instead of their own character set. That made it uglier, in my opinion.
I can understand many people not liking the Smalltalk-80 syntax, but we do get some new people to the language every year and quite a few of them find the syntax one of the nicest features.
How about Elixir and Erlang? They do pretty much exactly what Kay preaches.
Interestingly, the OO model that Wirth and Gutknecht implemented in the Oberon system corresponds better to Kay's message-based vision than Smalltalk-80. Wirth arrived here not by trying to emulate biology, but by trying to avoid the V-Table.
Java implemented the Simula 67 object model, confirmed e.g. by a 2017 Gosling lecture (as did early C++ and Smalltalk-80 to a significant degree).
Speaking of vtables, at Kristen Nygaard's 100-year birthday celebration Bjarne Stroustrup also gave a fascinating talk after Alan Kay's, and they had some spicy back-and-forth discussion afterwards! Both call themselves Nygaard's heirs, anbd it was a delightful and respectful interplay between very different world views.
Kay came to Simula as a reader, turned it into Smalltalk, and later knew Nygaard and Dahl as colleagues. Stroustrup was taught by Nygaard in person, as a student at Aarhus, and then used Simula for his PhD.
Roughly: Stroustrup said he never took much from Smalltalk. What he took from Simula was the static part, compile-time guarantees and a direct map to hardware with zero-overhead abstraction, and C++ was never meant to be just an object-oriented language, since not everything is a class hierarchy or a virtual function. Kay argued that late binding pays for itself because the human is the slow part of an interactive system, and that static typing is a good idea applied prematurely. They agreed that the real job of an operating system or the internet is never to crash and never lose anything, and came at it from opposite ends: Stroustrup is working on guarantees against dangling pointers, out of range access, and uninitialized memory in C++, while Kay pointed out that Smalltalk protected every object dynamically.
If you hate llm generated summaries then you can stop here and go watch the entire video yourself, but here are timestamps and summaries for people who don't have five hours to spare (although I highly recommend it -- I was watching it in real time when I witnessed the feedback performance between talks):
4:56:49: Stroustrup says he was never much inspired by Smalltalk. What he took from Simula was the static part: compile-time guarantees. "It would be nice to say yes, but to be honest, not much."
4:58:25: Stroustrup on garbage collection versus scope-based resource management (RAII): nobody has managed to combine them. Java's finalizers are his example, and somene mentions Lars Bak, "also from here" (Aarhus), says never use finalizers, they're evil.
5:00:24: Banter. Someone asks whether there's anything he likes about Smalltalk, and the reply is "Anything you like about me?"
5:00:47: Kay agrees reuse isn't a good reason for much, asks why people cling to old languages, and brings up the CrowdStrike crash taking down hospitals.
5:02:05: Stroustrup says CrowdStrike was a violated configuration rule, not a language problem. Programmers and managers are conservative and "confuse familiar with simplicity." He's not saying C++ is right for everything, and Python's all-dynamic approach is successful.
5:04 to 5:06: Kay says late-bound slowness pays for itself because humans are the slow part of interactive computing. Computing is held back by corporate legacy, and PARC was lucky to build all its own hardware and software.
5:07: An audience question about the next ten years. Kay says operating systems and the internet put you in a different seat of responsibility: the goal is never to crash and never to lose anything.
5:08:59: Stroustrup agrees, but says he doesn't control any operating system. He's working on guarantees in C++: no dangling pointers, no out-of-range access, no uninitialized memory.
5:09:55: Kay says typing is a really good idea, just premature in its static form. Smalltalk's dynamic typing protected every object.
5:10:34: Stroustrup says it's very hard to get hardcore developers to stop believing they can crash a system.
5:11:59 to 5:13:40: Kay says the Smalltalk image was a complete operating system, and that he made a living writing microcode. The field is guilty of not keeping up with the hardware. Stroustrup says he tried to talk hardware makers into adding support features, in his PhD, and failed.
> Computing is held back by corporate legacy, and PARC was lucky to build all its own hardware and software.
this really resonates... apple makes both the hardware and software, is massively profitable and yet swift is basically a much much better c++ in a lot of ways. and xcode is just totally absurd excuse of a development environment...
is it better than before and welcome improvement? yes, but fundamentally conservative compared to what parc was doing with much much less...
>Things seem to hang on in computing just because they work a little bit.
>MVC was originally done at PARC almost 40 years ago. The good part was philosophical -- the idea to adapt the notion of "cameras" and "worlds" in the original 3D graphics stuff I participated in at Utah 45 years ago. The bad part of MVC was how we implemented it -- much too much machinery, etc.
>We (my various groups since then, including Viewpoints Research) have not thought about MVC since, but have used and devised various viewing methods over the last 20+ years. I like to do views as "watchers" which do not affect what they are viewing. There are lots of ways to do this. Similarly, I like to also use "watchers" (context sensitive to the views) to catch needed inputs. We have never done a really satisfactory automatic inverter for dealing with the loss of "dimensions" that happen when a view is made (but we have done some experimental ones).
>One important criterion is for end-users of all kinds to be able to easily make their own views in a very powerful ad hoc way via construction. We have done a number of adaptations and generalizations of how this can be done in Hypercard -- and this seems to work well (enough).
>Since we always roll our own languages and development systems, we don't care about problems that other systems might have. For example, we have very little knowledge about C#, etc. We do try to learn from the few good systems that are out there.
> Kay came to Simula as a reader, turned it into Smalltalk
There is a significant difference between Simula I and Simula 67, and Kay in his 1969 dissertation only referenced the 1966 ACM paper on Simula I. It took many more years until Simula 67 was referenced in a publication by Kay or his team (specifically, "SIMLUA Begin" in Ingalls' 1978 publication about Smalltalk-76). The documented facts (see also Ingalls' 2020 ACM HOPL paper) rather suggest the following relations: Kay - Simula I - Smalltalk-72 and Ingalls - Simula 67 - Smalltalk-76/80
> Interestingly, the OO model that Wirth and Gutknecht implemented in the Oberon system corresponds better to Kay's message-based vision than Smalltalk-80. Wirth arrived here not by trying to emulate biology, but by trying to avoid the V-Table.
That's interesting! what did they do that corresponded better?
In contrast to the "usual" (i.e. Simula 67 based) OO approach, Wirth avoided virtual methods in his Oberon language, but instead used type extension (i.e. inheritance) to declare specialized message records (as the replacement to variant records of Pascal and Modula) which were handled by procedure-typed fields of record variables (i.e. objects) using polymorphic dispatch based on the dynamic message type. The intention was not to "correspond better" to Kay's vision (Wirth likely didn't know Kay nor was he interested in his visions), but he arrived at a similar design from a different motivation. And the analogy only holds when considering what Kay and team actually implemented (i.e. "message delivery" - a record in case of Oberon, a stream of tokens in case of Smalltalk-72 - via synchronous call semantics). Smalltalk-80 instead implemented compiled virtual methods and table-based polymorphic dispatch like Simula 67, just with a dynamically typed language.
Self took the path of removing things instead of changing the syntax. It kept Smalltalk's keyword message syntax, made even smaller (no assignment syntax, variables are just slots you send messages to), and took away the classes. Only objects remain, and they inherit directly from other objects. Then Randy Smith and John Maloney gave it a visual syntax: in the Self environment you program by direct manipulation of live objects, opening outliners and editing their slots, so the environment is the syntax and the text is mostly incidental.
Your speed point is answered by the same work. Craig Chambers, David Ungar and Urs Holzle's compiler for Self (customization, inline caches, adaptive recompilation) was so fast that the technology went on to HotSpot and V8, and those ideas are why Java and JavaScript are fast today. Removing the classes made the language simpler, and the simpler language turned out to be easier to make fast.
Then David Ungar, Harold Ossher and Doug Kimelman at IBM took the next thing away. Korz removes the objects and leaves the slots. A program is a flat sea of slots that belong to nothing. Each slot has a guard on named dimensions, and a message is sent in a context of dimension:coordinate bindings, mostly carried implicitly down the call chain the way "this" is in OO languages. The receiver is demoted to one ordinary dimension (rcvr) among any number, dispatch is symmetric over the whole context, the most specific matching slot runs, and a tie is an error.
The syntax is the least interesting part. The prototype was an interpreter written in Self, and the paper's examples look roughly like JavaScript with guards in front:
The semantics are the interesting part. The second pop is more specific, so it wins whenever the context says assertions: true. main() turns assertions on, and not one line of code in between mentions them: the binding flows down implicitly to every send underneath. You've added a new dimension of variation to a running program without touching anything between the top and the bottom. No layers, no aspects, no Visitor pattern.
If that sounds familiar, it's the same thing as Lisp Machine Flavors' before and after daemons, or CLOS's :before, :after and :around methods, or plain old subclassing: override a method, do some extra stuff first, call super (or call-next-method), then do some more stuff after. The more specific method gets the first crack at it, and decides whether and when the less specific methods run.
Korz just models that as slots with guards. The checking pop does its checks, then re-sends pop with assertions: false, which no longer matches its own guard, so the plain pop runs. Method combination isn't a language feature you need a MOP to change, it's a pattern you write with ordinary dispatch. (What "super" should mean in Korz is still an open question, since there's no class or owner object to be "super" relative to.)
Guards are simple: for each dimension, a slot can ignore it, require it to be bound (binding its value as a parameter), or require its coordinate to be or inherit from a given coordinate, like assertions <= true or rcvr <= stack. Coordinates are objects with parents, so "<=" means "is or inherits from", not numeric less-than, and matching a constant is just the case of a coordinate with no children. No arbitrary predicates, so no Pascal-style ranges like 10 < x < 20, unless you make a coordinate for the range and have its members inherit from it.
And "object" doesn't disappear, it becomes subjective. Group the slots by rcvr and you see ordinary objects. Group them by assertions and you see the checking layer. Group them by user and you see one person's view of the whole system. Same sea of slots, different cuts, and no cut is the privileged one. The name comes from Korzybski: the map is not the territory.
Korz is multi-dimensional. Procedural programming is zero-dimensional, and object-oriented programming is one-dimensional (the implicit receiver parameter, usually spelled self, this, or rcvr), so both are the special cases 0 and 1 of Korz. Korz can dispatch on any number of parameters, none of them special like self or this, and the guards on the slots decide which slot is the most specific one to dispatch to.
So a Self program is just a Korz program that happens to use only one dimension, called rcvr. Objects are subjective and assemble dynamically depending on how you're looking at them (the coordinates of the dimensions), and in the special case of single dispatch on rcvr, everything looks like an object.
Call it the faith of our fathers. Kristen Nygaard and Ole-Johan Dahl gave us classes in Simula. Alan Kay gave us objects sending messages in Smalltalk. Claude Shannon had already given us a sender, a channel and a receiver, and object-oriented programming made the receiver the one privileged thing every message is about. David Ungar and Randall Smith took away the classes in Self. Then Ungar, Ossher and Kimelman took away the receiver in Korz.
Which makes it a lot like Philip K. Dick's "Faith of Our Fathers" (Dangerous Visions, 1967). The Party keeps everyone docile with hallucinogens, so everyone sees the same benign human Leader on TV. Tung Chien gets an anti-hallucinogen from a street vendor and sees what the Leader actually is, and it isn't a man. The reversal is that the shared view was the drugged one, and when he meets the underground, it turns out that each of them saw something different.
There's no single true form, just what each viewer brings. Single dispatch is the stuff in the water: it makes everybody see the same objects. Korz is the antidote, and what an object looks like depends on the coordinates you're looking from. In Dick's afterword he quotes John Scotus Erigena, from AD 840: "We do not know what God is. God Himself does not know what He is because He is not anything." A Korz object isn't anything either, until a context gathers its slots.
That's also why you don't need things like the Visitor pattern, which is a kludge for the fact that you can only dispatch on one parameter. Multiple dispatch is something some object systems support, like Common Lisp's CLOS and its MOP, but Korz takes it all the way and has no special case for self/this/rcvr.
The Finest Object System You've Never Heard Of: "The Common Lisp Object System is the finest object system in existence, and I bet you've never even heard of it."
Why would you want multiple dispatch? The Margolus neighborhood for block cellular automata is a great example. Rules apply to all four rotations of a block of four cells, so the neighborhood is Center, Clockwise, CounterClockwise, and Opposite, instead of just one self. You can write elegant, concise rules that way, and the compiler can produce efficient code or lookup tables.
I've had success applying the ideas from Self to a file system based object system for LLM orchestrated simulations (moollm). Then David Ungar told me about Korz, which totally blew my mind and made me rethink a lot of things -- but it's beautifully backwards compatible with what I've been doing with Self.
Here are some notes on applying Korz to cellular automata (with neighborhood and time dimensions), and to adventure game parsers and simulators like Zork (with direct object, verb, indirect object, location, and player dimensions). David Ungar assured me Zork is only coincidentally an anagram of Korz, but it's too sweet a coincidence to pass up, because Korz is really useful for elegantly modeling that kind of stuff.
This is a great post, thanks. I've been following prototype systems since I first logged into lambdamoo in 91, and Self is an old intellectual muse of mine but this is the first time I'd seen Korz.
You might be interested in my lang/environment "mica" which attacks this same dimension of problems from a relational/datalog angle and then makes object/prototype identity hopefully emergent out of that: https://github.com/timbran-project/mica -- relational dispatch feels like a broadening of multiple dispatch.
I feel like I may have ended up at a similar place as Korz without realizing it. I will need to dig into this paper.
Speaking also of multiple dispatch and prototypes, there's also this paper from an old acquaintance: https://www.cs.cmu.edu/~aldrich/courses/819/salzman-pmd.pdf which I used to find interesting (and built my first version of "mica" back then around the idea).
At this point in time I think a few key observations should be clear:
- Putin wages an invasion, with the primary goal to occupy territory. This is what they officially say too, bla bla bla Ukraine should give up Donbass etc... bla bla bla.
- At the same time, Putin also wages a genocide. This is in many ways similar to other wars, e. g. Israel expanding and occupying Palestine, just on a large scale Putin commits to his genocidal war ambition here (see the rumours of another wave of upcoming mass mobilization in Russia).
- Unfortunately, and this is an even bigger problem for more people in the future: Putin has no interest and desire, but also no longer any real possibility to end his war. He married the thought of the war to not only his own personal survival but that of imperialistic Russia. I don't really see how negotiations could work now (Trump acting as agent Krasnov won't do anything useful anyway, other than be a spokesperson for Putin - note that Yuri predicted this in the 1980s: https://www.youtube.com/watch?v=5It1zarINv0) and this means Putin can only escalate further. While many think Putin is insane, I think the path of escalation "makes sense" IF you are willing to use nukes. While the USA meta-jabait trolls ("he won't use nukes"), I am pretty certain that he would. Which then brings us to the biggest question here:
- Why is the EU not already mass-producing nukes for all member states?
It can not continue that terrorists such as Putin continue to threaten europeans with total annihilation. Relying on the USA is a losing strategy; a replacement for NATO is necessary, one that can also include more actors, including Canadians. Either way I do not understand european politicians refusing to build up a nuclear arsenal for all members in the EU. That makes no sense. We all know Russia under Putin will continue to escalate daily. At some point these EU politicians then have to answer why they did not build up nukes. Agent Krasnov will never harm his business partner - he maximizes on his own personal wealth. Worst US president ever but best russian asset.
> Either way I do not understand european politicians refusing to build up a nuclear arsenal for all members in the EU. That makes no sense
I am not sure if you are trolling. Producing nukes takes time, even with advanced industrial economy like EU, it would take a few months to develop and test nukes. And I would not trust country like Hungary with nukes!
Much more effective is to manufacture weapons. Soon EU will double its tank production to 5 dozens a year!
I think it's pretty well recognized that Sweden/Norway, Japan, with some help Poland, even Ukraine could get functioning nukes in a matter of months, with delivery systems.
You don't have unannounced nuclear powers now because despite what's being propagandized for the last 5 years, the rules base world order functioned, and brought stability, despite it's flaws - it wasn't perfect, but there was an effort to abide by treaties and international law.
It's was the product of WW2, and to some extent, the Cold War.
Just because you have waves of bots saying it was bad, you haven't seen yet anyone saying how the "Multipolar world order" is going to be better.
There's no project other than autocracies surviving by oppressing neighbors freely by decree.
I had to Google that claim, and apparently you're talking about one of the Russian disinformation campaign before the second invasion of Ukraine in 2022?
In the book 1984, the country was at war with another country. Then they changed which country they were at war with overnight, modifying history books to pretend they had always been at war with that country. The public just went along with it.
If Putin wants an exit strategy (I’m not sure he does), he can simply declare that all terrorists were defeated and the “special operation” achieved its goal. Then hold a victory parade and have state media say that Russia won. The Russian public would be so glad the war was over that they wouldn’t care.
What would be the point of nuking Ukraine if you want to occupy it?
Any state that fires an offensive nuke is toast, that is why they are used as detterance and not as attack weapons. MAD is a very real thing. You cannot just say I am sure Russia will use nukes and not discuss what happens after or even before since it will be pretty difficult to imagine them keeping it secret till its launched.
Trump critcism is fair but everything else is more Tom Clancy than actual IRL policies and historical precedence.
Every nuclear nation plans on winning a nuclear exchange. Of course, what 'winning' means is debatable, but they very much plan to beat the threat and not just bluster about mutual nuclear annihilation.
Do you really think the U.S. would attack Russia? Do you think the U.S. would allow the EU to level Russia (which it probably doesn’t have the ability to do)?
I don't think that the US would attack Russia as retaliation for a nuclear strike against Ukraine. But the US would probably step up aid to Ukraine. And more importantly, nuclear escalation would likely trigger economic sanctions by key neutral trading partners such as India.
What Putin is feeling out is the very real possibility he uses a nuke on Kyiv or invades/attacks a NATO member and Europe just wrings their hands and turns away.
edit: there's no difference between launching a conventional cruise missile and one armed with a nuclear warhead. You'll only know after the attack not before.
I personally use both, and keep using both. There are much more Golang job in the market now. Noone planning to ditch Go in my network or unhappy with it. Highload E-commerce, logistics, etc are way easier to write in Go IMHO.
Discover a very good niche for Rust - geo spatial analytics. Would not do it Go or Python. LLMs gave a huge boost to Rust too. Claude produce a very high code ... if designed right. Lot of feature complete libraries now.
"The Mafia" is... many different things.
From self-defense post-war southern-italian village organisations to pure-evil predatory psycho-clans, to anything in between.
> IN “The Godfather”, Don Vito Corleone refuses to engage in the heroin trade because he considers it “a dirty business”.
The movie was well-planned by Francis - but the mafia is a mass-murder organisation, without exception. Japan finally got the better of Yakuza for the most part (it is nowhere near as powerful as it was once); Italy still struggles, in particular with regards to Ndrangheta. So any article that attempts to white-wash the mafia in Italy - nope, sorry, not even good movies such as the godfather should disguise the mass-murder organisation. See how they bombed Giovanni Falcone to death, let's not forget that; and more recently how Ndrangheta executed women (2026; see https://www.bbc.com/news/articles/c39mr81j2j1o) who stopped being silent about the genocidal activities of Ndrangheta. Let's put it short: the mafia needs to be eliminated completely. It's not easy since they infiltrated so much in Italy and in parts elsewhere (just study how Capone in the USA got big, then you realise that the USA has an even bigger problem here - plus, fentanyl too), but it has to be done. There is no alternative unless you want organisations to undermine the state and continue its genocidal tendencies. You can be sure they are also involved in smuggling weapons, thus contributing to genocide outside of Italy directly as well.
Please no more white-washing articles of the mafia as glorious heroes "because they keep fentanyl out of Italy". (Besides, this is not even correct to begin with; fentanyal at the least right now, plays a very small role in Europe at best; in the USA this is different. See how Trump tries to blame Canadians for Fentanyl, smuggled via eggs, which is another one of his non-stop lies about Canadians.)
The first two seasons are great, watch it with subtitles (fun fact: in Italy it was also shown in tv with subs because most people cannot understand neapolitan dialect).
it is absolutely critical to watch Gomorrah in Italian. The English dubs are comically poor quality (think of how MS Word used to emotionlessly read text aloud).
That's not true. Trump no longer has a majority (see the coming elections) yet continues to be of inferior quality at all times. MAGA no longer supports Trump as they did two years ago, he lost million supporters already, and continues to lose more. He is now a sinking ship.
> No matter how toxic you are, you can amass support at the speed of light.
> That's also not true either. Toxicity leads to backlash.
Wait till AI driven job losses really start to mount. Nothing divides people faster than an empty stomach. The republicans are leaving a poison pill - they will profit from AI and when democrats win and the job losses really start to hit hard, the democrats will be left holding the blame bucket. Obviously they are not exactly crying hoarse for AI safeguards/job protections either because national security/donors etc.
That is true. We see that with Trump, where he tries to force the EU to open markets to the US corporations who will just steal data from EU citizens.
Why can't the EU learn more from Canada? Canada realised that with Trump there is no way to make a deal. So cut things down where possible, diversify - the EU still has to learn this lesson. In particular Germany is totally US-addicted - no idea why, other than, of course, the obvious answer ("we need to export into the USA", aka selfish greed from Germany here).
Because Germany is critically dependent on LNG imports from US.
"
Gas covered a little more than a quarter of Germany’s primary energy use in 2025, making it the country’s second most important energy source. Germany is among the world’s biggest natural gas importers – around 95 percent of its gas consumption is met by imports, according to energy research data group AGEB.
"
"
Energy industry association BDEW said that Norway has now become Germany’s top gas supplier by far, with about 45 percent in 2025, transported by pipeline. Around one tenth of the gas used in the country arrives as liquefied natural gas (LNG) directly at one of four import terminals along the coast. In 2025, around 95 percent of that LNG came from the US.
"
European countries are trading gas between them, we have to look into whole European imports. For example Germany is import lot of US gas through Belgium.
"
Russia has continued to supply a sizeable portion of gas imports, although the EU has decided to fully phase them out by 2027. Most natural gas in a gaseous state was imported from Norway (52%), Algeria (20%), Russia (10%), and the UK (8%) in 2025. LNG came from the US (55%), Russia (14%), Qatar (9%), and Algeria (6%).
"
Buying US helicopters when they've been developing one with France. But Germany has no choice: It has been literally occupied by the US forces and it's only recently that it has regained the right to have an army, but there are still 200k US troops in Germany (among other means of influence).
Germany had it's Bundeswehr the whole time since it joined the Nato 1955 same year the US occupation officially ended. And there are not even remotely 200k us Troops in Germany anymore.
No idea where you get your Infos from, bit a short googling would show that this is simply not true.
First off - decoupling from Trump-USA is a must. Canadians noticed
this; european countries are still slow. The Netherlands is faster;
the biggest slow-ass behemoth is Germany - no clue why. Germany is
a big reason why the EU fails, but also the expansionistic agenda
and what not (why do only poor countries want to join the EU;
UK left, Switzerland and Norway are not going to join, so there
are indeed INTERNAL problems, but let's go back to the dependency
on the USA).
So while more alternatives here are the logical answer, as well
as eliminate the greedy US corpoations, I am not sure NixOS as
it is right now is ideal. On paper, NixOS should solve EVERYTHING.
For instance, if a build status works for one user, the environment
guarantee should mean it works for EVERYONE ELSE. Same with other
problems and hardware, so in theory, NixOS should be perfect.
In practice, though, I found working with NixOS annoying, for many
reasons. A static system that has issues, is not good. A static
system that restricts me in problem solving, is not good. Plus,
Nix is ugly to no ends - I have no idea why the NixOS team thought
a new programming language is required. Why do I need to define
static elements in Nix? Why not make that more free form? I already
describe my whole system via yaml files, which in turn ruby uses
to generate everything I need. Then there are smaller issues, like
why do I need to use systemd on NixOS, why can I not used versioned
AppDirs with a name scheme similar to GoboLinux (hashed program
directories on NixOS are, of course, also versioned app-dirs, but
I hate reading 7897389nughuewz789gewh2t93h923-hghwugeiw73, that
simply tells me nothing. Why not have /Programs/Python/3.15.0/ ?
It can't be simpler than that.)
Anyway - good for the Netherlands to push here, Denmark, Sweden,
Finland will also push, even France, though slower. Now please
everyone, help us convince the german government to stop being
such a tool for Trump. Merz is a failure anyway, but the problems
go far deeper than merely Trump, and with the AfD going to seize
power, idiocy will again dominate in Germany. That's very bad.
Germany is soooooooo slow here. Microsoft even managed to kill
LiMux years ago. They have placed their economic hitmen in Germany,
so the whole EU does not work anyway because Germany will keep on
dragging every other country down. It is thus very understandable
why real innovation comes from the smaller countries in the EU, as
they are quicker to innovate. Unfortunately the big german behemoth
will roll over them and again cripple many required things in the
EU.
Europeans are absolutely delusional, but I hope they're serious about dropping Microsoft this time. European governments have been pretending to do this for about 20 years at this point, though.
Microsoft isn't what it used to be. Maybe soon it will be called Microsoft/OpenAI, then OpenAI/Microsoft, then just OpenAI.
It's a bad sign that they chose NixOS instead of something boring like Debian, though (and it seems France, too.) Makes me suspect that this is being driven by a single strong personality who will eventually lose interest or even rugpull support, leaving the project in disarray and a poster child for criticizing doing anything but buying Microsoft as European flakiness. On the other hand, I'm happy that it will involve money being put into NixOS.
Then again the whole court system is so skewed in favour of who has more money.
reply