Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A new approach to web performance

ampproject.org

Post reply on HN
Print view View original

101–110 of 177 posts

Re: A new approach to web performance

#101

Post by cramforce »

barkingcat wrote: post #94
coldtea wrote: post #91

Earlier quoted context omitted.

> What annoys me is how Google is selling this project. At least Facebook is honest about their Instant Articles. This isn't an "open standard" guys, and it's not about performance! It's about the single piece of js that's allowed on AMP pages and the amp-tags such as and that only Google controls. This is not a Google project.

if you run a whois on ampproject.org, the results clearly indicate it's owned by google. Registrant ID:mmr-87489 Registrant Name:DNS Admin Registrant Organization:Google Inc. Registrant Street: 1600 Amphitheatre Parkway Registrant City:Mountain View Registrant State/Province:CA Registrant Postal Code:94043 Registrant Country:US Registrant Phone:+1.6502530000 Registrant Phone Ext: Registrant Fax: +1.6502530001 Registr…

Yep, I'm a Google employee. ampproject.org has the full list of partners working together. One example is https://blog.twitter.com/2015/introducing-accelerated-mobile...

Re: A new approach to web performance

#102

Post by cramforce »

tolt wrote: post #95
coldtea wrote: post #91

Earlier quoted context omitted.

> What annoys me is how Google is selling this project. At least Facebook is honest about their Instant Articles. This isn't an "open standard" guys, and it's not about performance! It's about the single piece of js that's allowed on AMP pages and the amp-tags such as and that only Google controls. This is not a Google project.

Looks like it is https://googleblog.blogspot.dk/2015/10/introducing-accelerat...

Its a joined project by many partners. See other comment in thread for details.

Re: A new approach to web performance

#103

Post by possibleNoob »

mhw wrote: post #48

This is obviously Google's response to Facebook's Instant Articles and Apple's News. Behind all the technology is the main business goal of delivering a content platform that has the sponsoring company's ad network baked in to it.

How does facebook instant articles technology work?

Re: A new approach to web performance

#104

Post by cramforce »

scrollaway wrote: post #70
ducuboy wrote: post #38

What annoys me is how Google is selling this project. At least Facebook is honest about their Instant Articles. This isn't an "open standard" guys, and it's not about performance! It's about the single piece of js that's allowed on AMP pages and the amp-tags such as and that only Google controls. Performance is just the story they are selling in exchange of absolute control of the Web. After all, any publisher can ea…

What are they selling, exactly? Why does this need to be a framework, with js and all that? I'm not asking cynically, and following it up with "oh, they should just do x instead".... I legitimately do not understand what's going on here. What's the added functionality? I read the article twice, I don't get it. I'm going through the spec, I don't get it. I looked at the article source, I really don't get it, it's just…

You might get it :) There isn't that much to it. AMP is as much about technology as finally getttig that tech adopted. Since AMP is built on web tech there is nothing in it that you cannot chose to do yourself

The problem we are solving is that many sites don't.

Re: A new approach to web performance

#105

Post by cramforce »

tempodox wrote: post #33

I suspect that the issue of web performance is less a technical problem than an organisational one. We have the technology to build performant pages right now, as well as best practises — they're just not used pervasively enough. As long as the business processes that produce the slow pages don't change, no shift in technology alone can save us.

Exactly. AMP is very much about addressing that issue.

Re: A new approach to web performance

#106

Post by cramforce »

mhw wrote: post #48

This is obviously Google's response to Facebook's Instant Articles and Apple's News. Behind all the technology is the main business goal of delivering a content platform that has the sponsoring company's ad network baked in to it.

We support currently many / future most (if they chose to participate) ad networks and there is no rev share.

Re: A new approach to web performance

#107

Post by gorhill »

I personally choose to block ubiquitous 3rd parties by default[1], to fight both bloat AND privacy exposure.

This AMP project reduces the bloat but at the cost of increased privacy exposure. If I globally block `ampproject.org` when visiting a AMP-enabled web pages, the pages do not render at all.

My understanding is that now all "Google and its partners" have foiled the ability of visitors to protect their privacy with this AMP project -- and all these partners are given access to my browsing history.

This goes completely counter to "The Internet is for End Users"[2]. I hope people will boycott by blocking wholesale `ampproject.org` as 3rd party -- this needs to fail.

[1] Examples: `twitter.com`, `facebook.[com|net]`, `gravatar.com`, `fonts.googleapis.com`, etc.

[2] http://mnot.github.io/I-D/for-the-users/

Re: A new approach to web performance

#108

Post by mreiland »

creshal wrote: post #35
mreiland wrote: post #34

Earlier quoted context omitted.

At one point gamefaqs.com would generate static pages and serve those everywhere it could. This was before cnet bought the site though, I have no idea what they do nowadays, your post just reminded me of it.

It doesn't matter much, the 70+ embedded youtube videos some users put into their FAQs will kill your browser either way.

Can you link to an example of this? I've been on gamefaqs since the very beginning and I've never seen that. In fact, the vast majority of FAQs on that site are still text.

Re: A new approach to web performance

#109

Post by GFischer »

ducuboy wrote: post #96
coldtea wrote: post #84

Earlier quoted context omitted.

> Remember who actually killed it? Yeah, that was also Google.. by discontinuing their Reader - a very good tool with lots of users but no revenue. If a single company killing a sigle product could kill RSS, then it wasn't that alive in the first place. The fact is, after 10 years of RSS being available in blogs, news sites and elsewhere, Reader still had an insignificant number of users in the web scale of things. A…

Ok but that still shows how much Google cares about open standards. And did you just say "few tens of millions" of users is insignificant? How many users are we here on Hacker News again?

It's, ironically, a case of the "embrace and extinguish" philosophy that Microsoft was reviled for.

I remember reading posts by several people which said they weren't going to build a RSS reader because they didn't want to compete with Google Reader.. and then they went ahead and killed it.

RSS didn't really "take off" with mainstream users (I guess today's equivalent is Twitter), but it filled an interesting niche.

RSS -> Twitter

Usenet -> many proprietary platforms

IRC -> Slack

XMPP never took off

Many open, interoperable services died off or never took off, but companies built similar services and are enjoying success.

Re: A new approach to web performance

#110

Post by coldtea »

barkingcat wrote: post #94
coldtea wrote: post #91

Earlier quoted context omitted.

> What annoys me is how Google is selling this project. At least Facebook is honest about their Instant Articles. This isn't an "open standard" guys, and it's not about performance! It's about the single piece of js that's allowed on AMP pages and the amp-tags such as and that only Google controls. This is not a Google project.

if you run a whois on ampproject.org, the results clearly indicate it's owned by google. Registrant ID:mmr-87489 Registrant Name:DNS Admin Registrant Organization:Google Inc. Registrant Street: 1600 Amphitheatre Parkway Registrant City:Mountain View Registrant State/Province:CA Registrant Postal Code:94043 Registrant Country:US Registrant Phone:+1.6502530000 Registrant Phone Ext: Registrant Fax: +1.6502530001 Registr…

>I can't understand why you say it's not a Google project if it's being funded by google and made by a google employee.

For the same way that tons of open/collaborative projects with multiple partners are not "X projects" even if they started and/or are hosted by X.

Heck, even something like Webkit is not an "Apple project"...

Downvotes? Are you kidding me? What part of "open source initiative" containing multiple industry leaders (like Twitter, and lots of others) don't people understand?

Post reply on HN