Well, that explains the post. However, that's not 1337, that's LOLCAT; a derivative of texting language, itself a derivative of common IRC abbreviations.

1337-5p34| was developed to make the text hard to read/index and was "cool" for the hip 90's h4X0rz generation. i.e. Back when putting Zs on everything was kewl. :-P

I'd insert some completely random references that make fun of the movie Hackers, but that would be admitting far too much about my knowledge of the 90's computer culture. ;-)

My first reaction to the parent post is, "I'll bet he encoded a cool circuit design into the ASCII of his text!!! COOL!"

Then I realized he was posting from a cellphone. Probably the same one he had when he learned HDL "10 YEERS AGO". :-P

Now that Xilinx has released new chips, the old ones are pretty cheap.

The old ones were always cheap. I got my Spartan-3 kit about 5 years ago for $150. That's what the smallest Xilinx kit is selling for now.

As many people have pointed out, FPGAs are so cheap now that there are plenty of other boards for less. My problem with those boards is that you don't often get the comprehensive devkit you get from Xilinx. As a hobbyist getting started with FPGAs, I found the Spartan kit to be incredible at hand-holding you through the basics of getting into hardware design. Diving into logic theory took care of the rest.

The board layouts ended up being far more of a challenge. Without an instructor to guide you, getting the correct solutions for circuit voltages was a bit of a challenge. Not to mention selecting the right parts among the 11 billionty parts available. A little persistence can get you through it, though. I just wish I'd stop forgetting how a transistor works. Drives me nuts having to relearn it every time. (Probably because it still boggles me a bit. It makes perfect sense... and then it doesn't. Grrr.... :-P)

Trying to explain to a potential employer why you know JHDL and not verilog or VHDL is kind of depressing. JHDL's last release was 2 years ago and I'm not sure if it is an active project any more.

I think you miss the point. I'm not saying that he shouldn't learn VHDL and/or Verilog. Just that doing a bit of JHDL can give him some good experience with the way circuits lay out. He can actually see how, say, an adder circuit is constructed. Armed with that knowledge, he can more confidently write VHDL/Verilog code that will translate into the hardware he wants rather than some random circuitry that seems to do the right thing.

The lack of updates is disappointing, but not really a show-stopper. Even if the hardware JHDL supports falls into disuse, the simulation tools will still operate. And that's all one really needs for the learning experience. :-)

Hardware: I highly recommend the Spartan Starter Kits. They're dirt cheap, well supported by the industry, and come with a good toolkit. There's not much more you need to know other than you'll probably want a serial cable in addition to the JTAG cable the kit ships with.

I'll grant you that the fabric isn't very large by today's standards, but it's still enough space to learn about the hardware. By the time you outgrow the fabric, you should have a good idea of what size hardware you want. In fact, your next board may even be a custom design based on a bus like wishbone. ;-)

Software: The Xilinx stuff (pronounced "Zy-Links") comes with a full toolkit for VHDL/Verilog development including an IDE, place and route tools, and software to reconfigure the FPGA. It's all quite slick and easy for a beginner to use.

Language: The most common route taken by new hardware developers is to learn Verilog. They do this because it's similar to C and that makes them comfortable. THIS IS A BAD IDEA. I can't count how many hardware designers swear up a storm when they see a Verilog project with loops and other software constructs stuck into them. See, the comfort and familarity of C makes new hardware developers forget that the hardware is a fixed layout. There is no for loops or control logic as you think of it. It all ends up flattening to hardware. If you write regular software constructs, you'll end up with the least efficient circuit possible.

From this perspective, learning VHDL is better because you won't have that comfort and familiarity that might tempt you into creating poor circuits.

I actually recommend doing some JHDL code for a while. It's lower level than VHDL, but that's a good thing. You have to think about every wire connection and how it all links up. When you're done, you can easily step through your circuit and see how it plays out in hardware. Even better, you learn how to properly use software constructs like loops to create a large number of static hardware objects. This will make your code better without falling in the trap of trying to write software.

That's my 2 cents anyway. Good luck! :-)

You joke, but between the Canvas and Web Socket standards, I don't see any reason why they couldn't.

Granted, WebSockets have yet to be implemented in browsers, but I hear Google owns a fairly popular one...

wasnt that the whole point of XWindows?

Yes. But it failed to account for future advancements in graphics technology. Thus regular desktop usage became too heavyweight for wide deployment. Thin clients splintered in the directions of Citrix, NX, and VNC. Microsoft also screwed over Citrix and developed RDP.

NX basically is the X11 protocol with many of the issues that make it suck removed. This is accomplished through imperceptible delays to bunch up commands, compression of packets, and caching of previously executed series of commands.

XWindows was remote window graphics developed at Stanford and fortified at MIT during the 1980s.

X Windowing System, actually. X11 for short.

Read this:

http://www.joelonsoftware.com/articles/APIWar.html

Specifically, scroll down to the section "Enter the Web". After reading that, you should understand that it's not about keeping Internet Explorer dominant. It's about holding back the progress of the web.

Another source (in print):

http://www.amazon.com/Barbarians-Bill-Gates-Jennifer-Edstrom/dp/0805057544

I'm sorry, but this is just not true.

