cdud3

Exactly. That's why there are in maximum benchmarks of current WSL comparing to older WSL releases just like in the announcement.

While every few weeks we read about "some more factors performance improvements is being worked on" we know how the current state looks like. Let's wait till we are talking about single digit percentage of improvements being worked on and newsworthy.

and yet they have solutions in place to work around all that to do all sorts of things with all there customers data without any customers knowledge because for example law enforcement agencies may demand that for one of there customers one day...

Fact is if you put it in the cloud you lost control. Data, services and integrity is gone. Uploading your stuff to Pirate Bay may actually be more secure because downloading it is maybe illegal :-)

And yet it's still factors faster without a whole Windows around it.

With specialized agents it could be as simple as "Upgrade your current used generic model to the better one specialized better on your tasks for only $10" rather then today's "we ship everything in one model no matter what you really need so you need our cloud subscription" approach.

If jokes are hate speech, then my life is a human rights violation.

We had an own good-releases directory in our svn repository! That's when you realize old habits are hard to change.

The easiest way is to actually review the prompt input, put it through a LLM to catch the typical missing steps and automatically forward the result as review comment to the MR.

Let the LLM wars start!

> You can make your own numbers look incredible while reducing the throughput of the entire team.

Taken how some companies award promotions and bonus this is actually a double win. You not only improve your own numbers but also make this of your competition worse! /s

The JavaScript interpreter is shared too since the Plasma Weather app is loaded as a shared library plugin into the Plasma process and uses the functionality already loaded and present in RAM. The same concept is used with background services which run in the kded process. There is no need to have a set of full web browser processes per service.

Correct.

The KDE Plasma weather app takes in maximum 1MB.

You don't. This days run your C/C++ code through AI and fix the issues it found. That gives you more in shorter time.

I prefer to have such detailed readme's created by a LLM while iterating over no iteration documentation at all and usually the later is the standard.

Because that's the only argument left after Kimi beats Fabel in results, price and autonomy.

Because Android was the door to there services. That's very much the same situation we have with model creation right now. China understood it, they act on it and as a result they are winning.

A lot of this companies are also in parallel evaluating running Chinese models inhouse to be independent of the good will and profit margins of externals.

This is where Oracles "datacenters for rent to run your own Chinese models" strategy will benefit. The LLM SaaS game is a lost one thanks to China.

To add to that: Elop announced the end of N9 weeks before it's release and more then a year before the first Lumina was available. Dead on arrival not even shipped in major markets. Yet the N9 was years ahead any competition of that time.

That and like crazy increasing burocracy.

Because this companies defined the goal to replace humans with AI what didn't happen. What happened is that the humans can work faster and have more coffee breaks while the AI iterates for the next review and iteration round by that human.

The AI bros industry needs to keep the impression that employees can be replaced with something more cheap since otherwise where will all the money come from that is burned right now?

The biggest advantage systems has is also it's biggest disadvantage: the amount of functionality. Even with lot of functionality being optional this days, dlopened at runtime if present, it's still bigger then a simple shell script or.tpur own 20 lines of C-code. The later may, in some cases like running anyways only one app in full screen, more then enough. In some embedded setups you may not even need that but just run your app as pid 1 and be fine.

A lot of the monetarization strategies for LMM's depend on the need to use them via SaaS subscriptions. If companies start to realize that local AI is cheaper, provides good enough results and makes them independent then that monetarization strategy falls apart and a whole industry collapses.

That's a npm supply chain attack style but next level for the Enterprise game: hack one and get access to everything of all of them since they are all unrestricted connected and with each other.

And then they force us to install cloudstrike, antiviruses and client side monitoring because "us are the security problem".

Or use QtWebEngine which uses Chromium under the hood, provides a stable and rich API and enables sharing rather then bundling the browser runtime + is Cross-Platform + security updates are handled too.

That will not help catching up to DeepSeek.

Depends on if this are really zero days or only to the public known zero days.

Putting it out from "only a small group of people/companies exploit it" to the public is the way how you get it fixed. In this case it seems that was the only way that was left after Microsoft refuses cooperation. What counts are the results: This are fixed now.

dictatorships are not there main customers. There are many, also western, governments and their agencies customers of such services.

Why not ignore unused variables in debug and warn in release mode?