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.
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.
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.
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.
The hardest part of climbing the ladder of success is getting through the crowd at the bottom.
