Nope, not trolling..

Since it is open source and has all those goodies it would seem to me that increasing the volume size capabilities would not be nearly as tall an order as starting over from scratch.

YASF or Yet Another File System.

Well someone has yet another personal project they want us all to take seriously. Really? I mean Really?

Of the numerous file systems out there, and I have tried a whole boat load of them, the one that is the most mature, most reliable, arguably the fastest is... Wait for it... From the company that everyone loves to hate...

Is NSS from Novell. It has more posix features then all of the rest of them, it is insanely fast, it provides undelete and complete repeatability and Novell has open sourced it. Nuff said.

What you are describing is a Software Engineer not an electrical engineer or an aerospace engineer or any other kind of civil engineer. I work with a boat load of civil engineers who are extraordinarily competent in their distinct skill set. They can do some prototyping in matlab and a few other things but when it comes to writing actual software they just need to step very far away from the compiler because their minds don't think in those spheres.

Write all the parts...:

• Insertion Function
• Deletion Function
• Traversal Function
• Search Function
• Sort Function
• Save to Disk Function
• Load from Disk Function

You can do this in C. C comes with EVERY Linux distribution so no additional parts or bits required. If you can do this, you really can do most anything and further more you will understand some of the more advanced concepts of computer programming, one of the most important is Memory Management. Now I know that with languages like Java you are far removed from those concepts bust just understanding what you have to do to manage your memory footprint will help you in those languages as well since you will have a much clearer understanding of what is going on under the hood. If you push a few boundaries you will understand some of less obvious parts of other languages.

My memory is really fading.. The S6g provided ~ 148 thermal megawatts which is ~ 45 megawatts of electricity. Although the Rankine cycle is pretty much fixed you can build more efficient turbines and steam generators that do not have to exist in the very tight confines of a submarine.

These small reactors already are designed and in production:

The S6W and its line of small reactors are reliable and safe. The rector compartment on a typical submarine is about 30' in diameter and 30' in length.

These generate ~ 50 Thermal Megawatts which translate into about 40,000 horse power or about 29 megawatts of electricity.

You damn fucking right when it comes to maintaining absolute control over things that can vaporize the planet. Until they are gone, we spend whatever it takes.

Do you really think that the United States military, very specifically, the part of it that can unleash a version of hell that you have trouble even imagining, does not have the budget to get those drives manufactured, one off or any other part of the system?

Wow, you just don't get it! Your remark implies that he is some sort of Luddite with the attitude of, "it worked for my grand pappy so it is good enough for me!"

What the man said is that they did a complete audit of the systems and given the requirements they determined that what they have is the most secure system they can come up with.

Your remark also implies that they should be all modern with a nice tomcat stack running php, python or god alone only knows what bit of Swiss cheese stack of cruft to control the very things that could quite easily turn this entire planet into a spinning ball of radioactive fire."

So AC, you really *think* you know what you are talking about, but in fact you really don't.

Postgres - in a high transaction environment if the vacuum goes sideways you just simply crash and burn and your data gets scrambled. On top of that, I double dare you to try and move from one machine to another, much less one hard drive to another.

MySQL - ACID much?

SQLLite Uhmm for little tiny projects, sure as long as you don't need ACID or more then one person using it.

Oracle - IF and it is a BIG ONE - you actually know how to use it, (If you have had the proper training, or you have been using it forever ) It will spin circles around pretty much anything out there. Do stupid things with it and just like any of the rest of them that are enterprise class ( MS-SQL, DB2, Postgres, Informix etc. ) they will not perform up to anyone's expectations.

So please go have a big frosty glass of Shut The Fuck Up.

Gui Editor - Easy, just get Kate. Not KWrite, but plain old Kate. Syntax highlight for just about every language, columnar selection and paste and all the bells and whistles you could want.

Sick to death of VI or VIM or EMACS for the simplest of CUI chores? Get Nano it is pico's older brother and works quite well.

This is really simple. They have the infrastructure, they have the bandwidth. There are a lot of really quality content generators out there that Google just rapes. Here is a really cogent explanation ( ironically on You Tube ) by Jack Conte of Pomplamoose.

http://www.youtube.com/watch?v...

Really listen to what he is talking about and you can understand how Yahoo could just kick Google's ass in this space.

Every can be broken into and some asshole can do arbitrary things on a users machine because...

• Defensive programming is not uppermost in their minds, performance is and that is a problem.
• Old code that should have been ripped out with extreme prejudice long ago still exists, eg: Driveby's

And on top of those two things there is the ever changing HTML specification, the ever changing CSS specification, and the bit of garbage called DOM.

And cracked by a "carefully constructed URL?!? What!?!?! Can these people simply not write a safe URL parser? I mean WTF?!?!?!?!

TBL dame up with the idea that was essentially Anonymous FTP and a bit of code that used a simple set of tags to format text so it displayed like the author intended it to be seen was pretty cool. Then came the committees with "Wouldn't that be cool" ideas and they implemented them with no regard for the implications.

The whole bloody mess in one huge kludge of hideously bad code, bad definitions, and bad implementations of pure garbage designed by a circle jerk.

We have waited for years for them to clean this fucking mess up and what have we gotten:

• Check boxes that still wont be sent back unless they are checked, if the are not checked they simply don't exist.
• Input boxes that still won't take a mask so that input is formatted correctly.
• Validation on the form submit event?!?!?! WTF, can we not have to submit the entire thing before we inform the user that their input does not meet expectations.
• Arbitrary timeouts that prevent large data sets from loading ( Ajax )
• An object model in Javascript that is utterly laughable and worse then C++ and Java which is saying quite a lot.
• A scripting language that is about as robust as wet cleanex

It is time for the madness to stop. Lets start over and make it correct this time.