Actually, Qt is dual licensed under the GPL and a prorietary Qt license. Not only that, but if TrollTech decides that they are no longer going to support the GPL'd version of their libraries, they become BSD'd... so it isn't going to be financially sound for them to do such a thing in the near future.
Yeh yeh. redundant... but this is pure (if unintentional) FUD.
Notice the careful use of "piece of software" -- Qt is a library. The use of the GPL for a library infects every single application that must link to it... which means every single KDE app, for a start.
This is definitely true. However, I have a few things to say concerning it:
TrollTech created the libarary, so they have the choice to determine how it is licensed. Personally, I agree with their form of licensing: if you want to have "the control of propriety" (sic) in your software, then you have to pay them for their efforts.
The GPL is much better than the original Qt License. It allows the community to (at the very least) maintain control of the last open-sourced version of the library. And now that the Windows libraries are open-sourced, there are even more opportunities open to the FL/OSS crowds.
kde-libs are also maintained under the LGPL. The trick is that if you want to develop a proprietary application on top of kde-libs, you'll need a license for the Qt Library. (Think of it as KDE dual-licenses their libraries under GPL & LGPL).
The license fees for Qt pay for the support of the library. This might not seem like such a big deal, until you consider that Qt funds (and in several cases, employs) many of the chief developers of KDE.
I'll believe in real AI when a military robot gets struck by lightning and subsequently malfunctions. It would enjoy the 3 stooges, reprogram itself and it's military bretheren. It could take apart a car in under 3 seconds & steal the nova trucks. Eventually, it would have to convince it's creator that it is, in fact, alive.
Right... but this is a prototype for a device which uses a roll-up display, not the display itself.
Either way, I'm quite excited about this. However, I hope that if this starts being used for newspapers... that they don't start looking like news webpages... tons of ads cicling the page. I prefer the tons of ads lumped at the bottom xor side.;)
Also, as far as the interface for an e-paper magazine is concerned... it would be excellent to have several "pages" of the paper (maybe a total of 4), and to advance a page, you actually turn it. Combine that with a few hyperlinks (for fast advancement) and you got yourself something which is usable and natural.
Crap... I should go get a patent for this -- no, wait!!! Everyone, remember this post for prior art!
Partially, it's a PR stunt, I believe. Around the same time the suit was filed, AMD was just releasing several new chipsets, and bringing up new fab plants. Two of the larger debuts of this time were their Turion and Athlon64 X2 lines. Around that same time, they also spun off their Flash memory branch into a subsidiary, and AMD proper said they would be dedicated to processors.
However, AMD has scheduled to bring a new Fab online soon (Fab 36 according to previous posts), and will surely bring more up as their revenue allows. Given this information, they will be able to produce adequate volumes for OEM sales by the time this suit has completed. That being said, you could say it's also a long-term plan.
Note that AMD never specified what damages they were seeking from Intel. They may be seeking an injunction against Intel's marketing practices, so that when they have the muscle of those new fabs, they don't have to worry about Intel's anti-competitive behavior.
This post is obviously hastily thought through, and almost pure speculation... However, it makes sense when you read their suit, as well as the news that was afoot around that time.
Right, but manual-command line stuff doesn't fall in the lines of "automatic", at least as far as he was describing it.
Think about MS Windows' Automatic Update... it will download patches for you, and then ask you (really, I find it more annoying than clippy) about a million times whether or not you want to install the updates. And when you don't turn off configurations in 2 different places, it will bitch at you that Automatic Updates is off... (This is XP SP2).
Interesting story: my roomate was in the middle of playing one of his games (on a week-old install), and a new update came out for XP... his computer downloaded and installed it. (His game got a tid bit laggy, but we figured the connection was tripping out). he was promptly kicked out of his game while his computer rebooted automatically. I was in hysterics.
In the strictest sense, no. The person who wrote the article should talk to Google, rather than getting/. in a tizzy. (As a matter of fact, he is on the Google Group, he just posted this in addition).
In his defense, though: it was a very well thought article, and after talking with him, I think it's a good idea. I hope he wasn't the one to post his opinion to/. though. (Eg. I hope it was some random/.er who was lurking GG).
That was definitely true some time ago... however, trends are starting to move more towards the following:
Pre-alpha: conceptualizing stage. Happens in front of one or a few programmers
Alpha: Internal bug testing. Not released to the public, usually.
Beta: Release to the public. Usually feature-rich, but not always. (See OSS)
Release-candidate: Iron out the bugs
Release: w00t. Time to spill your beer on the server.
Rinse and repeat beta & RC for every next release, when such a thing exists.
As far as google's betas go... They are using them to collect popular opinion, and implementing what people want, and what they will actually use. Why does GMail not support PGP/GPG encryption? Because most of their users didn't want it. If we were all privacy fanatics, though... then it would have been added in the beta.
Another thing about google betas: They tend to lack on the features, but be pretty tolerant of bugs. I'd much rather have a fault-tolerent beta that lacks features than a fault-laden beta where something new breaks with each release.
Well... I'm not sure about SuSE, but I know that RedHat and Mandriva both support such a device. It rests, safe and serene, nestled in its loving system tray. When updates are available, it changes from its tender green manner into a somewhat irritated orange. When critical updates are available, it becomes really noticable... a form of colicky red.
When it comes to community distributions... they may handle things differently. But they can afford to... as they are the true hobbyist form of Linux. (Well, except for K/Ubuntu)
Overall, though... The astroturfing/trolling was a refreshing experience. Nice to see that you can still bring up the oldies-but-goodies (no matter how false) of linux fix-its. As a matter of fact, you should be heralded as the paragon of all members on the site. I propose a petition! Let everyone who wants to assign Mr PorchPuppy a UID of 2^32 speak now, as it is surely his proper place amongst/.ers.
That doesn't change the fact that he has one, and cannot boot a LiveCD though...
My reccomendation to the GP: put in a bug report at the kernel (or your distros... or better yet, both!) bugzilla. If you provide some software testing, they'll hopefully fix it by the next release.
As far as your current problem goes... Unfortunately, my only advice is to find an IDE drive you can use... or a::cringe:: floppy drive to boot from. A flash drive might work as well... or a network boot.
Linux has become somewhat less stable of late, and that's the number one reason for this "tweak: of the development model. Since the BitTorrent days, you could see large flurries of patches being shipped in... And many (certainly not all) of those patches have been feature-upgrades or systems-rewrites.
Around the realease of 2.6.11, they added another "point" to the releases, in an effort to increase stability... which is why you saw 2.6.12.x releases. This helped the situation somewhat, but developement was still somewhat frenetic... Basically, this led to a degeneration of the overall quality of the code.
However, the developers know this, and (thankfully) they're doing something about it.:D So, rest assured, the solid kernel you're used to will be making a comeback soon.
Well, while the GCC crew was prepping their C++ ABI they managed to break it at least once as well. GCC3->GCC4 compiles slightly different. Quite a pain when you run Gentoo and KDE:-!
But, in all honesty... I don't really know why we respnded to the GP in the first place... It was most obviously a troll.
Then I would say it doesn't belong in YRO at all. Remove it entirely from this section. It doesn't have anything to do with "rights", as far as I am concerned. IT has to do with 2 dumbasses creating a worm and releasing it into the wild, with solely malevolent intent.
Heh. This will be seen as a flame... but I am of the opinion that these two should be tracked down and punished... IE. Their rights wern't being harmed when they were arrested, nor was there a "triumph" of personal rights over the government.
YRO should be reserved for real discussions of rights, not bullshit stories that explain the arrest of virii creators. My problem is not that it is on a boundary--it doesn't fit at all.
Maybe it's just me, but/. should really think about implementing a "crime" section for posts such as this... I don't believe that the arrest of a virus creator really falls within the realm of "Your Rights Online"...
According to recent reports, google is the most hated company, though. They kill innovation, commit mass copyright infringement, and don't have nearly as many results as yahoo. Duh!
Heh... I thought the likelyhood of this happening was about the same as Debi-- no. Appl-- no. Windows Vista releasing with all of the promised features.
Concerning their humor (yes, I am a white male)... I have never understood it either. So, I did the thing that any clueless nerd would, and asked how their humor worked.
Turns out, alot of the time, they just point out the stupid shit that us white people do. Like socks with sandals. We see it as "fashion statement", they see it as "defeating the purpose of sandals". A big bit of their humor is just seeing the inconsistencies that we throw out. Thing is, their punchline isn't overt, like ours. It's usually carried in the undercurrent of their speech, so it's lost upon us.
They didn't find it offensive that I asked, either... though I bet they had a good chuckle about it later.
Slashdot Mirror
Actually, Qt is dual licensed under the GPL and a prorietary Qt license. Not only that, but if TrollTech decides that they are no longer going to support the GPL'd version of their libraries, they become BSD'd... so it isn't going to be financially sound for them to do such a thing in the near future. Yeh yeh. redundant... but this is pure (if unintentional) FUD.
This is definitely true. However, I have a few things to say concerning it:
Hopefully, we'll get the point across, (shortly before their mail servers become shapely piles of slag).
Really? I poured them into the frontend, and now run Big Iron.
I'll believe in real AI when a military robot gets struck by lightning and subsequently malfunctions. It would enjoy the 3 stooges, reprogram itself and it's military bretheren. It could take apart a car in under 3 seconds & steal the nova trucks. Eventually, it would have to convince it's creator that it is, in fact, alive.
Either way, I'm quite excited about this. However, I hope that if this starts being used for newspapers... that they don't start looking like news webpages... tons of ads cicling the page. I prefer the tons of ads lumped at the bottom xor side. ;)
Also, as far as the interface for an e-paper magazine is concerned... it would be excellent to have several "pages" of the paper (maybe a total of 4), and to advance a page, you actually turn it. Combine that with a few hyperlinks (for fast advancement) and you got yourself something which is usable and natural.
Crap... I should go get a patent for this -- no, wait!!! Everyone, remember this post for prior art!
Sometimes you people read far too much into what another person says.
Sure looks to me like they have a relief effort link up...
However, AMD has scheduled to bring a new Fab online soon (Fab 36 according to previous posts), and will surely bring more up as their revenue allows. Given this information, they will be able to produce adequate volumes for OEM sales by the time this suit has completed. That being said, you could say it's also a long-term plan.
Note that AMD never specified what damages they were seeking from Intel. They may be seeking an injunction against Intel's marketing practices, so that when they have the muscle of those new fabs, they don't have to worry about Intel's anti-competitive behavior.
This post is obviously hastily thought through, and almost pure speculation... However, it makes sense when you read their suit, as well as the news that was afoot around that time.
Open sauce? Damn, guy. Next time read the results after you spellcheck ;)
Coz you know we all love that 11 minute dupe.
Damn... I was looking for that perfect obvious quip. Kudos to you for getting it first.
Think about MS Windows' Automatic Update... it will download patches for you, and then ask you (really, I find it more annoying than clippy) about a million times whether or not you want to install the updates. And when you don't turn off configurations in 2 different places, it will bitch at you that Automatic Updates is off... (This is XP SP2).
Interesting story: my roomate was in the middle of playing one of his games (on a week-old install), and a new update came out for XP... his computer downloaded and installed it. (His game got a tid bit laggy, but we figured the connection was tripping out). he was promptly kicked out of his game while his computer rebooted automatically. I was in hysterics.
In his defense, though: it was a very well thought article, and after talking with him, I think it's a good idea. I hope he wasn't the one to post his opinion to /. though. (Eg. I hope it was some random /.er who was lurking GG).
- Pre-alpha: conceptualizing stage. Happens in front of one or a few programmers
- Alpha: Internal bug testing. Not released to the public, usually.
- Beta: Release to the public. Usually feature-rich, but not always. (See OSS)
- Release-candidate: Iron out the bugs
- Release: w00t. Time to spill your beer on the server.
Rinse and repeat beta & RC for every next release, when such a thing exists.As far as google's betas go... They are using them to collect popular opinion, and implementing what people want, and what they will actually use. Why does GMail not support PGP/GPG encryption? Because most of their users didn't want it. If we were all privacy fanatics, though... then it would have been added in the beta.
Another thing about google betas: They tend to lack on the features, but be pretty tolerant of bugs. I'd much rather have a fault-tolerent beta that lacks features than a fault-laden beta where something new breaks with each release.
I'm surprised that /. hasn't decended en-masse to comment the hell out of his post. ;)
When it comes to community distributions... they may handle things differently. But they can afford to... as they are the true hobbyist form of Linux. (Well, except for K/Ubuntu)
Overall, though... The astroturfing/trolling was a refreshing experience. Nice to see that you can still bring up the oldies-but-goodies (no matter how false) of linux fix-its. As a matter of fact, you should be heralded as the paragon of all members on the site. I propose a petition! Let everyone who wants to assign Mr PorchPuppy a UID of 2^32 speak now, as it is surely his proper place amongst /.ers.
I think I've said enough though. Have a nice day.
My reccomendation to the GP: put in a bug report at the kernel (or your distros... or better yet, both!) bugzilla. If you provide some software testing, they'll hopefully fix it by the next release.
As far as your current problem goes... Unfortunately, my only advice is to find an IDE drive you can use... or a ::cringe:: floppy drive to boot from. A flash drive might work as well... or a network boot.
Around the realease of 2.6.11, they added another "point" to the releases, in an effort to increase stability... which is why you saw 2.6.12.x releases. This helped the situation somewhat, but developement was still somewhat frenetic... Basically, this led to a degeneration of the overall quality of the code.
However, the developers know this, and (thankfully) they're doing something about it. :D So, rest assured, the solid kernel you're used to will be making a comeback soon.
But, in all honesty... I don't really know why we respnded to the GP in the first place... It was most obviously a troll.
Heh. This will be seen as a flame... but I am of the opinion that these two should be tracked down and punished... IE. Their rights wern't being harmed when they were arrested, nor was there a "triumph" of personal rights over the government.
YRO should be reserved for real discussions of rights, not bullshit stories that explain the arrest of virii creators. My problem is not that it is on a boundary--it doesn't fit at all.
Maybe it's just me, but /. should really think about implementing a "crime" section for posts such as this... I don't believe that the arrest of a virus creator really falls within the realm of "Your Rights Online"...
According to recent reports, google is the most hated company, though. They kill innovation, commit mass copyright infringement, and don't have nearly as many results as yahoo. Duh!
Heh... I thought the likelyhood of this happening was about the same as Debi-- no. Appl-- no. Windows Vista releasing with all of the promised features.
Turns out, alot of the time, they just point out the stupid shit that us white people do. Like socks with sandals. We see it as "fashion statement", they see it as "defeating the purpose of sandals". A big bit of their humor is just seeing the inconsistencies that we throw out. Thing is, their punchline isn't overt, like ours. It's usually carried in the undercurrent of their speech, so it's lost upon us.
They didn't find it offensive that I asked, either... though I bet they had a good chuckle about it later.