Hacker Newsnew | past | comments | ask | show | jobs | submit | blinkingled's commentslogin

Total KDE fan and that's all I run at home. It's an interesting study also in desktop environment and software written in C++ and just how hard it is to get something that works for most people. Mistakes, corrections, building the basic blocks like Qt in the early days and keeping a bunch of people with differing cultures / tastes / backgrounds/needs motivated to make it better every day - fascinating achievement.

Thank you KDE folks - I contribute in terms of bug reports and attempts at fixes sometimes but this time I am signing up for a monthly donation - I encourage people to do what they can to keep a good thing going! https://kde.org/donate/


Agreed. I'm a late-comer to KDE, having used Linux for over 20 years but only switched to KDE in the past year. Too many annoying design decisions in GNOME and I got sick of wasting time configuring the trendy minimalist WMs. I find KDE to be a breath of fresh air. It's got sensible defaults, gets out of my way for the most part, and it's improved a lot since I last tried it in the mid-2000s.

Im a KDE user since the early Plasma 5 days, which is now more than a decade ago. It's awesome, usable, configurable, sleek and fun!

A week ago I bought a cheap mini-htpc and put Plasma Bigscreen on it, using a phone with KDEconnect as remote. So easy to use! So much better than AndroidTV let alone proprietary crap.

KDE is just great.


KDE connect for me is honestly the killer app in the whole ecosystem. In general at this point I'm less excited about the desktop itself because I've always lived in Emacs or the browser and most desktops more or less work these days, but the support system KDE has built around makes it stand out to me.

Connect, KdenLive, Krita, KFind and a whole bunch of other stuff is very useful.


> "KDE connect for me is honestly the killer app in the whole ecosystem"

Does KDE Connect cover some of the usefulness of Tailscale?


No, because Tailscale unfortunately does not implement multicast/mDNS/Bonjour required for KDEconnect: https://github.com/tailscale/tailscale/issues/1013

I also use KDE daily and need to add it to my yearly donations list (alongside FreeBSD, Signal, Bottles, and a few others).

Yeah, additionally anyone at Microsoft that keeps throwing out half usable COM frameworks for C++ should spend some time with KParts, KIO and Qt D-Bus bindings, maybe they would finally learn how to properly design one.

I asked it to implement the simplest todo in ghostty codebase and it failed badly - kept going in circles fixing one compile error and introducing another. Qwen 3.8 was slower (40 tok/s compared to 75) but did get it done.


> Qwen 3.8 was slower

Is that Qwen 3.8 27B? Because yes, you'd expect a plain 27B model to be better than a 24B-A2B MoE model all else being equal.

