6 ms·
I hate to say it, but this kind of bad analysis is just endemic in the Android modding world. There's no technical leadership at the top (the AOSP people are,
by ajross 14y ago
I hate to say it, but this kind of bad analysis is just endemic in the Android modding world. There's no technical leadership at the top (the AOSP people are, for the most part, silent except occasionally in bug reports like this), so people just throw whatever hack they want onto forums filled with even-less-clueful folks and things go viral.
If you tried this on a "real" Linux project you'd be laughed at. Where's the test showing latency improvement? Hell, there isn't even any identifaction of any code at all that reads from /dev/random (and of course it appears there is none).
It seems a little unfair, but frankly I blame Google for this mess. They refuse to run AOSP as a "project", which leaves the AOSP-derived projects a big soup of developers with no clear meritocracy. Some bits (Cyanogenmod) are really quite good. But the stuff on XDA is probably 60% useless junk.
- angryasian 14y agoA google engineer already came out and said this does nothing for ics and up.
- ajross 14y agoNot my point at all. If AOSP worked like, say, the kernel (or KDE, or gcc, or any other big project) this "fix" would have been submitted to and vetted by a functioning group of experts who would have immediately said "Dude, no." and it would have died silently. No such thing exists with AOSP. Google does their development internally. External patch submissions (if acknowledged at all) end up appearing in a usable release only months after the fact. So the poor excited hacker here (who, let's be clear, really didn't do anything wrong other than, well, being wrong) had nowhere to post a fix somewhere where it would be useful to people. So s/he threw it up on XDA with all the other junk, and we're now having this discussion.
- jrockway 14y agoDo "real" open source projects issue releases after every patch? I've recently submitted a small patch to Android and it showed up in the repository immediately. While there is some development done in secret, not everything is. You can git blame and email the developers and they will probably talk to you. (My experience is perhaps different because I have a @google.com email address, but the developers are actually nice people that do value open source, as far as I can tell.)
- DanBC 14y ago> this "fix" would have been submitted to and vetted by a functioning group of experts who would have immediately said "Dude, no." and it would have died silently. Maybe. Or maybe it would have been like all those "Turn off your Windows paging file" for XP and Vista websites. Or all those "RAM Booster" softwares. Users get sucked into a bunch of hokum, and having a clueful person tell them it's nonsense often does nothing to stop the nonsense.
- nitrogen 14y agoExcept there is merit to running without swap in some circumstances, and I wouldn't be surprised if projects like compcache bear some resemblance to some "compress your RAM" product out there.
- Dylan16807 14y agoI've also had real issues with windows using far too much ram for disk cache and swapping out in-use program data; a 'ram-cleaner' will at least help in this situation. My eventual duct tape was running cacheset once a minute to cut cache down to .5GB. Thankfully once I upgraded to windows 7 it stopped being a problem.
- DanBC 14y agoI accept that on HN most people know what swap is, and when it's okay (or beneficial) to turn it off, and how to do it, and who would notice the difference, and how big to set it if you do have it. But most people hearing this "Windows performance enhancing tweak" are not that knowledgable about their OS. Compare the MS article here (http://support.microsoft.com/kb/2160852 http://support.microsoft.com/kb/2160852) with, for example, this article with minimal details (http://www.howtogeek.com/howto/windows-vista/understanding-windows-vista-paging-file-size/ http://www.howtogeek.com/howto/windows-vista/understanding-w...).
- nitrogen 14y agoMaybe I'm more forgiving of the cargo cult tweakers than I should be, because that was one of the steps on the path to where I am now. Maybe my total understanding of virtual memory and other concepts would be more theoretically pure if I'd just ignored computers until learning the theory in school, but I think that, maybe, my hard-won experience makes me a more "empathetic" developer.
- nailer 14y agoAndroid master HEAD is always proprietary and always has been. Android master HEAD also fails Andy Rubin's own definition of open: https://twitter.com/Arubin/status/27808662429 https://twitter.com/Arubin/status/27808662429, since that website is out of date. Only a few people inside Google are allowed to see it. Their colleagues aren't allowed to sit in the same cafeteria as the Android developers, much less see the source code, until it's already done. If it was actually Open Source, XDA developers would actually have real, original development, and features like lock screen widgets, officially added in JB 4.2 in 2012, would have been completed by the community in 2009. Only old, already released versions of Android are Open Source. This makes it useless for real developers - who would want to fix something that might already be a non-issue as of six months ago? As a result, the only 'community development' in Android is people who know how to tweak settings files and make ROMs with particular apps and settings built in.
- ajross 14y agoAll of this is true. But it's not the choice between two extremes. Google doesn't have to wall off community development in order to develop new features in secret. There's no reason they couldn't curate an AOSP project where submissions like this one (although obviously not this particular one!) could be made in a way that was truly useful to the community. It would cost money and time, and maybe they don't have that. But it's something that other FOSS players do, so it's not an impossibility.
- eloisant 14y agoWell, if they work on version n+1 internally and secretly it's highly unlikely a patch for version n will have any value. In order for patches to be relevant, they should be on the HEAD of the project where most developers are working, not the old, released, finished, version.
- ibrahima 14y ago> If it was actually Open Source, XDA developers would actuall have real, original development, and features like lock screen widgets, officially added in JB 4.2 this year, would have been completed by the community in 2009. I agree in general that if AOSP was an actual open source project things would be better but I don't think XDA would be any different. It's been full of end users for years now and most of them are easily fooled by stuff like this. CyanogenMod is developed in the open and they do have quite a few contributors, but it's not terribly ground breaking (although some of their features do get reimplemented in AOSP eventually). The fact is that the Android project is really a gigantic codebase and it takes a lot of time to get started (and even on a really fast machine, 20-40 minutes to build), and a lot of the work CyanogenMod developers do is porting to hardware that's unsupported by AOSP, not feature development.
- krakensden 14y ago> If you tried this on a "real" Linux project you'd be laughed at. Not really- the Ubuntu forums are an identical cesspool. There are just too many users for developers to interact with, so they hide in forums like IRC and mailing lists that drive off most of their non-technical users.