I had to keep checking the top banner to make sure I wasn't on freerepublic after reading the comments on here. So much utter nonsense about death panels and across-state-lines-magic. I don't think I've seen so many misinformed comments on slashdot before, and I've seen a few emacs and kde4 threads in my time.
Ok, then what is your point exactly? That people should be prevented from leering over anyone clothed under the age of 25? Or just that we allow it to happen and "consider it bad"?
As an older guy, even those under 25 are young to me... not because of an age gap of a decade, but because their minds are still developing... not to mention the lack of experience that comes with being so young. Things were different when the average life expectancy was 40, but we don't live in those times anymore. Women aren't promised to men at age 13 and immediately expected to have children. That kind behavior is considered more barbaric than the medical technology of the time.
I agree, if only because looking at sexually mature women under the age of 25 is pretty much the same as having sexual intercourse or marrying them. Pretty much.
Picture it being your daughter, and some creepy motherfucker eyeing her up. Put yourself in someone else's shoes.
Males looking at my fully clothed daughters? The horror! This is why all my daughters must wear burkas in public until the day they reach 18. Once they're 18 though, it's fair game for pervs to check them out.
If you get your kicks from looking at sexually and emotionally immature girls then you need to see someone.
I agree. These teenage girls with big firm perky breasts are obviously sexually immature and it is "creepy" for any human male to look at them in a sexual context.
How dare these creeps sexualize teenage girls with big firm full breasts? That sort of sexual attraction is completely unnatural and twisted. I'm glad reddit has taken the step of eliminating these pictures of fully clothed busty girls.
Next challenge: prevent men from looking at busty teenage jailbait out in public. These perverts must be stopped.
I think you mean that Amazon's ebooks only work on Amazon *software*. You can get a Kindle reader for most any major platform.
Very true. Should have said amazon hardware/software. It has the same result: amazon is the gatekeeper, and the files are accessible under their conditions.
At least with the music industry's drm'ed files they could be played on a multitude of devices from various companies. Amazon's ebooks only work on amazon hardware.
I also get the impression that pirating ebooks is far less common with Joe and Susie Consumer than with what occurred in the napster days with mp3s. I doubt ebook filesharing has much affect on the publisher's bottom line, since most of those who do it probably wouldn't have purchased the book anyway (and certainly not new in hardcover).
Regarding censorship bypassing, some have stated it is hypocritical for us to claim we do not allow illegal activity, and then claim our service is used in some countries to bypass censorship illegally. Again we follow UK law, there isn’t a law that prohibits the use of Egyptians gaining access to blocked websites such as Twitter, even if there is one in Egypt though there are certainly laws regarding the hacking of government and corporate systems.
But if the Egyptian government went through the appropriate channels and got a UK court order, presumably HMA would turn over the logs immediately. Besides, there are a number of censorship-related situations where HMA would apparently pass out user information like cookies at a bake sale regardless of whether a boogedy-boogedy scary middle east country is involved or if it is the US/UK... the wikileaks fiasco would be an obvious example.
Why not at least keep the connections logs for only 2 or 3 days? I would imagine that would still enable them to crack down on abuse while avoiding having to comply with most court orders.
The guy was referring to the Plasma libraries, not the Plasma desktop.
Ah ok, my bad. Obviously I'm not a developer (just a finicky hyper-critical desktop linux user!), but doesn't having buggy crash-ridden software like 4.0 plasma make it difficult to develop and test your own add-ons and related software? If I want to develop desktop widgets but plasma itself was continually crashing and burning, doesn't that slow the process as well?
It very well may not if the libraries are "mature", just wondering.
Your logic is that if you made no effort to find out any information on what you were installing, then someone else intentionally lied to you.
Your logic is that KDE wasn't intentionally trying to change the way software releases were labeled (alpha->beta->release) and used. Which they were. They moved out of the "beta" stage to a release that apparently wasn't actually supposed to be used by users. 4.1 either for that matter. Blaming the users for their lack of research on the topic is absurd.
You claim developers would still develop apps while KDE on the whole was in beta, but that just isn't the case. KDE Planet showed the number of commits and new developers, which exploded after the 4.0 release.
I never said there would the same number of developers working on KDE4 projects at that exact point in time, just that there was still a lot of interest at the beta stages. Exactly what was the massive drawback to waiting a few months until plasma was more mature and usable before release? I think avoiding the entire release debacle would have been far more beneficial in the long run versus being 2-3 months behind in development from where we are now. That's discounting that there may have been developers and users discouraged by the alpha quality of the 4.0 release and turned away from the project.
If kdelibs, phonon, plasma, etc. hadn't matured to a 4.0 release state
Plasma was no where near a release state with 4.0. It wasn't even beta quality.
Would you have preferred that they didn't release?
I would have preferred they had waited a few more months and had plasma be *somewhat* ready for day to day use before they crept out of beta stage. There was tons of interest in KDE4 even at beta stages, and there was nothing stopping developers from getting a head start at that point. Six more months of baking in the oven in order to avoid tarnishing KDE's good name would have been well worth it in my opinion.
It was a mistake to rush it so, and frankly the premature release wasn't even as discouraging as the fact that lead developers like A. Seigo are still too stubborn to admit it was poor judgment. That doesn't bode well for design and release planning for the future of the project.
Yet every single tech blogger says they were lied to in this massive fiasco that KDE 4 would be perfect on day one. Where exactly was that statement? I think the problem is that a few distros were pushing KDE 4 as a default desktop before it was fully ready for primetime, and Kubuntu in particular was shipping really broken packages.
Most notably in the 4.0 release announcement. It didn't state it was perfect, but it sure didn't give the impression that it wasn't ready for normal users. see: http://www.kde.org/announcements/4.0
In addition, the KDE team had been pimping the 4.0 release for months prior to the actual release date. When the betas were released in a horrifically unfinished state, users were told to keep calm because they were just betas, not the final release. When the final release was released, users were told to keep calm because it was never meant to actually be used by users. When 4.1 was released, users were told to keep calm.... and so on.
I think what actually happened is that the KDE team was very rushed at the end as they neared the release date, and decided to just dump out what they had rather than delay. After all, the google kde4 release party had already been planned and scheduled.
So Aaron is justified in saying 4.0 wasn't a disaster from a developer standpoint.
No, he isn't. After taking a step back and looking at the whole debacle of 4.0, it's simply stubborn to claim that it wasn't a total disaster, or at the very least misguided.
I thought Aaron Seigo was still insisting that there was no mistake with the release of 4.0, but that everything went perfectly according to plan?
When should these actually be considered stable by the average person... 5.6, 5.7? Also, are these 5.x releases also going to be termed SCs or Software Compendiums or whatever they are called, or has the wondrous KDE marketing team thought of a new catchy term? My suggestion: Kickass Release of Awesome Power, or KRAP. "Dude, I just dumped KDE KRAP 5.2 on my system! It doesn't have a functioning taskbar yet, but the rotating twitter desktop widget is sweet!"
I just love how everything "for the children" or anything relating to child pornography (which is absolutely despicable) can strip our rights away without notice. It's absolute bullshit.
It's interesting how so many boogedy-boogedy scare tactics have been used about child pornography over the years that even the mere mention of the term causes most people to use a qualifier like "which is absolutely despicable". Do you do the same when you mention murder (which is absolutely despicable) in a sentence? Or even actual child rape (which is absolutely despicable)?
Hilarious. Anyway, the point the OP and then myself made are that ebook prices, even in this profit-driven world, are a ripoff. That's it.
One might ask why there was even a remake of True Grit. Must be just a clear rip off.
I'm sure if they came out with a new vhs version of the original True Grit that was three times as expensive as the blueray, you'd defend that as a "temporal imbalance" due to marketing as well. God forbid anyone criticize a ridiculous price structure.
So they are essentially just driving up ebook prices to try and make a money grab. Otherwise the movie tie-in paperback would be just as expensive. Seems like a pretty clear rip-off.
Note the paperback is $7.93. No one has to pay for Charles Portis' book signings or speaking engangements. I fail to see why ebook prices should be above paper book prices any time they might be popular. Should that be the selling point of ebook readers? That you can buy older books which aren't popular for slightly cheaper than their paper versions?
I had to keep checking the top banner to make sure I wasn't on freerepublic after reading the comments on here. So much utter nonsense about death panels and across-state-lines-magic. I don't think I've seen so many misinformed comments on slashdot before, and I've seen a few emacs and kde4 threads in my time.
Ok, then what is your point exactly? That people should be prevented from leering over anyone clothed under the age of 25? Or just that we allow it to happen and "consider it bad"?
I'm still trying to figure out exactly when looking at pictures of clothed people became equivalent to having sex with them.
As an older guy, even those under 25 are young to me... not because of an age gap of a decade, but because their minds are still developing... not to mention the lack of experience that comes with being so young. Things were different when the average life expectancy was 40, but we don't live in those times anymore. Women aren't promised to men at age 13 and immediately expected to have children. That kind behavior is considered more barbaric than the medical technology of the time.
I agree, if only because looking at sexually mature women under the age of 25 is pretty much the same as having sexual intercourse or marrying them. Pretty much.
Picture it being your daughter, and some creepy motherfucker eyeing her up. Put yourself in someone else's shoes.
Males looking at my fully clothed daughters? The horror! This is why all my daughters must wear burkas in public until the day they reach 18. Once they're 18 though, it's fair game for pervs to check them out.
If you get your kicks from looking at sexually and emotionally immature girls then you need to see someone.
I agree. These teenage girls with big firm perky breasts are obviously sexually immature and it is "creepy" for any human male to look at them in a sexual context.
How dare these creeps sexualize teenage girls with big firm full breasts? That sort of sexual attraction is completely unnatural and twisted. I'm glad reddit has taken the step of eliminating these pictures of fully clothed busty girls.
Next challenge: prevent men from looking at busty teenage jailbait out in public. These perverts must be stopped.
In fact I believe Kindle ebooks are the MOST cross platform ebooks out there as their reader app is on every single platform.
The key word here being their reader app.
It's a meaningless distinction. Amazon retains control over how their ebooks are used/consumed, regardless of what platform they are on.
I think you mean that Amazon's ebooks only work on Amazon *software*. You can get a Kindle reader for most any major platform.
Very true. Should have said amazon hardware/software. It has the same result: amazon is the gatekeeper, and the files are accessible under their conditions.
Especially now with amazon getting into the publishing business: http://www.nytimes.com/2011/10/17/technology/amazon-rewrites-the-rules-of-book-publishing.html?pagewanted=all
At least with the music industry's drm'ed files they could be played on a multitude of devices from various companies. Amazon's ebooks only work on amazon hardware.
I also get the impression that pirating ebooks is far less common with Joe and Susie Consumer than with what occurred in the napster days with mp3s. I doubt ebook filesharing has much affect on the publisher's bottom line, since most of those who do it probably wouldn't have purchased the book anyway (and certainly not new in hardcover).
But if the Egyptian government went through the appropriate channels and got a UK court order, presumably HMA would turn over the logs immediately. Besides, there are a number of censorship-related situations where HMA would apparently pass out user information like cookies at a bake sale regardless of whether a boogedy-boogedy scary middle east country is involved or if it is the US/UK... the wikileaks fiasco would be an obvious example.
Why not at least keep the connections logs for only 2 or 3 days? I would imagine that would still enable them to crack down on abuse while avoiding having to comply with most court orders.
Never happen! Linus wouldn't be seen dead in a bus!
Ha!
The guy was referring to the Plasma libraries, not the Plasma desktop.
Ah ok, my bad. Obviously I'm not a developer (just a finicky hyper-critical desktop linux user!), but doesn't having buggy crash-ridden software like 4.0 plasma make it difficult to develop and test your own add-ons and related software? If I want to develop desktop widgets but plasma itself was continually crashing and burning, doesn't that slow the process as well?
It very well may not if the libraries are "mature", just wondering.
Your logic is that if you made no effort to find out any information on what you were installing, then someone else intentionally lied to you.
Your logic is that KDE wasn't intentionally trying to change the way software releases were labeled (alpha->beta->release) and used. Which they were. They moved out of the "beta" stage to a release that apparently wasn't actually supposed to be used by users. 4.1 either for that matter. Blaming the users for their lack of research on the topic is absurd.
You claim developers would still develop apps while KDE on the whole was in beta, but that just isn't the case. KDE Planet showed the number of commits and new developers, which exploded after the 4.0 release.
I never said there would the same number of developers working on KDE4 projects at that exact point in time, just that there was still a lot of interest at the beta stages. Exactly what was the massive drawback to waiting a few months until plasma was more mature and usable before release? I think avoiding the entire release debacle would have been far more beneficial in the long run versus being 2-3 months behind in development from where we are now. That's discounting that there may have been developers and users discouraged by the alpha quality of the 4.0 release and turned away from the project.
If kdelibs, phonon, plasma, etc. hadn't matured to a 4.0 release state
Plasma was no where near a release state with 4.0. It wasn't even beta quality.
Would you have preferred that they didn't release?
I would have preferred they had waited a few more months and had plasma be *somewhat* ready for day to day use before they crept out of beta stage. There was tons of interest in KDE4 even at beta stages, and there was nothing stopping developers from getting a head start at that point. Six more months of baking in the oven in order to avoid tarnishing KDE's good name would have been well worth it in my opinion.
It was a mistake to rush it so, and frankly the premature release wasn't even as discouraging as the fact that lead developers like A. Seigo are still too stubborn to admit it was poor judgment. That doesn't bode well for design and release planning for the future of the project.
Yet every single tech blogger says they were lied to in this massive fiasco that KDE 4 would be perfect on day one. Where exactly was that statement? I think the problem is that a few distros were pushing KDE 4 as a default desktop before it was fully ready for primetime, and Kubuntu in particular was shipping really broken packages.
Most notably in the 4.0 release announcement. It didn't state it was perfect, but it sure didn't give the impression that it wasn't ready for normal users. see: http://www.kde.org/announcements/4.0
In addition, the KDE team had been pimping the 4.0 release for months prior to the actual release date. When the betas were released in a horrifically unfinished state, users were told to keep calm because they were just betas, not the final release. When the final release was released, users were told to keep calm because it was never meant to actually be used by users. When 4.1 was released, users were told to keep calm.... and so on.
I think what actually happened is that the KDE team was very rushed at the end as they neared the release date, and decided to just dump out what they had rather than delay. After all, the google kde4 release party had already been planned and scheduled.
So Aaron is justified in saying 4.0 wasn't a disaster from a developer standpoint.
No, he isn't. After taking a step back and looking at the whole debacle of 4.0, it's simply stubborn to claim that it wasn't a total disaster, or at the very least misguided.
I thought Aaron Seigo was still insisting that there was no mistake with the release of 4.0, but that everything went perfectly according to plan?
When should these actually be considered stable by the average person... 5.6, 5.7? Also, are these 5.x releases also going to be termed SCs or Software Compendiums or whatever they are called, or has the wondrous KDE marketing team thought of a new catchy term? My suggestion: Kickass Release of Awesome Power, or KRAP. "Dude, I just dumped KDE KRAP 5.2 on my system! It doesn't have a functioning taskbar yet, but the rotating twitter desktop widget is sweet!"
I just love how everything "for the children" or anything relating to child pornography (which is absolutely despicable) can strip our rights away without notice. It's absolute bullshit.
It's interesting how so many boogedy-boogedy scare tactics have been used about child pornography over the years that even the mere mention of the term causes most people to use a qualifier like "which is absolutely despicable". Do you do the same when you mention murder (which is absolutely despicable) in a sentence? Or even actual child rape (which is absolutely despicable)?
Probably not.
You sound Australian.
Your internet sucks. Stop trying to drag the rest of the world down with you.
It's probably due to the over-saturated coverage on slashdot, but I feel like FF4 has almost been released for the past year now.
One might ask why there was even a remake of True Grit. Must be just a clear rip off.
I'm sure if they came out with a new vhs version of the original True Grit that was three times as expensive as the blueray, you'd defend that as a "temporal imbalance" due to marketing as well. God forbid anyone criticize a ridiculous price structure.
So they are essentially just driving up ebook prices to try and make a money grab. Otherwise the movie tie-in paperback would be just as expensive. Seems like a pretty clear rip-off.
It doesn't have to be new AND a best seller. Just one or the other is enough apparently.
Behold a $12.99 ebook of a novel written in 1968: http://search.barnesandnoble.com/True-Grit/Charles-Portis/e/9781590206508/?itm=4&USRI=true+grit
Note the paperback is $7.93. No one has to pay for Charles Portis' book signings or speaking engangements. I fail to see why ebook prices should be above paper book prices any time they might be popular. Should that be the selling point of ebook readers? That you can buy older books which aren't popular for slightly cheaper than their paper versions?
Take any popular book such as Steven Kings "Under the Dome" and compare prices. Ebook 10, Paperback 12, Hardcover 20).
Check out a current bestseller, "Fall of Giants" by Ken Follet. It's more expensive as an ebook than in hardcover!