PostGres compares ok on a lot of workloads, but when the rubber really hits the road that is when it starts to fall apart.

They must fix the TXID ID problem. It will now at least shut down when it is getting close to rolling over, but the vacuum process will just kill your performance in very high transaction workloads. Not that Oracle would not have the same problem if they were using a 32 bit number for the value, but with the size of the ID Oracle uses this won't happen for ~ 140 years.

Immovability... PostGres gets some great performance but it does so at the cost of the data files being so close to the metal that you can't move them to another host that is not exactly the same as it is moving from. If that is not true you have to do an SQLDUMP of the data. That is a fairly fatal flaw in my opinion.

So yes you can use PG in place of Oracle, to a point, but after that point it just does not perform as required.

I migrated a PG DB to Oracle 11g EE and it runs quite smoothly. The application would quickly overwhelm PG without some serious changes to the PG code.

Yeah that's reassuring and all. The WC3 takes security very seriously as well as do the makers of Mozilla, IE, Chrome, Opera, Safari et al. but never the less we still have drive by's, we still have machines with AV software, anti-malware, Sand Boxing software etc installed and they still get through and steal whatever they want.

Javascript is a language that scares the hell out of anyone who takes security seriously. You can shove text at any object and presto that is now executable code, oh yay!!! Your code ( yeah I looked ) is full of the convention of function( "function{}" ) and that is just as bad as PHP taking links to remote servers as parameters to functions. Do you really think this is going to survive in the wild? Really dude this is injection just waiting to happen. I applaud your cleverness, but this "software" is going to get ass raped and your reputation is going to be ruined.

There are better ways to do this. Doing this in the web browser as it currently exists is just foolish. I am building an application frame ( appFrame ) that can run actual applications free from the asshattery that is HTML and CSS.

This thing has access to my hard drive, to fucking save files!!!!

This thing will never, ever, be used anywhere I have a say about. This is ripe for someone to hook it from another page and write shit to anywhere on your hard disk that you have permission to write to. Drive By's were bad enough but now we have opened the flood gates. The script kiddies and the black hast are going to have a field day owning anyone who runs this.

The Browser is bad enough as it is with "precisely formed" URL's being able to rape your machine, and now this. Some PHB is going mandate this and the number of machines and networks jacked is going to be quite a show.

No one has been able to successfully sand box a browser. The browser was never ever supposed to be able to access the local machine directly, but in the name of the all mighty cloud we keep tearing down barrier after barrier and no one is saying anything about it, we just keep changing chairs while the band plays.

ROFLMAO!

Spreadsheets are great tools for accounts and they have made their life a lot easier. But you are right, they are evil because suddenly accountants started using them to do things that should have been done in databases etc. But I think we have only ourselves to blame if you really think about it.

I mostly agree with what this guy says with the exception of Quatro by the old Borland. Quattro by all accounts was eating Lotus Development and Microsoft's lunch in the spreadsheet department. It had WYSIWYG natively before either of them ( 123's was an add-on and excell didn't even have one) and it worked beautifully. Embedded graphs were there, Multiple Sheets and a function library that was richer than either of the others.

Then the Look & Feel lawsuit hit. Jim Mansey ( if he stood in front of me today, I would punch him hard and punch him again even harder ) after having let 123 rest on it's laurels took Borland to court, in Boston. Borland eventual prevailed but not until it had spent most all it's cash and suffered the basic abandonment of Quattro by the marketplace because of the suit.

That really was the beginning of the end for innovation in the spreadsheet world. Excel has turned into a bloated beast that no one really likes, but it is the only thing left in the marketplace ( Don't get me wrong I wholly support Open / Libre Office but they will never overtake Excel as the simply have to play catchup constantly ) that anyone can field. Quattro still exists but the last release was about 2 years ago

While I agree with some of what you say, I cannot help but disagree completely with:>/p>

Such ideas are a complete waste of machine resources, ram, registers, and cpu cycles et al. "Modern Languages" have to do more than should ever be required to account for programmer laziness. Dynamic typing? Takes up huge amounts of resources to have to constantly figure out what the type of EVERY variable it encounters. Virtual Machines? More splitting of cpu time because none of those "modern" languages know how to deal w/multiple cores, hell we barely have languages that can deal with multiple cpu's as it is.

FSB speeds rarely, if ever, exceed 450MHZ and then the cpu is in a pretty much constant wait state for data. Disk I/O is still pretty damn slow when compared to everything else. SSD's have contributed a large amount in improving that but they still make the whole system wait. Network I/O still crawls in comparison unless you are using very specialized and very expensive technology that is mostly reserved for things like mainframes ( think IBM's Deep Blue ).

