Google Brings AmigaOS to Chrome Via Native Client Emulation
First time accepted submitter LibbyMC writes "Google's approach to bringing older C software to the browser is demonstrated in bringing the '80s-era AmigaOS to Chrome. 'The Native Client technology runs software written to run on a particular processor at close to the speeds that native software runs. The approach gives software more direct access to a computer's hardware , but it also adds security restrictions to prevent people from downloading malware from the Web that would take advantage of that power.'" Chrome users can go straight to the demo.
So an emulator running on 2010 era hardware can almost run at speeds of the native technology on 80's era hardware.
wow
If I want an emulator, I'll get an emulator.
We must go deeper!
.... this will be found under the "apps" chrome browser links .... right along with Facebook...
a new Duke Nuke... errrr ..... nevermind...
What's the point of this recent spate of in browser OS inception? Do we really need yet another abstraction layer in the software stack? It would seem that these guys want to make it so.
What kind of processor and internet pipe will I need to run Amiga OS, inside Chrome, on "my" Chromebook?
So it takes 20 years to finally get a Great OS on my modern computer, though it runs on top of a crappy OS (Windows. Yes, i know a lot of peeps run Linux, but I'm referring to Windows, because Linus isn't really a crappy OS).
Sweet!
All joking aside, I've always thought the AmigaOS should of went to a linux kernel and brought the sweetness of the Amiga OS as a GUI.
Be seeing you...
A browser running in a browser would be even more secure.
There is not going to be a second time, kthxbye.
With Chrome Version 31.0.1650.63 on OSX 10.7:
Error: NaCl module load failed: PnaclCoordinator: Compile stream chunk failed. The PNaCl translator has probably crashed.
Needs Chrome 31 or high, no iOs or Android. Also:
/. is really loosing it.
Version 30.0.1599.114 Ubuntu 13.10 (30.0.1599.114-0ubuntu0.13.10.2)
So Windows only.
Please stop with cutesy loading messages (reticulating splines, fetching slippers, percolating coffee). You were too lazy to include an accurate bar indicating when the loading process would finish, and you are insulting our time wasted looking at your "jokes".
Why the hell would I want my browser to be able to do that?
This just smacks of something which is going to become a huge security issue, even if Google is trying to prevent malware.
Lost at C:>. Found at C.
As a former long time Amiga user, this seems to work pretty well on the outset, and gives an authentic experience in regards to the clock timing and boot time. (though it thankfully may be a little faster :) ) It looks like they are using the emulation code from Cloanto (Amiga Forever) which has been around for quite a long time now.
This OS and demos may look very simple to younger folks, but it was quite groundbreaking at the time. the H.A.M. (Hold and Modify) demo showing 4096 colors was pretty impressive at a time when most PCs were stuck with 256 colors. There are a lot of really nice demos for the Amiga from the demoscene that took all of that a step further even, hopefully someone thought to save and compile them.
The only issue I ran into so far is on the juggler demo, the ESC key is needed to exit the demo, while on the emulator the ESC key is what switches you away from the emulator mouse to your native mouse, so it does not trigger an ESC on the Amiga. (you need to reset the emulator) Juggler doesn't let you pull down the screen to reveal the workbench. There may have been a keyboard shortcut that I have forgotten about to toggle screens. I haven't touched an Amiga in 20 years.
Hats off to the coders, brought back a lot of memories.
Sometimes, Google just baffles me. The lack of direction in their product lines makes me shake my head.
We have several distinct software platforms:
1) Android. Development in XML with Java used as glue to hold everything together. Unless you don't. You can use standard C libraries and call the Linux kernel directly, bypassing the Dalvik Java VM.
2) Chrome browser. Development largely in javascript, again there are some obvious exceptions. Javascript is, of course, preferred because it's safer, so ChromeOS protects you by having everything done in Javascript. Except that it isn't.
3) ChromeOS. Kinda/Sorta like using the Chrome browser, except that it's not, because you are developing things that run as if they were actual clients. In Javascript. And of course, this too, is just as strictly enforced.
4) But Let's not forget the 4th platform in the trio: Google's Go language is clearly a contender, and it's designed to replace C, except for a few bone-headed decisions like linking everything statically resulting in enormous binaries. Because you really, really need to have the same library installed once for every app installed, because that way you get to recompile everything installed on your system any time a security update comes out for your favorite library. Except that, of course there are exceptions here, too.
And most importantly, you cannot target all these platforms with any single codebase written in any language. It's like they are trying to make their product suite as difficult as just using products from multiple vendors anyway.
I have no problem with your religion until you decide it's reason to deprive others of the truth.
Just think about all the great old Amiga/Commodore-64/etc games you could sell using something like this. I'll pay good money for Bard's Tale I/2/3 and Raid on Bungling Bay.
Wish they ported it to asm.js, at least that works in other modern browsers. But hey, that wouldn't upsell their own replacement web stack components, so I can sympathize. Far better to create their own tech no one else wants then it is to put their resources into something like Shumway or other tech that wasn't invented there.
If it's not sync'd to the video refresh it's going to be a very choppy, tear-ridden experience.
"Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
What is this, ActiveX reborn?
Better known as 318230.
Whoohoo! Less than 20 minutes of tinkering with it and I got a Guru Meditation!
Aaaah, the memories...
I'm not a software developer, but as a long-time network admin it always struck me that shared libraries were a great idea except when they weren't.
Before I switched to FreeBSD, Linux always seemed to have headaches with shared library problems, with some apps not working with some versions of shared libraries and a general nuisance being made with multiple versions of shared libraries being around.
Windows, of course, has its reputation for DLL hell, which I think was more of an issue in really old versions than it is now.
Given the size of storage generally available now, is it really so bad to have statically linked binaries? It greatly increases application portability and version independence and probably makes package management a lot simpler and more risk-free since you don't have to worry about shared libraries.
I've always been tempted to do a statically linked buildworld to see just how much extra space it takes.
The beta looks pretty good the future of slashdot!
Really, the Amiga OS nowadays is just a plaything for a few very hardcore hobbyists willing to pay for overpriced, underpowered custom hardware that isn't even directly compatible with the original Amiga anyway. Amiga OS (and the original hardware) was fantastic in its day, and beat the living heck out of MS-DOS and early Windows, but that was a long time ago. Anyone for whom Amiga OS/hardware compatibility was essential or even useful would have been forced to give up and migrate elsewhere by the late-90s at most. For that reason, even if one *could* upgrade it to a modern OS, it'd make more sense just to write a new OS from scratch- the "classic" core would just end up being legacy baggage that would please the Amiga obsessives because they could call it Amiga OS, but have little real world use beyond muddying the design.
(Sorry, didn't want that to sound like a dismissal of the genuinely innovative Amiga OS, but things have moved on too far now).
Also, the rights to the various Amiga and Commodore IPs (names, hardware and software all separate) have been split up, passed around like a bad game of pass the parcel, sublicensed and disputed; I won't go into the details because (a) I can't be bothered and (b) I'm not sure myself! :-)
:-)
But... yeah. Technically, last time I heard you can still buy a "modern" AmigaOne and run the new versions of AmigaOS on it.
(*) Though that may be for values of "active" comparable to the rate of flow of glass in medieval windows. And yes, I know that's possibly a myth.
(**) To be fair, this is mentioned on Slashdot at regular intervals, so it's possible that many of you are aware of this anyway. The rights to the Amiga name, to manufacture the hardware and to the OS http://news.slashdot.org/comments.pl?sid=2710941&cid=39268663
"Slashdot - News and Chat Sites Deviant". (Click "homepage" link above for details).
That allows ASM.JS to do C64 emulation in a much more cross-browser compatible way.
Meanwhile Here's the Unreal 3 engine running using ASM.JS
They are running Amiga OS 1.3 please...... At LEAST be able to do AmigaOS 2.1..
The Truth is a Virus!!!
So, Google have done a deal with cloanto for the ROM licensing? Thought not...
I run: Windows, OS X, Linux, FreeBSD. Just because you have a hammer, doesn't mean everything is a nail.
Amiga is always surfacing with new purchasers with great plans that
never work out. This one just might fly.
I've honestly been avoiding Chrome like the plague, if someones trying
to force something on you, I figure it can't be a good thing. I mean you click
the wrong area on just about any web page you find yourself downloading
Chrome.
But this Amiga things got me, I have two other boxes just like this one http://i42.tinypic.com/2hwpx82.jpg
all Amiga related "stuff", mostly games.
I started on the TRS-80 III, and I couldn't find software for it, if I did it was spendy
and just what Radio Shack stocked, I learned Assembly language only because an assembler showed up.
So when I got the Amiga I grabbed everything Amiga I could due to the famine I had with the TRS-80. :} and was happy to copy whatever you brought
I was the one you visited if you wanted Amiga software
with you.
I still have two Amiga 500's, a 2000 and a 3000; that 3000 is like a bad penny. I enjoyed it :}
very much, ran a BBS from it, then sold it... twice; it always returned as a "gift"
I really would like to see this same setup in asm.js to see how it compares.
I wrote a Commodore PET, Vic-20, C64 and Apple ][ emulator in native-client as well. You can play with it here: http://www.scale18.com/nc/game/game.html
I got a Guru Meditation!
-- 29A the number of the Beast