Put the knife down and take a green herb, dude. (c) Ruffin Bailey 2001-2021

WebKit Isn't Breaking the Web. You Are | Webmonkey | Wired.com:

We at Webmonkey hope it’s obvious that building WebKit-only sites is a waste of time. If you’re only interested in iOS users then take a tip from Instagram and build a native app.

Let's just quickly say that's crazy advice, and it misses the point of Glazman's critique.

If you don't know Objective-C, by all means, leverage what you do know if it'll make a strong HTML5 app for mobile devices. Use PhoneGap. Enjoy. No guilt required. Seriously, if you can't code HTML5 for other browsers you need to learn to code Obj-C in Xcode? Insane and inane.

The point is that those who use HTML5 shouldn't use browser-specific prefixes. Not sure how I feel about that either. If one browser (or rendering engine) is so far in front of another, then it's going to "win" the adoption war. Examples are written with webkit prefixes, they're copy and pasted, seem to work okay for their intended browser, and we're done. It's a non-trivial expense to learn that webkit isn't a standard if you're a gunslinger. (I'm not arguing we should be gunslingers, but that browsers should realize they exist. LOTS of them.)

If the other browsers support those CSS standards with their own prefixes (and with standardized ones), it's a heck of a lot easier to have the browsers support the different models than every programmer. Any time you're asking a programmer to write something twice to do things right (really, I'm pretty tired of if (document.getElementById) { branch1 } else...), you're doing it wrong. Get the cheese off of your face. Normalize. Put the logic where it belongs.

To be clear: In this case, it means Firefox needs to get over itself and chase WebKit. IE might follow. Do we care?

It's an ivory tower versus the market issue. You can't control programmers absolutely. I, in theory, like where Glazman is going. And in practice, just mentioning it will lessen the issue. Let's just stop pretending it's a zero-effort change for programmers to write platform neutral code and, therefore, as long as browsers are less than 100% equal, you'll always have a percentage of the code in the wild that supports one over the other.

Degrade? Sure. Write to treat each version of each browser equally? Impossible. [sic]

Labels: browsers, firefox, standards, webkit

title: Put the knife down and take a green herb, dude.	descrip: One feller's views on the state of everyday computer science & its application (and now, OTHER STUFF) who isn't rich enough to shell out for www.myfreakinfirst-andlast-name.com Using 89% of the same design the blog had in 2001.
FOR ENTERTAINMENT PURPOSES ONLY!!! Back-up your data and, when you bike, always wear white. As an Amazon Associate, I earn from qualifying purchases. Affiliate links in green.
x MarkUpDown is the best Markdown editor for professionals on Windows 10. It includes two-pane live preview, in-app uploads to imgur for image hosting, and MultiMarkdown table support. Features you won't find anywhere else include... MarkUpDown Multiline Table & Bootstrap Grid support. Beautiful Easy Actions that keep the Markdown flowing. HTML paste to paste HTML source into your documents. You've wasted more than $15 of your time looking for a great Markdown editor. Stop looking. MarkUpDown is the app you're looking for. Learn more or head over to the 'Store now!

Tuesday, May 28, 2013
Google Has Already Removed 8.8M Lines Of WebKit Code From Blink \| TechCrunch Google Has Already Removed 8.8M Lines Of WebKit Code From Blink \| TechCrunch: [May 15th, I believe] at the Google I/O developer conference, the Blink team provided an update about the state of the engine. As Alex Komoroske, a product manager on Chrome’s Open Web Platform told the audience, the team has already removed 8.8 million lines of code from the original WebKit repository. [emph mine] Wow. It looks like most of this was low hanging fruit -- "the company argued that it was doing so because WebKit had become somewhat unwieldy to maintain because of the wide range of platforms it needs to support. In the process" -- but still impressive. Labels: Google, webkit posted by ruffin at 5/28/2013 09:37:00 AM

Monday, August 06, 2012
No, WebKit Isn't Breaking the Web. That's how it works. WebKit Isn't Breaking the Web. You Are \| Webmonkey \| Wired.com: We at Webmonkey hope it’s obvious that building WebKit-only sites is a waste of time. If you’re only interested in iOS users then take a tip from Instagram and build a native app. Let's just quickly say that's crazy advice, and it misses the point of Glazman's critique. If you don't know Objective-C, by all means, leverage what you do know if it'll make a strong HTML5 app for mobile devices. Use PhoneGap. Enjoy. No guilt required. Seriously, if you can't code HTML5 for other browsers you need to learn to code Obj-C in Xcode? Insane and inane. The point is that those who use HTML5 shouldn't use browser-specific prefixes. Not sure how I feel about that either. If one browser (or rendering engine) is so far in front of another, then it's going to "win" the adoption war. Examples are written with `webkit` prefixes, they're copy and pasted, seem to work okay for their intended browser, and we're done. It's a non-trivial expense to learn that `webkit` isn't a standard if you're a gunslinger. (I'm not arguing we should be gunslingers, but that browsers should realize they exist. LOTS of them.) If the other browsers support those CSS standards with their own prefixes (and with standardized ones), it's a heck of a lot easier to have the browsers support the different models than every programmer. Any time you're asking a programmer to write something twice to do things right (really, I'm pretty tired of `if (document.getElementById) { branch1 } else...`), you're doing it wrong. Get the cheese off of your face. Normalize. Put the logic where it belongs. To be clear: In this case, it means Firefox needs to get over itself and chase WebKit. IE might follow. Do we care? It's an ivory tower versus the market issue. You can't control programmers absolutely. I, in theory, like where Glazman is going. And in practice, just mentioning it will lessen the issue. Let's just stop pretending it's a zero-effort change for programmers to write platform neutral code and, therefore, as long as browsers are less than 100% equal, you'll always have a percentage of the code in the wild that supports one over the other. Degrade? Sure. Write to treat each version of each browser equally? Impossible. [sic] Labels: browsers, firefox, standards, webkit posted by ruffin at 8/06/2012 09:02:00 AM

<< Older \| Newer >>