Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
False, bloat IS a problem.
I do video processing, KDE 3.5 worked fine (90% under load, two streams doing real-time processing). KDE 4 is unable to do a single stream without losing frames.
Why do I have to buy a more powerful machine to run KDE 4 and do the sane task I am alraedy doing in KDE 3.5?. That's BLOAT
Insane. And it looks like the KDE devs are not even considering making the whole Akonadi and associated daemons mess optional. What happened to good old Kmail?
I just hope someone in the KDE project hears users and backtrack to KDE 3.5.
Just port-it (and desktop applications) to QT. 4 and star anew KDE 3.6.
Many people stays with KDE 3.5, they/we deserve an alternative; otherwise GNOME people will get a lot of new users, and KDE (and maybe even worse, QT) will fade into oblivion as of 'what once was a great DE'.
msgs modded at 5 = 11: 10 are blatantly pro-Google, the other one = 5 Funny
The moderation system is geing vandalized by Google fan boys.
The best technique I've learned is to first write out in English a comment describing what you are about to write in code, then write the code after the comment. If you can't explain what you are going to do in English to begin with, you probably aren't ready to write the code.
I fully agree with the basis of your position. After more than 30 years programming, the way I like to comment my code, is attaching a comment for every instruction. The intention is to explain in plain words what code is doing at every step, and larger and broader ideas on the heads of functions and/or definitions/classes.
The result is verbose of course, but it can be read linearly, and the underlying algorithm is fully explained. The reader have a plain explanation of the why's and the how's of the code.
The sooner we start using AGPL for every piece of FOSS code, the better. IMO it's the only way to avoid FOSS being marginalized by big companies like MS or Google.
USA has a monopoly on IT (MS has the PC section, Google the Internet search market), and those companies are both killing FOSS. MS fights openly (the viral factor anyone?), while Google is fagoziting FOSS, (Android vs Linux kernel), (Chrome vs Safari).
He's been promoting MS interests (eee) with-in the FOSS movement for too many years. The only open question IMO, is how long it will take to the GNOME people to get rid of his 'works'.
you are afraid of 'the cloud'
So, if plain old 'server' is being called 'cloud' Let me get it scathologically: The 'cloud' is full of s***, you better beware of the rain
Google fanboys lemma: 'In Gog we trust'
Why is it so odd to just be generous? Why must generosity have some hidden motive? Can't a person (or a company) just be nice once in a while?
If this were Microsoft announcing a free public DNS service, sure, I'd be wary, but Google hasn't given me reason to mistrust them.
How much they pay you, to say such a naive and blatant Google apology?
I have to say: Thanks, but NO thanks.
Monoculture is bad. Google is trying to bypass/replace internet and open source. Free/open source coders should be start using Affero GPLv3 license in every piece of software (starting by gcc, and the linux kernel) to stop this madness.
SoC = Marketing.
Plain and simple, a cheap marketing strategy. Wake me up when some project in SoC targets any sensible Google technology (search/ocr/translation/gis/etc/etc).
I am sorry, but I have to say it.
Slashdot moderation system is being vandalized by Google fanboys. The same happened some years ago in other public forums, we called them astroturfers.
Just correlate moderation points of pro-Google posts versus anti-Google ones.