in my mind Swift is a much better language to include than rust, unfortunately the support for Swift on Linux is so bad currently that it's not worth exploring.
If ever integrated Swift might change the whole paradigm
Linux is one of the most complicated OS in the history of OS and both of them understand this in someway or the other, it's still not cracked enough market share to dominate the personal computer market even in 2025, but is already on millions of other devices except PCs and a small change in decision like r4l brings the whole perspective into matter, after the fact that rust is highly compute intensive language and low end processors might not be able to catchup the speed in the best possible way these industries work, memory is cheap to include and hence the decision to include Python was a comparatively easy one, but rust is a highly balanced choice currently which makes the decision more difficult for Linux to include R4L in kernel, hence the dissolution on parts in which to include.
This is based on my limited experience with rust, but I believe we really need to give rust more time to mature it enough to see where we're going with the builds to actually decide on this matter, even personally. Plus, Linux has been keeping the Linux Kernel project alive for so long that he probably already has got the experience of knowing the repercussions of a wrong decision. Being hasty in this scenario doesn't solve the problem
rust utilizes various methods at compile time which significantly increases compute, such as compiler is optimised for memory safety, which causes it do a lot of tasks and changes at compile time unlike C and inturn during execution to ensure ms, which could easily be avoided, it is good for overflow situations but in terms of compute required in exchange for the program is simply(currently) not at the level that would be great to have in Linux kernel, in a few years maybe
Exactly my point in terms of the chipsets, and the limited acceleration in capacity of evolution per year for small chip manufacturing companies unlike mediatek and qualcomm, furthered by silicon shortage and many other manufacturing facts, including a language like Rust at this stage should be subject to observation.
Few things have changed since posting here, I've implemented markdown support on comments and in each item, but comments are currently only on the first level of comment tree.
I'll try porting on them, TUI Browsers are amazing, but React Native is very restrictive in the platform and architecture it utilizes. That's why it has not been my first choice, there are dependencies just stacked over each other like jenga blocks, waiting to crash. It's really not a way to build a future proof software.
But who cares? as long as it's fast right?
Technically anything with a webview should load the site, so maybe some polyfills could do the job.
**This is some bold text!**
This is normal text
> Those who have paid even passing attention to modern productivity software will recognize the language and aim of Agenda, a project from more than 30 years ago, and therefore the broad endeavor of saving time, breaking silos, and endlessly iterating on what essentially amounts to the same few products, over and over, decade after decade.
Despite the posted title, this article is really about productivity apps and the people who use them. For each new app, they hope that this one will finally be the one that magically makes them "productive" where all the previous ones have failed. It then goes on to speculate on why they would do so and subsequently veers off into tangents on bullshit jobs, the role of middle managers in startups and (through a somewhat tortured metaphor of gaming as self-actualization) the role of leisure in the modern economy.
Fun article but not really about product hunt after the first few paragraphs.
1] https://play.google.com/store/apps/details?id=dev.hemanths.p...
2] https://paisa-tracker.app/
reply