A good way to counter PK'ing is just to force hardcore rules. If you die, you get shipped back to level 1, no experience, no possessions, no training, nothing. In a way, it gets rid of the attitude of "If I die, I'll just respawn somewhere."
So, PK'ing won't go away, but everyone will be well aware of PK'ers, and there will be mobs of people that will band together to kill a PK'er, or an army to kill a group of PK'ers.
Making it seem even more like real life, with all of the consequences, will help alleviate the PK'ing. It won't get rid of it entirely, as evidenced by the crazies that live in this world, but at least it will stop those ones that PK because they know that there are no real dire consequences.
welcome to america. where the most incompetent employee is promoted to the position where he/she will do the least amount of damage... Management.
Bad paraphrase of Scott Adam's "The Dilbert Principle."
"The basic concept of the Dilbert Principle is that the most ineffective workers are systematically moved to the place where they can do the least damage: management." -The Dilbert Principle, p.14
Excellent. They counter your paranoia by turning you into their own little advertising machine. It ranks right up there with wearing clothes that say "Old Navy," or "Aeropstale" on them. They don't pay me to wear them, so I'm not going to go "spread the word."
The original recipe that AB used was much better than the one they use now. The recipe changed as a result of prohibition, when nearly every other competing brewery bit the big one (with exception of miller.) AB specialized at that time in making sodas and cattle feed.
After prohibition, it was left to market researchers to find the best selling beer formula, which led them to produce this bland fizzy thing that they called "Budweiser." Later on, the "Lite" revolution hit the market, which putrified the beer even more.
And you know what really stinks? All of the AB breweries have the capability of producing some excellent beers! It sucks that the market tells them not to.
A lot of times, just installing a service pack will upgrade the kernel in Windows. Windows 2000 & Windows XP do not have differences only in the kernel, and I think I've seen NTKernel.dll being updated at least a couple of times when installing service packs.
As for Linux 2.4->2.6, the only issue(s) I ran into were driver and ignorance related. I compiled ALSA and the network drivers directly into the kernel, but I didn't know that you need to manually set the volumes for the mixer. After I did that, I use alsamixergui, my sound worked fine. The only other issue that I had was the Nvidia graphics driver not working correctly. I re-compiled that, and it works just fine now.
I'd say that a bigger update to your system is an update to GCC, or an update to GNOME or KDE.
If I cared enough about the topic to actually do the research, you would definitely get an accurate report. Since it seems that you care deeply about such things, I'll leave it to you to drudge up the names and the totals. I'm pretty certain that you're going to find that I'm correct in where I stand.
If you don't like the top 30 totals, then you can get all of the top 50 totals for the past ten years, and you'll probably get near the same percentage.
Of course, this is all speculation, but as I've said, I don't care enough about it to actually invest the work. I think that females are just as gifted as males are, but I also take into account the actual popularity of the "sport" amongst the sexes.
CRN: Where do you see Linux being successful today?
TAYLOR: Definitely on the edge. You're just seeing edge services continue, such as firewall, appliances and those types of devices. Obviously, Unix migrations are happening. That's where, primarily, custom applications that people have written in-house are being moved over to Linux. But you're not seeing this huge ISV community created. Yes, some ISVs are being created, but not any massive ones. And the other place we see it is high-performance computing, scientific computing clusters that have lots and lots of servers.
The #5 is a 10 peice Chicken McNugget meal. It isn't even a burger. Sometimes the nuggets are undercooked, and quite possibly detrimental to your health. Plus, there are only 10 peices, not a really filling number like 20. It costs about $4.60 or so.
Yeah, I hit McDonald's a lot.
Anyway. He's trying to say that Window has three peices. 1: Kernel. 2: Core OS & GUI. 3: Servers. If someone wants only the "Diet Coke" in his eyes, then we have to strip away two of the three. So, what part do you want? The Kernel? The GUI? The servers? All being said and done, you will not have the functionality that you need.
Anjelina and Alexandra are probably the exceptions that prove the case. If there have been two women that have been ranked within the top 30 for the year in the past 9 years, we can do some math on it.
We take the top 30 for each of the 9 years, and we will have 270 total players that have been ranked. If there have been only 2 women of that 270, I'd say that it is a rather skewed ratio.
I'm not sexist, but I can make a rather valid observation that men tend to approach games like Chess in a way that is completely different than women. With regards to whether or not they are more successful, the evidence has to speak for itself.
"It's not the fact that divorce is legal that's killing our marriages, it's the bad marriages that are causing so much divorce."
I'd take it even further than that, and say "It's not the fact that divorce is legal that's killing our marriages, it's because divorce is legal that people don't think twice about getting married."
And for those, it kinda sucks since they'll need a new computer to go with their spanking new GFX card.
Doubtful. They'll probably have to drop ~$120 for a branch spanking new mobo that supports PCIX, but they won't have to replace any of the other components. I'm sure Nvidia, AMD, or VIA will chug out a mobo that has socket A + PCIX, and Intel will come out with a Socket 478 + PCIX board (that'll probably be the first one that hits the market).
I think that.Net has a very good chance of crushing Java in the realm of web apps. It's an excellent tool that has many things to work with. Java does too, I'll admit, but you run into the design problems and virtual machine things with java. The JVM is too tight to work with, and the work-arounds (to get to the OS) are rather kludgy.
I do think that Java is a good tool, but as far as efficiency goes....Net has it beat. As far as development tools go,.Net Studio beats pretty much everything that's out there. I only wish we could come up with a good GTK or QT based RAD environment like VS.NET, because it would be a hell of a lot nicer to do my work away from Windows (bleh).
...they can enfore their patents and - whooops, Mono/dotGnu have vanished.
Are you sure you have a good understanding of what a patent is? They are not enforceble if you do not use the same method as the one that is patented. Essentially, MS has patented certain algorithms that happen within Windows.Forms, which can be and are being rewritten in another way.
I doubt that an API is patentable, since it isn't a method or a material object. Then again, if it were, enforcing it against Mono or DotGNU is pointless... the projects are not profiting from the sale of the technology. They don't even exist in the same marketplace as the framework, since they are completely free.
It is a semantic difference, but the difference between them manifests itself in performance. When you script a page, you have the http server running the script for each page that is being requested. You also have the server spawning processes to handle things like (in MS terms) ActiveX, ADO, (in Unix terms) external library calls, external programs for handling things, etc.
When you can compile the code, you don't have to worry so much about the performance of the http server, nor do you have to worry as much about the speed of the server. You have the benefit of threads, asynchronous execution, etc. This increases the stability of the http server itself, because the execution environment has been separated from the the server (which is not the case in scripting).
As for developer vs. programmer, I've found that there's not much of a difference between those terms. I'd call the HTML/Dreamweaver/Flash people "webmasters" or "web designers" mostly because they don't have the pretense of actual coding. I certainly wish that there was a separate and distinct term for those of us who love and understand how computers function, care about the efficiency of the internals, and code to that effect. I've met many "programmers" that judge actual programming languages by the number of libraries that the producers of a particular IDE have shipped. I've also met many that solve the performance problem by throwing hardware at it, instead of resolving the source of the problem.
CGI just means that there is compiled code that sits next to the server, and the server talks to it. You don't have the issues in JSP and ASP.NET that you do in ASP/PHP/PERL (context-switching, waiting on OS-calls, etc), because they are not interpreted.
You will always loose functionalty or efficiency when trying to make sure your system can port to everything.
You couldn't be more wrong. You can do almost anything with the tools that are present as a standard. The real issue is whether or not you want to bother to learn how to use them.
On the other hand... if someone shipped FireFox as the "Internet" icon on the desktop, they also wouldn't care. They would use it. Then they would complain when they can't get that site with embedded Media Player streaming to work.
As one who does do web design, I'm very inclined to enquote 'programmers.' There is very little that a web designer has to understand, and even less if you introduce them to the "webbot" world of Frontpage.
It's very important to follow the set standards. There's a reason why every other business adheres to these standards, because adhering is in their best interest. MS gets away with permitting developers to program outside of the standards, because it has leveraged it's desktop monopoly. People assume that IE is going to be used by everyone, and so they don't pay attention to the more important issue of interoperability.
BTW, selectedValue does follow proper OO structure, since it is just a Property of the Select element. It isn't standard, nor is much more work to type in the standard-adhering way. Javascript is kinda dangerous to work with, mostly because a lot of people turn it off.
Web developers are not programmers. Their work consists mainly of scripting. I know. I get paid to do it. Unless a web developer delves into the world of CGI, I wouldn't consider them a programmer. ASP.NET is CGI, C is, JSP is, ASP is not. PHP is not. PERL is not.
I, myself, could do without MS's "additions." Some of them have been useful, yes, but mostly they are detrimental. Have you ever tried to develop and integrate a client-side ActiveX control that gets embedded in the browser? I have. It sucks.
Yeah, but if a gang of newbs all got together and killed the higher level PK, then it would be done.
Then again, it's doubtful if you could have a high level PK'er, unless they start out normal and get twisted towards the end.
A good way to counter PK'ing is just to force hardcore rules. If you die, you get shipped back to level 1, no experience, no possessions, no training, nothing. In a way, it gets rid of the attitude of "If I die, I'll just respawn somewhere."
So, PK'ing won't go away, but everyone will be well aware of PK'ers, and there will be mobs of people that will band together to kill a PK'er, or an army to kill a group of PK'ers.
Making it seem even more like real life, with all of the consequences, will help alleviate the PK'ing. It won't get rid of it entirely, as evidenced by the crazies that live in this world, but at least it will stop those ones that PK because they know that there are no real dire consequences.
welcome to america. where the most incompetent employee is promoted to the position where he/she will do the least amount of damage... Management.
Bad paraphrase of Scott Adam's "The Dilbert Principle."
"The basic concept of the Dilbert Principle is that the most ineffective workers are systematically moved to the place where they can do the least damage: management."
-The Dilbert Principle, p.14
Give credit where credit is due.
I'm glad I hold that distinction. A pity it wasn't something stupid like:
Excellent. They counter your paranoia by turning you into their own little advertising machine. It ranks right up there with wearing clothes that say "Old Navy," or "Aeropstale" on them. They don't pay me to wear them, so I'm not going to go "spread the word."
The original recipe that AB used was much better than the one they use now. The recipe changed as a result of prohibition, when nearly every other competing brewery bit the big one (with exception of miller.) AB specialized at that time in making sodas and cattle feed.
After prohibition, it was left to market researchers to find the best selling beer formula, which led them to produce this bland fizzy thing that they called "Budweiser." Later on, the "Lite" revolution hit the market, which putrified the beer even more.
And you know what really stinks? All of the AB breweries have the capability of producing some excellent beers! It sucks that the market tells them not to.
A lot of times, just installing a service pack will upgrade the kernel in Windows. Windows 2000 & Windows XP do not have differences only in the kernel, and I think I've seen NTKernel.dll being updated at least a couple of times when installing service packs.
As for Linux 2.4->2.6, the only issue(s) I ran into were driver and ignorance related. I compiled ALSA and the network drivers directly into the kernel, but I didn't know that you need to manually set the volumes for the mixer. After I did that, I use alsamixergui, my sound worked fine. The only other issue that I had was the Nvidia graphics driver not working correctly. I re-compiled that, and it works just fine now.
I'd say that a bigger update to your system is an update to GCC, or an update to GNOME or KDE.
If I cared enough about the topic to actually do the research, you would definitely get an accurate report. Since it seems that you care deeply about such things, I'll leave it to you to drudge up the names and the totals. I'm pretty certain that you're going to find that I'm correct in where I stand.
If you don't like the top 30 totals, then you can get all of the top 50 totals for the past ten years, and you'll probably get near the same percentage.
Of course, this is all speculation, but as I've said, I don't care enough about it to actually invest the work. I think that females are just as gifted as males are, but I also take into account the actual popularity of the "sport" amongst the sexes.
You have to love this shit.
CRN: Where do you see Linux being successful today?
TAYLOR: Definitely on the edge. You're just seeing edge services continue, such as firewall, appliances and those types of devices. Obviously, Unix migrations are happening. That's where, primarily, custom applications that people have written in-house are being moved over to Linux. But you're not seeing this huge ISV community created. Yes, some ISVs are being created, but not any massive ones. And the other place we see it is high-performance computing, scientific computing clusters that have lots and lots of servers.
Huge ISV's. Hmm... Wall Street. Amazon. Yahoo. Google. IBM.
The #5 is a 10 peice Chicken McNugget meal. It isn't even a burger. Sometimes the nuggets are undercooked, and quite possibly detrimental to your health. Plus, there are only 10 peices, not a really filling number like 20. It costs about $4.60 or so.
Yeah, I hit McDonald's a lot.
Anyway. He's trying to say that Window has three peices. 1: Kernel. 2: Core OS & GUI. 3: Servers. If someone wants only the "Diet Coke" in his eyes, then we have to strip away two of the three. So, what part do you want? The Kernel? The GUI? The servers? All being said and done, you will not have the functionality that you need.
This marketing dude is stupid and duplicitous.
Yeah, he'll realize that it's hard to drink beer why the pizza slice is in the way.
Anjelina and Alexandra are probably the exceptions that prove the case. If there have been two women that have been ranked within the top 30 for the year in the past 9 years, we can do some math on it.
We take the top 30 for each of the 9 years, and we will have 270 total players that have been ranked. If there have been only 2 women of that 270, I'd say that it is a rather skewed ratio.
I'm not sexist, but I can make a rather valid observation that men tend to approach games like Chess in a way that is completely different than women. With regards to whether or not they are more successful, the evidence has to speak for itself.
The Gay Quake 3 Arena Championship
Heh... Imagine the new Models and Skins that come out for that one. Uh oh, he's got his rocket launcher loaded and pointed.
"It's not the fact that divorce is legal that's killing our marriages, it's the bad marriages that are causing so much divorce."
I'd take it even further than that, and say "It's not the fact that divorce is legal that's killing our marriages, it's because divorce is legal that people don't think twice about getting married."
I would, but I posted already. Doh!
And for those, it kinda sucks since they'll need a new computer to go with their spanking new GFX card.
Doubtful. They'll probably have to drop ~$120 for a branch spanking new mobo that supports PCIX, but they won't have to replace any of the other components. I'm sure Nvidia, AMD, or VIA will chug out a mobo that has socket A + PCIX, and Intel will come out with a Socket 478 + PCIX board (that'll probably be the first one that hits the market).
I think that .Net has a very good chance of crushing Java in the realm of web apps. It's an excellent tool that has many things to work with. Java does too, I'll admit, but you run into the design problems and virtual machine things with java. The JVM is too tight to work with, and the work-arounds (to get to the OS) are rather kludgy.
I do think that Java is a good tool, but as far as efficiency goes... .Net has it beat. As far as development tools go, .Net Studio beats pretty much everything that's out there. I only wish we could come up with a good GTK or QT based RAD environment like VS.NET, because it would be a hell of a lot nicer to do my work away from Windows (bleh).
Are you sure you have a good understanding of what a patent is? They are not enforceble if you do not use the same method as the one that is patented. Essentially, MS has patented certain algorithms that happen within Windows.Forms, which can be and are being rewritten in another way.
I doubt that an API is patentable, since it isn't a method or a material object. Then again, if it were, enforcing it against Mono or DotGNU is pointless... the projects are not profiting from the sale of the technology. They don't even exist in the same marketplace as the framework, since they are completely free.
Microsoft Windows 2000 was written with GNU/Emacs!
It is a semantic difference, but the difference between them manifests itself in performance. When you script a page, you have the http server running the script for each page that is being requested. You also have the server spawning processes to handle things like (in MS terms) ActiveX, ADO, (in Unix terms) external library calls, external programs for handling things, etc.
When you can compile the code, you don't have to worry so much about the performance of the http server, nor do you have to worry as much about the speed of the server. You have the benefit of threads, asynchronous execution, etc. This increases the stability of the http server itself, because the execution environment has been separated from the the server (which is not the case in scripting).
As for developer vs. programmer, I've found that there's not much of a difference between those terms. I'd call the HTML/Dreamweaver/Flash people "webmasters" or "web designers" mostly because they don't have the pretense of actual coding. I certainly wish that there was a separate and distinct term for those of us who love and understand how computers function, care about the efficiency of the internals, and code to that effect. I've met many "programmers" that judge actual programming languages by the number of libraries that the producers of a particular IDE have shipped. I've also met many that solve the performance problem by throwing hardware at it, instead of resolving the source of the problem.
CGI just means that there is compiled code that sits next to the server, and the server talks to it. You don't have the issues in JSP and ASP.NET that you do in ASP/PHP/PERL (context-switching, waiting on OS-calls, etc), because they are not interpreted.
CGI does not mean "I rolled my own HTTP handler."
You will always loose functionalty or efficiency when trying to make sure your system can port to everything.
You couldn't be more wrong. You can do almost anything with the tools that are present as a standard. The real issue is whether or not you want to bother to learn how to use them.
On the other hand... if someone shipped FireFox as the "Internet" icon on the desktop, they also wouldn't care. They would use it. Then they would complain when they can't get that site with embedded Media Player streaming to work.
As one who does do web design, I'm very inclined to enquote 'programmers.' There is very little that a web designer has to understand, and even less if you introduce them to the "webbot" world of Frontpage.
It's very important to follow the set standards. There's a reason why every other business adheres to these standards, because adhering is in their best interest. MS gets away with permitting developers to program outside of the standards, because it has leveraged it's desktop monopoly. People assume that IE is going to be used by everyone, and so they don't pay attention to the more important issue of interoperability.
BTW, selectedValue does follow proper OO structure, since it is just a Property of the Select element. It isn't standard, nor is much more work to type in the standard-adhering way. Javascript is kinda dangerous to work with, mostly because a lot of people turn it off.
Web developers are not programmers. Their work consists mainly of scripting. I know. I get paid to do it. Unless a web developer delves into the world of CGI, I wouldn't consider them a programmer. ASP.NET is CGI, C is, JSP is, ASP is not. PHP is not. PERL is not.
I, myself, could do without MS's "additions." Some of them have been useful, yes, but mostly they are detrimental. Have you ever tried to develop and integrate a client-side ActiveX control that gets embedded in the browser? I have. It sucks.