Kind of offtopic: I did some Ruby and I find some of the conventions really confusing; for example, the lack of “()” when calling a method. You never know if you’re accessing a property of calling a method until you grep the code. Am I the only one who feels this?
> 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.
Oh my fscking god... the comments in this thread are just... It's like trying to explain to a 5 years old why candys are not free...
If it's behind a paywall, it's because the creators want you to pay for the content. It doesn't matter if you can bypass the paywall with a user agent hack or if you must install daemon tools and use 54 different keygens and cracks and patches and firewalls to block ping-home requests. It just doesn't matter because you're tampering the paywall and getting for free what the creators of the content are willing to charge for.
I mean... how damn brain dead do you have to be to not understand that?
How about paying? That will let you do more, in less time, and won't require an extra browser plugin, which means that it will use even less resources than using a plugin to bypass the paywall.
Your lawnmower (your website) is in your backyard (your servers). If I go to your backyard (your servers) and I get/use your lawnmower (your website), I'm 1) trespassing privet property (the paywall) and 2) using something that I'm not allowed to use (your lawnmower, your website that requires me to pay for the content).
No matter how easy is it for me to go into your backyard (bypass your paywall), it's still an offense.
How about stop the development? The fact that you can break the paywall (easily) doesn't give you the right to do it. Current laws (in that country) state that it's ilegal, so why do you insist in doing it?
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...