Some people will never buy a CD again. That's fine, that's not me. I find songs online, and if I like the artist, I used to go buy their CD. When MP3s were in the wild I spent more time in CD shops than ever before.
I recently took the time to rip all my CD's onto a computer into Vorbis format, my originals are sitting safely in my closet.
Now you're telling me that I might buy a CD (that I probably would already have the MP3s to at this point), and I wouldn't be able to rip and listen to it?
So the money I've been spending on CD's is now working AGAINST me? That makes me think twice.
The current gaming industry is saturated with games, and in order to get your game out there you need a publisher, except that publishers are very well aware of the current over-saturation situation, they realize this because they're not making the huge amount of dollars they're used to making in the past, and this has nothing to do with piracy.
If you have an idea for a game, to get started, your best bet is to find a license to pitch it under. It's not a co-incidence that more and more games have "branding" (Street Fighter, Grand Turismo, NASCAR, Lego, Mary Kate and Ashley Oslen, etc, etc).
If you can find a game that could fit a license, write a short summary of it, in less than a page.
Draw some fake screenshots of what the game would look like, and head down to the Game Developer Conference or the recently passed E3 with this and pray someone will look at you.
Keep in mind, as you do this, thousands of other people are doing the same. If you're lucky, and chances are you won't be (sorry to say), the publisher will ask to see a "demo" of the game, sometimes they'll pay you, sometimes they won't. If you're "small" (ie less than 30 people), they probably will figure you're just a bunch of guys who "wanna write a game" (which you are).
If they like the demo and you deliver on time, they may decide to consider publishing the game.
It helps if you're in Canada or Australlia as the currency works in favour of the publishers.
Head over to http://www.joystick101.org/ and http://www.gamasutra.com/ for more info.
This isn't a troll, it's reality.
And you just thought the music industry was bad...
If you were thinking about going out and just getting Tribes 2 for Linux, you may want to think again. I've been on the beta cycle for it, and have lost countless hours doing nothing more than sitting in front of my computer playing it. Infact, I would say that unless you're absolutely sure you won't mind being seriously addicted to a game for the next dozen months, you should think again.
There are lots of good reviews about Tribes 2 (for Microsoft and Linux alike), so I won't touch on the game here (go read them!)
Seriously, the only thing that is a draw back in this game is the hardware needed to play it (it's just as bad - if not worse - on Microsoft). But if you've been looking for an excuse or good time to upgrade your system (3D card specifically), this is definately it.
ACPI, last I checked was still very much a WIP on Linux. Mind you, also from what I've read it's horridly complex.
The bootup time may be the same as Windows, but that doesn't mean it couldn't be better. When you're a desktop user (note the thread topic:), you may turn your computer off when you leave work for the night and turn it on in the morning (Yes, you could power save - see comment 1)
The logo patch does exist, that's why I suggested it be included. Some people like watching the kernel probe for non-existant IDE controllers and watch it complain about resetting buses on startup. Some of us don't care anymore (they've watched it boot, they know it'll get there).
As far as your comment about ATA with IDE, so long as humans are making hardware, humans will need to fix hardware problems in software after the hardware is made.
Putting a big buffer on mpg123 doesn't solve the problem of too much IO to actually shovel the audio to the soundcard in a timely fashion.
The rest of your comments don't warrant replies, no offense, but I think you realize that.:)
How about improving "apm -s" so I don't need to manually unload my cs sound driver (and first kill xmms which constantly reopens/dev/mixer causing it to get reloaded?).
How about improving boot up time? Including the bootup logo patch?
How about getting DMA mode working on all the IDE controllers out there and having them intelligently configure themselves (I've lost more than one disk to hdparm tweaking).
How about making my mp3's not get choppy when my system starts swapping? (short of needing to apply rtlinux patches and nice --19'ing mpg123).
(DMA overruns too!)
How about including a kflushd that's smart about laptops?
How about cleaning up the documentation for proc.txt, with some examples of what humans could set things to.
How about splitting scsi, ham radio support, pcmcia, architectures, etc, etc into seperate tarballs so I don't need to download them all, or watch make depend go through them all?
I can't imagine that the same schedule() used to handle Apache and Oracle would do the same job as running GNOME..
If I could be selfish and ask for three things from IBM doing Linux work, they would be:
1. Compiler technology to improve code generation of the GCC tools (including gdb).
2. TrueType Fonts. Surely IBM has some fonts lying around from years ago that they would not mind making public.
3. Video CODECs, (integration into the OGG/Vorbis project).
IMHO, IBM Should focus on what they need in Linux to migrate their AIX userbase over to IBM Linux first though (attempting to not NIH existing resources). Supporting both AIX and Linux is a long-term support and resource nightmare.
Linus has blessed an old version of gcc (ala egcs) as the stable version of gcc to build kernels, so RH includes it as "kgcc". But if you compile your own kernel, you knew that, right?
The big GCC complaint is that object files, *.o, won't be compatable between 2.95.2 and 3.0 - except for C (and Fortran?), so basically C++.
This means you can't distribute *.o files made in C++ from one OS to another.
Maybe some of you have had to do this before in your life, but I never have. And if you do, older versions of GCC are freely available for you to downgrade to (but if you're the type that sends C++ object files around, you knew that).
The ELF binaries that GCC makes are still 100% portable.
RH7 looks like it was made for 2.4.x kernels, but when they realized that 2.4.x was still down the road they decided to release it with 2.2.x.
If I were RH, I would have released it for two reason: (1) there comes a time when you must freeze something for QA and only do bug fixes, and from that point on there are no new features. If RH sat on 7.0 too long it would have been completely out-dated by the time 2.4.x came along.
And (2) releasing now means that they can drop 2.2.x support and start focusing properly on 2.4.x, and getting DRI/AGPGART/GLX/etc/etc worked in properly.
There have been 613 bugs logged against RH7 in Bugzilla (as of earlier today). Something like 287 of them are "NOTABUG" or "DUPE", and another 300 or so are "FIXED".
This says to me that out of everyone calling Red Hat unstable, and unusable, etc, etc, less than 600 people have taken the time to do something productive about it.
Red Hat ships with FVWM. They believe everything they see with RedHat 5.1/5.2, and that's just fine. If they think the latest and greatest UI stuff for X is fvwm95, they can just go ahead and believe it.
Slashdot Mirror
Of course, there really is a CJAN already.
Next there'll be an article on the first maintainable Perl program greater than 6 lines long.
One set of rules, given out by an organization deciding who gets what and how they get it.
That's Globalization.
That's also Communism.
I thought we figured out that Communism doesn't work because of greed.
Some people will never buy a CD again. That's fine, that's not me. I find songs online, and if I like the artist, I used to go buy their CD. When MP3s were in the wild I spent more time in CD shops than ever before.
I recently took the time to rip all my CD's onto a computer into Vorbis format, my originals are sitting safely in my closet.
Now you're telling me that I might buy a CD (that I probably would already have the MP3s to at this point), and I wouldn't be able to rip and listen to it?
So the money I've been spending on CD's is now working AGAINST me? That makes me think twice.
The current gaming industry is saturated with games, and in order to get your game out there you need a publisher, except that publishers are very well aware of the current over-saturation situation, they realize this because they're not making the huge amount of dollars they're used to making in the past, and this has nothing to do with piracy.
If you have an idea for a game, to get started, your best bet is to find a license to pitch it under. It's not a co-incidence that more and more games have "branding" (Street Fighter, Grand Turismo, NASCAR, Lego, Mary Kate and Ashley Oslen, etc, etc).
If you can find a game that could fit a license, write a short summary of it, in less than a page.
Draw some fake screenshots of what the game would look like, and head down to the Game Developer Conference or the recently passed E3 with this and pray someone will look at you.
Keep in mind, as you do this, thousands of other people are doing the same. If you're lucky, and chances are you won't be (sorry to say), the publisher will ask to see a "demo" of the game, sometimes they'll pay you, sometimes they won't. If you're "small" (ie less than 30 people), they probably will figure you're just a bunch of guys who "wanna write a game" (which you are).
If they like the demo and you deliver on time, they may decide to consider publishing the game.
It helps if you're in Canada or Australlia as the currency works in favour of the publishers.
Head over to http://www.joystick101.org/ and http://www.gamasutra.com/ for more info.
This isn't a troll, it's reality.
And you just thought the music industry was bad...
Well, looks like the gaming industry is now learning what Microsoft is like, the way every industry has painfully learned for the past dozen years.
Welcome aboard.
Tribes 2 has been out for about a week.
If you were thinking about going out and just getting Tribes 2 for Linux, you may want to think again. I've been on the beta cycle for it, and have lost countless hours doing nothing more than sitting in front of my computer playing it. Infact, I would say that unless you're absolutely sure you won't mind being seriously addicted to a game for the next dozen months, you should think again.
There are lots of good reviews about Tribes 2 (for Microsoft and Linux alike), so I won't touch on the game here (go read them!)
Seriously, the only thing that is a draw back in this game is the hardware needed to play it (it's just as bad - if not worse - on Microsoft). But if you've been looking for an excuse or good time to upgrade your system (3D card specifically), this is definately it.
ACPI, last I checked was still very much a WIP on Linux. Mind you, also from what I've read it's horridly complex.
:), you may turn your computer off when you leave work for the night and turn it on in the morning (Yes, you could power save - see comment 1)
:)
The bootup time may be the same as Windows, but that doesn't mean it couldn't be better. When you're a desktop user (note the thread topic
The logo patch does exist, that's why I suggested it be included. Some people like watching the kernel probe for non-existant IDE controllers and watch it complain about resetting buses on startup. Some of us don't care anymore (they've watched it boot, they know it'll get there).
As far as your comment about ATA with IDE, so long as humans are making hardware, humans will need to fix hardware problems in software after the hardware is made.
Putting a big buffer on mpg123 doesn't solve the problem of too much IO to actually shovel the audio to the soundcard in a timely fashion.
The rest of your comments don't warrant replies, no offense, but I think you realize that.
How about getting ACPI working?
/dev/mixer causing it to get reloaded?).
How about improving "apm -s" so I don't need to manually unload my cs sound driver (and first kill xmms which constantly reopens
How about improving boot up time? Including the bootup logo patch?
How about getting DMA mode working on all the IDE controllers out there and having them intelligently configure themselves (I've lost more than one disk to hdparm tweaking).
How about making my mp3's not get choppy when my system starts swapping? (short of needing to apply rtlinux patches and nice --19'ing mpg123).
(DMA overruns too!)
How about including a kflushd that's smart about laptops?
How about cleaning up the documentation for proc.txt, with some examples of what humans could set things to.
How about splitting scsi, ham radio support, pcmcia, architectures, etc, etc into seperate tarballs so I don't need to download them all, or watch make depend go through them all?
I can't imagine that the same schedule() used to handle Apache and Oracle would do the same job as running GNOME..
Why not try ditching LILO for GRUB?
You can turn cookies off too, but that doesn't mean you'll get far on webpages these days.
How long before we come to "you can turn off copy protection, but you won't be able to install anything on your computer"?
If I could be selfish and ask for three things from IBM doing Linux work, they would be:
1. Compiler technology to improve code generation of the GCC tools (including gdb).
2. TrueType Fonts. Surely IBM has some fonts lying around from years ago that they would not mind making public.
3. Video CODECs, (integration into the OGG/Vorbis project).
IMHO, IBM Should focus on what they need in Linux to migrate their AIX userbase over to IBM Linux first though (attempting to not NIH existing resources). Supporting both AIX and Linux is a long-term support and resource nightmare.
Hrm, good point.
The included KDE1 libraries (which are C++) were built with the backwards compatable egcs C++, so at least KDE is okay.
Linus has blessed an old version of gcc (ala egcs) as the stable version of gcc to build kernels, so RH includes it as "kgcc". But if you compile your own kernel, you knew that, right?
The big GCC complaint is that object files, *.o, won't be compatable between 2.95.2 and 3.0 - except for C (and Fortran?), so basically C++.
This means you can't distribute *.o files made in C++ from one OS to another.
Maybe some of you have had to do this before in your life, but I never have. And if you do, older versions of GCC are freely available for you to downgrade to (but if you're the type that sends C++ object files around, you knew that).
The ELF binaries that GCC makes are still 100% portable.
RH7 looks like it was made for 2.4.x kernels, but when they realized that 2.4.x was still down the road they decided to release it with 2.2.x.
If I were RH, I would have released it for two reason: (1) there comes a time when you must freeze something for QA and only do bug fixes, and from that point on there are no new features. If RH sat on 7.0 too long it would have been completely out-dated by the time 2.4.x came along.
And (2) releasing now means that they can drop 2.2.x support and start focusing properly on 2.4.x, and getting DRI/AGPGART/GLX/etc/etc worked in properly.
There have been 613 bugs logged against RH7 in Bugzilla (as of earlier today). Something like 287 of them are "NOTABUG" or "DUPE", and another 300 or so are "FIXED".
This says to me that out of everyone calling Red Hat unstable, and unusable, etc, etc, less than 600 people have taken the time to do something productive about it.
Red Hat ships with FVWM. They believe everything
they see with RedHat 5.1/5.2, and that's just
fine. If they think the latest and greatest UI
stuff for X is fvwm95, they can just go ahead
and believe it.