Slashdot Mirror


Retro Roundup: Old Computers Emulated Right In Your Browser

An anonymous reader writes: If you ever wanted to program an Altair, an Apple I, or a COSMAC ELF you may think you either have to buy one (expensive now) or load and configure simulation software. However, there's a slew of browser-based emulators for everything from a PDP-11 to Windows 1.0 out there. Some use Java, but many use Javascript and many perform better on a modern PC then they did in their original. If you want to learn some history or just want to finally play with the computers you saw in the magazines 35 years ago, these are great fun and slightly addictive.

78 comments

  1. Re:Than they did in the original? Original what? by njahnke · · Score: 2

    than the original hardware. It's terrible writing but I can tell what is meant somehow.

  2. Re:Than they did in the original? Original what? by Anonymous Coward · · Score: 1

    Just because we can still understand it doesn't mean we should let people get away with bad writing. If people keep writing badly, this new bad form becomes the new standard.

  3. LOL .. cows? by gstoddart · · Score: 3, Funny

    Oh, come on ... I expected to see an "emulators are for cows" post by now. Someone is slacking off.

    Moo.

    --
    Lost at C:>. Found at C.
  4. Re:Than they did in the original? Original what? by CozmicCharlie · · Score: 1

    Just because we can still understand it doesn't mean we should let people get away with bad writing. If people keep writing badly, this new bad form becomes the new standard.

    I agree! We stop people from misusing the words "bad" and "badly".

  5. Zophar's Domain by martiniturbide · · Score: 1

    We keep trying at Zophar's Domain Javascript but we need more help.

  6. JSMESS by Anonymous Coward · · Score: 1

    No mention of JSMESS. The Hackaday editors are getting almost as bad as the Slashdot editors: http://www.archiveteam.org/index.php?title=Javascript_Mess

    1. Re:JSMESS by Anonymous Coward · · Score: 0

      good god.. why??

  7. Re:Than they did in the original? Original what? by jabberw0k · · Score: 1

    I should like to informate you, if you care to be orientated, that we increasingly hear more about malwares, softwares, firmwares, and hardwares. I recommend listening to some musics.

  8. Re:I have a better idea by jedidiah · · Score: 1

    ...plus, I don't see what the big deal is in terms of "installing an app". If the web version can be turnkey, then so can the 'app' variant.

    --
    A Pirate and a Puritan look the same on a balance sheet.
  9. Bunch of whiners in this discussion so far by kheldan · · Score: 4, Insightful

    Also, people who apparently either don't have any sense of fun, or perhaps they're all millennials and poo-poo anything older than they are, or maybe both. For cryin' out loud, people, these emulators for (in some cases literally) antique hardware aren't intended for 'serious' use, or development, or anything like that: They're intended to be fun to play with, or maybe educational since most of them are emulating systems that either don't exist anymore or are so rare that you'll likely never even see one in the flesh. Yes, some of us are old enough that we actually owned (or built, as the case may be) some of these systems, but again: If you're complaining about them then I question whether you have any sense of what's fun or not. When some of these computers were available, screwing around with computers was still fun; they're not as much fun in many ways now, because it's all too much serious business, and too much of it is closed-source, proprietary, locks the user out, physically inaccessible, or in some extreme cases you get prosecuted or sued in civil court for getting caught messing with it. In many cases some of the hardware may as well be potted in a solid brick of opaque epoxy, for all the good it'll do you to try to get at the actual hardware. Building a complete computer system from component parts (i.e. requiring soldering)? So impractical now as to be nigh-unto impossible (I could do it, but there's no point anymore). The closest thing we have anymore is you younger guys screwing around with microcontrollers (many of which are more powerful than many of the computers being emulated here, ironically enough), but even then you have to have an entire modern computer just to write the simplest code for them, there's no 'front panel' where you can enter machine code directly, one byte at a time. Don't knock it 'till you try it, guys (and ladies).

    --
    Are YOU using the TOOL, or is the TOOL using YOU? Think about it!
    1. Re:Bunch of whiners in this discussion so far by ArhcAngel · · Score: 2

      In many cases some of the hardware may as well be potted in a solid brick of opaque epoxy, for all the good it'll do you to try to get at the actual hardware.

      Actually there are numerous industries (auto being one) that do this very thing with their proprietary electronics.

      --
      "A person is smart. People are dumb, panicky dangerous animals and you know it." - K
    2. Re:Bunch of whiners in this discussion so far by kheldan · · Score: 2

      Actually there are numerous industries (auto being one) that do this very thing with their proprietary electronics.

      Heh, where do you think I got the reference from? I've seen things that were like that. I also used to (back in a previous life) repair arcade games; it was not at all uncommon in that industry for them to sand the part numbers off all the ICs on a PCB to deter pirates from copying the design. Would also make it damned near impossible in some cases to repair them.

      --
      Are YOU using the TOOL, or is the TOOL using YOU? Think about it!
    3. Re:Bunch of whiners in this discussion so far by Pseudonymous+Powers · · Score: 4, Insightful

      Agreed, for the most part. Most of the posters seem to be angry because these emulators are browser-based, because apparently native or app-based emulators for forty-year-old game consoles whose killer app was a purple block that chases a cyan block are for real, legitimate, artistic visionaries, while browser-based versions are for dumb stupid babies.

      This strikes me like a 45-year-old dude whose hobby is modelling 16th-century Spanish sailing ships in balsa-wood setting fire to the basement workshop of a 35-year old dude someone whose hobby is building 16th-century Portuguese sailing ships out of matchsticks after their parents naively set up a play-date for them.

    4. Re:Bunch of whiners in this discussion so far by ArhcAngel · · Score: 3, Interesting

      What I found most humorous was when I was working for a Delphi remanufacturing shop. GM's Delphi A/C Delco design engineers actually baked dummy circuits into their ECM's. They did nothing but if a component in the circuit went bad the entire unit failed. I think I repaired more dummy circuits than actual working circuits on that ECM.

      --
      "A person is smart. People are dumb, panicky dangerous animals and you know it." - K
    5. Re:Bunch of whiners in this discussion so far by Anonymous Coward · · Score: 0

      Actually, you have it backwards. It's millennials who are obsessed about javascript. They deserve all the hell they get for that.

    6. Re:Bunch of whiners in this discussion so far by Grishnakh · · Score: 1

      What are you talking about? The comments I see aren't poo-pooing emulation, they're poo-pooing *browser-based* emulation. Maybe you've gotten too old and forgotten, but I actually remember the days when applications ran natively on computers, rather than only in browsers with HTML5 and CSS and JavaScript. Native emulators for all these systems *already exist*, and have been around for many years, and they're naturally going to run far faster and have better features than anything that runs on a browser. Can a browser-based app save your NES game state at any arbitrary point so you can restore it? I doubt it. But I can easily do that with MESS, and I can play CastleVania without using all my (older) machine's memory too.

    7. Re:Bunch of whiners in this discussion so far by Anonymous Coward · · Score: 0

      > Can a browser-based app save your NES game state at any arbitrary point so you can restore it?

      Yes.

      > I doubt it.

      That's because you don't know what you're talking about.

    8. Re:Bunch of whiners in this discussion so far by 0dugo0 · · Score: 2

      With the help of emscripten native emulators are being ported to the browser, warts, features and all. See eg. JSMESS. For games this is great because there is often a ceiling for the speed you need and you can get it out of any recent hardware. There is _nothing_ easy about getting something to run natively in MESS the first time. If you want to share the CastleVania experience you can embed it in a tweet. How awesome is that!

    9. Re:Bunch of whiners in this discussion so far by kheldan · · Score: 1

      Holy crap, I thought the arcade game industry was paranoid, but that absolutely takes the cake, and as it turns out the cake really is a lie! XD

      --
      Are YOU using the TOOL, or is the TOOL using YOU? Think about it!
    10. Re:Bunch of whiners in this discussion so far by ArhcAngel · · Score: 1

      Yeah, they had a joint venture with Suzuki I believe it was where their ECM was being used in some cross branded vehicles and they didn't want Suzuki reverse engineering their circuit. What's funny is back then the whole thing was a few logic gates and some FETs to drive the fuel injectors. Nothing like what goes into them today.

      --
      "A person is smart. People are dumb, panicky dangerous animals and you know it." - K
  10. The article makes you believe by Anonymous Coward · · Score: 0

    that the browser is the only way to relive these old machines. There are high-quality emulators for all of those machines, most notably FS-UAE and WinUAE for all things Amiga. Running most of those machines in a browser, even the older simpler ones, will usually be a bad experience.

    1. Re:The article makes you believe by Anonymous Coward · · Score: 1

      Did you read the linked article? They talk about SIMH and replica hardware (like the one in the video which is pretty cool)

    2. Re:The article makes you believe by Anonymous Coward · · Score: 1
    3. Re:The article makes you believe by Anonymous Coward · · Score: 0

      Agreed, I can't believe anyone wants to experience gaming history on the same level as a fucking browser app. It looks terrible, it feels terrible.

  11. Re:Why run LUDDITE computers in APPS? by Anonymous Coward · · Score: 0, Interesting

    It's a waste alright. 4ghz cpus for what? To emulate old 8 and 16 bit machines in javascript? what a waste.. there are already better native emulators out there that run locally and provide much better experiences.

  12. Lots of interesting comments at -1 by Morgaine · · Score: 0

    Actually, there are plenty of rational comments in this thread, but they've all been moderated down to -1.

    Why all non-favourable comments have been greeted with "nuke from orbit" is an interesting question, but it's clear that in this thread, rational discussion and dissenting opinion is not welcome.

    Slashdot seems to be getting more and more like this. I've been here a long time, but I can't really say I know why it's happening. I don't. Maybe the art of nuanced discussion is disappearing from public spaces in general.

    --
    "The question of whether machines can think is no more interesting than [] whether submarines can swim" - Dijkstra
    1. Re:Lots of interesting comments at -1 by squiggleslash · · Score: 3, Insightful

      Well, 90% of them are off-topic, complaining about the wording, or just trolls about Java. I'm not entirely sure what nuanced discussion in the -1 realm you're referring to. I think the nearest I saw to a remotely reasonable modded down comment was a whine about how the poster felt the browser was not the right place for a computer emulator, which... didn't address even the reasons implied in TFS.

      Me, I'm very glad people are building these things. Keeping older platforms alive isn't just nice for nostalgia reasons, it reminds us of the good things we're missing today and stops them from being forgotten.

      --
      You are not alone. This is not normal. None of this is normal.
    2. Re:Lots of interesting comments at -1 by kheldan · · Score: 1

      I've been here longer than it appears I have, just lost access to my original account..

      What you're seeing happen here, is an influx of common, garden-variety trolls, along with some sad-sacks who, for whatever reasons, seem to only be interested in being negative and starting arguments solely for the sake of starting arguments, not because they have any particular viewpoint they want to defend. You're right, though, the overall tone of this place (and many places where discussions can happen on the Internet) has changed over the years. Don't let 'em get you down, though. I've found that identifying them, then dismissing them publicly and ignoring them seems to be effective; trolls and trouble-makers will go in search of the low-hanging fruit they seem to prefer once they discover that they can't get inside your head.

      --
      Are YOU using the TOOL, or is the TOOL using YOU? Think about it!
    3. Re:Lots of interesting comments at -1 by Anonymous Coward · · Score: 2, Informative

      Me, I'm very glad people are building these things. Keeping older platforms alive isn't just nice for nostalgia reasons, it reminds us of the good things we're missing today and stops them from being forgotten.

      The problem, as I see it, is that by doing it in Javascript, we're introducing a new dependency: the code will only work on a browser produced in 2015.

      That's because Javascript, as implemented in a browser, is itself is a moving target. Go on, just try to browse the modern web in Mozilla 1.0. Or Firefox 3.6. You'll find half the Javascript-dependent sites of 2015 simply doesn't work on older browsers. Sometimes it's performance-related (Slashdot's JS is a prime example of a site that took several seconds to render in older Firefoxes, but worked fine on IE), and some of it fails to render anything at all.

      Compiling C/C++ to native gives you a binary that, once compailed, will continue to work as long as the hardware does. Win10 runs 32-bit binaries that are 15-20 years old without compilation. Linux rebuilds from source are typically a "make" command away. (If such support is ever dropped, run a Linux or Windows gues in the VM hosting solution of 2030.)

      From the point of view of a software preservationist, I fail to see the point in adding a dependency on "Your 30-year-old ROMs now require whatever Javascript interpreter shipped with the binaries for Chrome 44-through-57, IE11 from mid-2014 to late-2016, and Firefox 41-through-56."

    4. Re:Lots of interesting comments at -1 by Anonymous Coward · · Score: 0

      What you're seeing happen here, is an influx of common, garden-variety trolls, along with some sad-sacks who, for whatever reasons, seem to only be interested in being negative and starting arguments solely for the sake of starting arguments, not because they have any particular viewpoint they want to defend.

      The same situation in discussion forums for various MOOCs usually written by millennials or broomstick-up-the-anus pedantic people. These days computers are less fun to explore than those older computers many of us owned.

    5. Re:Lots of interesting comments at -1 by Pseudonymous+Powers · · Score: 2

      The problem, as I see it, is that by doing it in Javascript, we're introducing a new dependency: the code will only work on a browser produced in 2015. That's because Javascript, as implemented in a browser, is itself is a moving target. Go on, just try to browse the modern web in Mozilla 1.0. Or Firefox 3.6. You'll find half the Javascript-dependent sites of 2015 simply doesn't work on older browsers.

      Is that strictly relevant? I think the dependency we're really introducing is: the code will only work on a browser produced in 2015 or later. If an emulator was originally built for Firefox 41, five years from now I won't care whether or not it runs in Firefox 1.0 as long as it still runs in Firefox 2020.

    6. Re:Lots of interesting comments at -1 by Anonymous Coward · · Score: 0

      Oh, look at that! We have a modern day Senator McCarthy on our hands! Here he is, spewing his "trolls" here, "trolls" there nonsense. He's even got a list of "trolls", too! It's funny that he can't actually define what a "troll" supposedly is, though. It just ends up being defined as everyone he doesn't like! Now that I've dared call him out on his bullshit, I'm sure I'll end up being mislabelled a "troll" by him, and I'll find myself on his "troll" list.

    7. Re:Lots of interesting comments at -1 by Anonymous Coward · · Score: 2, Insightful

      The problem, as I see it, is that by doing it in Javascript, we're introducing a new dependency: the code will only work on a browser produced in 2015. That's because Javascript, as implemented in a browser, is itself is a moving target. Go on, just try to browse the modern web in Mozilla 1.0. Or Firefox 3.6. You'll find half the Javascript-dependent sites of 2015 simply doesn't work on older browsers.

      Is that strictly relevant? I think the dependency we're really introducing is: the code will only work on a browser produced in 2015 or later. If an emulator was originally built for Firefox 41, five years from now I won't care whether or not it runs in Firefox 1.0 as long as it still runs in Firefox 2020.

      Correct. That's the point I was trying to make. I do not believe the JS of today will run in Firefox 2020. The language is still evolving. (Not as bad as Perl4/5/6 or Python2/3, but it's still fragmenting.) The assumption - possibly fallacious - is that because the JS of 2015 doesn't run in the browsers of 2010, the JS of 2010 probably doesn't run in the browsers of today, because things can be deprecated and removed from the standard as well as added to it. Does the BLINK tag work today? I'm glad it doesn't, but you get the point...

      Code compiled for x86 has a better track record of backwards compatibility; the odds are much greater that a Win10 x64 binary will run on Windows 2020, and an ELF compiled today will be compatible with the ABI of Linux Anydistro 2020, than it is that anything written in the JS of today will run on Anybrowser 2020.

      We're now dependent on two sets of developers: one set of crusty greybeards to can translate 8-bit schematics into code, and a second set of bushy blackbeards who can translate anything into Javascript. Advantage to the blackbeards for cross-platform compatibility, but I hope they're still around 20 years from now.

    8. Re:Lots of interesting comments at -1 by Anonymous Coward · · Score: 1

      He's even got a list of "trolls", too! It's funny that he can't actually define what a "troll" supposedly is, though.

      Got to love it when they self-identify like this.

    9. Re:Lots of interesting comments at -1 by Anonymous Coward · · Score: 0

      Oh yes, you mentioned the keyword: machine independence. If you target JS you can run it on your desktop...... and mobile, and tablet, and refrigerator, and car, and whatever device you have that can run firefox... and this is rather a big deal.

    10. Re:Lots of interesting comments at -1 by ras · · Score: 4, Informative

      The problem, as I see it, is that by doing it in Javascript, we're introducing a new dependency: the code will only work on a browser produced in 2015.

      Well you can rest easy then, because no one is writing this stuff in JavaScript.

      What triggered this change is Emscripten, which is a back end for LLVM that targets ... JavaScript. Actually it targets asm.js, which runs at about 1/2 native speed in Firefox (not so fast in Chrome, because Google thinks the solution to the same problem is NaCl).

      What that means is any compiler that uses LLVM can now compile to asm.js. Which means any program written in Python, Rust, Go (there are a whole pile of languages) can now be compiled to run in the browser. In particular Clang is a C compiler for LLVM. Dosbox is a x86 + MSDOS emulator, written in C. Ergo Dosbox can now be compiled to JavaScript and this run in the browser. Js-dos is a site apparently dedicated hosting games that does just that. The game console emulators are also written in C. So they to can and now have been compiled to asm.js. Because modern web browsers support WebGL, OpenGL games that have been open sourced (like Quake3) have also been compiled to JavaScript, and run spookelly well. Which is how we get to the plethora of games mentioned in the article. Pity it didn't mention the technology behind it.

      But why stop a games? Sqlite3 has been recompiled for Javascript. It can do in browser SQL queries in about 2ms, and is a damned site nicer to use than wandering through a spiderweb of Javascript objects. But why stick to something sane? You can now do ffmpeg encoding in your browser.

    11. Re:Lots of interesting comments at -1 by Anonymous Coward · · Score: 0

      Since when have we expected old software to handle new formats? That's called "forward compatibility" or "future-proofing," and you have to be very careful to make it work. Almost no software is made this way; the expectation is that the platform will evolve, and sooner or later you'll have to update your software.

      Backward-compatible browsers, like we have now, will handle old formats as well as new. Your assertion that "compiling C/C++ to native ... will continue to work as long as the hardware does" is not strictly true. I have lots of old software that sort-of-runs, but either crashes, freezes, has a messed-up interface or otherwise misbehaves. It's more by accident than by design that so much software continues to work, mostly because BIOS+x86+Win32 has been kept around way past its prime.

  13. Re:Than they did in the original? Original what? by Anonymous Coward · · Score: 0

    So every anonymous poster to the internet needs a grammar checker?

  14. Java might be faster than my PDP-11/05 ? by jpellino · · Score: 2

    If not, I'm shipping the whole thing out to Sun, postage COD.

    --
    "Win treats sysadmins better than users. Mac treats users better than sysadmins. Linux treats everyone like sysadmins."
  15. related: My native FLEX / 6809 machine emulator by fyngyrz · · Score: 4, Interesting

    My native FLEX / 6809 machine emulator (for Windows XP and at least several Windows versions on up... don't use Windows any more, so I dunno. :)

    Late-70s / early-80's machine era.

    Front panel, graphics card, single stepping, lots of software including assemblers and compilers. Stable.

    If you ever used 6809 Flex, you'll be right at home. Otherwise, probably don't bother.

    --
    I've fallen off your lawn, and I can't get up.
    1. Re:related: My native FLEX / 6809 machine emulator by complete+loony · · Score: 2

      A friend of mine is building a C65 clone. It started as a hobby, using an FPGA to implement the CPU, RAM, sound & video chips. But a whole bunch of 8-bit enthusiasts have joined together to start building everything from cases to IO boards for connecting original peripherals.

      --
      09F91102 no, 455FE104 nope, F190A1E8 uh-uh, 7A5F8A09 that's not it, C87294CE no. Ah! 452F6E403CDF10714E41DFAA257D313F.
  16. SGI? by iCEBaLM · · Score: 1

    Still no MIPS SGI emulators, I want my IRIX damnit!

    1. Re:SGI? by mvdw · · Score: 1

      Yeah, agreed. I have some old proprietary IRIX software I'd really like to be able to run, and don't want to have to fire up (read: make work) any of the old SGI hardware I have lying around. Would be better if I could just emulate it...

  17. Re:Why run LUDDITE computers in APPS? by Anonymous Coward · · Score: 0

    ikr, and what are magazines anyway? Is that what 8-bit apps used to be called or something?

  18. Re:Than they did in the original? Original what? by JustOK · · Score: 1

    Or grammar chess for the more advanced.

    --
    rewriting history since 2109
  19. Re:Than they did in the original? Original what? by Anonymous Coward · · Score: 0

    Checkmate!

  20. Re:Than they did in the original? Original what? by Anonymous Coward · · Score: 0

    If they're using Chrome, they've already got one built-in.

  21. TRS-80 Basic by CohibaVancouver · · Score: 1

    One thing that was cool about my TRS-80 Model I (and indeed of most PCs 35 years ago) was it booted straight into a BASIC interpreter. You cold literally start typing BASIC - And many of us did.

    Kids today.

    Now get off my lawn.

    1. Re:TRS-80 Basic by rsclient · · Score: 1

      My first computer was a ZX80 -- fond memories!

      I liked it enough that my hobby Calculator app for Windows is now programmable in BASIC. It turns out that making a BASIC interpreter is pretty simple these days; there's a bunch of parser-generators to make it simple to program up the language, and modern computers are super-fast even when dealing with non-optimized code. In fact, the hard part is that people expect more GUI bits in the code, and getting those to all work took longer than the actual programming.

      The downside is that it doesn't emulate any particular computer, and it's missing some nice features like "graphics" and "multiple statements on a line".

      Link to app: https://www.microsoft.com/en-us/store/apps/best-calculator/9wzdncrdfd6x/

      Link to manual: https://bestcalculator.files.wordpress.com/2015/09/bestcalculatorbasicreference.pdf/

      --
      Want a sig like mine? Join ACM's SigSig today!
    2. Re:TRS-80 Basic by __aaclcg7560 · · Score: 1

      The TRASH-80 was before my time. I got the Commodore VIC-20 and 64 in the early 1980's when I became a teenager.

    3. Re:TRS-80 Basic by ag0ny · · Score: 3, Interesting

      That's actually how I learnt to code as a child, using MSX-BASIC. I'm now 40 and still using MSX computers (real hardware, though the emulators are useful for development).

      If you're interesting in learning to code for these things (they're Z80-based, like the TRS-80), I'm writing a course about coding with the MSX-C compiler. 26 chapters released so far:

      http://www.lavandeira.net/rele...

  22. Re:Than they did in the original? Original what? by pteddy · · Score: 1

    Thanks to you. I will do the needful.

  23. Ohio Scientific by tomhath · · Score: 2

    Wow, blast from the past. My first ever computer was an Ohio Scientific "Superboard"; single board computer with a keyboard on the motherboard, no case, power supply, or monitor. Came with 8KB of RAM, only ran Basic (Copyright Microsoft, 1978) and 6502 assembler (entered in hex). You could load and store your programs to cassette tapes at 300 baud. At the time I was programming IBM/370 mainframes at work in FORTRAN IV. Now get off my lawn.

    1. Re:Ohio Scientific by Anonymous Coward · · Score: 1

      On the UK version (UK-101) you could mod the UART to use 600 or 1200 baud for the cassette, and another hardware mod let you switch between 1 and 2 MHz clock (which made PacMan very difficult).

    2. Re:Ohio Scientific by Anonymous Coward · · Score: 1

      My C1P (US version, with case) was moded to 600 baud cassette, and 2MHz clock; so it wasn't just the UK version that could do this.

  24. Re:I have a better idea by tomhath · · Score: 1

    How about you support the app on Windows, Mac, and Linux? Oh wait, the browser does that already.

  25. Nerd sniped by Anonymous Coward · · Score: 2, Funny

    Damn this article, ended up playing Rogue for almost two hours.

  26. Reversi? by KatchooNJ · · Score: 1

    All I need to know... Does Windows 1.0 come with Reversi?

    --
    "Never give up, for that is just the time and place when the tide will change." -Harriet Beecher Stowe ^_^
  27. The Unix emulator is broken by LichtSpektren · · Score: 2

    It keeps printing SYSTEMCTL: NOT FOUND. What's up with that?

    1. Re:The Unix emulator is broken by pla · · Score: 1

      Just mount the partition from any ol' bootable CD and 'cat' the logs to get more information.

      Oh, wait...

    2. Re:The Unix emulator is broken by Anonymous Coward · · Score: 0

      Press the run button. Then when it prompts @ type: unix Then press enter. cd => chdir backspace => # line delete => @ lower case => stty -lcase (or is it --lcase?) Control+C => Del Control+D => PrtScr

  28. Re:I have a better idea by khellendros1984 · · Score: 2

    I am positive that every system emulated in Javascript already has native-code emulators available on those 3 OSes and more. Plus, they'll be available offline and use a fraction of the processing time to run full speed. This is a plus if I want to run some of them on my older laptop with a 4:3 screen, or if I want to use my kinda crappy tablet with its attached keyboard; neither of those systems is necessarily fast enough to run the emulators with the extra Javascript overhead (at least, it would limit me to the older systems, probably pre-90s).

    If I want to try something out as a one-time thing, want to access it from multiple computers, or can't install software locally, then sure, I might choose to run the Javascript version of the software. Both ways have their benefits, and that's pretty obvious.

    --
    It is pitch black. You are likely to be eaten by a grue.
  29. BASIC be damned! by Alwin+Henseler · · Score: 2, Funny

    Built-in BASIC = cool, you say? Damn you!

    I've wasted countless hours in my life typing BASIC, only to achieve modest results. If only a more powerful language had been included in those machines... Say Forth, or C, or Lisp, or <insert structured-language-of-choice here>. Had any such language been built into popular machines of the day, science and technology would have advanced so much faster that every citizen on this planet would have had his/her own flying car and faster-than-light spaceship by now. But no... BASIC.

    I've made many attempts to bring a logical structure into my BASIC programs. To number lines in steps of 10, in order to insert lines as needed. To reserve a range of line numbers for sub-routines. Only to find out that for programming, line numbers AREN'T NEEDED IN THE FIRST PLACE. Or editing - using a "LIST" command to show a few lines, move cursor to one, edit a copy of it elsewhere on screen, and have it inserted back in. Only to find out later that editing text is easily done full-screen. Yes... BASIC.

    Then I found out about machine code. It was like being in coder's heaven, being God of the machine, but very difficult because it was like inching forward with tiny, dangerous steps on a minefield all the f**king time. Knowing that you'd still need that BASIC interpreter to get running, and that the same BASIC interpreter would often get in the way, and eat globs of precious RAM even though you weren't using it anymore. And that no assembler was built in, because there wasn't any room left in the ROM after putting BASIC in there. Grrr.... BASIC.

    And let's not get started about the days of Disk Operating Systems. Cryptic commands to do even the simplest of tasks, that low-and-behold actually made a machine somewhat useful.

    And to add insult to injury, it turned out that even for low-spec-machine-I-was-stuck-with-because-dad-couldn't-afford-anything-better, many of those more powerful languages were actually available! Some even for free! So manufacturers could have built them into their machines! But no.... BASIC.

  30. Hello, world! in PC assembly by Anonymous Coward · · Score: 0

    b:
    debug
    a
    mov ah,9
    mov dx,109
    int 21
    int 20
    db "Hello, world!$"
    <enter>
    g

    1. Re:Hello, world! in PC assembly by Anonymous Coward · · Score: 0

      Heresy! intel, DOS?! Try DEC alpha and AT&T syntax, lamer.

    2. Re:Hello, world! in PC assembly by Anonymous Coward · · Score: 0

      OK. You've got a DEC Alpha emulation that runs in the browser?

      No?

  31. Republicans killed them by Anonymous Coward · · Score: 0

    Republicans hate cows, it is the way of their kind.Trumpet, trumpet, trumpet.

  32. Re:I have a better idea by Anonymous Coward · · Score: 0

    > How about we don't do it in the browser (for a change)? I have a proper operating system already.

    That's great until you want to show it to someone else.

    "Hey, check out this cool emulator I was playing with at home. First, let me download this package and unzip it and then install it and all its dependencies, then configure it and play around with the settings to find out why it doesn't work on your video card and why there's no sound...

  33. Re:Why run LUDDITE computers in APPS? by Anonymous Coward · · Score: 0

    Tell you what, if I buy a single-core 1GHz CPU to play with these, will you approve?

    Oh, forgot... I don't care what you think.