XFree86.org changes a few words in their license, and within four months almost every major Linux distribution and BSD has dumped it.
Er...no on the BSD part. Let's see who -has- actually switched.
OpenBSD: Yup, but not to Xorg. They created yet -another- fork (for now at least?).:P
NetBSD: Nope. XFree86 4.4.0
FreeBSD: Nope. Haven't done much at all, and the current used version is still 4.3.0 (Xorg might become default and is in ports right now, but you'll probably be able to use 4.4.0 if you want to)
Darwin/OS X: Xdarwin?? I'm not sure if this applies or not.
I haven't included ekko, mir, etc because they are far from major.
At this point, all Microsoft has to do to keep things proprietary is not implement the new standard. Why should they want to implement it when they can do some crazy com/.net solution that nobody can use except on a Windows PC?
That's where the competition comes in. A site may say, oh, you need a newer browser to view this properly. Well, Microsoft doesn't have it, so, um, sorry, use Mozilla/Firefox or Opera. As soon as people discover that IE is "broken", they become a lot more willing to switch away.
And then you have to get developers and whatnot to use your standard. An open standard has an advantage there, since -anyone- can do it without paying Microsoft.
On the other hand, IE -does- hold the upperhand, and web developers are always needing to maintain as much compatibility between browsers as possible (or, at least IE), so they might not use something most of the people can't use easily. So you definately have a point. It's not going to be easy to keep microsoft from exerting its market dominance
I don't like these reviewers who shit tout court negative opinions only because there is ONE new feature that doesn't fit properly into his GUI accustomations
Just update CVS from FreeBSD whenever they apply the fix. If FreeBSD haven't made a new release yet, then you might want to turn off public access until it's fixed.
The issue has been announced via the normal announcement channels for FreeBSD and an advisory which explains what to is available. I actually got the FreeBSD advisory before I heard about it on slashdot.
Guys, it's time to face the facts. C is a relic from a time when compilers were stupid. Declare all your variables before executing code, declare all your functions before using them, include headers that almost invariably break one another, hurrah.
I'm so glad that every time I write C I get to write each function signature several times, that's lovely. In addition, C takes much more time to compoile than Java/C# because all the stupid headers take forever to parse.
What will you use for your low level device drivers? Or how about that code that needs run fast? I don't know about compile (C does compile faster than C++ though), but C runs faster than java and C# (only -sure- about the first one). In fact, the java virtual machine and compiler are both written in C. Face it, C isn't dead yet, even though people have been trying to say so for years.
So, in conclusion, C compatibility is a bug, not a feature.
Other posts have mentioned this is -link- compatibility. Remember, D is meant to live in the real world as a binary outside of a vm. Link compatibility becomes a pretty damn useful thing when you need to work with other people's libraries.
Yahoo used to use Google, but they bought Inktomi and have switched to their search engine. MSN also uses the Inktomi search engine, but tweak the results.
Right before google became a big name, yahoo used inktomi (inktomi used to be a really big name in the search engine industry). Yahoo used to use google more recently, but now they don't.
WUSB on the other hand is FAST. It seems like a waste to use it for a keyboard or mouse.
Ahh, but usb support of mice and keyboards is a well known standard (hid). You need very little to get it working with today's drivers.
Re:To curb the anti-Red Hat gibberish
on
Red Hat Recap
·
· Score: 2, Insightful
He wasn't implying that, he simply said that red hat contributes. They don't just take the 200 buck licenses lauging to the bank, they pay people to make stuff available for everyone.
He may not have been trying to imply that, but it sounded like he might have been.
Remember gcc 2.96?
Uh what? That's a nice red herring. Again, red hat contributes back, the misbranded gcc is irrelevant here.
Ok, so the gnu link wasn't that informative. However, gcc 2.96 (before it was fixed) was -very- broken, and not an actual official gcc release, but instead the development version gcc + some patches redhat commited. Mplayer in particular had a lot of problems with it. Fortunately (as far as I know), Redhat didn't do anything else quite that bad, or I'd -really- rather not have Redhat's contributions.
Re:To curb the anti-Red Hat gibberish
on
Red Hat Recap
·
· Score: 1, Insightful
1) They release all their config tools under the GPL
GPL is far from a magic wand. (It won't make your code automagically perfect. You have to have programmers that can do that before that'll happen)
2) They contribute to the kernel, GCC, glibc, XFree86, GNOME, OpenOffice.org and other projects
I would too if my business was completely bassed on selling Linux.
I don't have any major hate of Redhat's stuff though, and I was mostly just pointing out the bad points. (Personally, I just don't like it because it felt too confining, so thus, tada, I didn't use it)
As it seems, that 90% of the trolling today was sent as Anonymous Coward, perhaps disabling anonymous posting completly would make BSD section of slashdot a nice place to discuss again, just like it should be.
Or make ACs get -1 (or worse) starting out on the posts in your prefs. Also if the AC trolls do decide to get users, just add them to your Foes list and make those start out with a lesser score.
Occasionally being AC can be useful, especially if you want to post something *gasp* anonymously, or don't think something will fly well with the slashdot community and don't want your beautiful, beautiful karma to get damaged.:P
I HATE April first, you can never tell what's real, BSD on Game boy? Next youll tell me rush limbuagh is a drug addict and the cubs almost won the pennant
They said OpenBSD on a Gameboy, which can't be real. Now, NetBSD on the other hand....
Your list is somewhat dependant on whoever wrote the original software. Ports/pkgsrc/etc are pretty much at the mercy of whoever wrote the software in the first place.
Slashdot Mirror
XFree86.org changes a few words in their license, and within four months almost every major Linux distribution and BSD has dumped it.
Er...no on the BSD part. Let's see who -has- actually switched.
OpenBSD: Yup, but not to Xorg. They created yet -another- fork (for now at least?). :P
NetBSD: Nope. XFree86 4.4.0
FreeBSD: Nope. Haven't done much at all, and the current used version is still 4.3.0 (Xorg might become default and is in ports right now, but you'll probably be able to use 4.4.0 if you want to)
Darwin/OS X: Xdarwin?? I'm not sure if this applies or not.
I haven't included ekko, mir, etc because they are far from major.
CEO of Network Time Protocol?....what?
COOKING IS AN ART. if it wasn't, any regular joe could pick up a copy of the Joy of Cooking and be running a four-star restaurant in a week.
Hold on, I'll be getting my Nobel Prize for Chemistry in a week. And those grants are coming in already!
At this point, all Microsoft has to do to keep things proprietary is not implement the new standard. Why should they want to implement it when they can do some crazy com/.net solution that nobody can use except on a Windows PC?
That's where the competition comes in. A site may say, oh, you need a newer browser to view this properly. Well, Microsoft doesn't have it, so, um, sorry, use Mozilla/Firefox or Opera. As soon as people discover that IE is "broken", they become a lot more willing to switch away.
And then you have to get developers and whatnot to use your standard. An open standard has an advantage there, since -anyone- can do it without paying Microsoft.
On the other hand, IE -does- hold the upperhand, and web developers are always needing to maintain as much compatibility between browsers as possible (or, at least IE), so they might not use something most of the people can't use easily. So you definately have a point. It's not going to be easy to keep microsoft from exerting its market dominance
I don't like these reviewers who shit tout court negative opinions only because there is ONE new feature that doesn't fit properly into his GUI accustomations
Ever heard of POLA?
I agreizzle completelizzle. Iizzle's awesomizzle thaizzle theizzle keeizzle thingizzle yoizzle doizzle't neeizzle ouizzle, anizzle yoizzle caizzle brinizzle whaizzle pluginizzle yoizzle wanizzle iizzle!
Just update CVS from FreeBSD whenever they apply the fix. If FreeBSD haven't made a new release yet, then you might want to turn off public access until it's fixed.
The issue has been announced via the normal announcement channels for FreeBSD and an advisory which explains what to is available. I actually got the FreeBSD advisory before I heard about it on slashdot.
Of course not. This is not the first vulnerability either.
Just because you found a bunch of problems a while ago doesn't mean you shouldn't look at the code again later.
Hasn't anyone LOOKED at the code?
Have you ever considered the possibility that they may have discovered the vulnerability by looking at the code?
They still have to make sure everyone knows about it, you know.
Jefferson wanted more than a right to bear arms, he wanted a constitutional right to revolution.
Not only did he want it to be a constitutional right, but he thought we should have one every 20 years.
Latency sucks, though.
Well, not only does it take a while to get there, but then you have to worry about seek time too!
Actually, they data transfered across Sweden, part of Europe and then the United States which (according to them) took up 10,157 miles total.
Two issues we are particularly focused on improving are the small versions of the icons, ...
The small version of the firefox icon looks like a glove (or it does to me at least).
Do we get to metamod too?
Using swap is not bad.
No it isn't, but constantly swapping a lot things in and out is, and you'll notice a considerable slow down of your machine.
And that's when you need to consider buying more ram.
"My code is self documenting"
Hey, not all of us are cobol programmers!
Don't give yourself root either. :P
Guys, it's time to face the facts. C is a relic from a time when compilers were stupid. Declare all your variables before executing code, declare all your functions before using them, include headers that almost invariably break one another, hurrah.
I'm so glad that every time I write C I get to write each function signature several times, that's lovely. In addition, C takes much more time to compoile than Java/C# because all the stupid headers take forever to parse.
What will you use for your low level device drivers? Or how about that code that needs run fast? I don't know about compile (C does compile faster than C++ though), but C runs faster than java and C# (only -sure- about the first one). In fact, the java virtual machine and compiler are both written in C. Face it, C isn't dead yet, even though people have been trying to say so for years.
So, in conclusion, C compatibility is a bug, not a feature.
Other posts have mentioned this is -link- compatibility. Remember, D is meant to live in the real world as a binary outside of a vm. Link compatibility becomes a pretty damn useful thing when you need to work with other people's libraries.
Yahoo used to use Google, but they bought Inktomi and have switched to their search engine. MSN also uses the Inktomi search engine, but tweak the results.
Right before google became a big name, yahoo used inktomi (inktomi used to be a really big name in the search engine industry). Yahoo used to use google more recently, but now they don't.
It looks like yahoo bought inktomi about a year ago, so I guess that's what they are using again.
WUSB on the other hand is FAST. It seems like a waste to use it for a keyboard or mouse.
Ahh, but usb support of mice and keyboards is a well known standard (hid). You need very little to get it working with today's drivers.
He wasn't implying that, he simply said that red hat contributes. They don't just take the 200 buck licenses lauging to the bank, they pay people to make stuff available for everyone.
He may not have been trying to imply that, but it sounded like he might have been.
Uh what? That's a nice red herring. Again, red hat contributes back, the misbranded gcc is irrelevant here.
Ok, so the gnu link wasn't that informative. However, gcc 2.96 (before it was fixed) was -very- broken, and not an actual official gcc release, but instead the development version gcc + some patches redhat commited. Mplayer in particular had a lot of problems with it. Fortunately (as far as I know), Redhat didn't do anything else quite that bad, or I'd -really- rather not have Redhat's contributions.
1) They release all their config tools under the GPL
GPL is far from a magic wand. (It won't make your code automagically perfect. You have to have programmers that can do that before that'll happen)
2) They contribute to the kernel, GCC, glibc, XFree86, GNOME, OpenOffice.org and other projects
Remember gcc 2.96?
3) They're standing up and fighting SCO
I would too if my business was completely bassed on selling Linux.
I don't have any major hate of Redhat's stuff though, and I was mostly just pointing out the bad points. (Personally, I just don't like it because it felt too confining, so thus, tada, I didn't use it)
As it seems, that 90% of the trolling today was sent as Anonymous Coward, perhaps disabling anonymous posting completly would make BSD section of slashdot a nice place to discuss again, just like it should be.
Or make ACs get -1 (or worse) starting out on the posts in your prefs. Also if the AC trolls do decide to get users, just add them to your Foes list and make those start out with a lesser score.
Occasionally being AC can be useful, especially if you want to post something *gasp* anonymously, or don't think something will fly well with the slashdot community and don't want your beautiful, beautiful karma to get damaged. :P
I HATE April first, you can never tell what's real, BSD on Game boy? Next youll tell me rush limbuagh is a drug addict and the cubs almost won the pennant
They said OpenBSD on a Gameboy, which can't be real. Now, NetBSD on the other hand....
Your list is somewhat dependant on whoever wrote the original software. Ports/pkgsrc/etc are pretty much at the mercy of whoever wrote the software in the first place.