Shame they're not using a scripting language. I'm no stranger to C++, but it's a hell of a lot easier to mod a game with scripts. The best, IMO, was Jedi Knight's COG language.
Still, looks great! Can't wait to play with the SDK!
Agreed. I still have my 10-year-old DJ500, and regularly use it. But it did cost about £350. You can only compare printers of a similar cost. I'm guessing that's in the £450-500 range now.
Another vote for DirectFB.
I saw here that David Wexelblat says that "X needs to be replaced by a direct-rendered model, on which a backwards-compatible X server can be reasonably trivially implemented."
Sounds like DirectFB with XDirectFB running on top, doesn't it?
Get one of those numeric keypads designed for laptops with a USB interface. Then you can map the keys sung xmodmap.You could even put stickers on the keys.
I can hear that too. I can tell if a TV's on nearby - in another room or even downstairs. Always have been able to, although it was much more noticable when I was younger. High frequency devices are less noticable though.
What about the details on screen? I find that a white screen makes a higher-pitched noise than a blank one.
On another note, my old monitor used to make high-pitched noises every so often which could be solved by giving it a sharp whack.
As many people have pointed out here - it can shift a serious number of uh, numbers.
The language feels as though it's designed by a committee and has features tacked on left, right and centre. IO sucks arse, so don't expect to write a wonderful user interface for it (but you could always do a wrapper in another language, I suppose).
I use F90 at uni, and although it's a bit of a messy language it does what it's good at: spewing out tables of numbers. It is expensive for a single licence, however. I wouldn't bother with it if I didn't have access to the university number crunchers.
Why I keep going back to Debian
on
Is RPM Doomed?
·
· Score: 2, Insightful
I've used SuSE, RedHat, Mandrake, Debian and a few others in the past. I keep thinking that a distribution has enough new features to warrent me changing, and then I hit the dependency problem and go back to Debian again.
This happened a few weeks ago when I installed SuSE on my old laptop because of its PCMCIA support. In the end I has so much trouble finding a RPM and its dependencies, I gave up and stuck woody on there. It took longer to set up, but I just need a net connection and apt.
I'm tempted to switch to Gentoo, but then there's always source DEBs, aren't there:)
apt isn't perfect though. Over a modem it takes a few minutes to apt-get update, and hours to apt-get upgrade, but it does make it so much easier! Also, Debian are very anal about their distro, even about unstable. There are still no (official) KDE3 or Openoffice.org debs (mainly because they don't work on all the supported platforms), meaning that we do have to go hunting occasionally.
--teamonkey
Re:Not really...
on
Is RPM Doomed?
·
· Score: 2, Insightful
4. Switch to Debian or Slackware
As shown above, their package managers do not solve the problems mentioned in the article. The problems just happen not to show up so frequently because there aren't many distributions using these package management systems, and the ones that do are usually pretty close to the distribution they're based on. Much closer than completely different distributions like e.g. Red Hat and SuSE, which really don't have much in common except for the package manager.
If, say, Red Hat switched to using.debs, you'd immediately run into the problem that, due to totally different base systems, Red Hat.debs wouldn't run on Debian without changes and vice versa.
This is surely due to the various distributions not conforming to the LSB and FHS, rather than the shortcomings of the package management system? Debian is far more standards-complient than RedHat, and Slackware is even better.
With the version of apt that comes with woody, you can choose from which version you wish to install the debs from.
For example, you can track woody for the most part, but if you want the occasional package from sid you can do that too, and it will work out the dependencies automagically. The same would be true for multiple distros - just give it a different name and add the entries to your sources.list file.
My current system was originally Progeny Linux, which was then merged with woody, then sid. Using apt, I had no problems moving between systems.
Sure there were some incompatibilities between the packages, but the deb format is robust enough to at least identify the problems (and in some cases offer a solution). This, I believe, is where RPM falls down.
Well we already know from HIPPARCOS data that there's one star heading right for us. Due to pass close to us in few thousand years. Who knows what will happen? Can't remember it's name though, although if you're curious you could always search through HIPPARCOS data for stars with near-zero radial motion.
--jaa
Slashdot Mirror
...can we have the old one if they're done with it?
Maybe what you hear isn't what it's really like to live here.
If there's one thing we British are really good at, it's moaning. About everything. Look! It seems that writer's caught the bug already.
Shame they're not using a scripting language. I'm no stranger to C++, but it's a hell of a lot easier to mod a game with scripts. The best, IMO, was Jedi Knight's COG language.
Still, looks great! Can't wait to play with the SDK!
Agreed. I still have my 10-year-old DJ500, and regularly use it. But it did cost about £350. You can only compare printers of a similar cost. I'm guessing that's in the £450-500 range now.
Yeah, but it's still accurate to quite a few decimal places.
Another vote for DirectFB. I saw here that David Wexelblat says that "X needs to be replaced by a direct-rendered model, on which a backwards-compatible X server can be reasonably trivially implemented." Sounds like DirectFB with XDirectFB running on top, doesn't it?
Get one of those numeric keypads designed for laptops with a USB interface. Then you can map the keys sung xmodmap.You could even put stickers on the keys.
I can hear that too. I can tell if a TV's on nearby - in another room or even downstairs. Always have been able to, although it was much more noticable when I was younger. High frequency devices are less noticable though. What about the details on screen? I find that a white screen makes a higher-pitched noise than a blank one. On another note, my old monitor used to make high-pitched noises every so often which could be solved by giving it a sharp whack.
Even better: make this work with speech recognition! Star Trek, anyone? :)
Uh, didn't he say that he's a university student?
The language feels as though it's designed by a committee and has features tacked on left, right and centre. IO sucks arse, so don't expect to write a wonderful user interface for it (but you could always do a wrapper in another language, I suppose).
I use F90 at uni, and although it's a bit of a messy language it does what it's good at: spewing out tables of numbers. It is expensive for a single licence, however. I wouldn't bother with it if I didn't have access to the university number crunchers.
I've used SuSE, RedHat, Mandrake, Debian and a few others in the past. I keep thinking that a distribution has enough new features to warrent me changing, and then I hit the dependency problem and go back to Debian again.
This happened a few weeks ago when I installed SuSE on my old laptop because of its PCMCIA support. In the end I has so much trouble finding a RPM and its dependencies, I gave up and stuck woody on there. It took longer to set up, but I just need a net connection and apt.
I'm tempted to switch to Gentoo, but then there's always source DEBs, aren't there :)
apt isn't perfect though. Over a modem it takes a few minutes to apt-get update, and hours to apt-get upgrade, but it does make it so much easier! Also, Debian are very anal about their distro, even about unstable. There are still no (official) KDE3 or Openoffice.org debs (mainly because they don't work on all the supported platforms), meaning that we do have to go hunting occasionally.
--teamonkey
As shown above, their package managers do not solve the problems mentioned in the article. The problems just happen not to show up so frequently because there aren't many distributions using these package management systems, and the ones that do are usually pretty close to the distribution they're based on. Much closer than completely different distributions like e.g. Red Hat and SuSE, which really don't have much in common except for the package manager.
If, say, Red Hat switched to using .debs, you'd immediately run into the problem that, due to totally different base systems, Red Hat .debs wouldn't run on Debian without changes and vice versa.
This is surely due to the various distributions not conforming to the LSB and FHS, rather than the shortcomings of the package management system? Debian is far more standards-complient than RedHat, and Slackware is even better.
With the version of apt that comes with woody, you can choose from which version you wish to install the debs from.
For example, you can track woody for the most part, but if you want the occasional package from sid you can do that too, and it will work out the dependencies automagically. The same would be true for multiple distros - just give it a different name and add the entries to your sources.list file.
My current system was originally Progeny Linux, which was then merged with woody, then sid. Using apt, I had no problems moving between systems.
Sure there were some incompatibilities between the packages, but the deb format is robust enough to at least identify the problems (and in some cases offer a solution). This, I believe, is where RPM falls down.
--teamonkey
Well we already know from HIPPARCOS data that there's one star heading right for us. Due to pass close to us in few thousand years. Who knows what will happen? Can't remember it's name though, although if you're curious you could always search through HIPPARCOS data for stars with near-zero radial motion. --jaa