Comment by bsoles
6 days ago
To my dismay, my company uses JavaScript, HTML, CSS with a custom Chromium-based web browser installed on your PC. The performance is shit: GUI performance that should take milliseconds takes seconds to render with constant pinging of corporate servers and user activity logging. Development mostly done in IntelliJ or VS Code.
Those problems aren't JS/HTML/CSS problems, they are bad programmer problems. If the performance of your webapp sucks, then you did something wrong somewhere, but it wasn't choosing JS/HTML/CSS that caused the problem. There are plenty of very performant web applications.
At that point, what's the point in maintaining your own browser fork instead of just telling users to point their own (Blink, even) browser at localhost?
Control of the chrome around the browser page I guess.