Sorry, if this has been said, I've only read about half the comments on this one. If I were the other guys I would not pack it in. I would make a game that allows for total customization of teams.
I don't just mean creating guys with your own names and changing the colors of the uniforms. I mean being able to create your own bitmaps/textures for the uniform design, logo, and insignias on the field/endzones.
Then add a deep franchise mode like everyone is adding these days with college draft, managing concesions, etc etc. Leagues could start with a random pool of players and a draft. Players' names and appearances could be tweaked before the season started, but not their skill ratings (to keep it fair). Then every draft from then on would include fictional college players.
I know people like having their favorite NFL players on the screen in front of them, but if someone steps up and makes a game that offers a totally customizable experience (even with Stadium design, etc), I'm sure they would be able to keep a lot of sports-gamers in the fold.
about why Python hasn't gained acceptance in commercial software development circles. I find these last two articles nothing more than glorified flame bait. If some of the development community's best and brightest think this language is superior, why not drive an effort to help it put food on the table rather than relegate it to a tool that helps you write scripts to rotate witty quotes in your.plan file?
Pardon me while I go build a better mouse trap, pontificate on how much better it is and what a great mouse catcher I am, and then put it in my hamster's cage to prove it.
File this under 'why is this news?'
on
The Face Detector
·
· Score: 0
If I throw a bunch of tiny ball bearings in a bucket and shake it around, it may look like they are flowing, when in fact they are a bunch of solid objects moving in unison. These Helium-4 crystals work the same way, they're just a lot smaller than ball bearings so the line between flowing and just plain moving is blurred.
From my brief (1 day) experience with freenet, the other popular use will probably be kiddy porn. I saw a more than a few areas on freenet that just by their name were obviously child pornography. I uninstalled shortly after.
I was referring to after installation. But you are right, defaulting to no password is bad. I think it is bad to allow creation of multiple users during setup, period. I think even the casual technophile may interpret any users other than the first one as being regular (non-priviledged) users.
Although I can just see the support call volumes shoot through the roof if when SP2 is released it warns about users with blank passwords during the installation. In my opinion it should do that but every person that just bought their system with XP preloaded would probably be startled.
Actually you are wrong. Under 2K and above (I think NT and above actually) new users only appear in the users group. Now, that doesn't mean they cannot damage the system. They can still double click attachments with Trojans, they can still delete files that are pretty important (unless you have a process in place to lock down all files under the windows directory or the Program Files directory). But it is entirely untrue that new users are added to the Administrators group on the NT family of OSes.
Isn't imitation the sincerest form of flattery?
on
Essential .NET, Volume I
·
· Score: 5, Insightful
I'll take umbrage with the kneejerk "Java has been doing this for years" comments. Must every idea be so mind-bendingly unique to be deemed useful? Should we all start buying Ford Model-A cars instead of Durangos (or whatever) because Henry Ford "was doing that 100 years ago!"? Are the CLR-based language features a lot like Java? Yes. Should every derivative product be denounced as coming to the table too late? I think not.
Once more,.NET ( the bits for developers anyway) brings some better things to the table as well (as evidenced by Sun getting into the leapfrog game with Java v.Next features - Metadata (Attributes), etc).
Actually it metadata sounds a lot like.NET Attributes to me. I may be wrong. In any case my point was there were more similarities than some were willing to admit. In some ways it feeds the "embrace and extend" critics but in others it can serve as a validation.
While I'd agree that in its entirety.NET has been confusing, my experience has been those of us that drink the MS kool-aid are pretty impressed with the development tools. I've personally think web-services on any platform have been overplayed, so criticisms of that effort are probably warranted as well.
I haven't seen anyone mention (forgive me, I haven't read all 522 responses) the features of Java in the upcoming major release as revealed by Sun are essentially in lock-step with C#. Yes, its a leap-frog game and Java was there first, but it certainly discounts wholesale rejections of.NET language features from the Java crowd. Sun has even hinted that they will put more effort into providing (*gasp*) usable IDEs for Java development and have specifically cited MS' DevStudio as a forerunner in this category (although MS was certainly not the first with decent IDEs - props to Borland, et. al).
Finally, it should come as no suprise that.NET is targeted to Windows. Let's face it, Office and Windows are cash cows for MS and it only makes sense to highlight your platform when providing tools.
Even with some of these drawbacks, if you are developing to an MS platform,.NET development tools are far and away the best that have been available to you and I know of more than a handful of situations, anectdotal as they may be, where they have proven to provide real productivity benefits, and that is huge for developers.
So I guess my point is, don't throw the baby out with the bathwater. Yes, tying the OS (Win svr 2003) and Office and consulting services (and, and, and..) to.NET may have been confusing, but the development tools are top notch and solve more problems than they create.
Slashdot Mirror
... it is simply another security measure. I know it's a nit pick but given all the FUD (on both sides) surrounding DRM I thought I'd point it out.
I don't just mean creating guys with your own names and changing the colors of the uniforms. I mean being able to create your own bitmaps/textures for the uniform design, logo, and insignias on the field/endzones.
Then add a deep franchise mode like everyone is adding these days with college draft, managing concesions, etc etc. Leagues could start with a random pool of players and a draft. Players' names and appearances could be tweaked before the season started, but not their skill ratings (to keep it fair). Then every draft from then on would include fictional college players.
I know people like having their favorite NFL players on the screen in front of them, but if someone steps up and makes a game that offers a totally customizable experience (even with Stadium design, etc), I'm sure they would be able to keep a lot of sports-gamers in the fold.
Pardon me while I go build a better mouse trap, pontificate on how much better it is and what a great mouse catcher I am, and then put it in my hamster's cage to prove it.
http://www.identix.com http://www.viisage.com http://been.done.before
If I throw a bunch of tiny ball bearings in a bucket and shake it around, it may look like they are flowing, when in fact they are a bunch of solid objects moving in unison. These Helium-4 crystals work the same way, they're just a lot smaller than ball bearings so the line between flowing and just plain moving is blurred.
From my brief (1 day) experience with freenet, the other popular use will probably be kiddy porn. I saw a more than a few areas on freenet that just by their name were obviously child pornography. I uninstalled shortly after.
I was referring to after installation. But you are right, defaulting to no password is bad. I think it is bad to allow creation of multiple users during setup, period. I think even the casual technophile may interpret any users other than the first one as being regular (non-priviledged) users.
Although I can just see the support call volumes shoot through the roof if when SP2 is released it warns about users with blank passwords during the installation. In my opinion it should do that but every person that just bought their system with XP preloaded would probably be startled.
Actually you are wrong. Under 2K and above (I think NT and above actually) new users only appear in the users group. Now, that doesn't mean they cannot damage the system. They can still double click attachments with Trojans, they can still delete files that are pretty important (unless you have a process in place to lock down all files under the windows directory or the Program Files directory). But it is entirely untrue that new users are added to the Administrators group on the NT family of OSes.
I'll take umbrage with the kneejerk "Java has been doing this for years" comments. Must every idea be so mind-bendingly unique to be deemed useful? Should we all start buying Ford Model-A cars instead of Durangos (or whatever) because Henry Ford "was doing that 100 years ago!"? Are the CLR-based language features a lot like Java? Yes. Should every derivative product be denounced as coming to the table too late? I think not. Once more, .NET ( the bits for developers anyway) brings some better things to the table as well (as evidenced by Sun getting into the leapfrog game with Java v.Next features - Metadata (Attributes), etc).
Actually it metadata sounds a lot like .NET Attributes to me. I may be wrong. In any case my point was there were more similarities than some were willing to admit. In some ways it feeds the "embrace and extend" critics but in others it can serve as a validation.
I haven't seen anyone mention (forgive me, I haven't read all 522 responses) the features of Java in the upcoming major release as revealed by Sun are essentially in lock-step with C#. Yes, its a leap-frog game and Java was there first, but it certainly discounts wholesale rejections of .NET language features from the Java crowd. Sun has even hinted that they will put more effort into providing (*gasp*) usable IDEs for Java development and have specifically cited MS' DevStudio as a forerunner in this category (although MS was certainly not the first with decent IDEs - props to Borland, et. al).
Finally, it should come as no suprise that .NET is targeted to Windows. Let's face it, Office and Windows are cash cows for MS and it only makes sense to highlight your platform when providing tools.
Even with some of these drawbacks, if you are developing to an MS platform, .NET development tools are far and away the best that have been available to you and I know of more than a handful of situations, anectdotal as they may be, where they have proven to provide real productivity benefits, and that is huge for developers.
So I guess my point is, don't throw the baby out with the bathwater. Yes, tying the OS (Win svr 2003) and Office and consulting services (and, and, and..) to .NET may have been confusing, but the development tools are top notch and solve more problems than they create.