kinlan

Author here. Hello.

Bookmarklets are a massively under used feature. I love them :)

Well, that was one impulse purchase.

I live in Wales and in a rural community at least.

Yep, this was a huge priority for me.

I miss yayQuery too.

I know we're not going to agree. I know Google is advertising as major source of revenue. I also believe that it can only successful advertise through its search because the web is open and needs to stay that way.

Heh - It's hard to answer these questions when they are posited as loaded questions so clearly :D

I don't think it's about Google or Chrome winning. I believe Google is pretty clear that a healthy and open web where anyone is able to freely publish, monetize and consume content, as well as build and use apps is important for it's business and success. I think Google has a part to play in the success of the web, I think I can help be a force for good in the success of the web, however we're just parts of the ecosystem whole and the web will be around still long after Google.

I don't believe new features in Chrome will ever stop because we still believe the web should be able to do everything that other platforms can do and we want to keep offering that to people.

Oof - last week mine looked like an exploded sausage, but it was healing. Glad the long term issues weren't too bad for you.

I think there's a number of people who've said that they've lost trust in Google and that's pretty much the sum of it and why I felt like I needed to write up the post.

For me, there are three sets of people that I work with: Developers, Engineers in Chrome and Engineers on other browsers. Projects like Compat 2021 are super important to me to the point that if another browser vendor doesn't trust that we are working and pushing together then the project just won't succeed. If the partner browser (Safari in this question) doesn't trust the data we present, then the ecosystem won't trust the data or project. If the ecosystem doesn't trust data then the browser teams won't trust the project etc.

So even if it was just a small change in the number, it's trust all the way down.

Appreciate you adding this extra information in (also hey! on Twitter).

I don't have much to add, I understand it and I don't disagree with the frustration you have, because it's also not the first time I've heard it from many developers.

I'll keep working with the team to improve it, but it certainly takes time.

Thanks mate :) miss you.

I think the number of API's we add to the platform will always keep increasing. We certainly see a big part of the web as enabling Apps to come to the web, and we do make sure (now) to have developers committing to using those APIs. I know that also frustrates a lot of people too.

It's sad that it's got the point where the teams don't trust each other and it's clear that the perception is wider. I'm still hoping to change that around.

I wrote the post to as clearly as possible document what happened for the avoidance of doubt because it was me who made the mistake. I'll accept your point of view, but I'm also comfortable with my side of this.

BTW - I still have a thumb but there is a huge huge chunk missing. :D thankfully, the hospital said a lot of the skin on the hand will heal and grow back.

Yeah - I have to take the rough with the smooth. :D

:thumbs-up: - I've got some gnarly pictures, but I can say I am on the mend.

It was all pre-recorded. We clarified it in the live AMA after the pre-record.

I wouldn't even say it was that. No one asked me to write it, but I also want to make sure it was clear when and how the mistake was made. I'm not above pride in this case and in the long run I saw the two teams arguing over something that I had done and I value developers more than that.

As someone mentioned directly in this blog post I can tell you where I came from with the event at least. Trust. Making sure developers know what we're working and why we think it's important and when we can show everyone the data to back up our rationale. I think we still have a long way to go, but it's something I've always strived for my team (devrel) to do.

I felt that it was important to ask these questions on the AMA (there was a fair few in the sli.do in other areas around trust) that centered around all the different pieces of work we do but also knowing that we're not the AMP team we can only answer with our perspective - we try to do everything in the open and developers should rightly judge us on how well we do. I do encourage people to check out the blink process as a place to keep a check on what we are thinking about.

I've just pinged the team. :)

Yes. It was our team.

I guess people don't recognise the Emmerdale theme tune..

Wahh wahhh waaah wawawawahhh.

Yeah. You need to fix the CLI and add an emdedable API

Ah right. Well, I wished he did too with the amount of people I've told over the years :D

I can't find it, but I have a memory of him commentating "The race order is 1, 2, 3, 4" - it made me laugh at the time... I could be completely making it up, but I smile and think of Murray every time.

I heard he also came up with "A mars a day helps you work rest and play"

Im from Liverpool, live in Chester and love North Wales. I encourage everyone to visit this amazingly beautiful part of world.

I actually rather liked these images because there’s a certain grit to it that is still sometimes present.

Mhtml tends to not have JavaScript run with it because there is no origin attached to it. That's one of the benefits of web bundles, they can run with an origin attached so they have access to the correct storage and other sandboxing primitives.

The W3C has many wealthy companies as participants, they should support it more too given that each and everyone benefits from MDN being the central place for all browser API reference.

I lead of Chrome DevRel team and we contribute with tech writer support and work on the PAB, it appears too little still but there are many web standards aligned companies that could provide more support because they directly benefit from MDNs existence.

Chrome DevRel lead here. We don't want that. We want to support MDN and for it to remain browser agnostic.

Biased opinion. It depends if you've articulated the value of the function well. I do fear that if it's seen as a marketing function then it's an easy place to start tightening belts. If it's integrated into the product team then it's harder, imo.