I'll ignore the web-based X programs issue since I've already mentioned I'm against serving application inside the browser.
As for the Slashdot comments, Slashdot should be an App. In fact, Slashdot is a prototype for apps like feedly. Though the comments could still be served as read only on the html side... Somewhat like email lists archives.
As part of Chrome. Using the browser's own APIs. Similarly, you can use Mozilla's Marketplace in the desktop version of Firefox... Like I said earlier, a pox on both houses.
Even if the security issues could be put to rest, there's no justification for running applications in a document viewer. If Google is so concerned with serving up cross platform applications, they can package a VM and an App Store along with their browser. They can even conceive of their own URI scheme that will pass requests to the App Store to download and initialize Apps on the VM.
Is it really too much to expect something better then serving GUIs the likes of Facebook and Gmail inside the browser?
Yes. I am against both. Cross platform programming as an Interpreter running in a sandbox (JavaScript) or a bytecode VM (Java, NaCl...) shouldn't be done through the browser. The Internet should be slightly expanded HTML1 and CGI as far as I'm concerned. Maybe with an exception for audio\video if we can agree on a codec...
Keep application development and serving to the likes of Android's Play Store + Dalvik.
IBM should just scale back the Power series to the desktop. Just give us some nice RISCs. Now that their AMD acquisitions aren't panning out, they can use AMD's personal to get it done. They can even use the ATI patents to integrate graphics so they really are well positioned for the project.
Or maybe they can get their hands on MIPS. ImgTech doesn't seem to be doing anything useful with them. And coming around from both the low and the high-end will be quite devastating for Intel. Even pick up ImgTech along the ride.
Seriously, just spend it on desktop and mobile R&D. Linux is moving along fine right now and marketing your current line of 30000$ servers won't change anything.
The Linux scheduler under-prioritizes user interaction (keyboard\mouse\remote input and monitor\serial output) over disk and memory i/o by design since it's a server OS. There are out of tree schedulers that resolve all that and even a few Real Time ones that can guarantee interaction but Linus (justifiably) rejects them since Linux IS a server kernel.
Excellent read. FYI When discussing the ISO process it's useful to consider that committees of all kinds still operate under the same conditions and are composed by equally "qualified" personal...
It should matter. It's money that could have been put into R&D and quality engineering. Instead of innovation, we're now busying ourselves with deprecating a 15 years old bad OS in favor of a 30 years old antiquated OS. It's the technological and financial gap that we should have had between the west and the east.
We stopped working an investing in improving cars. The Japanese automobile companies won. We stopped working an investing in improving medicine. The Indian generic pharmaceutical companies won. We stopped working an investing in improving computing. The Chinese companies won.
Ballmer's personal wealth means everything to me: It's what's broken with the system of incentives. It's a manager that can't care enough about the future. It's money being bled out from coders salaries to management and marketing salaries.
It feels like a chicken and egg thing. The researcher has been asked about the decline of an operating system, and offered the change in architecture as the main reason.
It doesn't matter if Intel's x86 is technically more RISC or more CISC in this context. Or what minicomputers and personal computers were at the time. The point is that x86 out sold DEC hardware.
We could debate the facilities the architecture has to offer, and mention the abstractions x86 systems (like Windows) responded with... But all that matters is that once you try to port the system to another architecture, you end up with an inappropriate api model and a legacy of language and system design choices that were done in a different decade, for very different needs, and for completely different capabilities.
I'm told we're headed into an age of extreme parallelism and possibly non volatile MRAM. I will be mighty disappointed to see a POSIX system ported to something like that. But no doubt it will happen and no doubt it will kill off the closed source systems that can't offer effortless cross compatibility at little to no price. And big companies are just not that flexible.
Last I've checked, VLIW isn't even in desktop CPUs. And Intel's Itanium failed EPICly. In embedded, VLIW are purely an Intel thing and minor ARM dominance. As for your "old 32 and 64-bit RISC code", can you post a snippet? I've only seen MIPS64 so far but I'm a little curious about ARMv7's if that's what you're referring to... Or is it something different altogether?
I wish they could take the opportunity and do some work on the packaging system. Now that systemd has pretty much overhauled most of the user land, and Wayland will be forcing them to write the whole dependencies trees anyhow, and they already have their new installer, I'd like to see something like a cross between GNU Guix and Gentoo Portage be made for Red Hat\Fedora.
It wouldn't have made much sense a year or two ago to redo everything. But now since they obviously need to clean house, they might as well get some added value in there.
After all, even typography is all about making text more readable and beautiful. And that's not too objectionable unless you're an MLA submission committee. I'm sure there was a time when spaces, capital letters and punctuations were debatable as crutches.
I would personally find use in an algorithm that highlights nouns or verbs to facilitate speeder reading. Another idea I have is an eye tracker in an eBook reader that will pick up on you getting stuck on a word and will sound it out for you to hear. If you're still stuck, it could pop up a definition and a thesaurus.
For little kids and with enough computing power, you can have a Dora animation to do it where appropriate. For all I care you can have clippy too. That much is definitely within Gates' desire.
Slashdot Mirror
What's wrong with using a simple, RESTful, HTTP API? You can even support a JavaScript client using the same client.
I'll ignore the web-based X programs issue since I've already mentioned I'm against serving application inside the browser.
As for the Slashdot comments, Slashdot should be an App. In fact, Slashdot is a prototype for apps like feedly.
Though the comments could still be served as read only on the html side... Somewhat like email lists archives.
As part of Chrome. Using the browser's own APIs.
Similarly, you can use Mozilla's Marketplace in the desktop version of Firefox... Like I said earlier, a pox on both houses.
Even if the security issues could be put to rest, there's no justification for running applications in a document viewer.
If Google is so concerned with serving up cross platform applications, they can package a VM and an App Store along with their browser. They can even conceive of their own URI scheme that will pass requests to the App Store to download and initialize Apps on the VM.
Is it really too much to expect something better then serving GUIs the likes of Facebook and Gmail inside the browser?
Yes. I am against both. Cross platform programming as an Interpreter running in a sandbox (JavaScript) or a bytecode VM (Java, NaCl...) shouldn't be done through the browser.
The Internet should be slightly expanded HTML1 and CGI as far as I'm concerned. Maybe with an exception for audio\video if we can agree on a codec...
Keep application development and serving to the likes of Android's Play Store + Dalvik.
NaCl is a good implementation of a terrible idea: i.e Running software in the browser is all kinds of wrong.
IBM should just scale back the Power series to the desktop. Just give us some nice RISCs. Now that their AMD acquisitions aren't panning out, they can use AMD's personal to get it done. They can even use the ATI patents to integrate graphics so they really are well positioned for the project.
Or maybe they can get their hands on MIPS. ImgTech doesn't seem to be doing anything useful with them. And coming around from both the low and the high-end will be quite devastating for Intel. Even pick up ImgTech along the ride.
Seriously, just spend it on desktop and mobile R&D. Linux is moving along fine right now and marketing your current line of 30000$ servers won't change anything.
prior to 1700 because their kids wouldn't stop kicking the ball around the backyard long enough to read the good book.
When stun is no fun.
And lethal is so primeval,
There's only one true eliminator,
The ACME disintegrator!
Now, for only 99.95$
VAT not included.
Let be more specific. He is describing Adobe Bridge.
The Linux scheduler under-prioritizes user interaction (keyboard\mouse\remote input and monitor\serial output) over disk and memory i/o by design since it's a server OS. There are out of tree schedulers that resolve all that and even a few Real Time ones that can guarantee interaction but Linus (justifiably) rejects them since Linux IS a server kernel.
Excellent read.
FYI When discussing the ISO process it's useful to consider that committees of all kinds still operate under the same conditions and are composed by equally "qualified" personal...
It should matter. It's money that could have been put into R&D and quality engineering. Instead of innovation, we're now busying ourselves with deprecating a 15 years old bad OS in favor of a 30 years old antiquated OS.
It's the technological and financial gap that we should have had between the west and the east.
We stopped working an investing in improving cars. The Japanese automobile companies won.
We stopped working an investing in improving medicine. The Indian generic pharmaceutical companies won.
We stopped working an investing in improving computing. The Chinese companies won.
Ballmer's personal wealth means everything to me: It's what's broken with the system of incentives. It's a manager that can't care enough about the future. It's money being bled out from coders salaries to management and marketing salaries.
Like it or not, it's holding back performance:
http://www.dabeaz.com/python/GIL.pdf
Through I don't condone OP, down the rabbit hole we go: http://cm.bell-labs.com/who/ken/trust.html
That's Golang's Ken Thompson in case you were wondering...
It feels like a chicken and egg thing. The researcher has been asked about the decline of an operating system, and offered the change in architecture as the main reason.
It doesn't matter if Intel's x86 is technically more RISC or more CISC in this context. Or what minicomputers and personal computers were at the time. The point is that x86 out sold DEC hardware.
We could debate the facilities the architecture has to offer, and mention the abstractions x86 systems (like Windows) responded with... But all that matters is that once you try to port the system to another architecture, you end up with an inappropriate api model and a legacy of language and system design choices that were done in a different decade, for very different needs, and for completely different capabilities.
I'm told we're headed into an age of extreme parallelism and possibly non volatile MRAM. I will be mighty disappointed to see a POSIX system ported to something like that. But no doubt it will happen and no doubt it will kill off the closed source systems that can't offer effortless cross compatibility at little to no price. And big companies are just not that flexible.
Last I've checked, VLIW isn't even in desktop CPUs. And Intel's Itanium failed EPICly. In embedded, VLIW are purely an Intel thing and minor ARM dominance.
As for your "old 32 and 64-bit RISC code", can you post a snippet? I've only seen MIPS64 so far but I'm a little curious about ARMv7's if that's what you're referring to... Or is it something different altogether?
The computer says No.
I wish they could take the opportunity and do some work on the packaging system.
Now that systemd has pretty much overhauled most of the user land, and Wayland will be forcing them to write the whole dependencies trees anyhow, and they already have their new installer, I'd like to see something like a cross between GNU Guix and Gentoo Portage be made for Red Hat\Fedora.
It wouldn't have made much sense a year or two ago to redo everything. But now since they obviously need to clean house, they might as well get some added value in there.
After all, even typography is all about making text more readable and beautiful. And that's not too objectionable unless you're an MLA submission committee. I'm sure there was a time when spaces, capital letters and punctuations were debatable as crutches.
I would personally find use in an algorithm that highlights nouns or verbs to facilitate speeder reading.
Another idea I have is an eye tracker in an eBook reader that will pick up on you getting stuck on a word and will sound it out for you to hear. If you're still stuck, it could pop up a definition and a thesaurus.
For little kids and with enough computing power, you can have a Dora animation to do it where appropriate. For all I care you can have clippy too. That much is definitely within Gates' desire.
So, overall not a bad idea.