I dream of going back to big full height drives with the sort of data densities we have now backed down a couple of notches. Separate read and write heads. Elevator seeking and writing so that you can read in a terabyte on one rotation. Running on a parallel buss that clocks a byte of data onto the buss every clock cycle and connected by fiber optics.

Just imagine 64 or 128 fiber strands connecting every component. Experimental rates are over 100 terabytes per second, for a single fiber!!!!! Imagine even just 10% percent of that inside your machine! Your bus capable of signaling at 10 TBS!!! The CPU would be the component everyone is waiting for!!!

Now just imagine a machine that with a very efficient language like C without all the cruft that things like Java, Python, PHP and all those other "modern" bring to the table.

And of course one must imagine what a Beowulf cluster of those would be like...

Being from the Delphi camp for many years, I too recommend this, but they need to get the install worked out. Also they need to get LLDB worked out on the Mac because trying to load in another version of XCode to sit beside the latest for just the debugger is a royal pain in the ass.

Your position is not only short sighted but ignorant. Precedent precedes many many things. Think about the precedent this sets for someplace like Oklahoma where they push hard to denounce science and only want to teach that the earth and everything else was created in 6 days. Teachers have to push back just as hard and now they can be summarily dismissed if they don't fall into line.

Be very careful what you wish for.

Hmm you user the term ABEND

Were you ever a Novell CNE? The term of course means, Abnormal End, but it is rare to see the usage outside of the Netware ecosystem.

As to Pascal Programs failing gracefully and not taking the entire system with it... I think that might have been the advent of actual protected mode operation -v- declaration and discipline. In my early days of my programming career first learning how to use pointers effectively I would routinely crash my machine by running a pointer into the OS space ( MS-DOS 2.x and 3.x ) on 8088 machines and corrupting all sorts of data and code structures.

Having programming now fr more years that I care to admit to at times I have seen the proliferation of the mind set that simply ignores things like structure and massive abuse of the OOP model. These days you start looking through code and see variables created on an ad-hoc basis for no other reason than laziness when 20 minutes of code refactoring would have solved the problem and the system would have made far more sense and in the end would ave performed faster and been more logically cohesive.

As a matter of fact Watterson never licensed any part of C&H for anything. The guy could have made a medium to large sized fortune if he had, but to him the integrity of the strip was FAR more important. The only reason it is running is certain places is because King Features Syndicate has the right to redistribute the comic.

I was a huge fan of the strip. I mean I knew it had to happen at some point, but I was heartbroken when it stopped.

When my son was born I named him Calvin ( my maternal grandfather ), but the running joke is that he was named after the character. When he was two 3 weeks old, a woman who lived in the same building took a white One-Z and hand painted a beautiful Hobs on it. He is 13 now and it is framed on his bedroom wall.

Remember the old days of 64K code and data AND segment offset, and LIM sepc?

Wow, really?

It is called analyzing your project and mapping the thing out before you write a single line of code. Programming is a discipline as well as an art and a science.

I was once talking to a guy and he as complaining the compiler kept erroring out on "symbol table is full". I asked to look at his code and OMG he was declaring variables by the butt load, but the thing of it was they were all subtle variations of the same thing, and lots and lots of structs. So I should him how to make a linked list of a single of structs with variants. I explained that with little effort these would be declared on the heap and that running out of space in the symbol table would be a thing of the past. Also he was no longer limited by the stack and that he had all the memory the machine could muster for variables.

These days troubleshooting code has become such a chore simply because languages these days let you declare variables anywhere so you have to track down where things declared just to figure out what is happening and dynamically typed languages are the absolute worst thing to come along simply because they only add to the confusion since the compiler or intepreter has to try and determine intent and they all pretty much suck at doing it.

I have written pascal programs in excess of 100K lines broken up into many modules and I actually find them easier to debug than other so called modern languages simple because the discipline of declaration forces you to really think things through, rather than just popping things in here and there in an ad-hoc manner.

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.