Google Takes AMP to the OpenJS Foundation (techcrunch.com) 17
An anonymous reader quotes TechCrunch:
AMP, Google's somewhat controversial project for speeding up the mobile web, has always been open-source, but it also always felt like a Google project first. Thursday, however, Google announced that the AMP framework will join the OpenJS Foundation, the Linux Foundation-based group that launched last year after the merger of the Node.js and JS foundations. The OpenJS Foundation is currently the home of projects like jQuery, Node.js and webpack, and AMP will join the Foundation's incubation program...
Google also notes that the OpenJS Foundation's goal of promoting JavaScript and related technologies is a good fit for AMP's mission of providing "a user-first format for web content." The company also notes that the Foundation allows projects to maintain their identities and technical focus and stresses that AMP's governance model was already influenced by the JS Foundation and Node.js Foundation.
Google is currently a top-level platinum member of the OpenJS Foundation and will continue to support the project and employ a number of engineers that will work on AMP full-time.
Google also notes that the OpenJS Foundation's goal of promoting JavaScript and related technologies is a good fit for AMP's mission of providing "a user-first format for web content." The company also notes that the Foundation allows projects to maintain their identities and technical focus and stresses that AMP's governance model was already influenced by the JS Foundation and Node.js Foundation.
Google is currently a top-level platinum member of the OpenJS Foundation and will continue to support the project and employ a number of engineers that will work on AMP full-time.
not convinced about AMP (Score:1)
Native limits your audience to one OS (Score:2)
If you want the best experience, native is really the way go to.
Which operating system runs applications developed for "native"?
Mobile web app is a stop gap, and the usability is usually terrible to sucky.
For a hobbyist or startup publisher of HTML documents or for a hobbyist or startup developer of an online application, the web stopgap reaches users of Windows, macOS, X11/Linux, Android, and iOS in the time it takes for native to reach only one of them.
Re: (Score:2)
We're really getting to the point that "Write once, run everywhere" languages are coming out...
Re: (Score:2)
Long live FORTRAN!
Re: (Score:2)
Which operating system runs applications developed for "native"?
All of them but Android.
Actually, even Android does, but last I checked you ultimately had to do your graphics interface with Java or Kotlin. If that's no longer true, great; otherwise you can't have a fully native solution, where all your code is compiled for the host architecture.
I don't know how much it really matters at this point anyway. I imagine that the penalty is pretty small, or even limited strictly to first run now.
Re: (Score:2)
Re: (Score:2)
Which operating system runs applications developed for "native"?
All of them but Android.
Actually, even Android does
Then let me rephrase what I really meant: Which GUI toolkit does an application developed for "native" use? And how much time-and-money does it take to get an application developed for "native" approved on those platforms that require approval of each application for execution by members of the public?
Re: (Score:1)
If you want the best experience, native is really the way go to. Mobile web app is a stop gap, and the usability is usually terrible to sucky.
The fact HTML is used so frequently on the web over compiled software running in your browser evidences your claim isn't correct.
We finally ditched the last bits of native when flash/java was banished to the children table and now nearly all of the web is non-native interpreted data.
Even browser plugins don't do native anymore.
Not to mention AMP is still just markup, just a stripped down less complex version than full on html 5
It's very wasteful to deal with the full spec when you don't want or need it, esp
Re: (Score:2)
That's because only Google was trying to punish others for not using AMP.
And since Google controls 95% of the search engine business, "only" Google doing it still means it pretty much impacts everyone.
And the fact that Google downranks non-AMP sites is not the only reason people are leery regarding AMP. Per Wikipedia [wikipedia.org]: "Most AMP pages are delivered by Google's AMP cache" - meaning that Google is collecting all that traffic information.
Spying First, User last (Score:3)
JavaScript provides a "Spyware First, User Last" format for web content.
Re: (Score:2)
JavaScript provides a "Spyware First, User Last" format for web content.
SFUL? I don't remember that data structure from University; it must be new. All I remember is FIFO, FILO/LIFO ...
I also picked up LILO, RTFM and STFU somewhere along the way ...
OpenJS Foundation to Google : we don't want it (Score:2)
Even pushing this onto OpenJS Foundation's plate , this will always be a GoogleFirst project.
I Wish Google (Score:3)
Re: I Wish Google (Score:1)
DDG FTW
(Start there, then add !g to the results if poor, but your search-fu should be strong on any engine.)
Enjoy (Score:2)
Ads that cant be blocked as the ad friendly browser tech loads the ads as the site and the site as ads.
International News (Score:1)