31–40 of 87 posts
"Modern Web Development" does not mean "Works in Webkit", and it does a disservice to future/novice developers to reinforce that notion. What's dominant now was not in the not-too-distant past, and may not be in the not-too-distant future.
This is worth getting your head around just for the console. I've been transitioning all of my projects from python cgi scripts (yuck), to shtml files, javascript clients, and APIs that run on node.js. For somebody like me, that has been writing python+cgi for the last 5 years, diving into javascript was daunting . Terrifying even. Console made this a lot, lot, lot easier. In javascript, you can call console.log("thi…
It displays DOM properties and their current state. That's pretty important to any web developer.
"Modern Web Development" does not mean "Works in Webkit", and it does a disservice to future/novice developers to reinforce that notion. What's dominant now was not in the not-too-distant past, and may not be in the not-too-distant future.
"Modern Web Development" does not mean "Works in Webkit", and it does a disservice to future/novice developers to reinforce that notion. What's dominant now was not in the not-too-distant past, and may not be in the not-too-distant future.
Earlier quoted context omitted.
> a first-class citizen, has in fact set the mobile web back by years Steve Jobs started it. Everyone will follow it to the bitter end.
There's some revisionist history. When the iPhone was released, mobile apps were supposed to be HTML5 webapps. Developers cried for local apps. Apple responded to demand.
Sometimes it's useful to pretend that what you were going to do all along was merely a concession to outside demand.
This is worth getting your head around just for the console. I've been transitioning all of my projects from python cgi scripts (yuck), to shtml files, javascript clients, and APIs that run on node.js. For somebody like me, that has been writing python+cgi for the last 5 years, diving into javascript was daunting . Terrifying even. Console made this a lot, lot, lot easier. In javascript, you can call console.log("thi…
Earlier quoted context omitted.
I'm probably not the only one, but I have no idea where the separation between Chromium and Chrome actually is. Can anyone enlighten me as to where the separation really is? Is Chrome a fork of Chromium, is Chromium an upstream? I know they actively work together in a lot of ways but how exactly?
Chromium is the open source project that powers Chrome, the browser. Chrome Canary is upstream of Chromium, which is an upstream of Chrome.
This is a great resource and I'm glad Majd wrote it. However, this is really the kind of content that should be coming out of Google itself. Google is in an interesting position. Of all of the major Silicon Valley tech companies, I think Google is the one most seen as the "web" company, and yet they've staked a lot of their future on Android. Android, instead of making the web a first-class citizen, has in fact set t…
It's true- I've spent a lot of time developing HTML5-based apps (i.e. in a webview) and am already surprised at how much worse the Android web engine is than the iOS one. Google should be all over this (and with the release of Chrome of Android, perhaps they finally are) but it baffles me that it took this long. Meanwhile, it took Mozilla to create Boot To Gecko, a true web OS.
Earlier quoted context omitted.
It's true- I've spent a lot of time developing HTML5-based apps (i.e. in a webview) and am already surprised at how much worse the Android web engine is than the iOS one. Google should be all over this (and with the release of Chrome of Android, perhaps they finally are) but it baffles me that it took this long. Meanwhile, it took Mozilla to create Boot To Gecko, a true web OS.
The Chrome beta on ICS is great, but it's only accessible to Chrome Beta needs to be backported to at least 2.3