(All else isn't equal though of course - Qwen models are very, very good at coding)

Gemma-4 26BA4B would be a more similar comparison.


Yes 27B - not so much of a surprise but I was hoping for a usable coding model that's local and fast - this is fast but maybe not usable. I used Gemma4 26B before and it wasn't good in my testing.


That's not surprising. Even Liquid's own documentation states that coding isn't this model's strong suit. Its strength lies in tool calling.


Have you tried Gemma-4 26BA4B? I feel like it is underrated for tasks like that, but maybe I've just been lucky with my use cases.


in my experience it's stronger for terminal use, like chaining bash calls, monitoring background tasks, etc. rather than for straight up coding/swe work. Good with web search and file search rather than just editing software.


It's great to hear about $topic from someone no-nonsense and in-the-know like Greg KH. You can verify all of this too - since, well Linux kernel. (As opposed to what Microsoft or Apple claims to fix as far as LLM finds.)

Mythos may not be great today but it is not far fetched to imagine bug discovery, analysis and fixes can be made much quicker, accurate and even newly possible with specialized models trained on say Linux kernel specifics - with codemap/coding standards/threat models, good and bad coding patterns, tools to validate etc. an LLM can be much more relentless than humans and if it has the help to be accurate it will be worth the electricity burned. Oh and another model trained on triage data to validate the first one's findings would be good.

(I think Microsoft is doing this internally - different models trained internally alongside Mythos - there was some talk about it on the tubes, don't recall where exactly.)


> Mythos may not be great today but it is not far fetched to imagine...

I...

Look. Mythos was hyped up as the absolute best bug hunting tool ever made... no software was safe from its awesome bug-finding and exploit-writing capabilities. So strong was it that access _had_ to be limited to a select few pre-vetted entities, lest these awesome capabilities fall into the hands of Evildoers(!!!). Mythos' claimed capabilities were absolutely an important part of the "The LLM-based tools we're building are so dangerous that we must have new laws made to regulate us, or else all of humanity is likely to die!" story that the major LLM manufacturers have been building for a while and are telling now.

Now? Not even six months after release? "Well, yeah, okay, it's actually not that great. But imagine how great the next one could be!"... which is the story I've been hearing roughly every six months for what feels like five years now.

As an aside: I often wish we lived in a world where it was illegal for companies to use hype or any other types of emotional manipulation when advertising (or otherwise speaking in an official capacity) about tools that are to be used in a professional setting. Is it anything other than a bare statement of verifiable facts? Big fines, and repeat offenders get jail time. I know it's never going to happen, but it sure would be nice.


Every 6 months without exception people claim that the new generation of tools is absolutely incredible, and the old ones were total garbage, and that you only think they're crap if you were using the old tools. This just gets repeatedly memory holed again and again, and we're expected to always uncritically buy into the idea that they're actually good now against all evidence from the real world


Just for the 'record' - I am totally with you on the hype and just in general the normalization of sleazy behavior surrounding it but I'm not sure we as normal people have any say anymore including where our money is going to be invested.


> I'm not sure we as normal people have any say anymore [in regards to] where our money is going to be invested.

Unless that was your money being invested, and it was a substantial fraction of the total pool of money being invested, was there ever a time when "normal people" had a real say in where the money was being invested?

AFAIK, the only thing "normal people" can do is vote with their "feet" and pick a different prepackaged investment product, different investment company, or take their money and do the investment themselves.

Honestly, this comment of yours seems a non-sequitur and doesn't really address anything I said... you don't have the power to bend investment firms to your whim, but that doesn't mean that you need to -knowingly or not- carry water for the major LLM manufactures by perpetuating the "But think of how great the tools will be in the future!" meme. It has been years now, and everyone who has been paying attention can say with confidence that the LLM-based tools of the future are never that great... they're often not useless, but they're not worth the billions of dollars that have been and continue to be poured into their manufacture.

Related to your "We little people don't have any power anymore!" commentary, I note that TFA mentions that the kernel community has found that these LLM-based bug-finding tools have a false positive rate of ~50%. TFA goes on to mention that Coverity spent a huge number of years trying so hard to get people to buy its automated scanning software that had only a 20% false positive rate, and could not get enough people to buy the software.

Coverity went under because everyone hated how stupid and annoying the tooling was... at a 20% false positive rate. Once the hype machine starts slowing down, no one working at the coal face is going to buy a tool with a 50% false-positive rate. I personally very strongly believe that even if the tools had a 10% false positive rate, no one would pay the actual price that OpenAI and/or Anthropic would have to charge to recoup the research and manufacturing costs of a cutting-edge LLM-based bug-finding tool.


Even after acknowledging that LLMs are fuzzy matchers and have been hyped, I am in the camp that rationally believes they will get better at some things including hunting bugs / chasing security vulnerabilities - my point also is that you and me can do whatever we can but on the grand societal scale we are not going to make a difference as far as slowing LLM adoption down - it just makes sense for some things and there's a lot of people with time and money that will make it do the rest - that's how it works until everything is saturated in the market.

So no I have no way to address anything you said - that was the point, I don't believe you can - not with regulation and not with voting with your money (I am sure some people tried to vote with their money to slow down mega stores and keep the mom and pop shop alive - there maybe some of those still there, but largely it's big chains occupying most of the market) - that stuff hasn't worked - heck LLMs work better today that that stuff has ever.


> So no I have no way to address anything you said...

No, you do.

1) Refuse to spread the "Well, okay, the tools aren't good now, but imagine how good they could be in the future!" meme. And -because these tools are SAAS and the resources allocated to them can be adjusted at any time without warning- evaluate the tools soberly and dispassionately three to six months after release, and ignore 100% of what the manufacturer claims the tools do.

2) Remind people that the major LLM manufacturers have pretty much never not lied about the capabilities of the tools that they produce and sell. Remind folks that the rational thing to do is to ignore the claims of both the manufacturers and boosters and -given that the tools are deliberately designed to aggressively flatter [0] the operator- to evaluate one's interactions with these tools with a huge serving of skepticism.

I get that you feel like there's nothing you can do to change things. But -as I've repeatedly said- you can stop carrying water for these companies by repeating their propaganda.

Assuming that the regulatory-capture and retroactive-immunity [1] gambit the major LLM manufacturers are currently attempting fails, when the fucknormously huge bill for the tools and the fact that so many GPUs are sitting in storage become public knowledge, things will sort themselves out pretty quickly. I'm fairly certain that continued progression of the -IDK- ten or twenty+ lawsuits against the major LLM manufacturers for the crimes they've committed over the years will help push that process along.

[0] ...I think kids these days call this "glazing"...

[1] ...don't believe that Congress would retroactively make obviously illegal conduct legal thereby mooting all in-progress lawsuits seeking justice for that obviously illegal conduct? Go read up on the FISA Amendments Act of 2008.


