I have been watching the web grow for years now. I have seen the pain and delight of several models for transacting things on the web, everything from movies to to down and dirty data entry.
The problem is that I have yet to see an implementation through a browser that can challenge a native GUI implementation and yes this includes Sales Force, Google Mail, Google Docs and all the rest of them.
The hugest problem is latency. Even sitting on a T1 they are still clunky and due to browser limitations and incompatibilities they all suffer from the most bizarre and twisted coding problems I have ever seen.
CSS is STILL fundamentally broken and behaves erratically as evidenced by the box model, which you cannot to behave correctly browser to browser platform to platform.
DOM still has really niggling and dumb problems after all these years as well.
In the final analysis what we all want is a set of tools that will allow us to design a screen with a particular look and feel that will be presented exactly the same no matter where it is displayed.
Back in the day we had dumb terminals that did little more then accept X,Y print it here commands and handled it pretty well. The advent of the GUI show the promise of what could be accomplished and much of it was realized by using the native components that were designed, text boxes, pull down lists, buttons, radio boxes, check boxes etc.
Today you have to combine three very different styles of design and coding, they are HTML, CSS and Java Script to come up with anything that is remotely useful for doing anything more then displaying text.
We need to glue all those together in a coherent manner that brings it to a true object model.
Take for example the Box Model, these are normally represented by the DIV tag. Now the DIV tag has many modifiable properties, the border, the margins, the background, lots of stuff. But the problem is that many are those properties cannot be modified on the fly without having to make a modification in one or more of the three separate parts. To change the background I have to use Java Script to interrogate DOM to get to the right CSS selector and change that and my god what a pain that is! Would it not be simpler to just do this?
ImgBox = Box.New([styleReference]);
Further all since java scipt is loaded when the page is loaded it should be trivial to have static events pre-built for each component eg:
function ValidateText(){
if(value == NULL){
Alert("This is a required field!");
This.SetFocus();
}
}
LastName = TextInput.New([StyleReference]);
LastName.OnExit = ValidateText ;
Then as the user goes along doing whatever it is they are doing, some even triggers a background change, which for this example is an image, then would it not follow that that the following call would be far more appropriate then what we do now?
I understand that designers want things to be limitlessly fluid, but at some point you have to go back to the point of making proper objects and remove the utter randomness from it. ALL of this should be built into DOM instead of scattered across three desperate coding styles.
Everything ends up in DOM but the problem is most of it is far to loosely coupled and cannot access the display engines of the platform as it should. I know this notion goes against what we have all grown used to but I feel that it must be accomplished if we really want the browser to function as it should or can.
Look, I don't like that deal any more then you or anyone else does, but we all know the beast has a patent portfolio the size of Montana. Novell made a smart move for themselves and their customers. If you, like me, think that about 90% of software and business patents are complete idiocy, then use all the energy you are expending tilting at windmills to change the law.
Simply running around screaming the Novell is evil, when they in point of fact are not, is both counter productive to furthering Linux adoption and simply hows that you are unclear on what business and investors require when making multi-million dollar decisions about IT infrastructure.
Well I guess Novell could stop funding and or participating in any of
these projects
And you appreciate that Novell went to bat for the entire Linux community by pretty much single handedly cutting off SCO's lawsuit, which if it had prevailed would have gutted Linux for the most part and pretty much put and end to the Linux movement in general? Aww that is so nice of you and yet you now bite the hand that feeds you.
With friends like you, hell no one needs enemies
Novell has, without exaggeration done more for the acceptance of Linux in business in the last 3 years then Richard Stillman, Linus, Red Hat or any of them. Get a clue.
It is more then likely a push by the HSA to continue to justify their existence
So much of the heavy encryption stuff is Open Source that it is pretty much all over the world, and with the Air Force sending Nuclear Initiators to Taiwan you can be pretty sure all that stuff is pretty much available.
It could also be items that are pretty bleeding edge that the knowledge of is not in general circulation yet. Hell for 10 years after I got out of the Navy, I could not even export myself to a non-Nato country. I applied for a Visa to go to Czechoslovakia 6 years post service, and got a knock on my door.
Some of it I can understand the NSA, CIA and their like getting twitchy about but most of it, I don't see their point.
Most scripting languages look horrid IMO, but I don't even really like the look of C, it is far to easy to write unreadable code, and don't even get me started with C++ since I think operator overloading is the most asshat idea to come down the pike since Haskel. Complex code, even when well written is hard enough to decipher, much less code that looks like a SQL statement.
But all that is really beside the point. If you look at the utility of PHP it is pretty damn good, you don;t have to be a rocket scientist to get something useful done and if the architects decide that using a a "/" is beter then using "::" or something like "->>" or some other such nonsense, then just go with it, it is really just not that big of a deal.
There are lots of things I would like changed in lots of languages, but chances are that aint happening anytime soon unless I go out and invent my own scripting language. I could more then likely do a pretty damn good job of it, but the last thing the world needs is yet another scripting language.
Most of these scripting languages were designed to extend base languages and make them more accessible to more people. The days of writing in assembler except for the most abstract and lowest level bits and parts are long over, although I do still enjoy writing in assembler simply because it makes me think down to the level of the machine and understand the costs of doing something one way or the other.
I have found that the various scripting languages out there are an outgrowth of someone who programmed in a lower level language and simply either got bored with it ( completely understandable ) or wanted to wrap all of the low level functions they had designed into something more accessible, hence all the various scripting languages have their roots firmly planted in the soil of C.
Now none of that means that you have to write this stuff in C, you could write them in pretty any of the lower level languages that have compilers that generate native binaries. Writing a good interpreter is not by any means trivial, it is hard work.
So to the root of my diatribe, I would wager that most of the people bitching about the architects of PHP using the backslash as a name space separator could not even begin to write something like PHP and yet they feel so qualified to raise their collective voices in protest and condemn the decision of dev's who quite obviously do so, to be nothing more then pretentious and self aggrandizing and thusly they should be regarded with scorn and ridicule.
As to me, yup I am in the over 50 crowd who's shoulders others stand on and I also stand on the shoulders of others who's are broader then my own.
Ohhh that would be fucking brilliant now wouldn't it.
Lets have a little pissing ware over a single character and fork the the thing. This is gonna work REAL well, the dev's that build the software are all going to suddenly start contributing to your fork? Not bloddy likely since they are the ones who made this call.
Seriously, I mean WTF! It is a scripting language for fucks sake, why does it matter to you what they use? If you use the language, thats the deal, if you don't then use whatever C clone you like, there are plenty of them out there, or better yet, just program in C, why screw around with all the intermediate shite? You can write smaller, more compact & light weight server side programs in C then you can for just about anything else.
Scripting languages are for convenience, nothing more nothing less. Anything you can do in ANY scripting language be it Perl, Python, PHP, Rails or whatever, pick any of them, you can build faster, smaller and better programs in C.
Native binary languages for *nix system have all the same goodies in them just written at lower levels and you have to do a little work, or god forbid, some memory management, a horrific thought I know, but what do you think all this stuff is written in? Uhmm mostly C or its bastard stepchild, C++
Scripting languages are for those of a weak mind and poor technical skills and the singular lack of the ability to plan a system out before you write one line of code.
using concrete for shielding is shielding on the very very cheap.
There are much better neutron shields, but they are very exotic and expensive. Borated Polyethylene, hafnium, cadmium or any other material with large numbers of hydrogen atoms present, water being one of the better ones.
I don't know what world you are living in, but I have been working with NSS since its inception, and it is neither slow or buggy.
You want to know the real problem, well here it is... *nix heads, thats the problem. Instead using a tried and true solution that could be ported to generic *nix very quickly, they choose to re-invent the wheel and why? because its a religion to them. Novell broke a rule, and did what they had to do to cover their and their customers asses, namely the agreement with Microsoft. m well lets see what Novell has done to protect *nix shall we?
They dumped HUGE amounts of cash countering the law suite from SCO to protect Linux, but hey FUCK THEM right?
They brought Linux from obscurity and have turned out a distro that is clean, runs fast, is secure, has made its way into more corporations and paved the way for Linux acceptance in the the Fortune 500 then Red Hat ever even thought about, but hey FUCK THEM right?
Ohh yeah, they basically have funded the entire MONO project, but hey FUCK THEM right?
Their distro of OOo kicks ass and they shove everything they do right back to OOo dot org, which is the same as saying, they pumped as much if not more then Sun ever did into OOo, but hey FUCK THEM right?
I will put up an NDS powered NetWare server running F&P services against ANY Linux distro and it will blow its doors off. Hell I will put NetWare 3.2 ( still the record holder for F&P services ) against ANY OTHER OS out there and it will just leave it in the dust, and all of that speed comes down to the File System. before NSS it was the NetWare native file System. Slow to mount to be sure, but once mounted NOTHING could touch it in terms of speed an security. Then came NSS.. An 8TB volumes mounts in about 10 seconds and uses a MOST 4 megs of RAM and STILL blows the doors off of anything out there.
You want to do the Linux community a favor? Tell them to drop the "its a religion" bullshit and get them to use what has been made FREELY available to them.
Well gosh golly! What a surprise! Novell invested their time and money into porting NSS to an OS they are supporting, shocking I tell, simply shocking!
I do believe that SUSE uses the same kernel that all other *nix distro's use, correct me if I am wrong, but anything they change in the kernel gets pushed back out to the world right to opensuse,org
Does it need some dev work, yes I bet it does.
The point is, that is is FOOS, ZFS is NOT, it definitely has proprietary code, that SUN has no control over in it as has been discussed on/. many times.
NSS; however, does not since it was developed BY Novell FOR Novell to be the files system for NetWare. Novell open sourced the complete NSS system, all of it, every bit of it. The source is included with a SELS server, a bright DEV could port it over as a native FS for *nix and the *nix community would have a KILLER file System.
Since SLES is FOOS software then everything Novell does gets sent back into the community.
the "community" needs to get a clue, NSS is better then anything out there as of this writing. And it has one other thing that NONE of the others do and that is the ability to undelete ANY file in ANY directory, as long as the file and or directory has not been flagged as "purge immediate"
As the parent says, it is no big news flash. I was in the navy in the 70's and the 80's.. The machines we got were basically PC-AT's but they were re-worked with shielded EVERYTHING, everything had copper mesh around it, and if is was used for any seriously classified information it was in a room with the same mesh in the wall's, ceiling, floors etc.
Remember the movie "Enemy of the State"? The Gene Hackman character lived in an old warehouse and ALL of his electronic goodies were in a Faraday cage the size of an office.
NSS has no proprietary tail. It is now FOOS! Novell Open Sourced it like 3 years ago. The full and complete source is on the SLES DVD. It lived on forge.novell.com for a while as well.
I have no idea, it was just a guess. I agree with you that having Hep-C does not seem like a reason to have your medical yanked. This link provides some insight as to the why. It talks about treatments and so forth.
I had a Kidney stone once and I had to go through all kinds of tests and this that and the other, before I could get it re-issued. If you have ever had to deal with a Kidney Stone you would understand why. The pain came on within an hour and it put me on the ground it was so bad. Relief only came in the form of morphine at my local hospital.
Yes it is only ported to SUSE at this point, but lets face it that is Novell's focus. It is however FOOS and that is the point. Where are you going to get a file system, that has that much R&D and debugging behind it that is at that level and completeness and correctness.
One of the most critical and outstanding features of this file system is it's ability to add storage space On The Fly, no re-booting, no taking the server down. Shove another drive into a spare hot-swap cage slot, partition, mount and add to any volume and no one knows the event occurred.
Then look no farther then NSS ( Novell Storage Services ).
It is Open Source, you get the full source if you download SLES.
It has more of the desired features then anything else on the block right now.
This should be the default file system for Linux. It has years of very heavy duty R&D behind it, it is pretty much completely de-bugged and ready to rock.
I see your point, its a catch 22 in many, but not all regards; however, these things are being marketed as commuter vehicles that transition from flight configuration to road configuration.
Personally I think they should be classified as any Cessna 152/172 should be classified as a GA aircraft that require a Third Class medical Certificate because these things are going to be flown into civil airports near major business centers that have large population densities. If you don't like that, ammend the rules to prevent them from operating in any airspace requiring MODE C.
It is not like you are flying a glider out over the rolling hillside and chances are if you heart valve, pace maker, or whatever fails you are probably only going to kill yourself, but you are likely to be making an approach into the GA side of say Oakland, Hayward, San Jose, Palo Alto, San Carlos, all of which have large residential communities close by as well as major business centers with lots of people on the ground.
A third Class Medical Certificate is just NOT that hard to get and there is no age limitation.
Hey there.... Well, they are not technically breaking the rules because:
CFR 14.91.7(a) states: "No person may operate a civil aircraft unless it is in an airworthy condition."
CFR 14.91.7(b) states: "The pilot in command of a civil aircraft is responsible for determining whether that aircraft is in condition for safe flight. The pilot in command shall discontinue the flight when unairworthy mechanical, electrical, or structural conditions occur."
Now having said all of that, an aircraft made of composite materials is subject to hidden cracks just like metal. I think in this type of aircraft getting a fender bender or a "parking by braille" situation would call for a complete inspection of the affected part, since its "Front Bumper" is both a canard and a control surface. Anything less would be quite foolish.
Re:Oh, well, that explains everything...
on
C# In-Depth
·
· Score: 1
In its assembled state, it could be in ANY order. It is HIGHLY optimized. Un-Assemble just about any executable that is generated by a highly optimizing compiler and it is just about unreadable.
Compiled code is not for human consumption, it is for machine consumption. The guys that write these things spend HUGE amounts of time pouring over the instruction sets, figuring out the best way to combine them for the fastest computational result. It that looks like total gibberish, with recursive calls and leaf objects and it bears absolutely no semblance to to what it looked like in ANY hi level language, are you really that surprised?
Every instruction has a cost in terms of resources. The way you generate the fasted, tightest, least memory footprint code is to optimize those costs, and if that means you to some very very strange and seemingly illogical things with the final code that gets generated and it runs well, what do you care? It looks like well laid out C, or Pascal, or C++ or whatever the language and you can maintain it, then the rest is moot.
Slashdot Mirror
I have been watching the web grow for years now. I have seen the pain and delight of several models for transacting things on the web, everything from movies to to down and dirty data entry.
The problem is that I have yet to see an implementation through a browser that can challenge a native GUI implementation and yes this includes Sales Force, Google Mail, Google Docs and all the rest of them.
The hugest problem is latency. Even sitting on a T1 they are still clunky and due to browser limitations and incompatibilities they all suffer from the most bizarre and twisted coding problems I have ever seen.
CSS is STILL fundamentally broken and behaves erratically as evidenced by the box model, which you cannot to behave correctly browser to browser platform to platform.
DOM still has really niggling and dumb problems after all these years as well.
In the final analysis what we all want is a set of tools that will allow us to design a screen with a particular look and feel that will be presented exactly the same no matter where it is displayed.
Back in the day we had dumb terminals that did little more then accept X,Y print it here commands and handled it pretty well. The advent of the GUI show the promise of what could be accomplished and much of it was realized by using the native components that were designed, text boxes, pull down lists, buttons, radio boxes, check boxes etc.
Today you have to combine three very different styles of design and coding, they are HTML, CSS and Java Script to come up with anything that is remotely useful for doing anything more then displaying text.
We need to glue all those together in a coherent manner that brings it to a true object model.
Take for example the Box Model, these are normally represented by the DIV tag. Now the DIV tag has many modifiable properties, the border, the margins, the background, lots of stuff. But the problem is that many are those properties cannot be modified on the fly without having to make a modification in one or more of the three separate parts. To change the background I have to use Java Script to interrogate DOM to get to the right CSS selector and change that and my god what a pain that is! Would it not be simpler to just do this?
ImgBox = Box.New([styleReference]);
Further all since java scipt is loaded when the page is loaded it should be trivial to have static events pre-built for each component eg:
function ValidateText(){
if(value == NULL){
Alert("This is a required field!");
This.SetFocus();
}
}
LastName = TextInput.New([StyleReference]);
LastName.OnExit = ValidateText ;
Then as the user goes along doing whatever it is they are doing, some even triggers a background change, which for this example is an image, then would it not follow that that the following call would be far more appropriate then what we do now?
ImgBox.Background("/webroot/images/mygreatcorpimage.png");
I understand that designers want things to be limitlessly fluid, but at some point you have to go back to the point of making proper objects and remove the utter randomness from it. ALL of this should be built into DOM instead of scattered across three desperate coding styles.
Everything ends up in DOM but the problem is most of it is far to loosely coupled and cannot access the display engines of the platform as it should. I know this notion goes against what we have all grown used to but I feel that it must be accomplished if we really want the browser to function as it should or can.
Look, I don't like that deal any more then you or anyone else does, but we all know the beast has a patent portfolio the size of Montana. Novell made a smart move for themselves and their customers. If you, like me, think that about 90% of software and business patents are complete idiocy, then use all the energy you are expending tilting at windmills to change the law.
Simply running around screaming the Novell is evil, when they in point of fact are not, is both counter productive to furthering Linux adoption and simply hows that you are unclear on what business and investors require when making multi-million dollar decisions about IT infrastructure.
Well I guess Novell could stop funding and or participating in any of these projects
And you appreciate that Novell went to bat for the entire Linux community by pretty much single handedly cutting off SCO's lawsuit, which if it had prevailed would have gutted Linux for the most part and pretty much put and end to the Linux movement in general? Aww that is so nice of you and yet you now bite the hand that feeds you.
With friends like you, hell no one needs enemies
Novell has, without exaggeration done more for the acceptance of Linux in business in the last 3 years then Richard Stillman, Linus, Red Hat or any of them. Get a clue.
It is more then likely a push by the HSA to continue to justify their existence
So much of the heavy encryption stuff is Open Source that it is pretty much all over the world, and with the Air Force sending Nuclear Initiators to Taiwan you can be pretty sure all that stuff is pretty much available.
It could also be items that are pretty bleeding edge that the knowledge of is not in general circulation yet. Hell for 10 years after I got out of the Navy, I could not even export myself to a non-Nato country. I applied for a Visa to go to Czechoslovakia 6 years post service, and got a knock on my door.
Some of it I can understand the NSA, CIA and their like getting twitchy about but most of it, I don't see their point.
Most scripting languages look horrid IMO, but I don't even really like the look of C, it is far to easy to write unreadable code, and don't even get me started with C++ since I think operator overloading is the most asshat idea to come down the pike since Haskel. Complex code, even when well written is hard enough to decipher, much less code that looks like a SQL statement.
But all that is really beside the point. If you look at the utility of PHP it is pretty damn good, you don;t have to be a rocket scientist to get something useful done and if the architects decide that using a a "/" is beter then using "::" or something like "->>" or some other such nonsense, then just go with it, it is really just not that big of a deal.
There are lots of things I would like changed in lots of languages, but chances are that aint happening anytime soon unless I go out and invent my own scripting language. I could more then likely do a pretty damn good job of it, but the last thing the world needs is yet another scripting language.
Exactly..
Most of these scripting languages were designed to extend base languages and make them more accessible to more people. The days of writing in assembler except for the most abstract and lowest level bits and parts are long over, although I do still enjoy writing in assembler simply because it makes me think down to the level of the machine and understand the costs of doing something one way or the other.
I have found that the various scripting languages out there are an outgrowth of someone who programmed in a lower level language and simply either got bored with it ( completely understandable ) or wanted to wrap all of the low level functions they had designed into something more accessible, hence all the various scripting languages have their roots firmly planted in the soil of C.
Now none of that means that you have to write this stuff in C, you could write them in pretty any of the lower level languages that have compilers that generate native binaries. Writing a good interpreter is not by any means trivial, it is hard work.
So to the root of my diatribe, I would wager that most of the people bitching about the architects of PHP using the backslash as a name space separator could not even begin to write something like PHP and yet they feel so qualified to raise their collective voices in protest and condemn the decision of dev's who quite obviously do so, to be nothing more then pretentious and self aggrandizing and thusly they should be regarded with scorn and ridicule.
As to me, yup I am in the over 50 crowd who's shoulders others stand on and I also stand on the shoulders of others who's are broader then my own.
Pray tell, what absolutely needs to be compiled at run-time?
Ohhh that would be fucking brilliant now wouldn't it.
Lets have a little pissing ware over a single character and fork the the thing. This is gonna work REAL well, the dev's that build the software are all going to suddenly start contributing to your fork? Not bloddy likely since they are the ones who made this call.
Seriously, I mean WTF! It is a scripting language for fucks sake, why does it matter to you what they use? If you use the language, thats the deal, if you don't then use whatever C clone you like, there are plenty of them out there, or better yet, just program in C, why screw around with all the intermediate shite? You can write smaller, more compact & light weight server side programs in C then you can for just about anything else.
Scripting languages are for convenience, nothing more nothing less. Anything you can do in ANY scripting language be it Perl, Python, PHP, Rails or whatever, pick any of them, you can build faster, smaller and better programs in C.
Native binary languages for *nix system have all the same goodies in them just written at lower levels and you have to do a little work, or god forbid, some memory management, a horrific thought I know, but what do you think all this stuff is written in? Uhmm mostly C or its bastard stepchild, C++
Scripting languages are for those of a weak mind and poor technical skills and the singular lack of the ability to plan a system out before you write one line of code.
using concrete for shielding is shielding on the very very cheap.
There are much better neutron shields, but they are very exotic and expensive. Borated Polyethylene, hafnium, cadmium or any other material with large numbers of hydrogen atoms present, water being one of the better ones.
I don't know what world you are living in, but I have been working with NSS since its inception, and it is neither slow or buggy.
You want to know the real problem, well here it is... *nix heads, thats the problem. Instead using a tried and true solution that could be ported to generic *nix very quickly, they choose to re-invent the wheel and why? because its a religion to them. Novell broke a rule, and did what they had to do to cover their and their customers asses, namely the agreement with Microsoft. m well lets see what Novell has done to protect *nix shall we?
I will put up an NDS powered NetWare server running F&P services against ANY Linux distro and it will blow its doors off. Hell I will put NetWare 3.2 ( still the record holder for F&P services ) against ANY OTHER OS out there and it will just leave it in the dust, and all of that speed comes down to the File System. before NSS it was the NetWare native file System. Slow to mount to be sure, but once mounted NOTHING could touch it in terms of speed an security. Then came NSS.. An 8TB volumes mounts in about 10 seconds and uses a MOST 4 megs of RAM and STILL blows the doors off of anything out there.
You want to do the Linux community a favor? Tell them to drop the "its a religion" bullshit and get them to use what has been made FREELY available to them.
Well gosh golly! What a surprise! Novell invested their time and money into porting NSS to an OS they are supporting, shocking I tell, simply shocking!
I do believe that SUSE uses the same kernel that all other *nix distro's use, correct me if I am wrong, but anything they change in the kernel gets pushed back out to the world right to opensuse,org
Does it need some dev work, yes I bet it does.
The point is, that is is FOOS, ZFS is NOT, it definitely has proprietary code, that SUN has no control over in it as has been discussed on /. many times.
NSS; however, does not since it was developed BY Novell FOR Novell to be the files system for NetWare. Novell open sourced the complete NSS system, all of it, every bit of it. The source is included with a SELS server, a bright DEV could port it over as a native FS for *nix and the *nix community would have a KILLER file System.
Since SLES is FOOS software then everything Novell does gets sent back into the community.
the "community" needs to get a clue, NSS is better then anything out there as of this writing. And it has one other thing that NONE of the others do and that is the ability to undelete ANY file in ANY directory, as long as the file and or directory has not been flagged as "purge immediate"
As the parent says, it is no big news flash. I was in the navy in the 70's and the 80's.. The machines we got were basically PC-AT's but they were re-worked with shielded EVERYTHING, everything had copper mesh around it, and if is was used for any seriously classified information it was in a room with the same mesh in the wall's, ceiling, floors etc.
Remember the movie "Enemy of the State"? The Gene Hackman character lived in an old warehouse and ALL of his electronic goodies were in a Faraday cage the size of an office.
NSS has no proprietary tail. It is now FOOS! Novell Open Sourced it like 3 years ago. The full and complete source is on the SLES DVD. It lived on forge.novell.com for a while as well.
That size limit is very easily correctable.
LVM/ELVM each have their own problems that are well documented. NSS has all of that built in , debugged and is proven correct!.
I have no idea, it was just a guess. I agree with you that having Hep-C does not seem like a reason to have your medical yanked. This link provides some insight as to the why. It talks about treatments and so forth.
I had a Kidney stone once and I had to go through all kinds of tests and this that and the other, before I could get it re-issued. If you have ever had to deal with a Kidney Stone you would understand why. The pain came on within an hour and it put me on the ground it was so bad. Relief only came in the form of morphine at my local hospital.
Yes it is only ported to SUSE at this point, but lets face it that is Novell's focus. It is however FOOS and that is the point. Where are you going to get a file system, that has that much R&D and debugging behind it that is at that level and completeness and correctness.
One of the most critical and outstanding features of this file system is it's ability to add storage space On The Fly, no re-booting, no taking the server down. Shove another drive into a spare hot-swap cage slot, partition, mount and add to any volume and no one knows the event occurred.
Then look no farther then NSS ( Novell Storage Services ).
It is Open Source, you get the full source if you download SLES.
It has more of the desired features then anything else on the block right now.
This should be the default file system for Linux. It has years of very heavy duty R&D behind it, it is pretty much completely de-bugged and ready to rock.
I see your point, its a catch 22 in many, but not all regards; however, these things are being marketed as commuter vehicles that transition from flight configuration to road configuration.
Personally I think they should be classified as any Cessna 152/172 should be classified as a GA aircraft that require a Third Class medical Certificate because these things are going to be flown into civil airports near major business centers that have large population densities. If you don't like that, ammend the rules to prevent them from operating in any airspace requiring MODE C.
It is not like you are flying a glider out over the rolling hillside and chances are if you heart valve, pace maker, or whatever fails you are probably only going to kill yourself, but you are likely to be making an approach into the GA side of say Oakland, Hayward, San Jose, Palo Alto, San Carlos, all of which have large residential communities close by as well as major business centers with lots of people on the ground.
A third Class Medical Certificate is just NOT that hard to get and there is no age limitation.
Here is a link to the actual rules:
CFR 14.61.23
It probably has something to do with the meds he is/was taking.
Hey there.... Well, they are not technically breaking the rules because:
CFR 14.91.7(a) states: "No person may operate a civil aircraft unless it is in an airworthy condition."
CFR 14.91.7(b) states: "The pilot in command of a civil aircraft is responsible for determining whether that aircraft is in condition for safe flight. The pilot in command shall discontinue the flight when unairworthy mechanical, electrical, or structural conditions occur."
Now having said all of that, an aircraft made of composite materials is subject to hidden cracks just like metal. I think in this type of aircraft getting a fender bender or a "parking by braille" situation would call for a complete inspection of the affected part, since its "Front Bumper" is both a canard and a control surface. Anything less would be quite foolish.
Sorry I did not mean to post anonymously...
In its assembled state, it could be in ANY order. It is HIGHLY optimized. Un-Assemble just about any executable that is generated by a highly optimizing compiler and it is just about unreadable.
Compiled code is not for human consumption, it is for machine consumption. The guys that write these things spend HUGE amounts of time pouring over the instruction sets, figuring out the best way to combine them for the fastest computational result. It that looks like total gibberish, with recursive calls and leaf objects and it bears absolutely no semblance to to what it looked like in ANY hi level language, are you really that surprised?
Every instruction has a cost in terms of resources. The way you generate the fasted, tightest, least memory footprint code is to optimize those costs, and if that means you to some very very strange and seemingly illogical things with the final code that gets generated and it runs well, what do you care? It looks like well laid out C, or Pascal, or C++ or whatever the language and you can maintain it, then the rest is moot.