And more disappointed that distributions especially Debian the "universal operating system" has dropped support for i586 already (and is dropping support for i686)

Open-source doesn't have the same pressures of commercial software from Apple or Microsoft. I really love the idea of obsessive, perfectionism approach of providing indefinite hardware support to obscure old hardware (but especially once-popular old hardware), with adequate automated testing suites to test ancient hardware.

Maybe with agentic AI coding we'll be able to expand support windows, and even bring back hardware support for older hardware.

That may not be the biggest deal, because Ubuntu 25.10 itself is not going to be stable, thanks to switching from GNU coreutils to the uutils Rust rewrite, with Ubuntu 25.10 being a "see what breaks and fix it" canary before the long-term support 26.04 release in 6 months.

The costs of distros and the kernel steadily dropping older x86 support over the last few years never causes an outcry but it's an erosion of what made Linux great. Especially for non-English speaking people in less developed countries.

Open-source maintenance is not a obligation, but it's sad there is not more people pushing to maintain support. Especially for the "universal operating system" Debian which was previously a gold standard in architecture support.

I maintain a relatively popular live Linux distro based on Ubuntu and due to user demand will look into a NetBSD variant to continue support (as suggested in this thread), potentially to support legacy 586 and 686 too.

Though a Debian 13 "Trixie" variant with a custom compiled 686 kernel will be much easier than switching to NetBSD, it appears like NetBSD has more commitment to longer-term arch support.

It would be wonderful to develop systems (eg emulation) to make it practical to support architectures as close to indefinitely as possible.

It does feel like a big end of an era moment for Linux and distros here, with the project following the kind of decision making of big tech companies rather than the ideals of computer enthusiasts.

Right now these deprecation decisions will directly make me spend time working at layers of abstraction I wasn't intending to in order to mitigate the upstream deprecations of the kernels and distros. The reason I have used the kernel and distros like Debian has been to offload that work to the specialist maintainers of the open-source community.

The goal of universal compatibility that separates the Debian project from commercial software and even other open-source projects.

The legacy x86 architecture is still far more popular than some that platforms that Debian advertises as having official support for and there has been x86 based processors manufactured for niche applications until recently, eg, AMD Geode and others.

I find it really unfortunate Debian Project is removing official support for new x86 installations. The silver lining is it seems like they'll be an unofficial port and it's likely niche distributions like MX Linux and AntiX will maintain their own builds.

It would be ideal if open-source can develop stronger mechanims to keep support for the large numbers of these relatively niche architectures (eg, through increased usage of emulation over real hardware).

[1] https://wiki.debian.org/SupportedArchitectures

https://github.com/koreader/koreader

The biggest issue is the web browser doesn't have pagination, ie a next page button. *It only supports smooth scrolling using the touch screen*. Which on an e-ink display is a completely awful, insanely frustrating experience that I can't believe they ship it (and the Scribe is an 11th generation product).

Using a web browser to read pure text is a blurred mess that's takes several painful seconds to slowly scroll to the next page.

Since I bought the Kindle Scribe (big mistake due to the above issue), I've wanted to jailbreak it to install a non-terrible Wikipedia browser.

Eg the one available in the KOReader project -- the open-source alternative eink-optimized ebook app that is widely-supported across the eink ecosystem (including older Kindles).

Thanks for heads up that a jailbreak is finally available!

I wonder if "Drop, Cover, and Hold On" really is good advice for liquefaction zones for a very big earthquake.

[1] https://gis.data.ca.gov/datasets/b70a766a60ad4c0688babdd4749...

It's achieved by "dedicating a slice of T-Mobile's Mid-Band PCS [1.9 GHz] spectrum, to be integrated into Starlink satellites, launched next year", with each Starlink V2 satellite hosting two 5-6 meter long cell-spectrum antennas, in addition to the existing Ka- and Ku-band antennas.

They're aiming for the US with the trial, and growing to global coverage by entering into reciprocal roaming agreements with the international carriers who hold licences to the relevant mid-band spectrum.

Elon Musk says "this won't have the kind of bandwidth that a Starlink terminal would have, but it will enable texting. It will enable images. And if there aren't too many people in the in the cell-zone, you could even potentially have a little bit of video."

