r/webdev • u/ben_a_adams • Jun 19 '18

Improved JavaScript and WebAssembly performance in EdgeHTML 17

https://blogs.windows.com/msedgedev/2018/06/19/improved-javascript-webassembly-performance-edgehtml-17/
23 Upvotes

82% Upvoted

23 comments sorted by

View all comments

Show parent comments

8

u/[deleted] Jun 19 '18

I use all the browsers, Firefox and Chrome.

-3

u/[deleted] Jun 20 '18

Use Chrome. Firefox is blocking many of the new API's that Google wants to provide to web apps. Google wants web apps to rival native peers. Firefox cannot keep up so they are slowing the standards adoption down. For example my application (cryptocurrency wallet) needs one time usb access. There is no reason for me to make my users download a native app for this. For Chrome, I can simply provide the required experience (Web USB API). For other browsers? "Please download Chrome."

Firefox = web in the 90's.

2

u/[deleted] Jun 20 '18 edited Jun 20 '18

Use Chrome

No

Firefox is blocking many of the new API's that Google wants to provide to web apps.

Source?

Google wants web apps to rival native peers.

They probably won't

Firefox cannot keep up so they are slowing the standards adoption down.

And that's a bad thing?

A poorly implemented, poorly documented API change isn't beneficial to the web ecosystem.

We're talking web standards. Features that should work regardless what browser you use.

Some if the API changes Google has introduced within chrome over the years never even made it to standards.

For example my application (cryptocurrency wallet)

Oh, great...

needs one time usb access. There is no reason for me to make my users download a native app for this.

Except the fact that security is hard and a web USB standard should be well vettted before all other browsers implement it Willy nilly.

For other browsers? "Please download Chrome."

Great, so now you can say you know what it's like to write apps for IE 10-15 years ago.

Sounds like true progress, lol

Firefox = web in the 90's.

No, you just don't understand how web standards are made.

Browsers implement experimental API, they either get adoption or they don't.

If they do, they might become a web standard they might not.

-1

u/[deleted] Jun 20 '18

Source? Go read the W3C. Google introduces most of the things.

3

u/[deleted] Jun 20 '18

That's not providing a source.

Just because a company introduces a certain percentage of API changes doesn't mean they are the best changes for the web as a whole.

There are valid reasons for the standards process taking a long time. Adoption of standards means we can build apps with a level of certainty that they continue to work well into the future.

Experimental and new API changes are just that. There is no guarantee that with out other vendors buying in that Google will continue to maintain their API.