![]() ![]() So initially, there was ChromeOS as an app platform, and they had a backlog of all these APIs that they of sorts to be on the open web. ![]() And they started by filling all those gaps. So there were gaps in the platform that the platform just didn’t cover… And Fugu was his effort that people around Alex - but there’s a lot more people behind this - have started. And in many cases, these applications were lacking certain APIs. And on the Chrome team back then everyone was doing amazing things, like CSS Houdini, and all the hot topics were being dealt with… So I looked at “What are people doing on the web?” I noticed this tendency where more and more people were building amazing applications on the web. And I will tell you my view of project Fugu, but obviously, Alex has been around for way more time than I have been, so he will have a different view, so also get his, for sure… But what I will tell you is, when I started working on the Chrome team, I was looking for my niche. He still does web stuff, obviously… So very much do make sure that you get him on the show. I also use Firefox… But I think regardless of our usage of Chrome, I think I’m a fan of the Chrome Developer Relations team, and I’m super-excited to have you on the show today… So thank you, and welcome, Tom. I use a Chromium flavor as my primary browser these days, Brave. I do have to admit though, just to be fair - Tom, I don’t know how often you listen to this show, but I’m not sure we have a ton of Chrome users anymore on the panel. I always think of the Chrome Dev developer relations team as a whole, and there’s different roles within the developer relations team… There’s folks that work on engineering projects, like Tom, there’s folks that are really more focused on advocacy… I’ve always thought about that team as best-in-class. I have to say, for many years - I’ve been following the Chrome team for almost a decade now, and it’s been amazing to see kind of… I think that team specifically set the standard for how to do developer engagement, and how to do developer advocacy, and how to do developer education well. Use the code CHANGELOG and get the team plan free for three months. From error tracking to performance monitoring, Sentry helps teams see what actually matters, resolve problems quicker, and learn continuously about their applications - from the frontend to the backend. Sentry – Working code means happy customers. Try it free today with no credit card required at /jsparty This makes Lolo Code very Zapier-ish, but for devs. You can even write your own integrations. Use the visual editor to build your app, connect nodes, and add any npm libraries you need. All this without having to provision or manage servers. Lolo Code – If you’re familiar with building severless apps, think of Lolo Code as your backend with a visual editor that lets you think and build at the same time. ![]() Our platform enables frontend teams to do their best work. Vercel – Vercel combines the best developer experience with an obsessive focus on end-user performance. Learn more at /square to dive into the docs, APIs, SDKs and to create your Square Developer account - tell them Changelog sent you. There is a massive opportunity for developers to support Square sellers by building apps for today’s business needs. Square – Develop on the platform that sellers trust. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |