6 ms·
Adios Chicos, 25 Years of KDE
- anthk 1y agoEnd of the world? Finisterra in Galicia, Spain? That's in the Northwest past of Spain, facing the Atlantic. As you might guess, the currents and cliffs were so rough that the locals named the place "The end of the world" (Finis Terrae in Latin). On KDE, the best for the project would be an inmutable distro with Flatpak.
- 1oooqooq 1y agowhat you describe is not the best for anything. but sadly is the direction it will go, because people see the dollar signs "when valve buys the license" which will never happen because that ship already sailed.
- anthk 1y agoFor GNU/Linux, Flatpak it might be if GNU promoted a trully FOSS repo; but they already made their own Flatpak with GUIX, and the inmutable distro it's GuixSD itself with Plasma. On 'the ship already sailed', Gnome's performance it's really bad compared to Plasma.
- pabs3 1y agoGNU would never promote Flatpak, because Flathub isn't FOSS-only, and bringing proprietary software vendors into the Linux ecosystem seems like it was one of the goals of Flatpak into the first place.
- WorldPeas 1y agoNot to scaremonger, are we to expect some extent of software rot on KDE because of this change?
- Sammi 1y agoNo. This is one person leaving.
- jpetso 1y agoNo. Jonathan was co-maintaining KDE neon, which now has one developer left and is about to be joined by KDE Linux, another take on a Plasma-based distro. He also handled release manager duties, which have been transferred and running smoothly for a few months now. He may have contributed in other ways that I'm not aware of, but overall KDE is in a very good spot with many more developers working on stuff.
- tvb12 1y agoFor others who might not know, KDE Neon is a distribution. I was initially confused because I thought it might have been an alternative desktop environment to KDE Plasma. This is probably the greatest curse and blessing of modern Linux: there are an impractical number of distributions. I guess you could probably say the same thing for desktop environments, various services, bootloaders, etc.
- The_President 1y agoKDE has done a great job keeping up a good desktop environment. They need to be careful not to let developers determine resource usage, as we got ksysguard replaced with an inferior System Monitor this way.
- The_President 1y agoFor example, I just had to "race a memory leak" from the UI and the only resource available (in UI) was System Monitor. Unfortunately the memory leak won, and System Monitor never launched after 20 seconds, the system finally froze (during a system update), and now it's borked.
- bigyabai 1y ago> But in the end I lost my friends, my colleagues, my job, my career and my family. What’s a spod who just tried to do the right thing for society to do? I don't see enough people reflecting on this, much less in the open source community. Props to the author for being so honest about it. HN has a culture that is very eager to promote passionate computing, and I still consider that good thing. At the same time though, we put an immense amount of faith in technology, that "fixing" a problem in code or hardware will make it go away. It's a great religion for motivated tech workers, but also still a passionate lie. There are so many extenuating things that determine success and define your problem space, it becomes almost wasteful to sacrifice your personal wellbeing to "fix" a problem and renew your faith in technology. This happens everywhere, in startups and open source projects alike. Take care of yourselves, people.
- zevon 1y agoOof. I've had the experience of ex-colleagues, some of whom I thought had become friends, suddenly stopping all communication with me (In my case because I spoke up against mental and physical abuse against others). It hurt a lot. Hope surfing the wave helps.
- ____tom____ 1y agoI would encourage you to reach out the the friends you have worked with. Currently, this other person is controlling the narrative, and your friends may have been fed a very inaccurate view of what has happened.
- WorldPeas 1y agoprev: https://news.ycombinator.com/item?id=45252463 https://news.ycombinator.com/item?id=45252463
- dang 1y agoAh thanks! we've merged that thread hither.
- nomdep 1y agoThis story need some context. Who are Nate and Dave? Why the deal with Steam went automatically to Nate? UPDATE: Apparently it was a deal done months ago with the Blue Systems owner: https://pointieststick.com/2025/03/10/personal-and-professional-updates-announcing-techpaladin-software/ https://pointieststick.com/2025/03/10/personal-and-professio...
- rurban 1y agoShit move by Nate, but Jonathan did the right thing.
- logicchains 1y agoNate sounds like the kind of person to lie to your former colleagues about you; I'd suggest reaching out to them to tell them what happened. Staying silent is letting Nate win.
- nomdep 1y agoThe other side of the story: https://news.ycombinator.com/item?id=45266332 https://news.ycombinator.com/item?id=45266332
- raverbashing 1y agoHonestly, it seems some very technically minded people are very naive and very unprepared in regards to practical and legal aspects of life elsewhere. While building a career over such a project like KDE is certainly laudable it seems it leaves people in a very precarious position where the number of companies worldwide where you can be employed at any given time can be counted with the fingers in one hand, with some to spare
- sho_hn 1y ago> While building a career over such a project like KDE is certainly laudable it seems it leaves people in a very precarious position where the number of companies worldwide where you can be employed at any given time can be counted with the fingers in one hand, with some to spare Your average KDE contributor is an expert in at least two widely used technologies, C++ and Qt, and typically in several more. Purely KDE-related work may not be a huge employment market, but trust me it's not that hard for KDE folks to find work in general, and you will find them in many high places. That is to say that contributing is definitely not putting you into any precarious career positions :-)
- raverbashing 1y agoAgreed from the technical point of view But it seems most members of the community keep looking for jobs within the community and forget to look elsewhere
- billyjobob 1y agoDoesn’t sound like we have the full story from either side. This blog post from Nate reads like he is continuing to gaslight. But then Jonathan doesn’t explain why he didn’t just buy into the partnership like the other 2 did if he wanted to be a co-owner.
- probablypower 1y ago[flagged]
- bluedino 1y ago> It was the turn of the millenium when I got my first computer fresh at university. Windows seemed uninteresting, it was impossible to work out how it worked or write programs for it. What? There were plenty of books out by Petzold, Richter and Prosise.
- projektfu 1y agoThese are well-renowned books but I agree that it was hard to get started writing windows software. Win16 and Win32 were very strange APIs with a mixture of having to do things yourself, having the OS do it for you, and the OS calling you at unexpected times to get things done. WndProcs were re-entrant, because while you are handling WM_MOUSE you could get called by the OS to do a WM_PAINT. The whole architecture lends itself to spaghetti. Or, you could use MFC, and then you just had to trust the library to do things right. Debugging your code wasn't easy because it would get lost in things that MFC was doing that you don't fully understand. A lot of the source code was available, however. Or, you could use WTL, which was a third party library at the time that gave you a different way of doing it. Debugging into/through Windows itself was really difficult due to the lack of source code. All you had were symbols and assembly. Because of how it worked, you could easily find memory corruption in your program because of some boneheaded thing you did, but finding the cause of it was hard because of its highly non-sequential nature. Qt had a nicer approach with signals and slots, and used a more object-oriented way of building the software. Software was easier to understand. It also worked on Windows, but IIRC that part wasn't free. It is a long time since the late 90s so I am not sure about my memory. I enjoyed using Qt, though, and found it to be a much better programming model than straight Win32 or MFC. KDE was a great little system circa 2000, and it introduced the Konqueror browser that gave us the future we have today. Anyhow, that is a lot to say that I understand how an intelligent person could read Petzold and still feel like a dummy. Writing Windows software in the late 90s/early 2000s was often humbling and there wasn't as much support from things like StackOverflow and the rest at the time.
- Saaster 1y agoIt’s commendable to want to start a “cooperative socialist paradise”, you can pitch it and see if there’s interest with others. But it’s totally OK as well for others to not want to join that, and go the more conventional way. It sounds like Nate is set on starting a conventional company, and that should be fine. The previous company apparently never made financial sense so it also doesn’t work to just continue that model directly and so things and people get cut. It can be both hard to communicate and to hear, doubly so when you’re emotionally invested. That’s why IMO it’s important to separate your self worth from your job at some level, for your own mental wellbeing.
- justin66 1y agoWhat is he even talking about here? We never had workers rights at Blue Systems, we were all on self employment contracts. This will continue at Tech Paladin. It is illegal but unenforceable when done on an international setup. But employment rights are not a luxury you can chose to do without if you enjoy your job and want some more flexibility in your work day. They are fundamental and life altering rights that change people’s lives as I discovered when my adopted children were taken away from me. Nobody should be doing business with or taking money from Tech Paladin else be party to illegal workers rights abuses.
- jkaplowitz 1y agoIt’s very common in the tech world to have a relationship between companies and international remote workers which legally meets the definition of employment in one or both countries but which pretends in the contract wording to be an independent contracting relationship. A lot of companies decide that the risk of getting caught in this deception and the penalties which would be imposed in that case are lower than the hassle, expense, and uncertainty of doing things the legal way; while some truly don’t even realize that it is in fact a deception. And there’s very little legal risk for the employee aside from the loss of rights and benefits they should be entitled to and legally unwarranted extra financial burdens on their part, so they often bow to macroeconomic factors and accept what sources of income they can find. Independent contracting can of course be fully legitimate if the substance of the relationship is arranged to match what the law understands independent contracting to mean. Maybe Nate’s legal advisors correctly concluded that the arrangement he’s implementing falls in this category. Maybe. But when the substance of the relationship is employment and only the legalese and payroll look like contracting, then what’s actually happening is the employer is dodging a lot of mandatory contributions to the employee’s local social security systems (such as pension and healthcare) and a lot of the mandatory employment protections applicable in that jurisdiction. This also pushes some or all of the mandatory contributions and benefits which legally should be the employer’s financial responsibility onto the misclassified employee, and usually without a sufficiently compensatory increase in contracting rate vs the amount they’d be paying in salary if it were correctly handled as employment. (The illegal contracting rate in an international context might still very well be above legal local employment salaries. But I’m instead comparing to what the salary would be if the exact same working relationship were handled according to the law, such as the same employer might often offer to employees in their headquarters jurisdiction.) The employee can make a huge mess for the employer if they ever report the misclassification to the authorities with adequate proof of the true nature of the relationship, because misclassifying an employee as an independent contractor is illegal. The employer will often be audited and required to pay unpaid social contributions going back years. Sometimes the employee can also recover contributions they paid which should never have been their responsibility according to the law. But most don’t want to risk informal blacklisting from the industry or even the stress of engaging in that complaint process in the first place.
- nycticorax 1y agoSo, first off, it seems like Jonathan Riddell not working on KDE anymore is a huge loss for the KDE community. But I'm not sure I really understand what happened. AFAICT, Valve had a contract with Blue Systems, specifically a subunit of Blue Systems that does KDE development. Blue Systems decided to sell that subunit to Techpaladin, Nate Graham's company. Riddell was unhappy about this, and proposed that... I guess that Blue Systems not sell to Techpaladin? Or that Techpaladin reorganize itself into a worker-owned company? And then when Graham declined to do this, stuff happened, and eventually Riddell got fired from Techpaladin, or not hired by Techpaladin, and now Riddell is not getting paid to work on KDE. So Riddell has (not unreasonably) decided to stop working on KDE. And the other people who once worked for Blue Systems and now work for Techpaladin have decided to keep working for Techpaladin. Am I missing something? Being unfair to someone?
- chao- 1y agoThis is my takeaway as well. Having brushed up against a few things like this, I assume there is more back-and-forth about reorganizing Tech Paladin than what is published. However, I am certainly not suggesting an escalatory exposé of communications, as it likely does nothing to change the two bottom line facts: Riddell was not included in the new company, possibly over their disagreement regarding company structure, but this isn't something we could know for certain. Following that, Riddell decided to end contributions to KDE. EDIT: Updated to reflect details from https://pointieststick.com/2025/09/16/a-few-corrections-about-the-transition-from-blue-systems-to-techpaladin/ https://pointieststick.com/2025/09/16/a-few-corrections-abou... reflecting that "...at no point was [Nate Graham] or Techpaladin ever Jonathan’s employer."
- jajuuka 1y agoI got distracted by the Quaker thing and went down a rabbit hole. But overall Jonathan seems like a decent person and major loss to KDE. Only thing I'm confused about is why he got shunned and I guess he had issues with his family too. Just about anything could explain that so I feel like that's a critical piece here but I'm not looking to violate anyones privacy or force them to divulge such information. Just something that could explain where Jonathan is coming from in all this. I read Nate's response and it seems very hand wavy. Regardless hope Jonathan can continue doing what he loves somewhere else.
- sombragris 1y ago> But in the end I lost my friends, my colleagues, my job, my career and my family. As a Plasma user and a part of a KDE team for 10 years at some time (in the past), reading this really breaks my heart. I hope Jonathan can find peace and healing.