News for hackers. Stuff that matters.
Re:iCab: Alternative Browser for macOS by jonfw on Monday April 20, 2020 @12:21PM (#22925357)
What industry are you in that people aren't adopting web apps? At my work we use a ton of web-apps. Chrome-books offer nothing but web apps and they're doing pretty well these days.
Re:iCab: Alternative Browser for macOS by asveikau on Monday April 20, 2020 @01:14PM (#22925939)
OK, sure. My point is: how many of them hard-depend (no graceful failover) on APIs introduced in the last 5 years though? You could build a pretty good web app 5 years ago, and many people did. Has the fundamental abstraction changed that much? I'm extremely skeptical of the claim.

If somebody does depend on something obscure like javascript APIs for bluetooth [like someone in this thread cited], are they doing that as a desktop app with chromium embedded or are they a more traditional webpage? Does it completely fall over and explode if you don't have bluetooth support in the browser? That would be pretty unreasonable for most developers.

What I'm saying is there is a difference between the bleeding edge stuff or things that push boundaries and common practice. And if you are coding against that other stuff, you also need a fallback for if it doesn't work.

Re:iCab: Alternative Browser for macOS by neurostimulant on Monday April 20, 2020 @07:17PM (#22929954)
There are tons of changes under the hood that made webapps development easier in the past 5 years, and not all of them can be polyfilled. For example, ES6 Proxy is something an end user won't even notice it exist, but now used at fundamental level on many webapps. Developers that depend on it won't trade their productivity gain from using the new api with supporting browsers that has less than 1% marketshare.