Yes it is crap for developers, but this initiative is for advanced users and not developers. Basicaly it tells users how to run the most recent and greatest KDE right out of CVS, and how to report bugs. From there they can do as always, run the most recent software just for the kick, and report the bugs they encounter. Or they can decide they want to do something good to pay back the KDE team for its hard work, and just try out every obscure feature and make sure it all works. Doesnt mean you have to code, it just mean you have to know how to use applications and think for yourself.
And it is enshrined in the human right convention as well, which all european countries have signed (and have to sign to join the EU), but which US has not (because you break rule number 1 regurarly).
The court of human rights outpower the respective supreme courts in european countries, and is thus protecting the freedom of speech internationally and regardless of what current governments in the member country might try.
Oh yes, your puny constitunal protection of this freedom is not unique or especially strong.
Not quite accurate. 3dnow! was the precursor to SSE and not MMX (K6 already had MMX). The reason AMD ended up with a different extension was they were first like they were with x86-64, but in this case Intel decided to make their own incompatible extension rather than copying AMDs.
Well "fractions of a second", just isn't good enough. When dealing with massive amounts of email it shouldn't take more than a fraction of a millisecond, or the email-server and applications will simply suck.
As for the Intel thing. The selling point of AMD has always been they where fully "Intel Compatible". They had to be, otherwise noone would buy their product.
Oh yes it does. The speed-difference between gcc and icc is in fact bigger on Athlon64 than on P4. This is the reason Intel changed v8 to detect non-Intel chips and go in slowmo, or refuse to run if you havent included the slowmo version.
They did. Have you heard AMD use any other names for MMX, SSE and SSE2 than MMX, SSE, SSE2. They also note in there documentation that their implementations are compatible with Intels.
Notice btw, that SSE was just Intel last attempt of trying to get around having to copy AMDs implementation. SSE is really superior, just more featurefull, which could have come from extending 3dnow as well.
It's meant to distinguish itself from other x86 instruction sets that *aren't* IA32. Get over it, Linus.
Like AMDs or what? Are you astroturfing by any chance?
There has never been any confusion over the x86 name. It came after 486 and pentium kept the same instructions-set at 386, where each previous generation had been "unique". So the line goes: 8088, 8086, 80286, x86, x86-64.
If that should look any other way it would be IA8, IA16, IA16+crap, IA32 and AMD64
No problem, the symtoms can be read from the excerpts of file-listings all over the net. Almost every directory contains an empty.eml file, something usually generated by the Nimda-virus that ironically the leaked win2000 SP1 is vulnable to, but which SP2 isn't.
but the meat in big mac is not meat for the most part but only "meat". In the 90s they lost the right to call it beef-meat in the EU since it didnt contain enough beef to qualify (they could still call it mixed meat though).
Not that I am an expert, but the most commonly praised feature about KWord, is that it works differently from most wordprocessers; making somethings harder and others easier.
Supposedly it works more like a layout-editor, like those used to print magazines and newspapers.
AFAIK DCOP doesn't depend on Qt directly and has C-bindings. The problem is with depending on C++, and depending on Qt for communicating with KDE-programs. Many KDE-programs uses the Qt-internal structures to stream over DCOP, that makes it very difficult to communicate with them without Qt.
Libraries are "used" by developers. Practically no one uses Xlib nowadays, the uses widgets toolkits that depends on Xlib (and was written by a few people using Xlib) instead.
So it powers your whole desktop, and your whole desktop depends on it. But still it is very little used.
D-BUS is the replacement for DCOP. "Agnostically" written in C this time to help GNOME developers swallow (not so agnostically though since Glib kept sneaking in, but fortunately got replaced in the end).
It does have a few neat features that DCOP doesnt. Like being system-wide, and thus support signals from the kernel (implemented by HAL) and signals from other non-desktop application like Apache.
Slashdot Mirror
Yes it is crap for developers, but this initiative is for advanced users and not developers. Basicaly it tells users how to run the most recent and greatest KDE right out of CVS, and how to report bugs. From there they can do as always, run the most recent software just for the kick, and report the bugs they encounter. Or they can decide they want to do something good to pay back the KDE team for its hard work, and just try out every obscure feature and make sure it all works. Doesnt mean you have to code, it just mean you have to know how to use applications and think for yourself.
And it is enshrined in the human right convention as well, which all european countries have signed (and have to sign to join the EU), but which US has not (because you break rule number 1 regurarly).
The court of human rights outpower the respective supreme courts in european countries, and is thus protecting the freedom of speech internationally and regardless of what current governments in the member country might try.
Oh yes, your puny constitunal protection of this freedom is not unique or especially strong.
Not quite accurate. 3dnow! was the precursor to SSE and not MMX (K6 already had MMX). The reason AMD ended up with a different extension was they were first like they were with x86-64, but in this case Intel decided to make their own incompatible extension rather than copying AMDs.
I remember some survey. It seemed surprisingly few people reacted to a desperate female voice yelling RAPE or help!
I think most people are not _ignoring_ alarms, they just dont care.
Well "fractions of a second", just isn't good enough. When dealing with massive amounts of email it shouldn't take more than a fraction of a millisecond, or the email-server and applications will simply suck.
What dont you have a pdf-reader or are you full of shit?
Reference to SSE:
White paper on Athlon XP
As for the Intel thing. The selling point of AMD has always been they where fully "Intel Compatible". They had to be, otherwise noone would buy their product.
Oh yes it does. The speed-difference between gcc and icc is in fact bigger on Athlon64 than on P4. This is the reason Intel changed v8 to detect non-Intel chips and go in slowmo, or refuse to run if you havent included the slowmo version.
They did. Have you heard AMD use any other names for MMX, SSE and SSE2 than MMX, SSE, SSE2. They also note in there documentation that their implementations are compatible with Intels.
Notice btw, that SSE was just Intel last attempt of trying to get around having to copy AMDs implementation. SSE is really superior, just more featurefull, which could have come from extending 3dnow as well.
It's meant to distinguish itself from other x86 instruction sets that *aren't* IA32. Get over it, Linus.
Like AMDs or what? Are you astroturfing by any chance?
There has never been any confusion over the x86 name. It came after 486 and pentium kept the same instructions-set at 386, where each previous generation had been "unique". So the line goes: 8088, 8086, 80286, x86, x86-64.
If that should look any other way it would be IA8, IA16, IA16+crap, IA32 and AMD64
I prefer the term: "Fully AMD Compatible"
Or for 13 year olds to mix with red soda..
No problem, the symtoms can be read from the excerpts of file-listings all over the net. Almost every directory contains an empty .eml file, something usually generated by the Nimda-virus that ironically the leaked win2000 SP1 is vulnable to, but which SP2 isn't.
In fact the code is filled with tell-tale signs of a windows virus, meaning it has at least been on an infected windows machine at one time.
The Linux thing is just Microsoft/media twist.
Criminal?? What criminal?
Someone broke a license agreement, that has a usually monetary penalty, but it is not a crime and doesnt make you a criminal..
It has be emulated in a boyband though: PRESS PLAY ON TAPE.
:)
Check out their new CD too
but the meat in big mac is not meat for the most part but only "meat". In the 90s they lost the right to call it beef-meat in the EU since it didnt contain enough beef to qualify (they could still call it mixed meat though).
Not on sparc. mcpu on sparc means the same as march on i386. For mcpu behaviour use mtune on sparc.
No the reason you didnt learn of exceptions, is to protect you. C++ exceptions are crippled bastards only their mother Bjarne can appreciate.
If people in generel knew more of C++ exceptions, the C-trolls would have much more ammunition. It is better simple not to talk about them.
The same goes partly for STL
I know libgsf is somewhere in the dependency-chain of the MS-office filters for KOffice. Don't know if it is used though.
KOffice uses wvware2 and libwmf, which are now shared by abiword and koffice.
Not that I am an expert, but the most commonly praised feature about KWord, is that it works differently from most wordprocessers; making somethings harder and others easier.
Supposedly it works more like a layout-editor, like those used to print magazines and newspapers.
No apparently the rest of the world cuts is itself off from you.
It is as easy to use C++ libaries in C as it is to use glib in C++. Both has a foreign object model that needs to be bridged.
Only problem with C++ from C is name-mangling, but it can be overcome by simple C-bindings.
AFAIK DCOP doesn't depend on Qt directly and has C-bindings. The problem is with depending on C++, and depending on Qt for communicating with KDE-programs. Many KDE-programs uses the Qt-internal structures to stream over DCOP, that makes it very difficult to communicate with them without Qt.
Libraries are "used" by developers. Practically no one uses Xlib nowadays, the uses widgets toolkits that depends on Xlib (and was written by a few people using Xlib) instead.
So it powers your whole desktop, and your whole desktop depends on it. But still it is very little used.
D-BUS is the replacement for DCOP. "Agnostically" written in C this time to help GNOME developers swallow (not so agnostically though since Glib kept sneaking in, but fortunately got replaced in the end).
It does have a few neat features that DCOP doesnt. Like being system-wide, and thus support signals from the kernel (implemented by HAL) and signals from other non-desktop application like Apache.
apt-get kick wimp?