Sure but on the flip side, skills not being in context means that for many harnesses, the model simply never finds them. Whether MCP or Skills are "better" depends extremely heavily on the context management functionality of your harness because if you use a relatively naive harness (i.e. one that implements MCP and Skills in a straightforward way), MCPs will generally be more effective, especially if your model is local-only (i.e. dumb), but at the cost of context.
That'll work great until your first customer from a CJK or RTL language writes in, "Hey, how come I can't type in your app?", or the blind user writes in "Hey how come your app is completely blank?" then you'll be right in the middle of the "Find Out" phase
These strategies are fine for toy apps but you cannot ship a production app to millions or even thousands of people without these basics.
A pervasive "Someone needs to do something!!!" attitude is why. Americans will forever wait for the school principal to come and get everyone into trouble
There is a lot of direct action happening right now in Minneapolis, with people keeping watch on every block. I agree this level of organizing should be happening nationwide.
The country that lived through pervasive mass state surveillance by secret police for 40 years is unsurprisingly quite cagey about digital centralization of records, even so many years later
Transit companies are pretty bad at PKI infrastructure and internet security combined with the inefficiencies inherent in German bureaucracy / anti-centralization as well as the inherent insecurity of the SEPA model sometimes make crime possible
> Germany has a tendency to wish something into existence with a law
After living here five years I've finally realized the same thing - Germany is the country of Rules, often well-intentioned, but no one actually follows them. It's especially damning when those rules actually are important and would protect regular people esp. around labor and housing, but oops zero meaningful enforcement. Wish we'd have 1/10th the rules but people had to actually follow them
Tauri's approach of using the system Webview just doesn't scale to millions of users. You will end up having to tell your customers, "In order to fix the bugs in our app, you need to install a new version of your OS", or in the case of Apple, sometimes even saying, "You need to buy a new computer to use our app". It's not a great conversation to have.
Philosophically, it also optimizes something that doesn't really matter much in 2025, download and disk space - despite the perceptions, the system Webview usually uses the same order of magnitude memory as Electron; maybe a little less, but not a Lot less. We can see the WhatsApp rewrite on Windows to use WebView2 as evidence of that.
The one time that Tauri is legitimately better though, is if you've got a lot of Rust code that you want to integrate - GitButler for example uses Tauri and it works for them because they have a lot of Git systems code and it's all in Rust.
We (GitButler) however keep running into packaging issues that make all but a very small handful of linux distros "usable". There are also numerous papercuts that we keep getting due to Tauri being comparably less mature.
We've been making steps towards moving away from Tauri. We now already have the capability to run our rust backend as a web-server and use the frontend in a regular browser. One of the next steps is to package the frontend into an electron app, and run the web-server as a sidecar process.
While there may be size downsides to packaging an entire browser - size isn't really a big issue compared to the program simply not working on a large user demographic.
reply