But apart from given what I've seen from my experience with handling maildir, actually implementing mail sync, storage, and all the other things associated with mail AND calendar, it sounds risky to use a project this young.
8,589 karma · joined April 16, 2012
But apart from given what I've seen from my experience with handling maildir, actually implementing mail sync, storage, and all the other things associated with mail AND calendar, it sounds risky to use a project this young.
For people that want a terminal client with tabs, integrated html viewer(including images), markdown compose, MCP, with unified inbox, I built notmutt.
It's funny how the US is amazing because it takes the worlds research, but China is horrible because it steals IP from companies it invests in.
Whatever, even if you ignore the company IP side of things, 8 out of 10 top 5G research Universities are Chinese now.
Not long ago I remember reading that Britain was complaining about how Germany was creating counterfeit items with british labels and that Made in Germany back then was something imposed on them to deal with this situation. It was some sort of Trade conference in Europe in the 19th century I believe, but I cannot find that book anymore.
To the people that say "why can't Huawei make a 5G phone". Huawei was manufacturing their chips with 5G modems at TSMC until the US went after them trying to turn them into HTC or Alstom Energy, but it failed. It's one of the reasons why Taiwan now has zero leverage as the US has been hollowing them out since the last administration. But Huawei have been building their own domestically produced modems for a few years now.
I used to attend the communication network meetups with all the professors in Germany and mI think all of them agree that all that energy sanctioning China should have been spent on actual competition domestically in the West.
The goal is to have a very fast terminal mail client where you don't have to wait for any operations and that is tightly integrated with notmuch(a common mail full text search engine) tagging engine, and other workflows(like crm queues and ai summary's if enabled in the config).
There is a document that explains why it was made in go. It has the best notmutt cgo bindings, and there are other reference terminal clients I can use as reference. althogh himalaya(rust) also looks interesting.
I would love to get some help with it, but I don't know where I should post it to get people interested.
With how easy it is to build apps now, is it really unreasonable to bring the old one back in a simple/cheap/sustainable way, that shields it off of being bought by those nightmare data brokers?
What should happen is that we take the lessons that we learned from this current iteration of the web and desktop and turn it into a new generation while cutting out the crap we don't need.
Sandboxes get better, yeah, but this is akin to leaving your door open in a neighborhood with violent crime and then saying I built this awesome laser guided Kevlar chamber that scans introducers upon entry instead.
But Nvidia is a terrible open source and consumer company. They gatekeep a lot and oftentimes it's only open source in name. Outside contributions are often slow-walked or rejected if they don't align with business incentives , and leadership is retained 100% in a couple of people from a certain country.
Meanwhile this particular thing now that the shell frameworks are converging into QuickShell and others are barely worth mentioning.
I'm not even going to criticize DHH for getting that money, good for him. My critique is solely directed at the rest of the VC ecosystem. Meanwhile China has a highly competitive ecosystem for hard tech graduates.
Dude, because that is how wayland is designed. X is a display server. Wayland is a protocol with implementation. If you want tiling, you have to roll your own, with ALL the protocols that are needed. It's up to clients to render. It was one of the fundamental critiques people had of the whole thing. 15 years in, and it's still the same. Need Vulkan rendering? See you in two years. And then every single WM has to implement it. Not even the basic premise of fractional scaling is solved properly, except in the one use case which is single monitor usage.
It's not about collaboration. wlroots was an attempt at having a standardized layer, and many protocols made it back into upstream actually. But even there, no two wlroots compositors are the same. We used to call these WMs, because the compositor layer could be separate on X. Anyway, bugs persist for years, some parts are never fixed, lots of basic features that existed in X for decades needed people to implement in their own compositor report back and then create a standardized protocol. So KDE has their own, gnome has their own, Hyprland recently rolled their own, etc.
And then there is of course gnome, which seems to want to break random basic functionality for no good reason(hello tray icons). Gnome of course didn't use to be like that.
But a plug, the absolute best wlroots based compositor I have used is mangowm[1][2]. You report a bug in the morning and in the afternoon dreammaomao has a solution for it. Of course I'm exaggerating a bit, but I think I've used pretty much every major Wayland compositor extensively so far.
But, at the same time. A design that requires everyone to implement their own protocols and everyone to refix the same bugs in their own compositor is inherintly bad.
I have been using Wayland as my daily driver. Some compositors lacked SHM support in their screen sharing, others have other issues. We only recently got proper text input support, and it took forever to fix in chrome and electron(it's been fixed for a few releases, but you'll still come across older electron software). How did they manage to make it so the cursor movement is dependent on the scaling mode in a way that client rendering library's need to be aware of it otherwise the cursor ends up in the wrong location by the way?.
In X, if the WM crashes, X is still running, and you can just restart the WM. In Wayland, if you hit a bug it takes everything down with it.
The first release was 14 years ago, we're still fixing screen sharing.
I just learned that despite all the boasting of fractional scaling support in Wayland, one of the base protocols, wl_output actually returns the same scaling mode for two screens even if they have a different scaling setting.
One thing I also never got is why the displays have to have absolute coordinates when you place them on a global coordinate system that is dependent on the scaling mode of the screen.
Also, KDE is the only WM that has managed to properly implement scaled Xwayland windows.