^ What is untrue is this statement. You offer it up with no backing as if we're supposed to accept it as reality. Well, it isn't. At least not anymore.

I've been observing non-technical users for a while now, trying to understand what it would take to make them switch. You know what I found? It just took critical mass. That was it. Over the past year, there's been a subtle shift in the way users treat alternative browsers.

Specifically, there's a huge amount of peer pressure *not* to use Internet Explorer! Just pop up in any chat room, forum, or other internet site and mention that you're using Internet Explorer. The responses used to be ambivalent. Now, you'll have just about everyone there descend on you and tell you which browser you should use!

Even in real life, I'm seeing the same trend. The message that "Internet Explorer == Viruses/Bugs/End of the World" seems to be percolating into the zeitgeist. Even the least technical of users tend to be very afraid of using IE and prefer to use FireFox or Safari whenever possible.

See, what you're espousing is the old wisdom. Something that used to be true, but no longer is. The reality of here and now is that the old wisdom is no longer true. For me, it took observing an event of an IE user finding it humorous that an HTML5 game didn't work in IE, and still getting pressed by those around him to explain why he would possibly be using such a POS as IE.

Open your eyes. I think you'll see much the same thing. The only thing propping up IE's market share at the moment is the IE6 "corporate standard" in many companies. Once that falls (and it WILL fall), IE is done for.

Oh, for crying out loud. The parent is NOT, I repeat NOT, flamebait.

Well, ok. Calling Carter a dolt was uncalled for, but so is saying the same of Bush. You see, the government has a bit of an unwritten rule around the pronunciation of "nuclear". It's a rule that was introduced for propaganda purposes, but hasn't always worked like they want it to.

Basically, government officials always pronounce the weapons as "nucular arsenal". This pronounciation is intended to associate the term with "bad", "danger", and "massive destruction". When they're referring to nuclear in the context of power generation or some other "good" aspect, it's supposed to be properly pronounced as "nuclear".

Of course, it didn't exactly work out as planned. The public sees no difference between "nucular" and "nuclear". Worse yet, the politicians often get the two mixed up anyway, thus failing at the message they're supposed to be delivering. But the concept is still out there and the Presidents have tried to somewhat follow it.

If you're interested in the origin of the use of "nucular" in the government, it goes back to Eisenhower. Eisenhower pushed a program known as "Atoms for Peace". Unfortunately, he couldn't pronounce "nuclear" correctly to save his life. As such, the term "nucular" ended up in the government lexicon.

Besides, there's a long tradition of never contradicting the President. Past or present. A tradition abused by the airforce to get the name of the RS-71 changed to SR-71. But that's another story... ;-)

It's not that Google can't or couldn't create a successful operating system... it's that for the vast majority of Windows users, they're not going to switch OS's.

If there's anything I've learned from the current browser war, it's that the best way to take down Microsoft is not another monopoly, but healthy competition.

i.e. FireFox has done a bang-up job in being a strong competitor to Internet Explorer. Yet it remained fairly niche until Safari, Opera, and Chrome all worked there way into people's lives.
They're all still niches in of themselves, but they add up to a whole that presents a serious competition to Microsoft. Worse yet, they've captured enough marketshare to where the idea of IE being the "only option" has mostly gone the way of the dodo.

Competition for Windows will need to be the same. No one Operating System will dethrone it. Not Linux, not OS X, not Google Chrome OS. But together, in competition, they can become more than the sum of their parts.

Aren't nuclear reactors kind of heavy

Yes. Though most of it is shielding which doesn't need to be installed near the rear of the vessel. Turbines are surprisingly compact and are not as heavy as one might assume. Same with the nuclear core.

and full of moving parts that break?

No. Or more precisely, "not exactly". Nuclear reactors generate heat. How you translate that heat into electricity is where your moving parts tend to come into play. Using a working fluid like helium combined with a Brayton cycle turbine is efficient, well tested, and highly reliable.

Some serious engineering is going to have to go into making the power source light enough

NASA already did the work for a probe called Prometheus. While Prometheus was scrapped to make budget room for the Moon return plan, the reactor designs should still be on file. There might need to be more development done to scale the reactor upwards, but it's not brand new engineering.

I have a problem where my X-server grows to over a gig of RAM even when all windows have been closed.

You do realize that X memmaps the video memory into its memory space? This gives it some rather crazy numbers for RAM usage even when it's running thin. Especially with modern cards having 512MB of video mem or more.

Otherwise I do not disagree with your general statements. :-)

No kidding. But this engine is able to take large amounts of energy and impart it into very little matter. 200 kW per engine for 5 newtons of thrust to be specific. At an Isp ranging from 3,000 to 30,000 seconds, it needs very little reaction mass to operate. But to sustain that much power, it needs a nuclear generator. And if you're going to pay for the weight to generate 200 kW, you might as well pay to generate a megawatt or more. You'll need to carry more nuclear fuel and reaction mass, but the high efficiency means that the reaction mass will be a relatively small mass penalty. The nuclear fuel is already pellet sized, so that's the least of your concerns.

Follow? Good.

I'm trying really hard to come up with an appropriate response to that. Unfortunately, you have left me speechless and dumbfounded. Maybe some day I'll even understand what the point was you were trying to make.