Summer has come here to the northern hemisphere and the world keeps on spinning with interesting things.
I’ve spent my last time organizing a week for mentors and startups this fall in Finland for the Google Developers Launchpad program, which is outlined below, and we also have news on handling Revenge Porn in Search, real-time data in Trends, a peak into Google’s networks and more!
Last week Google I/O took place and there were a lot of exciting announcements, ideas and releases! I’d like to shine some light on two of the most visionary ones from Google’s ATAP (Advanced Technology and Projects) group: Project Jacquard and Project Soli.
In my role at Google, I met a ton of people interested in what we are working at, what’s happening, how to get involved and learn more etc. Therefore, with this as the first post, I’ll be blogging about things that happened last week at Google.
Knowing your editor is important, and if it’s open source and you can add functionality, even better! Therefore, I dug into Atom from GitHub (which is open source!) to add something I like: a Hyperlink Helper.
Being a developer and having used a lot of code editors over the years, I think it’s a very interesting area both when it comes to efficiently but also in the program we spend many many hours in. At the moment, I’m back with Vim (more specifically, MacVim).
There seems to be this assumption with web sites nowadays that it has to be “rich media”. Animations galore, sound playing, videos autostarting (really?). And I’m having a sort of backlash reaction to all of that.
Being able to easily specify what to post with XMLHttpRequest is quite a powerful way of sending things to the server, using key/value pairs and FormData. However, many seem to have missed this gem, so I thought I’d outline it here.
All seats have been taken. Please write a comment to be put on a waiting list, there are always a number of cancellations, so there’s still a chance.
Geek Meet has been moved to January 16th.
Time to announce the first Geek Meet of 2013! I had plans on doing it at the end of this year, but with Christmas and surrounding activities for a lot of people, I decided to have it early next year instead.
I’ve always loved blogging, writing about things I’m interested in and then sharing and discussing it with like-minded people! Sometimes passionately agreeing, sometimes not so much. But I believe the discussion has always been good, and as long as it’s respectful, it’s quite constructive and an excellent base for building relations and bonds with people.
Peter-Paul Koch (PPK) wrote a blog post yesterday about his thoughts on Web developer relations management in the mobile world. Since I work for Mozilla, that he mentions, and I was also remotely involved in the discussion he refers too, I wanted to express my thoughts.
The desired future approach for storing things client-side in web browsers is utilizing IndexedDB. Here I’ll walk you through how to store images and files in IndexedDB and then present them through an ObjectURL.
The last week I’ve been contemplating whether to write anything or not about the situation with web browser vendor prefixes in CSS. I decided to share my thoughts on the problem and possible solutions.
First idea was to publish these posts on a regular schedule, but I’ve realized now it will be when I have enough good links (and time :-). Tons of links now, so, here goes – another issue of Robert’s read!
As part of making it easier to develop and analyze web pages, I previously released two extensions for Firebug: Firefinder and Inline Code Finder. I’m happy say they are now updated and are working with the latest versions of Firefox and Firebug!
When the AJAX wave came in 2005 when Jesse James Garrett coined the term and then everyone wanted it, one of the major shortcomings was that dynamic updates of only portions of a web page lead to inconsistent history handling and back/forward navigation button problems in web browsers and poor end user experiences. Enter the HTML5 History API.
Keeping track of multiple logins, passwords and services on Internet can be tedious at best, and projects like OpenID have tried to target that and make it easier and more secure for end users. Learning the lessons from OpenId and having a multitude of ideas how this can be made even better, Mozilla Labs has created BrowserID.
For the rest of 2011, I have a lot of intriguing countries/places to visit with exciting conferences to speak at, so I wanted to list them here. And who knows, maybe you will be attending any of those and we can get the chance to meet there?
Today I was just about to write a blog post about images and serving different sizes depending on the device accessing it. Then the Adaptive images post came up on the firstname.lastname@example.org mailing list. So let’s look at that and add my thoughts.
HTML5 is here to save us all: it has the cool functions, eye-dazzling features and APIs to go around. I get to see a lot of great things developed with HTML5, but I’d like to issue a word of caution as well.
A common discussion about HTML5 and whether to use it, and touched on in the HTML5 Hurdles article, is usually about fallback support and making it work in every web browser. But do we really need that?
Yesterday I attended the Stockholm Web Monkeys’ spring 2011 meetup in Stockholm, and I gave a short presentation and led a discussion about HTML5 – What’s good, what’s missing, web browser implementation takes.