My problem is with Game Consoles.
Right now we can pull out an old Nintendo or Genesis game and enjoy them.
Some of these games are 20+ yrs old!
What am I going to do 20yrs from now when I pull out my copy of Call of Duty and want to play it
on my new quantum computer. Are the servers still going to be there to send me the patches I need to play the game?
NOPE!
The life of a game is now dictated by how long the game company decides to support it.
I would have to disagree with the custom emulators. I have the GP2X hand held and it runs a dual core ARM processor and the emulators on there run flawlessly. Someone even built a Playstation 1 emulator that used the 2nd core as a GPU and it ran a lot of games. Now remember this is all on a 2 core ARM cpu at 500mhz. Just imagine what you could do with 6 cells.
I'm developer and I understand its not as easy as dropping a couple of lines in and wam bam it handles multiple cores. But its possible and just like there are custom emulators for a ton of other systems there will be ones for the PS3. It just takes some time.
I have confidence in our hacker brethren.
This is so true. I'm not sure why everyone is complaining about no access to the GPU when you have 6 cell processors at your disposal. Most emulators don't even use the GPU. They use software to generate the graphics from the CPU. Just update the emulators to us 2 or more cell processors and you'll probably have a better graphics layer then on a PC.
More and more companies will begin piling on crapware to firefox. Eventually people will get tired of it and move to Google Chrome. Which by that time will have solved this problem in there own extension api.
Unfortunantly I have a bad feeling that there not going to release IE8 until Windows 7 comes out. I personally don't care because I'm a die hard Chrome user, but I feel bad for the 60% of internet users that still use IE.:-(
You guys really can't see whats coming for Java.
Let me lay it out for you what the next 5 years is going to be.
1. Java finally dies on the desktop and.NET has 98% plus of the market on desktop.
2. Android and the iPhone are the dominant platforms for mobile and java stays in the low single digit percentage.
3. 95 plus percent of Businesses use.NET on the server or Mono when using Linux, Unix, Mac or Solaris. The last 5% are the big guys like Amazon & Google who will use Java only because its legacy.
4. Single digit percentage use JavaFX. Sun gives up on it.
I don't really understand why Sun bothers.
They had there chance with Java and blow it..NET will be the platform that you can write once and run anywhere. JavaFX is just said compared to Flash and Silverlight.
I believe you will get greater code reuse programming against.NET across many platforms than having to rebuild your library every time you change platforms. I'm sure a lot of iPhone devs would of loved to reuse some GUI widgets they built on Mac. Plus you get garbage collection.
This is unsurprising, not only because of the platforms, but also because MS appear to be completely ignoring native development, and have been pouring everything on.NET. Which is fair enough, but.NET is going to be MS's method of gradual lock in (Mono implements.NET, but not all of it can be implemented without patent hindrance, which means even with Novell's help, it's not a "forever" solution). Apple's focus upon actual APIs rather than ".NET does XYZ but this feature doesn't work in native!" is definitely an attraction in my opinion (native being ignored is particularly in reference to development tools - for instance, nearly all the features of MSVC "Team System" are irrelevant for native code)
That makes no sense at all. So developing for an API that only works on 1 system makes more sense than developing for a totally mobile Framework which works on PC, tablet, mobile, embedded, Server...etc. Yeah lets hope your boss isn't relying on your expertise.
If it doesn't run Visual Studio I don't want it!
Right now nothing comes close to VS and its great tools. Plus you get WPF on windows and you can reuse that for Silverlight.
Plus who wants to learn Coco. Who names a programming language COCO!
Slashdot Mirror
My problem is with Game Consoles. Right now we can pull out an old Nintendo or Genesis game and enjoy them. Some of these games are 20+ yrs old! What am I going to do 20yrs from now when I pull out my copy of Call of Duty and want to play it on my new quantum computer. Are the servers still going to be there to send me the patches I need to play the game? NOPE! The life of a game is now dictated by how long the game company decides to support it.
Try Mono http://www.mono-project.com/
The real question is...Is it a Cylon?
I would have to disagree with the custom emulators. I have the GP2X hand held and it runs a dual core ARM processor and the emulators on there run flawlessly. Someone even built a Playstation 1 emulator that used the 2nd core as a GPU and it ran a lot of games. Now remember this is all on a 2 core ARM cpu at 500mhz. Just imagine what you could do with 6 cells.
I'm developer and I understand its not as easy as dropping a couple of lines in and wam bam it handles multiple cores. But its possible and just like there are custom emulators for a ton of other systems there will be ones for the PS3. It just takes some time. I have confidence in our hacker brethren.
This is so true. I'm not sure why everyone is complaining about no access to the GPU when you have 6 cell processors at your disposal. Most emulators don't even use the GPU. They use software to generate the graphics from the CPU. Just update the emulators to us 2 or more cell processors and you'll probably have a better graphics layer then on a PC.
More and more companies will begin piling on crapware to firefox. Eventually people will get tired of it and move to Google Chrome. Which by that time will have solved this problem in there own extension api.
Unfortunantly I have a bad feeling that there not going to release IE8 until Windows 7 comes out. I personally don't care because I'm a die hard Chrome user, but I feel bad for the 60% of internet users that still use IE. :-(
Everyone forgets about Mono.
You guys really can't see whats coming for Java. Let me lay it out for you what the next 5 years is going to be. 1. Java finally dies on the desktop and .NET has 98% plus of the market on desktop.
2. Android and the iPhone are the dominant platforms for mobile and java stays in the low single digit percentage.
3. 95 plus percent of Businesses use .NET on the server or Mono when using Linux, Unix, Mac or Solaris. The last 5% are the big guys like Amazon & Google who will use Java only because its legacy.
4. Single digit percentage use JavaFX. Sun gives up on it.
I don't really understand why Sun bothers. They had there chance with Java and blow it. .NET will be the platform that you can write once and run anywhere. JavaFX is just said compared to Flash and Silverlight.
I tried to post it as anonymous but it wouldn't show. So I created a user and than it showed. I guess the system eventually picked it up.
You could point that same response toward M$. ;-)
Of course that would mean that Macs are just like PCs....and we wouldn't want that.
I believe you will get greater code reuse programming against .NET across many platforms than having to rebuild your library every time you change platforms. I'm sure a lot of iPhone devs would of loved to reuse some GUI widgets they built on Mac. Plus you get garbage collection.
This is unsurprising, not only because of the platforms, but also because MS appear to be completely ignoring native development, and have been pouring everything on .NET. Which is fair enough, but .NET is going to be MS's method of gradual lock in (Mono implements .NET, but not all of it can be implemented without patent hindrance, which means even with Novell's help, it's not a "forever" solution). Apple's focus upon actual APIs rather than ".NET does XYZ but this feature doesn't work in native!" is definitely an attraction in my opinion (native being ignored is particularly in reference to development tools - for instance, nearly all the features of MSVC "Team System" are irrelevant for native code)
That makes no sense at all. So developing for an API that only works on 1 system makes more sense than developing for a totally mobile Framework which works on PC, tablet, mobile, embedded, Server...etc. Yeah lets hope your boss isn't relying on your expertise.
If it doesn't run Visual Studio I don't want it! Right now nothing comes close to VS and its great tools. Plus you get WPF on windows and you can reuse that for Silverlight. Plus who wants to learn Coco. Who names a programming language COCO!