HN user

_em6m

133 karma
Posts10
Comments6
View on HN

A +15 year web-dev guy here.

One of the greatest fears (...) is that Web developers would increasingly take the easy way out and limit their support and testing to Chrome

Now, I must ask, why should we (web developers) be the responsible for making everything work with every browser? It's literally the same thing as asking application-oriented developers to code and test their apps for every major compiler out there.

We can't be the responsible for making every webpage compatible with every browser. Period. There are standards, and it's not really our problem that Chrome implements them in a week, while Firefox takes 6 months, Edge 2 years, Konqueror 10 years, and so on.

It takes a lot of time and energy to build and test websites for 3 or 4 different browsers. And it takes even more time to implement workarounds for every browser that doesn't support that thing that your boss asked you to implement. And "shit must be done by the end of the day".

Don't take me wrong. Go go browser diversity! But not if that means that I should take the burden.

Maybe ask the question the other way around. Why should they keep compiling everything from source? What are the benefits?

"it's going to be 304 bytes (...) instead of 6 bytes!"

O...M...G... I mean... Let me check again what year it is.

Please stop writing bullshit just because you can have a blog for free...

The main problem with "other toolkits" vs Electron apps is that they are not as simple to use in order to create a very good looking UIs. Compare how easy it is to use HTML and CSS in order to create a very complex UIs with all sort of effects vs how utterly complicated is to override, let's say, Qt's ::paint() method in order to achieve rich text inside a label. Let me repeat it. Rich text inside a label. Such a simple thing...