My girlfriend sells hearing aids and proffessional grade ear plugs. There are relatively cheap (20 euro) earplugs which you can re-use, that will not affect sound quality. Great stuff for those ueber-loud concerts.
Actually, I play in a multi-acoustical-instrument band (not jazz though), and we *have* to use amplification because some instruments are so much louder than others. The more silent instruments (flutes mostly, acoustic bass) would not be heard.
This makes it sound almost like a bad thing. Why not develop some new technology seperately so it can mature, then integrate it bake into the 'big core' for better efficiency, develop a new generation seperately, etc...? Not a bad thing as I see it, but a natural cycle of technology.
I had this problem with ATI's fglxrx driver. Try using the open source one (radeon).
Re:Things I'd like to see from GNOME.
on
Gnome 2.10 Released
·
· Score: 2, Insightful
On the one hand, you've got people complaining about not enough new features in GNOME. "Look at these release notes! No new features, just these optimizations in Nautilus!"
On the other hand, in the same story you've got other people complaining, saying "Look at all these features! Why do they keep adding and adding? Let's focus on bug-fixing and performance instead!"
Bender: "There's nothing wrong with murder. Just as long as you let Bender wet his beak."
Leela: "You're blackmailing me?"
Bender: "Blackmail is such an ugly word. I prefer extortion. The x makes it sound cool."
So, we've come full circle. GNOME removes all extra clock applets from version 2.0 after the Sun usability study (and rightly so!). A few years later, KDE adds extra clock applets. Sheesh.
Alright, I'll calm down, it's just in the addons package. But it's still a usability problem.
I think your case is pretty well answered by the core team: FreeBSD 5.0 wasn't supposed to be as fast as 4.x, and users were warned months ahead about it. Being unhappy with it after such a big warning really seems pretty strange to me.
Also, 5.0 really isn't as slow as many people make it out to be. The main slownesss is in GCC 3.2, not in the system itself.
Actually, I found Eugenia's questions rather flame-bait-like. Note that I actually haven't read many of her articles before, so I'm not too sure about her history of writing bad articles, but questions like
"FreeBSD 5.0 has come out [..] many were unhappy with the instability and slowness the 5.0 release offered compared with the 4.x branch [..]"
are really, really bad. She really has a knack for asking questions with a really negative tone and making many (bad) assumptions. The core team handle these well enough, making really clear that any assumption made in these questions are wrong.
Re:Please, AOLTW, switch to NS from IE for AOL..
on
Netscape 7.0 is Out
·
· Score: 2, Interesting
Really? I'd imagine these 'clueless' users would call the bank in question rather than AOL, and the conversation would go something like:
This means I can convert another few of my friends to the Lite Side. Provided Loki this time doesn't screw up Linux Mode as they did with Myth2 (parsing procfs).
1) What is the fundamental difference between *BSDs in terms of driver compatibility, or can drivers be ported easily? Specifically interested in PCI-related stuff.
Porting drivers is not easy. I remember seeing some documentation about it, but can't remember where, what or how.
2) Which of the BSDs has 64-bit support for Alpha? Again, interested in 64-bit memory and PCI access. I have a feeling FreeBSD's alpha port doesn't, whereas NetBSD might.
Both FreeBSD and NetBSD have full 64 bit support, IIRC. There are some glitches in the alpha port of FreeBSD since it's relatively new (and FreeBSD's first port), but from what I hear it's stable as hell.
... will it be implemented cross-platform? An open source DVD player will not only be good for Linux, but for everyone in general (that is, users of other Unices, MacOS and even Windows).
It really would be a shame if things like this will be implemented Linux-only. Aside from the kernel driver (is that necessary?), porting should not be too difficult...
What if AT&T hadn't sued any operating system using the BSD code, back in (93, 94, 95, can't remember exact year)? This a setback for the OS'es, as any AT&T code had to be rewritten. Which was quite a lot, IIRC.
Slashdot Mirror
You mean I actually have to log in and leave a message now?
*sigh*
Very well then.
Thanks, Taco, from the bottom of my heart. You certainly defined my internet experience for the last 14 or so years.
- Theo
My girlfriend sells hearing aids and proffessional grade ear plugs. There are relatively cheap (20 euro) earplugs which you can re-use, that will not affect sound quality. Great stuff for those ueber-loud concerts.
Actually, I play in a multi-acoustical-instrument band (not jazz though), and we *have* to use amplification because some instruments are so much louder than others. The more silent instruments (flutes mostly, acoustic bass) would not be heard.
This makes it sound almost like a bad thing. Why not develop some new technology seperately so it can mature, then integrate it bake into the 'big core' for better efficiency, develop a new generation seperately, etc...? Not a bad thing as I see it, but a natural cycle of technology.
How dare you post that without screenshots! Everybody loves screenshots!
UGA screenshot
Because vnc2swf doesn't work when using direct rendering for GL graphics and Xv for movies.. Kinda sucks, but that's life.
I had this problem with ATI's fglxrx driver. Try using the open source one (radeon).
On the one hand, you've got people complaining about not enough new features in GNOME. "Look at these release notes! No new features, just these optimizations in Nautilus!"
On the other hand, in the same story you've got other people complaining, saying "Look at all these features! Why do they keep adding and adding? Let's focus on bug-fixing and performance instead!"
There's just no pleasing some people. Really.
No, by the same token, if everybody had a copy of the latest OS, no one would *use* it.
You're welcome! :)
(I developed that patch)
So, we've come full circle. GNOME removes all extra clock applets from version 2.0 after the Sun usability study (and rightly so!). A few years later, KDE adds extra clock applets. Sheesh.
Alright, I'll calm down, it's just in the addons package. But it's still a usability problem.
I think your case is pretty well answered by the core team: FreeBSD 5.0 wasn't supposed to be as fast as 4.x, and users were warned months ahead about it. Being unhappy with it after such a big warning really seems pretty strange to me.
Also, 5.0 really isn't as slow as many people make it out to be. The main slownesss is in GCC 3.2, not in the system itself.
"What browser are you using?"
"Uhmm... the new AOL"
"Right, uhm, okay, we'll have to fix it then"
Note, though, that I'm not an American :)
Yeah. And the sad thing is, me and a friend of mine actually figured this one out all by ourselves :(
Yes, the easter egg can be triggered as follows:
(for recent versions of Window Maker):
- In your PropList files, change every instance of GNUStepGlow.tiff to GNUStep3D.tiff.
- Open the about box.
- Click on the icon.
(for older versions):
- The icon is already GNUStep3d.
- Open the about box.
- Click three times on the icon.
Have fun!
Dig these sassy chicks: http://www.freebsd.org/~jkh/lw2000/
... and it's called VIGOR. :-)
This means I can convert another few of my friends to the Lite Side. Provided Loki this time doesn't screw up Linux Mode as they did with Myth2 (parsing procfs).
:)
This was the only game they were hanging on to.
KDE. Definately KDE.
GNOME leaves ~7 Core Dumps on my harddisk after a 5 minute session, on FreeBSD-STABLE.
Never had the problem with Linux, 'though.
1) What is the fundamental difference between *BSDs in terms of driver compatibility, or can drivers be ported easily? Specifically interested in PCI-related stuff.
Porting drivers is not easy. I remember seeing some documentation about it, but can't remember where, what or how.
2) Which of the BSDs has 64-bit support for Alpha? Again, interested in 64-bit memory and PCI access. I have a feeling FreeBSD's alpha port doesn't, whereas NetBSD might.
Both FreeBSD and NetBSD have full 64 bit support, IIRC. There are some glitches in the alpha port of FreeBSD since it's relatively new (and FreeBSD's first port), but from what I hear it's stable as hell.
... will it be implemented cross-platform? An open source DVD player will not only be good for Linux, but for everyone in general (that is, users of other Unices, MacOS and even Windows).
It really would be a shame if things like this will be implemented Linux-only. Aside from the kernel driver (is that necessary?), porting should not be too difficult...
What if AT&T hadn't sued any operating system using the BSD code, back in (93, 94, 95, can't remember exact year)? This a setback for the OS'es, as any AT&T code had to be rewritten. Which was quite a lot, IIRC.
This article is an almost exact copy of an earlier article on CNet. Many good points were made on the MozillaZine article about the CNet article.