Only because you saw and compiled the code yourself... or maybe your compiler had been hacked, or the libraries that Hello World depends on were hacked, or maybe you ran the executable without compiling it yourself. Or maybe the operating system modified the executable before/during/after runtime. Are you sure your printf had a null terminated character at the end of the string?:)
These are typical security bugs that can be avoided, but most companies/organizations/individuals/ ignore them. There are many more, and they can affect any program... even hello world.
Right, driver problem... not poor design of the network block device API... no never that... nor a problem with quality control for signed drivers... not that either... yep! vista includes no breakthrough in driver management and recovery... great state of the art system guys.
It's funny how I've been enjoying multiple month up time on Windows computers too. Sometimes 4 to 6 months at a time, continuously on, and most times under heavy load and stress. Usually running things all day, and through the evening. The only times the computer goes off is literally when the power gets disconnected. This has been the case with my machines since XP came out. Recently, I did have a Linux machine that croaked though.
I'd like to go back to the days when you could just press the button on the side of the box.
Leave the logout as the only option in the menu.
shutdown, and restart only after logout (on the login screen)
sleep automaticaly after a period of no activity. (no need for menu choice)
He get his ideas from the trance state that he goes into... Not really credible, even for todays scientists...
Still... Even if there were anti-gravity devices, cranes and motors would have been prevelant. Steele working, and other metal working industry would be prevelant. We have space shuttles, and yet there is a lot more infastructure necessary to make that happen. I'm sure they did not just leap technologies until they had this anti-gravity device.
If everything went to hell, I doubt that some future society would find a space shuttle, but I bet they would find an electric motor, a gasoline engine, and a crane or two.
Technology does not occur in an isolated environment. It quickly spreads among societies, even enemy societies. Rest assured that this is enough reason to think that a far technologically advanced Atlantis is a myth.
By the way, I read that article, and although it is interesting, I really think it is beyond the point. The point is that various legislation protects property, and patents are used for software. Legalease will always be the area of specialist attorneys.
Movies are protected by copyright.
The method of producing effects can be patented.
Algorithms are really methods.
There are some good books on patents and copyrights that would probably help you know more about this subject.
There is some controversy about whether it is ethically correct for software to be patentable, but currently it is the law that you can. The thrust of this controversy is given by the close relationship between Math (algorithms) and softare. Mathematical formulas can't be patented, even they can be trade secrets.
These are fairly new advances by IBM and Sun in the PC market... Oh wait, I mean server market for machines that cost an arm and a leg. And I think they are great. Really, I do. I also agree that Plug and Play doesn't really work at all the way it was intended to work. I'm just saying that it was innovative and that it helped computing in general.
Wait a minute, didn't MS Word come first... Wasn't there this thing called Rich Text Format... Couldn't all modern word processors just be reinventing a "wheel"...namely the type writer.:)
They might add a feature that isn't in the standard, but that doesn't mean that the standard is irrevocably broken. Many standards are growing entities that are added to as necessity dictates.
Since, the underlying data format is inherintly extensible, if the format is modern and well designed (as this one is) then it could last (even with modifications) a very long time. I would say 20 years or so, which isn't as long as txt files will last (forever), but still a pretty long time.
Also, on another topic, I would like to point out, that most implementors are not going to give more than a cursory glance at the standard before implementation begins. They'll work from example documents, and then they will look up whatever extensions to various tags that need to be implemented after they get a skeleton of a system in place.
Begin Rant
This is how most systems are developed. So, even this doc is 10k pages, I don't care if the format is understandable. I'm not going to read most of that doc anyway. If it is that long, it must be filled with a ton of unnecessary garbage. Then again, the smtp rfc is less than 20 pages, and *I think* half of it is filled with unnecessary text that can be taken for granted. (I'm just saying here that perhaps my view is skewed) Standards need to remove all ambiguity if possible. That typically means unnecessary clutter to an average developer.
Mostly common sense stuff like this: show an error if the data is too big or whatever
There is probably page after page talking about how every feature works with every other feature...thus adding a lot of duplicate garbage.
End Rant
1.) Put the disc in a sheath, effectively doubling the size of the disc, but rendering it safe from scratches.
2.) Double the size of the protective platstic layer on the disc, or make that protective layer much harder.
3.) Develop technology that can see at a higher resoultion to avoid needing to refocus.
4.) Use more than one laser focused at different distances.
5.) Speed up the ability to switch beams.
Though practically, none of these things are likely to happen... even if they are technically feasable (which I'm sure that most any scientist could figure out how to make that coating harder) it would mean that people could actually use the same discs for a longer period of time, and it would cut into margins for the producers of the discs. I mean come on, how hard is it to make it so that setting the disc on a flat surface (like a coffee table) for a day or two causes the disc to be unreadable. It's ridiculusly easy to scratch now.
Maybe you haven't used many of their products or you take all of the features for granted. I would be dumb not to admit that they don't rely heavily on previous work, but there *was* a lot of innovation that came out of their research and development. Some of the ideas didn't work out for the best, but they led to concepts that work well enough.
For example: Plug and Play might not work as it was intended, but at least now you can get a system that will work. I can add or remove a hard drive or a video card, or whatever, and the kernel doesn't panic. It just find the new hardware and chugs happily along.
Not many solar panels have really gone that long. A more reasonable estimate (given a bit more research) points to %80 efficiency through 20 years of age. About 20 years is the break even point given current energy costs, by the way. Those cells will probably not last much more than 5 more years past 20 (given the typically steep degradation of components after that)...
Mostly, some relaxation might help. I know that it is hard to maintain a consistent tone in written communication. So, we'll give you the benefit of the doubt, and hope that you were just trying to be sincere.
I think this is correct behaviour, but there is nothing stopping anyone from changing the code on their own servers. If this mattered to me on my server, I would just modify the 3 lines of code that do this, and only have it load on startup of the server.
Or, it could be an added option to the already huge config file, during the next release. Maybe someone wants to add the feature?
If code is not your expertise, then you can probably pay someone $100 to do it for you.
Man pages -- examples of the worst documentation on earth. Could be vastly improved by a one line usage example at the top of every man page... Info pages sometimes have this.
Me -- Kid -- No.
Command Line -- I rather use it more than almost anything else. I launch my GUI tools from it. I have just about every useful command line memorized. I'm actually speaking from a point of view that consists of industry experience and knowledge. I like command lines for their speed of use. Though, they require a steep learning curve. A learning curve which is usually unacceptable, and definately not preferable.
(By the way, on the last versions of Ubuntu, Suse, and RedHat Linux that I've used, the gui front end to find doesn't work worth a damn most of the time, and sometimes just flat out crashes.)
Find has its place: in a script
Go out into your office, and ask the person at the front desk... oh hell, ask 10 random people in your office to write down on a piece of paper the proper usage for that find command of yours. Maybe they won't know... And maybe they can't use the crappy gui to figure it out either. But if they lose there stuff... telling someone over the phone or even while standing behind them how to use a command line tool is like taking a trip back to 1994. At least if it were back to 1985, I could feel like I was in a good scifi movie.
The parent was just saying "Hey, look at what is easy." while you are saying "Hey, look at what is more difficult."
There are other excellent find command line utilities that work better/faster/easier than find. I prefer locate, and the search tool provided with ActiveState perl. They are fast enough, and easy to use. Though locate will spit out a bunch of garbage unless you couple it with grep.
Showing me that find can be so powerful as to have like 60 command line parameters just further helps my point along.
Find should not have more than 10 or 15 command line parameters. Anything else is poor design. And 10 is pushing it. As you grow out of your dinosaur habbits then you will learn this. Maybe you'll write a large app some day, or have to maintain code or scripts that someone wrote with 60 parameters. (I hope not though.) It might give you new insight into what composes a good design.
It should be something like
find "whatever I am looking for"
simple scenario first, more complex scenarios added as command line switches. Or possibly... other commands.
By the way, most users feel this way.
Do some research. Make a survey. Work at 5 industry leading/fortune 500 companies. Whatever it takes. Then stop telling your Mom that she should crack open the command line to find where that great cookie recipe went.
Software algorithms can be considered art and is protected by a patent.
Algorithms used in a new and novel way together can be patented.
Copyright law protects the program as a whole.
Slashdot Mirror
Only because you saw and compiled the code yourself... or maybe your compiler had been hacked, or the libraries that Hello World depends on were hacked, or maybe you ran the executable without compiling it yourself. Or maybe the operating system modified the executable before/during/after runtime. Are you sure your printf had a null terminated character at the end of the string? :)
These are typical security bugs that can be avoided, but most companies/organizations/individuals/ ignore them. There are many more, and they can affect any program... even hello world.
Right, driver problem... not poor design of the network block device API... no never that... nor a problem with quality control for signed drivers... not that either... yep! vista includes no breakthrough in driver management and recovery... great state of the art system guys.
It's funny how I've been enjoying multiple month up time on Windows computers too. Sometimes 4 to 6 months at a time, continuously on, and most times under heavy load and stress. Usually running things all day, and through the evening. The only times the computer goes off is literally when the power gets disconnected. This has been the case with my machines since XP came out. Recently, I did have a Linux machine that croaked though.
I'd like to go back to the days when you could just press the button on the side of the box.
Leave the logout as the only option in the menu.
shutdown, and restart only after logout (on the login screen)
sleep automaticaly after a period of no activity. (no need for menu choice)
The same thing that we do everyday pinky... Try and take over the world!!!
He get his ideas from the trance state that he goes into... Not really credible, even for todays scientists...
Still... Even if there were anti-gravity devices, cranes and motors would have been prevelant. Steele working, and other metal working industry would be prevelant. We have space shuttles, and yet there is a lot more infastructure necessary to make that happen. I'm sure they did not just leap technologies until they had this anti-gravity device.
If everything went to hell, I doubt that some future society would find a space shuttle, but I bet they would find an electric motor, a gasoline engine, and a crane or two.
Technology does not occur in an isolated environment. It quickly spreads among societies, even enemy societies. Rest assured that this is enough reason to think that a far technologically advanced Atlantis is a myth.
Yes, we are all infedels, blah, blah, blah... Go home and burn your flag.
By the way, I read that article, and although it is interesting, I really think it is beyond the point. The point is that various legislation protects property, and patents are used for software. Legalease will always be the area of specialist attorneys.
Movies are protected by copyright.
The method of producing effects can be patented.
Algorithms are really methods.
There are some good books on patents and copyrights that would probably help you know more about this subject.
There is some controversy about whether it is ethically correct for software to be patentable, but currently it is the law that you can. The thrust of this controversy is given by the close relationship between Math (algorithms) and softare. Mathematical formulas can't be patented, even they can be trade secrets.
It also helps do that.
Yep, sad but true.
These are fairly new advances by IBM and Sun in the PC market... Oh wait, I mean server market for machines that cost an arm and a leg. And I think they are great. Really, I do. I also agree that Plug and Play doesn't really work at all the way it was intended to work. I'm just saying that it was innovative and that it helped computing in general.
Wait a minute, didn't MS Word come first... Wasn't there this thing called Rich Text Format... Couldn't all modern word processors just be reinventing a "wheel" ...namely the type writer. :)
They might add a feature that isn't in the standard, but that doesn't mean that the standard is irrevocably broken. Many standards are growing entities that are added to as necessity dictates.
Since, the underlying data format is inherintly extensible, if the format is modern and well designed (as this one is) then it could last (even with modifications) a very long time. I would say 20 years or so, which isn't as long as txt files will last (forever), but still a pretty long time.
Also, on another topic, I would like to point out, that most implementors are not going to give more than a cursory glance at the standard before implementation begins. They'll work from example documents, and then they will look up whatever extensions to various tags that need to be implemented after they get a skeleton of a system in place.
Begin Rant
This is how most systems are developed. So, even this doc is 10k pages, I don't care if the format is understandable. I'm not going to read most of that doc anyway. If it is that long, it must be filled with a ton of unnecessary garbage. Then again, the smtp rfc is less than 20 pages, and *I think* half of it is filled with unnecessary text that can be taken for granted. (I'm just saying here that perhaps my view is skewed) Standards need to remove all ambiguity if possible. That typically means unnecessary clutter to an average developer.
Mostly common sense stuff like this: show an error if the data is too big or whatever
There is probably page after page talking about how every feature works with every other feature...thus adding a lot of duplicate garbage.
End Rant
Oh, Shi...
These problems can be overcome.
1.) Put the disc in a sheath, effectively doubling the size of the disc, but rendering it safe from scratches.
2.) Double the size of the protective platstic layer on the disc, or make that protective layer much harder.
3.) Develop technology that can see at a higher resoultion to avoid needing to refocus.
4.) Use more than one laser focused at different distances.
5.) Speed up the ability to switch beams.
Though practically, none of these things are likely to happen... even if they are technically feasable (which I'm sure that most any scientist could figure out how to make that coating harder) it would mean that people could actually use the same discs for a longer period of time, and it would cut into margins for the producers of the discs. I mean come on, how hard is it to make it so that setting the disc on a flat surface (like a coffee table) for a day or two causes the disc to be unreadable. It's ridiculusly easy to scratch now.
Maybe you haven't used many of their products or you take all of the features for granted. I would be dumb not to admit that they don't rely heavily on previous work, but there *was* a lot of innovation that came out of their research and development. Some of the ideas didn't work out for the best, but they led to concepts that work well enough.
For example: Plug and Play might not work as it was intended, but at least now you can get a system that will work. I can add or remove a hard drive or a video card, or whatever, and the kernel doesn't panic. It just find the new hardware and chugs happily along.
Not many solar panels have really gone that long. A more reasonable estimate (given a bit more research) points to %80 efficiency through 20 years of age. About 20 years is the break even point given current energy costs, by the way. Those cells will probably not last much more than 5 more years past 20 (given the typically steep degradation of components after that) ...
Mostly, some relaxation might help. I know that it is hard to maintain a consistent tone in written communication. So, we'll give you the benefit of the doubt, and hope that you were just trying to be sincere.
I think this is correct behaviour, but there is nothing stopping anyone from changing the code on their own servers. If this mattered to me on my server, I would just modify the 3 lines of code that do this, and only have it load on startup of the server.
Or, it could be an added option to the already huge config file, during the next release. Maybe someone wants to add the feature?
If code is not your expertise, then you can probably pay someone $100 to do it for you.
Sounds cool. What are you currently working on?
That is some funny stuff. I'm an athiest, and I still say that is one of the better jokes that I've heard in a while.
Okay, I'll bite.
Man pages -- examples of the worst documentation on earth. Could be vastly improved by a one line usage example at the top of every man page... Info pages sometimes have this.
Me -- Kid -- No.
Command Line -- I rather use it more than almost anything else. I launch my GUI tools from it. I have just about every useful command line memorized. I'm actually speaking from a point of view that consists of industry experience and knowledge. I like command lines for their speed of use. Though, they require a steep learning curve. A learning curve which is usually unacceptable, and definately not preferable.
(By the way, on the last versions of Ubuntu, Suse, and RedHat Linux that I've used, the gui front end to find doesn't work worth a damn most of the time, and sometimes just flat out crashes.)
Find has its place: in a script
Go out into your office, and ask the person at the front desk... oh hell, ask 10 random people in your office to write down on a piece of paper the proper usage for that find command of yours. Maybe they won't know... And maybe they can't use the crappy gui to figure it out either. But if they lose there stuff... telling someone over the phone or even while standing behind them how to use a command line tool is like taking a trip back to 1994. At least if it were back to 1985, I could feel like I was in a good scifi movie.
The parent was just saying "Hey, look at what is easy." while you are saying "Hey, look at what is more difficult."
There are other excellent find command line utilities that work better/faster/easier than find. I prefer locate, and the search tool provided with ActiveState perl. They are fast enough, and easy to use. Though locate will spit out a bunch of garbage unless you couple it with grep.
Showing me that find can be so powerful as to have like 60 command line parameters just further helps my point along.
Find should not have more than 10 or 15 command line parameters. Anything else is poor design. And 10 is pushing it. As you grow out of your dinosaur habbits then you will learn this. Maybe you'll write a large app some day, or have to maintain code or scripts that someone wrote with 60 parameters. (I hope not though.) It might give you new insight into what composes a good design.
It should be something like
find "whatever I am looking for"
simple scenario first, more complex scenarios added as command line switches. Or possibly... other commands.
By the way, most users feel this way.
Do some research. Make a survey. Work at 5 industry leading/fortune 500 companies. Whatever it takes. Then stop telling your Mom that she should crack open the command line to find where that great cookie recipe went.
I know this. I was just trying to keep it simple for the majority of the slashdot readers who don't know what normalizing a vector means.
basically light reflects off of every object that you see. It would all be black or very dark otherwise.
Software algorithms can be considered art and is protected by a patent. Algorithms used in a new and novel way together can be patented. Copyright law protects the program as a whole.