Don't lower yourself like this. The people working on this are "normal people" too. Don't put them on a pedestal. That's part of the problem here: lionizing people who are actively lying to others to protect their bags and reputation. Stop acting like a pawn for these people. Buying into their delusions of grandeur is what's perpetuating this mess. LLMs are a tool, not a monolith.


I am not lowering myself or lionizing anyone - I am being practical about this. If we as a society have a workable stance for/against LLMs that is beneficial to all of us I am very open to hearing about it - It would however be fair to say that I am pessimistic given a lot of our collective history. And on oop of that nobody seems to be talking about any real solutions either this time around. Just being dismissive or being all-in are equally bad approaches.


> ...nobody seems to be talking about any real solutions...

I guess you didn't bother to watch the video that is TFA. Greg K-H mentions that if you're going to use LLMs to do bug-finding, you should use open-weights models that run locally and "harnesses" built by members of the community You really should watch the video to hear his reasons for why.

There's nothing wrong with LLM-the-technology. There's everything wrong with the major LLM manufacturers.


I wasn't talking about fixing the tools or using open weight models - I don't need to watch anything to know that's an option. You are also now contradicting your earlier stance somewhat by saying what I was saying - LLMs can and will get better - you have now introduced an irrelevant open vs close element which doesn't really matter. There's no way only open weight models and harnesses get better - if you understand even a little, proprietary models with access to same open information but with billions to burn on research and hardware will get better faster.


> You are also now contradicting your earlier stance somewhat...

Not even a little bit, no. Go back and read carefully. [0][1][2][3]

[0] <https://news.ycombinator.com/item?id=49943382>

[1] <https://news.ycombinator.com/item?id=49944036>

[2] <https://news.ycombinator.com/item?id=49951289>

[3] <https://news.ycombinator.com/item?id=49951466>


Ugh stop posting links dude - answer what do you mean by your previous claim for fixing everything you were complaining about earlier - "you should use open-weights models that run locally and "harnesses" built by members of the community" - like how is that not contradicting what you are saying - if open weights and local harnesses can do it Anthropic and OpenAI will do it faster and better. That doesn't make sense at all in this conversation.


> ...like how is that not contradicting what you are saying...

A careful and honest reader notes that I've never claimed or suggested that there exists a software project that will never get better with enough time and appropriately-focused effort.

But, the single thing in this thread that statement by GK-H addresses is your claim [0] that

  ...nobody seems to be talking about any real [alternatives to using LLMs provided by the major LLM manufacturers]...
Of the things I've talked about in this thread, that's the least important one. However, I do understand that it is the easiest one for you to talk about while still staying vaguely "on message".

[0] <https://news.ycombinator.com/item?id=49948725>


His presentation style may be no-nonsense, but the content is brimming with nonsense. I would like to hear Greg Kroah-Hartman explain how the Mythos output was 'only 10 real bugs' but there were simultaneously over 1300 CVEs issued last month. It seems not much counts as a 'real bug' when an LLM comes up with it, but when it's time to bully distros into shipping an LTS release, anything goes?


What he means is that the headline-grabbing mythos output amounted to 10 actual bugs out of 79^H6 (and all of those got CVEs because that's how linux does it). The other 1300 CVEs came from other sources (the big increase likely being everyone else running LLMs through the codebase and filtering through the false positives). The Mythos output is mainly meant as an example of how even the top-tier models still have a high false-positive rate and that can be pretty tiring to deal with.

I do think he repeats some myths in the video, or at least confidently states some things that are not demonstrated to be true, but his core point of 'you still gotta check these things' seems pretty solid.


> he repeats some myths in the video, or at least confidently states some things that are not demonstrated to be true

I am genuinely curious what the myths/unproven things he states - I watched the video and it's repetitive sure but not much felt controversial to me.


Every bugfix is assigned a CVE.

"the CVE assignment team is overly cautious and assign CVE numbers to any bugfix that they identify. This explains the seemingly large number of CVEs that are issued by the Linux kernel team."

https://docs.kernel.org/process/cve.html


Fair point, but he was talking about Mythos in particular and the point wasn't so much that LLMs will always have false positives rather he was saying they are causing a lot of them right now and how to deal with it.

Also as other replies said Linux kernel process is to assign CVE to everything - some of them may be just DDOSes, very hard to exploit and everything in between. All of them are bugs so they all get fixed and it's not a bad thing if distros ship those fixes and people update their kernel.


> this work is focused on laptops with Snapdragon X2 Series. It does not currently cover desktop form factors, earlier Snapdragon X platforms, or other development boards. Readiness also varies by OEM design and Snapdragon X2 Series variant.

So same ARM BS as usual - AMD and Intel x64 are still the kings when it comes to out the door Linux support.

I'll buy a ARM PC when I can swap its motherboard CPU and GPU to a newer gen and my existing Linux install boots up without having to flash a new bootloader and custom vendor kernel with proprietary GPU blob.


"I'll buy a ARM PC when I can swap its motherboard CPU and GPU to a newer gen and my existing Linux install boots up without having to flash a new bootloader and custom vendor kernel with proprietary GPU blob."

add in swappable batteries like older laptops and phones, and I would as well. not now though.


Makes me wonder how long until Framework starts shipping ARM-based motherboards. They already sell a RISC-V-based motherboard for the 13.


As a KDE Connect user for a few years I know it doesn't always work without reconnecting especially with sleep cycles on the phone and the laptop but it does everything on Android at least - clipboard sync, notifications, sms, calls, remote control and media playback control. Must be iOS restrictions that made the author go through the admirable effort.

IOW Linux ecosystem has better vertical integration without any direct ties with Android :)


