the graphics hardware in the xbox isn't gf3, it's between gf3 and gf4 in terms of power.
if pc games were meant to run on only a single version of a graphics card you could make them much more efficient. this is the case with the xbox, a single target, so graphics can be heavily optimised.
It is being ported, but the company that are doing it seem unlikely to release it as a consumer product. They already make LinDVD (the Linux version of WinDVD suprisingly). LinDVD is available to consumers as a standalone, it's only marketed to integrators making Linux appliances, and it's looking like the WMP port will be the same.
I meant that phone / pda combos (where microsoft is being trashed) would replace straight pdas, it's happening already, not that they'd replace desktops as the (/.) article suggests. having said that, i'm sure we will get away from the current pc form factor, the tablet pc form factor is a step down this route.
But I can't help thinking that the phone / pda combo is really what's going to dominate this space before long. And that is a space where Microsoft is doing really rather badly.
Unless ATI can manage some major optimisations for the 9800 over coming weeks, before boards become available we're unlikely to be sold on their latest must-have technology
well it seems/. can't handle gt & lt in plain text, which is a bit annoying.
basically, the register said exactly the same thing as the parent, only with more detail. they said it was from a bugtraq posting, they pointed out (which the parent missed) that the exploit really has very little to do with this tool they're claiming to have written (an exploit for mpg123? wow..)
is it? it seems like you just said exactly the same thing as the register, only with less detail:
>>The actual exploit was posted on buqtraaq yesterday.>
>>You can find it here. [securityfocus.com] That link has the original post from the group explaining what the exploit is, how the RIAA is supposedly involved, and it has the exploit as an attachment.>
>
>>Check it out and decide for yourself if it's a hoax.>
it's funny, because you've seen the same effect in two places and used it as an 'advantage' where it suited you and a 'disadvantage' where it didn't.
g4 / p3: the g4 makes more efficient use of each clockcycle, but isn't capable of reaching anywhere near the clock cycle limit of the p3. they end up with a similar maximum performance
p3 / p4: the p3 makes (slightly) more efficient use of each clockcycle, but cannot reach anywhere near the number of clockcycles. end result, the p4 is more powerful.
athlon xp / p4: the athlon xp gets more done per clockcycle, but cannot reach the number of cycles the p4 can. end result, they are pretty much neck and neck, taking turns at leading in performance.
ironically, in their obsession with clock cycles, mac fans have fallen into the same trap they always accused pc fans of falling for. it's like a sort of inverse 'megahertz myth', where they see the efficiency with which the processor uses each clock cycle as the be all and end all of processing power, which is just as obviously false as seeing the number of clock cycles as being the be all and end all of processing power.
the only real way to measure these things is with real world benchmarks, and a lot of them combined rather than a few hand picked to help the favoured system. (hint: amd / intel come out pretty close, macs are falling further and further behind, dual processor doesn't count, because you can do that with pcs too if you want)
nice operating system, shame about the hardware fascism.
yeah, jbuilder is like dreamweaver for java, it's horrible. it all seems great at first, 'oh look, this wizard will build all my EJBs for me straight from my database schema' (actually, that is quite cool), then you actually get round to looking at the code after playing for a bit, and you realise that it's turned into spaghetti.
also, apart from being slow, jbuilder just generally comes across as bloaty to me. i mean, i'm sure _someone_ wants all that stuff, but it goes too far for me. while i was using it, i seemed to spend almost as much time wading through the docs as i did working.
aaalso.. it's really doesn't seem to like most open source stuff. unsuprisingly it's heavily biased toward the commercial appservers (i work with j2ee).
eclipse however, is fast (relatively), simple in terms of interface and finding the actual functionality you need, and has superb support for open and closed type plugins. cvs works nicely, ant works nicely, junit integration is great, and so on.
to me jbuilder is everything that CLI junies hate about GUIs, whereas eclipse is how it should be, minimum bloat, maximum functionality.;)
before doom there were stacks and stacks of side scroller and vertical scroller shoot em ups, that had even less diversity that the current drop of first person shooters.
adventure games now tend towards rpgs like planescape torment and baldurs gate 2. what about deus ex? a superb adventure and fps rolled into one!
others have also listed many other notable games that don't fit your description.
i think far more of a problem now is, perversely, the huge market that games have, the volume that come out, and the immense costs associated with making a modern game. this has lead to publishers being wary of new and original games that may not have such large mass market appeal, leading to a dumbing down of a lot of the bigger name games.
luckily the creativity in the games industry holds this at bay, and we still get superb titles like gta3, deus ex, worms (a bit old i'll admit), the final fantasy series, and the total war series.
i think creativity and variety in games are alive and well. consoles could do with some more however.
on a side note, why the hell are most console games single player? i mean come on, the reason i bought my consoles is to play with my mates while chilling in the living room, if i wanted to be a hermit i'd just play pc games...
Re:mod parent up! (A Criticism Of PHP5's Namespace
on
Professional PHP4
·
· Score: 1
well i did finally get back to read it, and there are some interesting ideas.
to be honest, the only languages that i've used in an OO fashion are Java and PHP, and with PHP i've always treated it quite like it was java (as much as that is possible), including only having one class per file. i quite like that restriction, as it makes things easy to find, and reduces room for complexity and variations in naming conventions. but as i say, java was really my first introduction to something resembling proper OO, so im probably missing the advantages of what you are proposing:/
never the less, i'll keep an eye out for you next time i get some moderator points:)
Yes it's going to be much more object-oriented. Handy stuff like:
+passing by reference by default (rather than having to prepend ampersands all over the place) +multiple inheritance (i don't think this has been confirmed yet, personally i'd prefer something like java's interfaces, but that's because i love java;) +private member vars (again not confirmed yet afaik) +static member vars +exception handling! yay! +deletion of objects that are still referenced (optional of course;) +dereferencing of returned objects +object cloning +destructor methods
and.. well loads more, but if you want lots of detail go read the pdf;)
all quite exciting if you ask me. the one thing that has always frustrated me about php is it's partial OO support, and I think this will go a long way to fixing that. i can't wait.
>Where's my flying car?
:)
right here
(ok so you can't buy one yet, but it exists...)
http://www.moller.com/
no, because it was for a different reason.
(no need to repeat yourself btw)
the graphics hardware in the xbox isn't gf3, it's between gf3 and gf4 in terms of power.
if pc games were meant to run on only a single version of a graphics card you could make them much more efficient. this is the case with the xbox, a single target, so graphics can be heavily optimised.
as long as ms don't catch you... just because it's on linux doesn't make it open source ;)
sorry, that should read "LinDVD isn't available to consumers". Preview button you say? Never heard of it! ;)
It is being ported, but the company that are doing it seem unlikely to release it as a consumer product. They already make LinDVD (the Linux version of WinDVD suprisingly). LinDVD is available to consumers as a standalone, it's only marketed to integrators making Linux appliances, and it's looking like the WMP port will be the same.
I meant that phone / pda combos (where microsoft is being trashed) would replace straight pdas, it's happening already, not that they'd replace desktops as the (/.) article suggests. having said that, i'm sure we will get away from the current pc form factor, the tablet pc form factor is a step down this route.
But I can't help thinking that the phone / pda combo is really what's going to dominate this space before long. And that is a space where Microsoft is doing really rather badly.
Thankfully..
thresh. he was the first big name 'pro' fps player afaik.
ok fair enough. i guess im not qualified to determine the qualification of sites to qualify the quality of gfx cards ;)
Why's that? because they don't review graphics cards much?
ack! recursive argument alert...
quote:
doa3 is the best beat em up i've ever played :)
do you miss the fireballs and knives or something?
people with pacemakers, or anyone nearby on life support or similar would still be affected.
well it seems /. can't handle gt & lt in plain text, which is a bit annoying.
basically, the register said exactly the same thing as the parent, only with more detail. they said it was from a bugtraq posting, they pointed out (which the parent missed) that the exploit really has very little to do with this tool they're claiming to have written (an exploit for mpg123? wow..)
so why +5 informative?
is it? it seems like you just said exactly the same thing as the register, only with less detail:
>>The actual exploit was posted on buqtraaq yesterday.>
>>You can find it here. [securityfocus.com] That link has the original post from the group explaining what the exploit is, how the RIAA is supposedly involved, and it has the exploit as an attachment.>
>
>>Check it out and decide for yourself if it's a hoax.>
my post (parent) is a bit wrong, my apologies to humina. i misread your post, please ignore my first para :)
it's funny, because you've seen the same effect in two places and used it as an 'advantage' where it suited you and a 'disadvantage' where it didn't.
g4 / p3:
the g4 makes more efficient use of each clockcycle, but isn't capable of reaching anywhere near the clock cycle limit of the p3. they end up with a similar maximum performance
p3 / p4:
the p3 makes (slightly) more efficient use of each clockcycle, but cannot reach anywhere near the number of clockcycles. end result, the p4 is more powerful.
athlon xp / p4:
the athlon xp gets more done per clockcycle, but cannot reach the number of cycles the p4 can. end result, they are pretty much neck and neck, taking turns at leading in performance.
ironically, in their obsession with clock cycles, mac fans have fallen into the same trap they always accused pc fans of falling for. it's like a sort of inverse 'megahertz myth', where they see the efficiency with which the processor uses each clock cycle as the be all and end all of processing power, which is just as obviously false as seeing the number of clock cycles as being the be all and end all of processing power.
the only real way to measure these things is with real world benchmarks, and a lot of them combined rather than a few hand picked to help the favoured system. (hint: amd / intel come out pretty close, macs are falling further and further behind, dual processor doesn't count, because you can do that with pcs too if you want)
nice operating system, shame about the hardware fascism.
the project to brute force the key isn't part of the xbox linux project.
yeah, jbuilder is like dreamweaver for java, it's horrible. it all seems great at first, 'oh look, this wizard will build all my EJBs for me straight from my database schema' (actually, that is quite cool), then you actually get round to looking at the code after playing for a bit, and you realise that it's turned into spaghetti.
;)
also, apart from being slow, jbuilder just generally comes across as bloaty to me. i mean, i'm sure _someone_ wants all that stuff, but it goes too far for me. while i was using it, i seemed to spend almost as much time wading through the docs as i did working.
aaalso.. it's really doesn't seem to like most open source stuff. unsuprisingly it's heavily biased toward the commercial appservers (i work with j2ee).
eclipse however, is fast (relatively), simple in terms of interface and finding the actual functionality you need, and has superb support for open and closed type plugins. cvs works nicely, ant works nicely, junit integration is great, and so on.
to me jbuilder is everything that CLI junies hate about GUIs, whereas eclipse is how it should be, minimum bloat, maximum functionality.
sorry but i really think that's rubbish.
before doom there were stacks and stacks of side scroller and vertical scroller shoot em ups, that had even less diversity that the current drop of first person shooters.
adventure games now tend towards rpgs like planescape torment and baldurs gate 2. what about deus ex? a superb adventure and fps rolled into one!
others have also listed many other notable games that don't fit your description.
i think far more of a problem now is, perversely, the huge market that games have, the volume that come out, and the immense costs associated with making a modern game. this has lead to publishers being wary of new and original games that may not have such large mass market appeal, leading to a dumbing down of a lot of the bigger name games.
luckily the creativity in the games industry holds this at bay, and we still get superb titles like gta3, deus ex, worms (a bit old i'll admit), the final fantasy series, and the total war series.
i think creativity and variety in games are alive and well. consoles could do with some more however.
on a side note, why the hell are most console games single player? i mean come on, the reason i bought my consoles is to play with my mates while chilling in the living room, if i wanted to be a hermit i'd just play pc games...
well i did finally get back to read it, and there are some interesting ideas.
:/
:)
to be honest, the only languages that i've used in an OO fashion are Java and PHP, and with PHP i've always treated it quite like it was java (as much as that is possible), including only having one class per file. i quite like that restriction, as it makes things easy to find, and reduces room for complexity and variations in naming conventions. but as i say, java was really my first introduction to something resembling proper OO, so im probably missing the advantages of what you are proposing
never the less, i'll keep an eye out for you next time i get some moderator points
no benchmarks im afraid, but anecdotal evidence seems to suggest there's not a huge difference in terms of efficiency.
i think the real issue is in terms of coding style, passing by reference is just more OO, and seems more intuitive to me.
can someone at least set the parent of this ( "A Criticism Of PHP5's Namespaces (plz read! :)" ) up tp +1.
;)
:/
some interesting points, i'm going to come back and re-read tomorrow when i'm a bit more awake
wish i hadn't caned my moderator points yesterday
Yes it's going to be much more object-oriented.
;) ;)
;)
Handy stuff like:
+passing by reference by default (rather than having to prepend ampersands all over the place)
+multiple inheritance (i don't think this has been confirmed yet, personally i'd prefer something like java's interfaces, but that's because i love java
+private member vars (again not confirmed yet afaik)
+static member vars
+exception handling! yay!
+deletion of objects that are still referenced (optional of course
+dereferencing of returned objects
+object cloning
+destructor methods
and.. well loads more, but if you want lots of detail go read the pdf
all quite exciting if you ask me. the one thing that has always frustrated me about php is it's partial OO support, and I think this will go a long way to fixing that. i can't wait.