In this case it just means that current design and manufacutring process have very good yield.
This isn't true most of the time and when that happends they end up disabiling things that don't work on chips and sell them at lower speeds or with less cache.
I did notice atleast one thing. The summary from Google is better than the one from Bing. Maybe the people from Bing made the choice to make the page shorter so people need less scrolling.
Windows 7 is faster at than Windows XP it says in the documentation. Sure slightly, but still sucks. It takes longer than Windows startup and that is saying something.
Actually, if you read some of the other comments or the article you might have noticed they charge extra for rushhour. And that is one of the primairy goals, make the rushhour less frequent and less busy.
It doesn't really matter if it is a working draft or standard.
Browser vendors will propose specifications and implement it.
Usually with a browser-prefix like with CSS3 features: -webkit or -moz
This is to get in the field- and implementation-testing. If everyone has seen how it works, it will be made a standard otherwise it will be changed and deprecated.
You have to remember Australia is by size-comparison one of the worst connected regions in the world. I doubt their national connections are in much better shape.
There is 'one' 5.12Tbps 'cable' which delivers almost half of their capacity.
Funny thing is, not many might be lit, but even something as remote as Svalbard has that much capacity.
I find - it is usually easier to manage less code - has very little depencies - is usually easier to debug - is usually more efficient
I have a feeling some people just don't even check anymore what dependencies they suck into it.
Just recently, I had to look at Microsoft Exchange, a database had a problem. And the commandline tool to fix it didn't work anymore either.
I took depends.exe and looked at it. The commandline tool to fix the Exchange database files indirectly depends on Internet Explorer. I copied a dll in the directory from an other machine and now the commandline tool works again.
No-one suggested that. He mentioned: there is no killer appplication for people to install the runtime. Not even an application from Microsoft themselfs.
Probably, but maybe they also have set the microcode up in such a way to prevent such things from working ?
In this case it just means that current design and manufacutring process have very good yield.
This isn't true most of the time and when that happends they end up disabiling things that don't work on chips and sell them at lower speeds or with less cache.
It could also means AMD isn't competitive.
I did notice atleast one thing. The summary from Google is better than the one from Bing. Maybe the people from Bing made the choice to make the page shorter so people need less scrolling.
Yes, Windows roaming profiles suck.
Windows 7 is faster at than Windows XP it says in the documentation. Sure slightly, but still sucks. It takes longer than Windows startup and that is saying something.
On my home SSD-based system it takes the stupid BIOS longer to get started than the boot time all the way to Firefox.
It is pretty crappy BIOS though ;-)
Booting the OS, me doing the login and applications including Firefox takes 7 seconds.
At home I also have a SSD and the stupid BIOS takes more time than Ubuntu on SSD.
Well, in the article it said they would put a taxi-like-euro-counter on your dashboard so you could see the price of what you are doing.
It might have some affect* on some people.
* If I get that one wrong, sorry English is not my first language.
Actually, if you read some of the other comments or the article you might have noticed they charge extra for rushhour. And that is one of the primairy goals, make the rushhour less frequent and less busy.
I think the use of Android/ARM could potentionally bring down the price a lot more than what they produced.
Many people voted in Belgium and still no parlement.
That is why most european countries have working cheap healtcare.
It doesn't really matter if it is a working draft or standard.
Browser vendors will propose specifications and implement it.
Usually with a browser-prefix like with CSS3 features: -webkit or -moz
This is to get in the field- and implementation-testing. If everyone has seen how it works, it will be made a standard otherwise it will be changed and deprecated.
We've tried to do the plugin architecture for years.
They are trying to add some of those abilities to the browser as native features.
Which allows for much better integration.
I don't think it is that bad as you mentioned.
Firefox developers did implement different things that Chrome (for example) didn't have.
Have a look at this site:
http://caniuse.com/
Firefox 5.0 84%
Chrome 13 (from last week ?): 90%
Also have a look at the differences:
http://caniuse.com/#compare=y&b1=firefox+5&b2=chrome+13
Firefox 6 is planned for 3Q of 2011 and the beta's currently support 86%
Sorry, I was just looking at that 5.12Tbps which handles Australia and turns out it isn't even in service yet.
You have to remember Australia is by size-comparison one of the worst connected regions in the world. I doubt their national connections are in much better shape.
There is 'one' 5.12Tbps 'cable' which delivers almost half of their capacity.
Funny thing is, not many might be lit, but even something as remote as Svalbard has that much capacity.
Actually, if you had looked at Opera. You would find FireFox looks more like Opera.
less is definitely more, atleast if you ask me.
While I'm making lists, I should have added:
- easier to read code
- easier to understand code
- done faster reading the code
I prefer "less code"*.
I find
- it is usually easier to manage less code
- has very little depencies
- is usually easier to debug
- is usually more efficient
I have a feeling some people just don't even check anymore what dependencies they suck into it.
Just recently, I had to look at Microsoft Exchange, a database had a problem. And the commandline tool to fix it didn't work anymore either.
I took depends.exe and looked at it. The commandline tool to fix the Exchange database files indirectly depends on Internet Explorer. I copied a dll in the directory from an other machine and now the commandline tool works again.
Some people really are crazy.
* Not to the extreme ofcourse.
I don't know, all I know is. The people that got scared might just be jumping to conclusions.
I don't know if they will drop .net, but I agree that if Microsoft wouldn't want .net anymore they would drop it like it's hot.
And there would be nothing anyone could do to keep it going.
No-one suggested that. He mentioned: there is no killer appplication for people to install the runtime. Not even an application from Microsoft themselfs.
Actually, you missed something and that was the part that this whole scare is about. You mentioned web, not Windows 8.
In Windows 8, the new interface is build on top of IE10 and HTML5/JS and that combines with IE won't support silverlight on the long run.
That got the silverlight people really scared, because it looks like Microsoft will be dropping silverlight.
While I'm looking at my other screen.
All I wonder is, if Windows Explorer will ever get it right when predicting how long it takes to copy or zip something.
It has been saying for atleast for 4 minutes: 10 seconds remaining and now it says 5 seconds remaining. Right, eventhough the bar says: only 85% done.
right...