Musk claims 2 to 4 megabits per cell-zone, 1000-2000 simultaneous voice calls per cell-zone, with the cell-zone of course being much larger than a terrestrial cell-tower.

[1] https://www.t-mobile.com/news/un-carrier/t-mobile-takes-cove...

[2] https://youtu.be/F8zS2rU-URo?t=325

But far worse is Patreon's messaging platform. Write a long message, then accidentally have a window resize event occur and lose your entire message.

Patreon's problem with losing text has burned me more times than other products with similar issues (like creating a Jira issue).

Some platforms like Slack do a much better job of saving a draft.

Really great crowd-sourced recommendations with useful reviews.

Though while AlternativeTo allows filtering by open-source status, it doesn't do so by license.

The key thing is if one party wants to be able to pass the larger number without that pivotal vote, they need to appeal to a greater fraction of society and win more seats so they don't require that particular vote.

This quirk means that even small states like Wyoming have equal Senate representation as the populous states like California, Texas or New York.

This arguably undemocratic over-representation gives the smaller states much more power in certain areas, but this is by design. It provides incentive to keep large rural states part of a single nation. Compromises like that makes a country as a whole stronger.

Another interesting aspect is US Senate terms are long (6 years), with a third of members up for reelection happening every TWO years. Compared to the House of Representatives which has 4 year terms, and half up for reelection every 2 years. The net effect is it requires several election cycles to have a big impact on the passage of laws. This contributes to stability.

Comments URL: https://news.ycombinator.com/item?id=27385845

Points: 8

# Comments: 4

I'm not associated, I just use it for a personal project and find it great. Not perfect, but still great.

hosted.weblate.org is only free for open-source projects, but it shouldn't be hard to find alternative hosting, or launch a Docker container in the cloud??

To me, it seems like the same story is playing out again.

Pros:

For general project discussion, Sourceforge's traditional discussion forum is far superior to Github/GitLab issues (though I haven't tried Github Discussions beta yet). The forum can be configured for users to be able to post without creating an account (though only as a specific user named "Anonymous", not arbitrary names) which is as important feature when creating software for users who aren't likely to have Github or Sourceforge accounts.

Sourceforge download statistics tracking of releases (including graphing per country and with arbitrary timestamps) is far superior to Github, which doesn't offer even private tracking of download numbers without directly using their API. This is actually a really ridiculous situation.

Cons:

Sourceforge recently added the ability for the project administrator to mark any review as spam, which automatically hides it. This single change has completely ruined the trustworthiness of Sourceforge's reviews, as unscrupulous application authors are able to mark all poor reviews as spam so users only see good reviews. Because of this, I recommend AlternativeTo (http://alternativeto.net/), as they have better review non-interference policy.

Sourceforge's entire website seems to go into maintenance mode for a few minutes every 24 hours, which is frustrating for those in less favorable timezones.

Even after using it for a long time, Sourceforge user-interface and settings/permissions is overly complex, confusing and non-intuitive. I find Github's well designed settings page much easier. Though admittedly Github has its share of UI quirks. New Github users are understandably initially confused by the concept of Pull Requests (which should have been called Merge Requests) and the fork user-interface. As a developer familiar with both tools (and git, PRs etc) I find Github easier to use than Sourceforge, which is saying something.

Many Sourceforge projects tend to have their source code mirrored on a rarely updated Github project, which then gets forked and developed without changes being upstreamed, which causes fragmentation.

Many third-party tools (like CircleCI) tend to target only Github (and to a lesser degree GitLab/Bitbucket) and ignore Sourceforge entirely.

It's too easy for newbie users to download older releases (Github has the same issue unless you create a Github Pages site to highlight the most recent release).

Conclusion:

Sourceforge is actually a reasonable tool to develop open-source software in 2021.

For new projects I would generally suggest sticking with Github and GitLab, but for existing projects on Sourceforge changing hosting to Github may not be required.

The real killer is lack of integration of third-party tools like CircleCI. That's enough to switch to Github. But you will likely miss the excellent download statistics, anonymous support forum and user review system.