If battery life is an issue, it will just create bigger market for docking stations and on-the-go chargers - there are plenty of those for iPod already.
Why did Apple start with core duo processors? They could have made a clean break to 64bit x86 hardware, instead of going 32bit and having to migrate later?
Because when Mac OS X was ported to x86, x86-64 didn't exist yet (Jobs admitted that they had x86 builds since the beginning of Mac OS X).
I've switched to DVORAK for a moment (typing with 3/4 of my previous QWERTY speed), but then I gave up and returned to QWERTY:
Keyboard shortcuts in applications are designed for physical QWERTY layout. I couldn't be bothered to remap them in every app.
DVORAK loses it's advantage in languages other than English and English is not my first language.
Windows' built-in DVORAK layout is a typical Microsoft's almost-standard-but-annoyingly-not-quite, so I wouldn't be able to comfortably use any Windows machine.
IE6/7 have all those weird box model problems with XHTML 1.0
No, IE can handle box model perfectly. It's XHTML it can't handle at all. You must be sending your pages as HTML (text/html) and you've put XML prolog in your HTML, which triggers quirks mode (you may think it's XHTML, but browsers see it as HTML with lots of syntax errors and bogus DOCTYPE).
Spammers need domains for hosting spamvertised websites. Not only e-mail is spammed with them, but also blogs/forums and search engines. If domains were more expensive, banning of them would be more effective.
The whole point of the article is that blurring and pixelating beyond recognition isn't enough. You don't need to see the original numbers, you just have to find numbers that blur to a similar blob. It's a dictionary attack with blur as a hash function.
That's the case already. I've checked Opera, Safari and (Gecko-based) Camino - all have completly separate set of prototypes for each frame, so you can't circumvent XSS protection using prototypes.
So it seems there's nothing to get excited about - you must have exploitable XSS vulnerability to begin with, so it's not the end of the internet just yet.
Opera doesn't really identify as IE - it just prepends MSIE user-agent string to it's own, so can be detected regardless (if you intentionally look for it).
Anyway, these stats seem to be for US, not EU. Opera has much higher usage in Europe (3-8%, reaching 15% in some countries). Also Linux is over 1%.
I don't know the details, but for me the problem is simple:
if it's because of Opera's bug or lack of neccessary feature, it's Opera's fault and go complain to bugs.opera.com/wizard.
if it's because website uses crappy code, broken browser-detection - get the damn website fixed
Market share, not being open-source or having lame name does not define whether browser can handle pages properly or not. Opera, in most cases, perfectly can.
There's a problem with über-smart semanting search engines - if they provide answer right away (by understanding semantics and/or choosing very relevant snippet), there will be little incentive for users to visit web sites that provided the information. This means that search engines will steal ad revenue from content providers and content providers will revolt agains such engines.
Imagine Internet had Hawaiian origin - you'd be wanting to break the DNS to use your "odd" characters like "c" and "d". Why would you want to "fix" Hawaiian alphabet if it's not broken for Hawaiians!?
When Tiger came out, I've seen lots of applications broken and... lots updated. Now developers are moving to Universal Binaries. I'm surprised that Apple gets away with this, but as long as they do - IMHO it's a good thing: almost nobody uses unmaintained software.
Slashdot Mirror
If battery life is an issue, it will just create bigger market for docking stations and on-the-go chargers - there are plenty of those for iPod already.
s/XHTML/DOM that XHTML can represent/ and you have how every browser works.
Browsers don't render HTML as it is, they render DOM tree which may be derived from HTML or XHTML serialization, built using JavaScript, etc.
I am familiar with Windows Mobile interface and that's exactly why I'm drooling over iPhone.
I've switched to DVORAK for a moment (typing with 3/4 of my previous QWERTY speed), but then I gave up and returned to QWERTY:
<!DOCTYPE html>
<meta charset=utf-8>
<h1>Hello world!</h1>
<p>This is a complete, valid HTML5 document
and it does work in current browsers as intended, even in IE6.
No, IE can handle box model perfectly. It's XHTML it can't handle at all. You must be sending your pages as HTML (text/html) and you've put XML prolog in your HTML, which triggers quirks mode (you may think it's XHTML, but browsers see it as HTML with lots of syntax errors and bogus DOCTYPE).
obligatory hixie reference
Spammers need domains for hosting spamvertised websites. Not only e-mail is spammed with them, but also blogs/forums and search engines.
If domains were more expensive, banning of them would be more effective.
I think that is should cost much more to buy a new domain name.
It would harm spammers registering throw-away domains for each "marketing campaign".
It's the appeal of a Rolls-Royce vs old pickup truck. Pickup truck can do much more and is cheaper.
No, you don't. You can play iTunes Store tracks using free iTunes software (or is it illegal too, because you have to buy Mac OS X/Windows to run it?)
So you could see it yourself and have a laugh ;)
Heck, I see no difference between tags and keywords (except in coolness factor).
The whole point of the article is that blurring and pixelating beyond recognition isn't enough. You don't need to see the original numbers, you just have to find numbers that blur to a similar blob. It's a dictionary attack with blur as a hash function.
That's the case already. I've checked Opera, Safari and (Gecko-based) Camino - all have completly separate set of prototypes for each frame, so you can't circumvent XSS protection using prototypes.
So it seems there's nothing to get excited about - you must have exploitable XSS vulnerability to begin with, so it's not the end of the internet just yet.
Opera doesn't really identify as IE - it just prepends MSIE user-agent string to it's own, so can be detected regardless (if you intentionally look for it).
Anyway, these stats seem to be for US, not EU. Opera has much higher usage in Europe (3-8%, reaching 15% in some countries). Also Linux is over 1%.
But it is (sortof) supported already via user stylesheets/scripts, as explained in TFA
If you think JS is slow, you haven't tested Opera's implementation.
I don't know the details, but for me the problem is simple:
Market share, not being open-source or having lame name does not define whether browser can handle pages properly or not. Opera, in most cases, perfectly can.
This is already a problem to some extent - Nielsen wrote about this in 2k4.
WindowDragon allows resizing windows in FVWM way - hold modifier and you can drag and resize in any direction, by any point inside window.
Imagine Internet had Hawaiian origin - you'd be wanting to break the DNS to use your "odd" characters like "c" and "d". Why would you want to "fix" Hawaiian alphabet if it's not broken for Hawaiians!?
When Tiger came out, I've seen lots of applications broken and... lots updated. Now developers are moving to Universal Binaries. I'm surprised that Apple gets away with this, but as long as they do - IMHO it's a good thing: almost nobody uses unmaintained software.
You mean something like this?