Does KDE connect work with other, non KDE window managers?


Yes, and it's great. But you can't iMessage / SMS or get Notifications with iPhone.


My absolute favorite feature in KDE Connection is full audio device output / input control remotely so I can silence notifications without getting up or start playing music through the speakers.


It even works on Windows.


yes, there's even a GNOME shell extension[0] that implements the KDE Connect protocol without needing the official KDE version.

[0]: https://github.com/GSConnect/gnome-shell-extension-gsconnect


Writing linkers must be incredibly rewarding - go has its own, there's mold, there's LLD, there's the OG GNU bfd LD and now Zig has one too! I am sure there's a Rust one too - Wild!

Every one of them is faster than the others too lol! Mold for one tries really hard to be GNU ld and to be useful as an independent linker most have to - I guess Zig/Go ones are purpose built so at least those don't duplicate GNU ld compatibility.


Wait till you hear how many programming languages there are


Sure, but one might imagine that linkers are generic and reusable, so you can just pick one off the shelf instead of making a new one 1-1 for each language. Empirically this line of reasoning seems to be incorrect.


Different programming languages are very obviously not the same thing - different cp command implementations are similar conceptually to having different linker implementations that all do the same thing. But you knew that so not sure if there was a point you were trying to make there.


> Different programming languages are very obviously not the same thing

It isn't obvious to me at all. The difference between Java, C# and Go is about as important as the difference between Makita and Bosch for power tools. Yes, some people swear by one or the other, but by the end of the day it really doesn't matter


Now they only need to make sure that a supply chain for replacement batteries exists, there is regulation and competition and options remain available for a reasonable price.

There are plenty of old Dell and HP laptops with replaceable batteries which can only be found on eBay or some random seller that does who knows what under the refurbishing process.


Exactly. I had phones and laptops with replaceable batteries in the past. I liked the idea of it, but in practice there was no OEM-quality replacement available by the time I wanted one. The device would have been usable to me still, but not with a random black market battery that may well be a fire hazard.

Having thought about this long term, I think the only solution to this would be mandating standardized battery cells. Rather than every phone model having a bespoke cell that is manufactured once and then obsoleted, they need to have standardized shape and electrical characteristics so that batteries being produced for new phones would also be useful to rehabilitate old phones.


I expect we'll see a spike in cell phone battery fires starting about a year after this goes into effect. Same deal as cheap external battery-powered travel power banks, which are already a problem.


> Now they only need to make sure that a supply chain for replacement batteries exists, there is regulation and competition and options remain available for a reasonable price.

No, they won't do the hard part. Just the minimum plus a ton of PR and back patting then move on.


I am a full time KDE/Arch user and since Plasma 6 haven't had any HiDPI issues including monitors with different DPI or X11 apps - of which there are very few nowadays.


Fedora 43 with KDE - have been using 140% scaling with my Dell Ultrasharp 32" 4k monitor - no issues whatsoever. I've noticed that the Dells do a pretty good job with Linux - I have used monitors of various sizes ranging from 27" to 43" and never had any issues on Linux.


I run plasma 6 on X11 and it also functions amazingly well on 200% scaling.


> Tesla’s fix will involve an additional redundancy to keep the lightbar affixed to the windshield, should the glue fail.

Good news - it only affects 6000 vehicles with the optional lightbar which is dealer installed. Bad news - Tesla finds it ok to let its dealers do glued lightbar installations and can't really fix the glue failing part so they are adding redundancy.


Stopped reading at proprietary. Seriously why would I care tying my app to something proprietary and have no way out of it?


What makes you think you can download it and use it yourself? This is just CloudFlare discussing their internal tech stack.


I meant the I have no interest in knowing anything about any company's internal tech stack and also no interest in tying my application to one company's internal stack. Much of it sounded like lock-in to me.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: