Yup, and the KDE team, and interested parties define the standard for KDE.
When he says 'define the standard' he means that the 'Users' are supposed to do it by flicking the channel on a metaphorical remote control - 'Users defining the standard' means 'Users picking which standard to follow'.
If you haven't been paying attention, most Users prefer the Microsoft standard.
It is legal - it's considered non-commercial distribution, which is fine.
There was discussion of it in the Napster defence PDF that was on/. a month or two ago. Napster would be free to use this as defense (since thier users are copying files without expectation of monetary compensation) but for the DMCA which redefines commercial distribution to include trading.
depends. in hexen ii, there was likely a way to switch to first person mode, but it would *suck*, and basically be a novelty. most games made in third-person mode are made that way for gameplay reasons, and if they provide a first person mode, it's generally not as useful. but, yeah, third-person shooter is a fairly widely used term =)
If I recall Nanosaur (from the computer store iMac demos years back), that would be classified as a Third Person Shooter (as would Hexen II, Heavy Metal : FAKK2, etc).
Mainsoft has been working on Windows-to-Unix solutions for some time, and the company has worked with Microsoft in the past, porting Microsoft's DCOM technology to Unix.
So, the concept that the law can decide to shut down the sale of games that may cause teen violence is totally legit in a Canadian context...
This isn't about 'causing teen violence'. It's about classifying a product as unfit for people under 18. Period.
Listen - Raven set out to make the most disturbing, graphically violent game possible. (including keeping track of how many times you kill enemies by shooting them in the groin, and about every other concievable way to focus the game on the act of graphical and brutal slayings).
Now they're pissed that someone agrees with them - that the game isn't suitable to be sold to children.
Talk about a bunch of whiners - they set out to do something, and are now complaining when thier own actions bite them in the ass.
incase you didn't read the article, the bulk of the work is being done by a company that had existed to port MS's DCOM architecture to Unix. very likely, the work done on this overlaps greatly with the work required to port MS Office.
Solaris isn't meant to run on x86. That's mostly a PR Port.
Solaris is for running on Sun boxen. It's good at what it does (even if it's stock install is a bit under-featured - install the GNU tools as soon as you boot it up =).
If you're building a network or application platform, your OS should either follow or dictate your hardware choice - they should never be chosen independantly. If you need to run servers under Solaris, that means you get Sun boxen. If you need to run servers on x86 boxen that you've already bought, you choose *BSD (or Linux, if that's your thing).
Putting Solaris on an x86 would be the same as putting Linux on a Sparc - yeah, it will work, but why bother?
Rather than focusing on the tired examples of 'hammers' and 'toasters' - both which take arguably no to minimal intelligence and skill to use, treat computers like they should be treated - like cars.
You need to learn how to use one, learn the idioms behind the design, and have some experience using them before anything about them become self-evident.
yes, but the point is that a) each config file, however messed up and crack-addled the author was when he came up with the format, usually has accompanying documentation (minimum being commented examples), and b) all config files can be mutilated and worked on with perl/sed/awk/bash/c/scheme/python/whatever, based on the fact it's a text file.
in windows, if i want to change the setting of a program, then i have to pray it's stored in an ini file. if it's in the registry, i might be able to figure it out, same with a config file. but modern programs both assume that the user will never be touching the file, so never document/give examples of the formats/ways to change the configuration.
even with vbscript/wsh (which is nifty, despite it's bad rep), the authors of the program had to keep user-use in mind when designing the objects and making certain properties/methods available, which is rarely done except in high-profile applications (word, etc).
in conculsion, umm... "SPOON!"
[The Tick started it's run from the start of the series on Teletoon last night.]
True, but if it could be shown that nVidia was selling the parts at a loss (i.e. losing money on each sale) with the intention of engaging in anti-competitive behaviour, they would be torn to shreds in court, rightfully so.
Pose the question like this : are raster graphics somehow superior to vector graphics?
At one point, video games were done with vector graphics (Tempest was the most memorable =) beacuse raster graphics were too expensive computationally to do. Once they were possible, much more freedom was allowed.
Polygons are basically vector graphics in 3d - an approximation generated by drawing lines through space to simulate the construction of objects. Whereas voxels are much more like pixels - you choose a resolution, and then you fill in each 3d point with a colour. They are just orders of magnitude more expensive than polygons, that's all.
The advantages? More freedom and realisim in what can be designed.
Yeah, and I wasn't exactly trolling either. Not only did I warn the clicking morons that it was porn, it's also *gasp* on-topic, as danni.com is a fucking porno site...
Slashdot Mirror
Yup, and the KDE team, and interested parties define the standard for KDE.
When he says 'define the standard' he means that the 'Users' are supposed to do it by flicking the channel on a metaphorical remote control - 'Users defining the standard' means 'Users picking which standard to follow'.
If you haven't been paying attention, most Users prefer the Microsoft standard.
--
Let the users define the standards.
... like they did with Windows.
--
It is legal - it's considered non-commercial distribution, which is fine.
There was discussion of it in the Napster defence PDF that was on
--
Where does sex fit in this?
I hope that doesn't go along with peeing....
(ewwww...)
--
depends. in hexen ii, there was likely a way to switch to first person mode, but it would *suck*, and basically be a novelty. most games made in third-person mode are made that way for gameplay reasons, and if they provide a first person mode, it's generally not as useful. but, yeah, third-person shooter is a fairly widely used term =)
--
Nanosaur is essentially a first-person shooter.
If I recall Nanosaur (from the computer store iMac demos years back), that would be classified as a Third Person Shooter (as would Hexen II, Heavy Metal : FAKK2, etc).
--
"The Fall of the Jedi" would work.... would parrallel with RotJ the same as TRotE parrallells with TESB...
--
Did you even *read* the article?
Mainsoft has been working on Windows-to-Unix solutions for some time, and the company has worked with Microsoft in the past, porting Microsoft's DCOM technology to Unix.
Did you go to Mainsoft's web site?
That should answer your question...
--
Holy missing the point, Batman.
So, the concept that the law can decide to shut down the sale of games that may cause teen violence is totally legit in a Canadian context...
This isn't about 'causing teen violence'. It's about classifying a product as unfit for people under 18. Period.
Listen - Raven set out to make the most disturbing, graphically violent game possible. (including keeping track of how many times you kill enemies by shooting them in the groin, and about every other concievable way to focus the game on the act of graphical and brutal slayings).
Now they're pissed that someone agrees with them - that the game isn't suitable to be sold to children.
Talk about a bunch of whiners - they set out to do something, and are now complaining when thier own actions bite them in the ass.
--
They can't port something that unstable onto linux.
c.f. Netscape
--
yeah... right....
incase you didn't read the article, the bulk of the work is being done by a company that had existed to port MS's DCOM architecture to Unix. very likely, the work done on this overlaps greatly with the work required to port MS Office.
--
Solaris isn't meant to run on x86. That's mostly a PR Port.
Solaris is for running on Sun boxen. It's good at what it does (even if it's stock install is a bit under-featured - install the GNU tools as soon as you boot it up =).
If you're building a network or application platform, your OS should either follow or dictate your hardware choice - they should never be chosen independantly. If you need to run servers under Solaris, that means you get Sun boxen. If you need to run servers on x86 boxen that you've already bought, you choose *BSD (or Linux, if that's your thing).
Putting Solaris on an x86 would be the same as putting Linux on a Sparc - yeah, it will work, but why bother?
--
I'd imagine they'd be out, you know, *hacking*...
--
Rather than focusing on the tired examples of 'hammers' and 'toasters' - both which take arguably no to minimal intelligence and skill to use, treat computers like they should be treated - like cars.
You need to learn how to use one, learn the idioms behind the design, and have some experience using them before anything about them become self-evident.
--
Note the word 'Experimental'.
Do you honestly think that anyone is going to trust thier customer's data, money and confidence to an 'experimental' database?
Until it's stable, it may as well not exist from the user's point of view.
--
yes, but the point is that a) each config file, however messed up and crack-addled the author was when he came up with the format, usually has accompanying documentation (minimum being commented examples), and b) all config files can be mutilated and worked on with perl/sed/awk/bash/c/scheme/python/whatever, based on the fact it's a text file.
in windows, if i want to change the setting of a program, then i have to pray it's stored in an ini file. if it's in the registry, i might be able to figure it out, same with a config file. but modern programs both assume that the user will never be touching the file, so never document/give examples of the formats/ways to change the configuration.
even with vbscript/wsh (which is nifty, despite it's bad rep), the authors of the program had to keep user-use in mind when designing the objects and making certain properties/methods available, which is rarely done except in high-profile applications (word, etc).
in conculsion, umm... "SPOON!"
[The Tick started it's run from the start of the series on Teletoon last night.]
--
True, but if it could be shown that nVidia was selling the parts at a loss (i.e. losing money on each sale) with the intention of engaging in anti-competitive behaviour, they would be torn to shreds in court, rightfully so.
--
Am I the only one, or does anyone else wonder if MS has anything to do with this roadmap varying from the nvidia pattern of 6 month cycles?
You *do* realize that the X-Box is nVidia hardware, and nVidia helped design it, and, and, and...
It's not like MS is the only one who stands to gain from X-Box sales.
--
You're forgetting about Capcom. =)
I'm just waiting for the Super Ultra Mega Tournament Champion Edition GeForce Alpha II.
--
actually, I didn't mean SSH. I mean, the process should be :
ndfa$ telnet coffee
Trying 10.1.1.25
Connected
uClinux 2.0.38.1pre7
username: coffee
password:
$ su - root
Password:
# make_coffee -strength 10 -cups 3
Making coffee now
Of course, this still doesn't solve the problem of needing to be root to run the make_coffee program.
--
not only that, he's telnetting in as root. shame on him. the coffeemaker should burn all of his coffee if he does that...
--
Pose the question like this : are raster graphics somehow superior to vector graphics?
At one point, video games were done with vector graphics (Tempest was the most memorable =) beacuse raster graphics were too expensive computationally to do. Once they were possible, much more freedom was allowed.
Polygons are basically vector graphics in 3d - an approximation generated by drawing lines through space to simulate the construction of objects. Whereas voxels are much more like pixels - you choose a resolution, and then you fill in each 3d point with a colour. They are just orders of magnitude more expensive than polygons, that's all.
The advantages? More freedom and realisim in what can be designed.
--
*sigh*
he has the processor -> he got a paper cut. ergo, the processor exists only on paper.
--
Yeah, and I wasn't exactly trolling either. Not only did I warn the clicking morons that it was porn, it's also *gasp* on-topic, as danni.com is a fucking porno site...
--
Steve Jobs coined the phrase "The next insanely great thing" or something along those lines. I'm sure you can take it from there.
--