← Back to context

Comment by jakelazaroff

2 hours ago

This point of view always confuses me, because web developers already need to deal with platform differences. Especially if your app app also runs in a browser, like Slack and Discord — at that point, what issues do the differing system webviews cause that you don't need to deal with anyway just targeting browsers?

It's also funny to me as someone who's been building websites for 20+ years at this point, because the platform differences used to be much, much worse. Coincidentally, I just saw this article, which makes the case nicely: https://www.bram.us/2026/06/21/do-websites-need-to-function-...

webkitgtk isn't just quirky, it's also much slower compared to more popular browser engines and is particularly bad with RAM usage.

> This point of view always confuses me, because web developers already need to deal with platform differences.

On Mac, I use Firefox and Chrome.

However, if I use a Tauri app on Mac, I have to use dated WebKit. It's out of a Tauri developer's control.

  • > On Mac, I use Firefox and Chrome.

    Sure, but many people use Safari, which runs that exact same WebKit engine under the hood. So if your app is available in the browser in addition to Tauri, you have to support it anyway. And at the very least, you as a web developer should be used to supporting it.