HN user

iSoron

130 karma
Posts11
Comments9
View on HN

I see it as a pendulum. In the old times, we used to write web applications in CGI, where there was no fixed structure whatsoever; the application programmer was responsible for creating the entire web stack with their own bare hands. Then the pendulum started swinging towards more structured frameworks and reached a peak with J2EE, where the application programmer only had to write a tiny piece of code (servlet) that went into a massive framework (servlet container), in a language that had a huge standard library (Java), following clear industry standards (e.g. JavaBeans, design patterns). By the time Rails appeared, the pendulum had started swinging back towards less structure and less formalism. Rails was still a framework, with a strong set of conventions, but it was quite simplified compared to J2EE. The pendulum then continued and people switched to Node.js, which was much more barebones and flexible than Rails. Right now, the pendulum seems to be reaching the opposite extreme with Go, where not only there isn't a framework, but there also isn't a virtual machine (everything is compiled to native code), the language itself is almost as simple as C, and there is barely any standard library.

If this is such a great idea, I would recommend the author of this proposal to work instead on a transpiler that converts the proposed javascript-only websites into a mix of HTML+CSS+js. If the idea catches on and, at some point in the future, people start using the transpiler almost exclusively, then the web browser developers could add direct support, and even eventually phase out support for legacy individual HTML/CSS/js files. Another benefit of implementing a transpiler first is that it would make the proposed javascript-only approach usable today.

"That’s not what we want on the store" -- Apple Vice President of Worldwide Marketing

What if I own an iPhone and HEY is what I want on my phone? How can I override Apple's decision? If I can't, who really owns this device?

Instead of consuming the extra energy, OP could also provide it to another customer through the grid, by selling it back to the utility company. This would reduce the total amount of energy that needs to be generated from non-renewable sources. If OP increases their own consumption instead, those non-renewable kWh are still being generated and causing environmental impact somewhere.

Looks like an interesting extension, but unfortunately I would never install it given that "this add-on can access data for all your websites". As far as I am aware, this means it can read and record all data in all websites I visit (including emails, banks, etc) and record everything I type anywhere (including usernames and passwords).

Even if the extension's source code is available on GitHub, there is no guarantee that the code hosted at addons.mozilla.org corresponds to the same one found on GitHub; and even if I (or someone else) could verify that the code is indeed the same, and that there is nothing malicious in it right now, there is no guarantee this will still be the case in future (silent) updates.

To be clear, this is more of a criticism to Mozilla Firefox's security model, not to this particular extension.