Killing people is not wrong in my moral code. Killing people without provocation is wrong. There are a multitude of circumstances when I could hold a gun to your head and pull the trigger with no remorse and no twinge of concience. There would be emotional feelings of disgust, etc, but I get bad emotions cleaning up runny dog doo too, and that is not against my moral code either. Let's not get into a "US hasn't been provoked" discussion either, as failure to obey articles of surrender is provocation enough for me, and that is not my argument. My only point is that: Killing is not wrong.
Yes, but NT is a microkernal architecture. The "kernal" includes all the associated kernal DLL's, not just the ntoskrnl file which mostly just contains the architechture to load the kernal.
Having experienced both though (and I love Linux BTW) as a workstation, running windows, they crash about the same, with Redhat maybe being a bit more stable. As a server, redhat kicks the pants off XP for stability though.
Actually I find that facinating, being a witness to the event, that the legend came full circle. I was not aware of this as being an urban legend. This may have been where he got the idea, having heard it from someone else in a bar or something (not being a technical person I'm sure he wasn't on the internet.)
In construction it is a very common thing to not be paid by your general contractor due to cascading bankruptcies. I have seen many contractors take different precausions against not getting paid, of which I found this one particularly clever. It's possible it's not a legend at all and does stem back to to the 30's and 40's or even before since the practice is very easy and cheap for a mason to perform, requiring only about a 10"x10" thin sheet of glass and about 15 seconds of installation time; about the same cost and time that accompanies laying a couple brick ties.
Needless to say (not trying to convince you of the legend, as both I and you are random internet entities that could care less what each other think) but that's the first urban legend I ever saw practiced:0
My boss used to do this. When I was in college I had a part time job laying brick. My boss would embed a glass pane halfwy up any chimney we built. He would then drop a brick down the chimney when the check cleared. When one check didn't clear, he got a call a few months later that the fireplace was defective. He told them he hadn't "turned it on" yeat because he hadn't been paid. As soon as he was paid, it started working.
The idea of a drive is persistant storage. Disk caching algorithms nowadays are excellent and normally surpass ram drives, since in reality, you are pretty much ALWAYS using a ramdrive. Not to mention the network issues brought up in other threads, and the simple fact that the main reason for raid 5 is redundancy of storage in order to boost reliability not just performance, and by putting everything in ram, there goes reliability. Sounds like, if you are not concerned with reliability as much, is a Raid-1 array, which implements striping but not parity.
No, it means they run a clean automated daily build, which is common practice for most projects. Incremental builds are great for devs, but the official build is most always done clean.
Even as a dev, I try to run a clean build of my systems when I leave Friday. I can't tell you how many times a weird bug has been caused by some missed dependancy that the make system wasn't rebuilding.
What I do is create a GUI thread which handles all interface to the GUI. All of my other threads then fire their events to that thread through an interface that IS threadsafe. The GUI thread then synchronously handles the GUI events. This abstraction away from your actual GUI API allows you to more easily port your app to another platform because all of your X11 specific code is contained in one place.
You can't have such a far swweping generalization. I know many cops who this is true for, but many others who idealistically signed up for the job to be a hero and keep society safe and are frustrated as hell spending alot of their time tax collecting by enforcing minor traffic violations.
A a citizen of the US, I have the constitutional right to arrest anyone I see fit to arrest. Arrest is not a special right of police officers, but a constitutional right of all citizens.
Re:Let's hope this means the end of veal
on
Lab-Grown Steak
·
· Score: 1
Vegitables aren't food. Vegitables are what food eats.
There have been studies on St. Johns Wort, I have read some of them before deciding to try the stuff myself.
The active ingredient is Hypercin. It is an interesting beast in that Hypercin works both as an SSRI and an MAOI. THhis combination is normally lethal, but for some as of yet unknown reason this particular chemical does not have death as a side affect, so it may be the best drug in the rare case of someone needing the effects of both classes of drugs. It is an extremely mild SSRI however, and exceeding the recommended dosage does not make it any stronger but only increases it's side affects. All in all, it is a rather safe chemical, but it is not recommended you mix it with any other SSRI or MAOI for fear of that potential lethal combination cropping un=p. Because of it's mild nature, it is generally not strong enough to treat any but the mildest cases of depression. If you "think" you are depressed, the depression is probably so mild that Hypercin might just work, and it doesn't need a perscription, so it's probably worth a shot if only FOR the placebo affect. If you have real clinical depression, your probably out of Hypercin's league and are better off with a stronger SSRI like Prozac, Zoloft, Celexa, etc.. or some other class of anti-depressants, like wellbutrin, or the tricyclics.
>How many open source success stories are there, >where the open-source solution is so clearly >superior that it's used by everyone? Uh, zero.
Well, as a developer, I see cygwin or mingW on just about every windows platform because nothing beats a goot GNU toolkit for development. As seperate projects that have each stomped all the competition, bash, grep, sed, etc are clearly dominant. Yes, most of these tools are clones of proprietary solutions, but most of them have come to completely replace their older cousins for reasons of quality, standardization or availability.
>Well, how about open source application that are >good enough to compete with proprietary >software? Uh, one. Mozilla, perhaps.
Same answer as above. Add apache to this list which is still the dominate web server. MySQL has a nice following and scares the poop out of SQL Server.. a huge Massively Multiplayer game (Dark Age of Camelot) runs it as it's backend because SQL Server and Oracle seemed to be just to expensive for the feature set they had beyond the Open Source solution. Back Orifice 2K WAS a popular remote admin tool for windows boxes, but the virus scanners kill it now.
>How many are "up-and-comers" that just need good >word-of-mouth to take over from a proprietary >solution? Uh, zero. (IE is already free-money)
If they need more word of mouth, then you probably haven't heard of them yet. There are some open source graphics engines which are up and coming and near ready to compete with their proprietary cousins.. gnutella has been a very nice architecture for one of the dominant P2P networks, which are very big with end users.
>The only one that I can think of MAYBE for the >latter category is Gimp, and the user interface >on that thing is so horrible as to be useless >for anyone but a true geek (at least, the last >time I used it which was admittedly a while ago).
uhh.. it's proprietary cousin's interfaces are just as bad. Face it, anything more complex then MSPaint is a geek tool and needs a geek interface.
Open source solutions fill a huge niche that needs filling. Many things in computer science need to be done, but there just isn't a nice $$ stream in it, so it gets neglected, or are simple enough that why pay for the solution when you can write it yourself, as is the case with alot of smaller tools (cat for example). Open Source projects typically don't dominate on the client side because 1) this is the biggest market and competition is fierce, and massive $$ goes into funding development for these platforms, and $=RAD. 2) Open Source projects don't advertise, since there is no profit motivation, hence the uninformed user remains uninformed. Therefore, there are few client side apps that are open source, because why support a project for free that is doomed? But don't knock the development model which gives us an excellent and protected public resource of shared pre-developed systems that don't need to be purchased or developed from scratch.
You can run palmOS on the network for all i care as long as it's not in the demilitarized zone. There are no security holes in any OS that is behind a firewall; this is the "safe" environment. It could me intentionally comprimized by a user on the inside (tcp over http would be a fun way;) but it's as safe as your firewall from outside attacks.
What you need to do to work with the multithreading issues, etc with the multiple systems is create your own primitives that you need, instead of using the vendor supplied ones. For instance, MSVC uses CRITICAL_SECTION whereas cc will use a mutex. The behavior of these are significantly different, but similar in function. What you need to do is create a class that acts as a Mutex, and implement this class differently on the different platforms. Then, in the code where rapid development counts, your Mutex can be used with no regard to platform differences. Do this for all platform dependent things suchas interlocked integer functions, thread creation/destruction, network functions, etc. Use the std lib to wrap some differences, such as file access.
And don't forget Ephedrine. In low dosages it makes you much sharper and more energetic. But go easy on it, too much and you will not be able to think and just sit there staring at the code and shaking.
I have to take serious issue with the numerous comments here about how long hours spent coding leads to kludges and hacks and inelegant code that is bound to fail. On the contrary, my best work has always been done in marathon sessions. While I have to agree that waiting until the last moment to get a project completed is assinine, there is nothing wrong with long marathon sessions.
In my experience, the worst code is written in small chunks, writing a bit of code, researching some more or going home, then writing another small chunk; the larger picture of the synthesis of the entire project never seems to come together this way. Unfortunately, this is the way most of us are encouraged to code... with lots of breaks and sleep in between. I have found that when I am in "the zone" coding, the best thing I can do is stay there as long as possible, going for as much as 72 hours at a time, and sometimes falling asleep on the keyboard, only to wake a few hours later and keep going. The code written this way in 1 week is more productivity than 6 months of my work normally. The code I write is elegant, and mostly bug free. At these times, the entire structure of the code all comes together in my brain, and I am just typing it out as fast as my fingers will go. Sleep is a waste of time when your brain is in overdrive. If you are looking for ways to "get through" these sessions, however, then you are not in the session and your best bet is to just go home. When you don't want the session to end and you are willing to forego sleep, food, restroom, nicotene, sex, just to keep going, THEN you are going to write some damn nice code, so don't you dare go home;)
But don't confuse long hours staring at the code and poking in a few lines with a marathon coding session.
Your generalizing too much here. There are many types of AI, and many languages to do them in. Each language is an abstraction of the problem space you are working in, so rather than making a blanket statement about a good language for AI, you should pair up the AI your talking about with a preferred language.
1) Genetic algorithms are probably in the category you are talkng about. Good ones take massive processor power to come up with. Once they are done though, the end result is generally small and fast. This type of AI is usefull fr finding a near optimal solution in a complex but static problem space, ie What is the best wing design for this airplane. C, C++, Assembly are typically good languages.
2) Neural networks. These can take up alot of processing power, or not, depending on their complexity. There is a rather large family of these also, existing in both asynchronous and synchronous forms. These are used to pattern match and generalize. Good for things like handwriting recognition. C++, Java are pretty good languages.
3) Pattern matching knowledge databases. These are good at cross referencing data by finding subtle patterns in it. The construction of the database and pattern finding is intensive, but use typically is not. Lisp, Java, SQL, Perl can be good here.
4) Expert systems. Used to categorize information for retrieval based on a information given by the user. Not at all processor intensive. Lisp, java good for this.
5) State machines. This is where our Robocode fits in. Very object like, I can hardly think of a better language than Java for it's simplicity. These are not very processor intensive. C++, or C# might be good candidates.
6) High level applied systems, lumping in natural language processing, vision recognition, etc.. These are generally heavy duty specialized systems that can be very data and processor intensive. C++ is a good general purpose choice for these, but each needs to be looked at individually.
Actually, I think the reason most viruses are simple is twofold: 1) Most of the times, some of the best strategies are simple ones. More complex better ones may exist, but they are not generally worth the trouble. I once saw a long run of a genetic state machine prisoner's dillema solver. Although some very interesting complex strategies came up after VERY long run times, the tit-for-tat strategy, which is one of the simplest, dominated most of the run.
2) I used to be interested in viri writing and the like when I was 12-14 and a mediocre coder. Once I got good at what I did, I realized that constructive tasks are much more rewarding then destructive. I assume it is probably like this with most coders. People who want to cause havok don't have the patience to build complex systems typically, and builders of complex systems don't want to rip others hard work apart because we have more respect for it.
Best one on the market so far is JumpGate. It kinda sucks though, as there is no planetside and physics is a bit broken, since people are so spoiled growing up in an atmosphere that they think drag is natural;)
A Star Wars Galaxies Expansion Pack is slated to have FFE-like space battles, but probably lacking the real physics also.
Elite 4 is (still) in early development. Multiplayer, but not massively so.
My company is working on one;)
Earth and Beyond is coming out soon. Limited Z axis range to increase Player encounters and planetside is done with Avatars only:P Probably no real physics here either.
> 500 + 250 + 200 = $950 and the judges will need $50 for beer and > pretzels. Sounds good to me. I figured Jorrit would come up with a > good use for the grant.
:-)
That $50 will stay on the account I created for it. It is a small reserver for later and also to pay for the costs of transfering money from USD to EURO and vice versa. BTW the $1000 is already slightly less due to the transferal on a EURO account.
Slashdot Mirror
Killing people is not wrong in my moral code.
Killing people without provocation is wrong.
There are a multitude of circumstances when I could hold a gun to your head and pull the trigger with no remorse and no twinge of concience. There would be emotional feelings of disgust, etc, but I get bad emotions cleaning up runny dog doo too, and that is not against my moral code either.
Let's not get into a "US hasn't been provoked" discussion either, as failure to obey articles of surrender is provocation enough for me, and that is not my argument. My only point is that: Killing is not wrong.
Yes, but NT is a microkernal architecture. The "kernal" includes all the associated kernal DLL's, not just the ntoskrnl file which mostly just contains the architechture to load the kernal.
Actually the Kernal is 60-80 MB ;)
Having experienced both though (and I love Linux BTW) as a workstation, running windows, they crash about the same, with Redhat maybe being a bit more stable. As a server, redhat kicks the pants off XP for stability though.
Actually I find that facinating, being a witness to the event, that the legend came full circle. I was not aware of this as being an urban legend. This may have been where he got the idea, having heard it from someone else in a bar or something (not being a technical person I'm sure he wasn't on the internet.)
:0
In construction it is a very common thing to not be paid by your general contractor due to cascading bankruptcies. I have seen many contractors take different precausions against not getting paid, of which I found this one particularly clever. It's possible it's not a legend at all and does stem back to to the 30's and 40's or even before since the practice is very easy and cheap for a mason to perform, requiring only about a 10"x10" thin sheet of glass and about 15 seconds of installation time; about the same cost and time that accompanies laying a couple brick ties.
Needless to say (not trying to convince you of the legend, as both I and you are random internet entities that could care less what each other think) but that's the first urban legend I ever saw practiced
My boss used to do this. When I was in college I had a part time job laying brick. My boss would embed a glass pane halfwy up any chimney we built. He would then drop a brick down the chimney when the check cleared. When one check didn't clear, he got a call a few months later that the fireplace was defective. He told them he hadn't "turned it on" yeat because he hadn't been paid. As soon as he was paid, it started working.
Dumb idea.
The idea of a drive is persistant storage. Disk caching algorithms nowadays are excellent and normally surpass ram drives, since in reality, you are pretty much ALWAYS using a ramdrive. Not to mention the network issues brought up in other threads, and the simple fact that the main reason for raid 5 is redundancy of storage in order to boost reliability not just performance, and by putting everything in ram, there goes reliability. Sounds like, if you are not concerned with reliability as much, is a Raid-1 array, which implements striping but not parity.
No, it means they run a clean automated daily build, which is common practice for most projects. Incremental builds are great for devs, but the official build is most always done clean.
Even as a dev, I try to run a clean build of my systems when I leave Friday. I can't tell you how many times a weird bug has been caused by some missed dependancy that the make system wasn't rebuilding.
What I do is create a GUI thread which handles all interface to the GUI. All of my other threads then fire their events to that thread through an interface that IS threadsafe. The GUI thread then synchronously handles the GUI events. This abstraction away from your actual GUI API allows you to more easily port your app to another platform because all of your X11 specific code is contained in one place.
You can't have such a far swweping generalization. I know many cops who this is true for, but many others who idealistically signed up for the job to be a hero and keep society safe and are frustrated as hell spending alot of their time tax collecting by enforcing minor traffic violations.
A a citizen of the US, I have the constitutional right to arrest anyone I see fit to arrest. Arrest is not a special right of police officers, but a constitutional right of all citizens.
Vegitables aren't food. Vegitables are what food eats.
There have been studies on St. Johns Wort, I have read some of them before deciding to try the stuff myself.
The active ingredient is Hypercin. It is an interesting beast in that Hypercin works both as an SSRI and an MAOI. THhis combination is normally lethal, but for some as of yet unknown reason this particular chemical does not have death as a side affect, so it may be the best drug in the rare case of someone needing the effects of both classes of drugs. It is an extremely mild SSRI however, and exceeding the recommended dosage does not make it any stronger but only increases it's side affects. All in all, it is a rather safe chemical, but it is not recommended you mix it with any other SSRI or MAOI for fear of that potential lethal combination cropping un=p. Because of it's mild nature, it is generally not strong enough to treat any but the mildest cases of depression. If you "think" you are depressed, the depression is probably so mild that Hypercin might just work, and it doesn't need a perscription, so it's probably worth a shot if only FOR the placebo affect. If you have real clinical depression, your probably out of Hypercin's league and are better off with a stronger SSRI like Prozac, Zoloft, Celexa, etc.. or some other class of anti-depressants, like wellbutrin, or the tricyclics.
>How many open source success stories are there,
.
>where the open-source solution is so clearly
>superior that it's used by everyone? Uh, zero.
Well, as a developer, I see cygwin or mingW on just about every windows platform because nothing beats a goot GNU toolkit for development. As seperate projects that have each stomped all the competition, bash, grep, sed, etc are clearly dominant. Yes, most of these tools are clones of proprietary solutions, but most of them have come to completely replace their older cousins for reasons of quality, standardization or availability.
>Well, how about open source application that are
>good enough to compete with proprietary
>software? Uh, one. Mozilla, perhaps.
Same answer as above. Add apache to this list which is still the dominate web server. MySQL has a nice following and scares the poop out of SQL Server.. a huge Massively Multiplayer game (Dark Age of Camelot) runs it as it's backend because SQL Server and Oracle seemed to be just to expensive for the feature set they had beyond the Open Source solution. Back Orifice 2K WAS a popular remote admin tool for windows boxes, but the virus scanners kill it now
>How many are "up-and-comers" that just need good
>word-of-mouth to take over from a proprietary
>solution? Uh, zero. (IE is already free-money)
If they need more word of mouth, then you probably haven't heard of them yet. There are some open source graphics engines which are up and coming and near ready to compete with their proprietary cousins.. gnutella has been a very nice architecture for one of the dominant P2P networks, which are very big with end users.
>The only one that I can think of MAYBE for the
>latter category is Gimp, and the user interface
>on that thing is so horrible as to be useless
>for anyone but a true geek (at least, the last
>time I used it which was admittedly a while ago).
uhh.. it's proprietary cousin's interfaces are just as bad. Face it, anything more complex then MSPaint is a geek tool and needs a geek interface.
Open source solutions fill a huge niche that needs filling. Many things in computer science need to be done, but there just isn't a nice $$ stream in it, so it gets neglected, or are simple enough that why pay for the solution when you can write it yourself, as is the case with alot of smaller tools (cat for example). Open Source projects typically don't dominate on the client side because 1) this is the biggest market and competition is fierce, and massive $$ goes into funding development for these platforms, and $=RAD. 2) Open Source projects don't advertise, since there is no profit motivation, hence the uninformed user remains uninformed. Therefore, there are few client side apps that are open source, because why support a project for free that is doomed? But don't knock the development model which gives us an excellent and protected public resource of shared pre-developed systems that don't need to be purchased or developed from scratch.
You can run palmOS on the network for all i care as long as it's not in the demilitarized zone. There are no security holes in any OS that is behind a firewall; this is the "safe" environment. It could me intentionally comprimized by a user on the inside (tcp over http would be a fun way ;) but it's as safe as your firewall from outside attacks.
What you need to do to work with the multithreading issues, etc with the multiple systems is create your own primitives that you need, instead of using the vendor supplied ones. For instance, MSVC uses CRITICAL_SECTION whereas cc will use a mutex. The behavior of these are significantly different, but similar in function. What you need to do is create a class that acts as a Mutex, and implement this class differently on the different platforms. Then, in the code where rapid development counts, your Mutex can be used with no regard to platform differences. Do this for all platform dependent things suchas interlocked integer functions, thread creation/destruction, network functions, etc. Use the std lib to wrap some differences, such as file access.
And don't forget Ephedrine. In low dosages it makes you much sharper and more energetic. But go easy on it, too much and you will not be able to think and just sit there staring at the code and shaking.
I have to take serious issue with the numerous comments here about how long hours spent coding leads to kludges and hacks and inelegant code that is bound to fail. On the contrary, my best work has always been done in marathon sessions. While I have to agree that waiting until the last moment to get a project completed is assinine, there is nothing wrong with long marathon sessions.
;)
In my experience, the worst code is written in small chunks, writing a bit of code, researching some more or going home, then writing another small chunk; the larger picture of the synthesis of the entire project never seems to come together this way. Unfortunately, this is the way most of us are encouraged to code... with lots of breaks and sleep in between. I have found that when I am in "the zone" coding, the best thing I can do is stay there as long as possible, going for as much as 72 hours at a time, and sometimes falling asleep on the keyboard, only to wake a few hours later and keep going. The code written this way in 1 week is more productivity than 6 months of my work normally. The code I write is elegant, and mostly bug free. At these times, the entire structure of the code all comes together in my brain, and I am just typing it out as fast as my fingers will go. Sleep is a waste of time when your brain is in overdrive. If you are looking for ways to "get through" these sessions, however, then you are not in the session and your best bet is to just go home. When you don't want the session to end and you are willing to forego sleep, food, restroom, nicotene, sex, just to keep going, THEN you are going to write some damn nice code, so don't you dare go home
But don't confuse long hours staring at the code and poking in a few lines with a marathon coding session.
Your generalizing too much here. There are many types of AI, and many languages to do them in. Each language is an abstraction of the problem space you are working in, so rather than making a blanket statement about a good language for AI, you should pair up the AI your talking about with a preferred language.
1) Genetic algorithms are probably in the category you are talkng about. Good ones take massive processor power to come up with. Once they are done though, the end result is generally small and fast. This type of AI is usefull fr finding a near optimal solution in a complex but static problem space, ie What is the best wing design for this airplane. C, C++, Assembly are typically good languages.
2) Neural networks. These can take up alot of processing power, or not, depending on their complexity. There is a rather large family of these also, existing in both asynchronous and synchronous forms. These are used to pattern match and generalize. Good for things like handwriting recognition. C++, Java are pretty good languages.
3) Pattern matching knowledge databases. These are good at cross referencing data by finding subtle patterns in it. The construction of the database and pattern finding is intensive, but use typically is not. Lisp, Java, SQL, Perl can be good here.
4) Expert systems. Used to categorize information for retrieval based on a information given by the user. Not at all processor intensive. Lisp, java good for this.
5) State machines. This is where our Robocode fits in. Very object like, I can hardly think of a better language than Java for it's simplicity. These are not very processor intensive. C++, or C# might be good candidates.
6) High level applied systems, lumping in natural language processing, vision recognition, etc.. These are generally heavy duty specialized systems that can be very data and processor intensive. C++ is a good general purpose choice for these, but each needs to be looked at individually.
Actually, I think the reason most viruses are simple is twofold:
1) Most of the times, some of the best strategies are simple ones. More complex better ones may exist, but they are not generally worth the trouble. I once saw a long run of a genetic state machine prisoner's dillema solver. Although some very interesting complex strategies came up after VERY long run times, the tit-for-tat strategy, which is one of the simplest, dominated most of the run.
2) I used to be interested in viri writing and the like when I was 12-14 and a mediocre coder. Once I got good at what I did, I realized that constructive tasks are much more rewarding then destructive. I assume it is probably like this with most coders. People who want to cause havok don't have the patience to build complex systems typically, and builders of complex systems don't want to rip others hard work apart because we have more respect for it.
1st
Best one on the market so far is JumpGate. ;)
;)
:P Probably no real physics here either.
It kinda sucks though, as there is no planetside and physics is a bit broken, since people are so spoiled growing up in an atmosphere that they think drag is natural
A Star Wars Galaxies Expansion Pack is slated to have FFE-like space battles, but probably lacking the real physics also.
Elite 4 is (still) in early development. Multiplayer, but not massively so.
My company is working on one
Earth and Beyond is coming out soon. Limited Z axis range to increase Player encounters and planetside is done with Avatars only
Bill Bohan wrote:
> Jorrit Tyberghein wrote:
> 500 + 250 + 200 = $950 and the judges will need $50 for beer and
> pretzels. Sounds good to me. I figured Jorrit would come up with a
> good use for the grant.
:-)
That $50 will stay on the account I created for it. It is a small reserver for later and also to pay for the costs of transfering money from USD to EURO and vice versa. BTW the $1000 is already slightly less due to the transferal on a EURO account.
Greetings,
http://www.geocities.com/procyon101/
Here it is.
QNX derivative developer here. glad to see someone else in this area not MS bound.