Linked by Thom Holwerda on Sat 23rd Oct 2010 22:23 UTC
"Windows 7 might be a massive commercial success and an undeniably rock solid piece of software, but Microsoft is apparently unwilling to rest on those soft and cozy laurels. Asked about the riskiest product bet the Redmond crew is currently developing, its fearless leader Steve Ballmer took no time in answering 'the next release of Windows'." Also of note in this same video interview thing: Ballmer states that Silverlight is now pretty much strictly a client, non-cross platform thing, while explicitly stating that when it comes to doing something universal, "the world's gone HTML5".
Thread beginning with comment 446951
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
The benefit is ...
by pica on Mon 25th Oct 2010 15:19
in reply to "RE: Maybe OT: The OS I am dreaming of"
Member since:2005-07-10
... that even closed source components (e.g. some graphic card drivers are closed source) are available on all hardware platforms.
The part up to the optimizing VM runtime can be provided be the hardware vendor.
The OS vendor provides the running on that runtime OS. Here is another benefit: The OS vendor only has to provide a single image. Has to patch only each issue once.
pica
Member since:2010-03-08
... that even closed source components (e.g. some graphic card drivers are closed source) are available on all hardware platforms.
The part up to the optimizing VM runtime can be provided be the hardware vendor.
The part up to the optimizing VM runtime can be provided be the hardware vendor.
1/Graphic card drivers are generally linked to a single hardware platform, so how do they benefit from that interpreted ecosystem, knowing that they'll include a large amount of bus-specific code anyway ?
2/The vendor does have to provide some kind of source code (as opposed to platform-dependent binary) if we want the program to be compiled/interpreted on multiple platforms. If he does not want it to be human-readable, the best he can do is using an automated code obfuscation system like the one offered by Java...
The OS vendor provides the running on that runtime OS. Here is another benefit: The OS vendor only has to provide a single image. Has to patch only each issue once.
Wrong, he must provide several images, since as you said a (tiny but necessary) part of the OS has to be hardware-dependent. Moreover, if the code has been properly written, the OS vendor generally only has to patch it once too. The extra step is to recompile it once for each supported platform, but if he doesn't do it, someone will have to do it at his place.
You can see it this way : either the OS vendor compiles one image per platform, or each user, on each platform, will have to compile an image in real-time at first boot and experience the sluggish Gentoo-style first impression that this leads to.
Edited 2010-10-25 16:18 UTC
About performance ...
by pica on Mon 25th Oct 2010 15:26
in reply to "RE: Maybe OT: The OS I am dreaming of"
Member since:2005-07-10
Features
Linked by David Adams on 05/16/13 4:23 UTC
OSNews is a sponsor of this year's O'Reilly OSCON in Portland, Oregon, USA. A lucky OSNews reader will win a free three-day pass, including two tutorials days. To win the pass, post a comment on this story saying something about Open Source Software or OSCON. We'll pick a winner at random next week. If you don't have an OSNews account, you may email us your entry. Part of the conference is the 9th annual Open Source Awards, and today the 16th is the deadline for nominations. If you'd like to nominate an outstanding open source contributor, do it here. Read on for more information about OSCON. Update: The 20% discount code for OSNews readers is "OSN."
Linked by Thom Holwerda on 05/11/13 21:41 UTC
"Windows is indeed slower than other operating systems in many scenarios, and the gap is worsening." That's one way to start an insider explanation of why Windows' performance isn't up to snuff. Written by someone who actually contributes code to the Windows NT kernel, the comment on Hacker News, later deleted but reposted with permission on Marc Bevand's blog, paints a very dreary picture of the state of Windows development. The root issue? Think of how Linux is developed, and you'll know the answer.
Linked by Thom Holwerda on 05/08/13 14:22 UTC
This is one of those news items that's fun to write, fun to read, fun to comment on, and where no one will be able to say anything unkind. It's all just one big ball of awesome fluffiness. TuneTracker, the BeOS radio automation software, has just released something very special: TuneTracker System 5, the first version designed entirely and specifically for Haiku. In fact, it actually includes Haiku in the software package. Better yet, TuneTracker also unveiled several system-in-a-box products - which have Haiku and TuneTracker pre-installed.
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Exactly twenty years ago, a document was published that played a huge role in establishing the web as we know it today. Twenty years later, and this simple and straightforward document is proof of an irrefutable fact: while closed technologies can change markets, open technologies can change the world.
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Oh multitasking. That staple of computing that got thrown out the window with many modern smartphones. We got some rudimentary thing in its place - but even as multitasking on phone and tablets improves, its user-visible side remains cumbersome. Windows 8 has a neat implementation, and now it's time Android follows in it footsteps.
Linked by Thom Holwerda on 04/24/13 22:24 UTC
They're here! Whether that excites you or not remains to be seen, but the Galaxy S4, which will most likely become the best selling Android smartphone of the year by a huge margin, has been reviewed by all the major sites, and there's lots of interesting conclusions in there - although I think most of you will get the gist.
Linked by Thom Holwerda on 04/18/13 11:21 UTC
Nokia has posted its quarterly results for the first quarter of 2013, and just like the quarters that came before, there's not a whole lot of good news in there. The rise in Lumia sales still can't even dream of making up for the sales drop in Symbian phones, and when broken down in versions, the sales figures for Windows Phone 8 Lumias in particular are very disappointing. In North America, Nokia is getting slaughtered.
Linked by Thom Holwerda on 04/16/13 9:29 UTC
The day has finally come: Google has started shipping Google Glass to the lucky few early adopters. Now that it's shipping, Google has also unveiled a lot more about the API and the specifications of the device itself. While the company had already given out substantial details at earlier occasions, there are still a few surprises here.
Linked by Thom Holwerda on 04/15/13 22:44 UTC
Almost exactly three years ago, I wrote about why OSNews was no longer OSNews: the alternative operating system scene had died, and OSNews, too, had to go with the times and move towards reporting on a new wave of operating systems - mobile, and all the repercussions that the explosion of smartphones and tablets have caused. Still, I was wondering something today: why aren't we seeing alternative operating systems on mobile?
Linked by Thom Holwerda on 04/14/13 18:22 UTC, submitted by MOS6510
You can say what you will about Windows Phone and Windows 8's Metro interface (I refuse to drop that name) - it's inefficient, unpopular, cumbersome, beautiful, ugly, organised, clean, limiting - but there's one thing we can all agree on: it's unique and distinctive. CNet has published a profile of Microsoft's Albert Shum, the man behind Metro, and he highlights what I think is at the very core of Microsoft's problems in mobile right now.More Features »
Sponsored Links
Member since:
2010-03-08
* embedded systems
* mobile Phones
* tablets
* desktops
* servers
It would just have a minimal hardware abstraction layer. This HAL only would cover CPU, busses and memory. Only this tiny HAL and a small VM "bootloader" would be CPU Architecture dependend.
Okay, until there I follow you. Sounds like a microkernel.
There I'm lost. It sounds like you would like to write almost all of this OS in interpreted code. This basically means recompiling most of the OS at every boot (except is JITed code is cached in some way). Performance would be horrible. Apart from technological achievement, what's the point of using this instead of platform-independent compiled languages like C and C++ ?
Again, why not a microkernel and high-level components written in platform-independents component languages instead ? What's the added benefit ?
Couldn't a properly done GUI infrastructure optimize for both ? (I'm thinking about this in my own OS project, but I'm not there yet so I can't tell about it being doable in practice)
Edited 2010-10-25 13:47 UTC