Become a fan of Slashdot on Facebook


Forgot your password?
Check out the new SourceForge HTML5 internet speed test! No Flash necessary and runs on all devices. ×

Comment Re:A modular PC? That's an amazing new idea... (Score 1) 78

The first Athlon CPU models from AMD used the EV6 bus from DEC (albeit on a slot connector like the Pentium 2/3), and plans floated around to build motherboards compatible with both Athlon and DEC Alpha 21264 CPUs only requiring a firmware swap (and an adapter card for the 21264).

I also hazily recall some computer vendor that came out around the time of the original BeBox that sold a computer claimed to have a modular motherboard, with expansion slots, memory, CPU bus, etc. on separate modules, but the name escapes me.

Comment Re:can somebody explain (Score 3, Informative) 83

It can't be that much different from emulating the games in some other language or platform. You'd have to emulate the CPU and chipset, collect input from the user (keyboard and mouse at least, and holy shit joysticks too!), and output the graphics (HTML5 Canvas) and sound (HTML5 audio) to the browser. Given that the MC68000 family of processors and the Amiga chipset have been emulated many times before already, plenty of inspiration exists to get you started.

Comment Nope (Score 1) 105

I don't see Philadelphia in the list of future or even potential cities for expansion. Shit, not even a single city within a six-hour drive. Nothing in the Northeast. The closest seems to be Raleigh-Durham. At this rate, it just looks like yet another half-assed Google project ready to go on the chopping block.

Comment Re:Couldn't have happened to a nicer company (Score 1) 47

It depended on smart compilers that just did not work. It's one advantage was a large memory space and AMD took that away. It was one of two big fumbles that Intel made at the time, the other was Netburst.

Intel had already ventured into the depend-on-smart-compilers rabbit hole before IA64 and Netburst with the 432, a ridiculous 32-bit stack-based object-oriented processor released before the 80386. The 432 failed, in part, because none of the compilers available for it could optimize code sufficiently well to work around its many crippling features (16-bit ALU, 16-bit data buses, 16-bit segment offsets, slow clock speeds) and it ended up slower than the 8086.

Of course if Motorla had an inexpensive 68000 available and IBM had used it in the PC we would all have been much better off.


The same is true if Apple, Atari, and Commodore had use the 6809 but the 6502 was also cheaper.

Not quite. Yes, it was cheaper, but the 6502 was by all accounts just as good as the 6809. Nevertheless, Apple, Atari, and Commodore all ended up migrating to the 68000 family in the end with the Lisa/Macintosh*, ST/TT/Falcon, and Amiga.

* the II GS was a dead-end

Comment Re:Wow the car knowledge here is bad (Score 1) 238

If water enters the exhaust and the engine is running, this is usually not a big deal because the air pressure from the engine will push it back out. Also, the exhaust valves don't suck in air so it will take some serious water pressure to get past those.

One only has to look at the wet exhaust systems used in boats for an example of what happens when water enters the exhaust. Hell, they even introduce water in them deliberately.

Comment The unrelenting march of technological progress (Score 5, Interesting) 164

This 1 TB/day threshold rang a bell as I remembered a BSD trumpeting a similar record, albeit in the opposite direction, in the late 1990s... and sure enough, Slashdot covered it back then:

Wcarchive Does 1.39tb In 24 Hours

Back then people had serious discussions about what sort of storage controller, network interface, and upstream connectivity was needed to achieve this result. Nowadays we can stuff that same performance in a trouser pocket. What an age to live in.

Comment A few ideas (Score 4, Insightful) 1839

Just a short list of ideas off the top of my head: * UTF-8. I used to get around it by using HTML entities, but nobody ain't got time for that now, and it's been a source of complaints for over a decade. * Click-bait headlines have no place in a site dedicated to serious technical subjects (or that at least takes technical subjects more or less seriously). * CmdrTaco, Hemos, and the rest of the original crew used to occasionally become involved in the discussions and rarely felt the need to withhold their opinions (iPod, anyone?), which gave the site a more personal feel -- a hybrid between a blog and a news site. This still can be seen in sites like some of the sites run by Gawker Media, and it seems effective in maintaining the readers involved. * If there will be editors, they ought to edit.

Comment Re:Microsoft (Score 4, Insightful) 200

True, Nokia was in trouble well before the WinPho fiasco, but Symbian was just a sympton rather than the disease. Management had allowed the company to branch off into different product lines and encouraged competition between them with apparently little fiscal oversight and paying no attention to the third-party developer community. So, they had S40 engineers working on almost-smartphone handsets to challenge low-end S60/Symbian handsets, S60 engineers trying to widen their product range, and Maemo/MeeGo engineers trying and failing to prove that their otherwise unwanted bastard child was a much better platform. While the managers had their heads firmly esconced in their rectums, Elop took advantage of their indecision and gave them a false sense of hope. Or, maybe not. There's a theory out there that Nokia management knew that they had a shit sandwich on their hands before Elop came along, and sought a way to wipe the slate clean without taking the blame directly if things went wrong. Microsoft and Elop appeared at the right time with an offer that they would happily not refuse: take a large amount of money in exchange for them taking out the trash for you, money that you'll be able to use to restart your phone business from the ground up in a relatively short time frame.

Slashdot Top Deals

Five is a sufficiently close approximation to infinity. -- Robert Firth "One, two, five." -- Monty Python and the Holy Grail