The problem is the status quo. People got used to have access to something (and I'm sure some have a legitimate reason for it), so it is conisdered bad form to remove said feature. That's the way I see it, at least.
For a start, most (if not all) ICS phones guarantee some kind of spec pre-requisite, (512mb of ram, non-crappy cpu and gup, internal memory space) that I suppose will help delivering a good experience.
And second, and most importantly, every version of Android adds new features and ways to access them, who are you to say that chrome doesn't need them? If it turns out it doesn't, I'm quite sure an APK will turn out somewhere.
And you forget that google doesn't profit from android directly. There were no licencing fees, or even need by google to push ICS anywhere. Google gains nothing by limiting chrome to ICS...... Unlike Apple that limited Siri to the iPhone 4S simply because they wanted to sell more phones. Siri's heavy lifting is not done on the phone and the old iPhone 4 was more than capable of playing the part. Actually, if you look at the iPhone 4S, 99% of the people buying it had no real need for it and I doubt that without Siri and all the marketing surrounding it Apple would have sold half the phones they did.
No, it means that making the whole system run slowly is extremely hard because of the way android works.
Even the fact that each application seems to be limited to 16MB of heap memory (on some phones, not sure if in all of them, but quite sure they all implement a limit) makes that task of making the whole system need a reboot extremely hard.
The "lack" of quality of the apps on the Android market (actually, a myth, since more and more apps exist on both platforms - so you might have the shitty apps, but the good ones are still there) has nothing to do with memory leaks. Badly coded iOS apps will leak even worse than Android apps and I'm quite sure apple doesn't test memory leaks (if you were a programmer you'd know that is actually an extremely hard thing to debug, much less evaluate).
And yes, I am a programmer, I did study computer science, I own an Android Market account with apps. But please explain to me what does that have to do with anything (at all).
Oh, that would be true, but according to my research each application has a limited amount of heap memory they can use (on a G1 it was 16MB). So even if you're a service, it's still not that serious.
Especially not as serious as a possible objective-c memory leak (since the author seems to be implying that memory leaks happen very frequently on android unlike iOS). Quite sure apple doesn't test your app for memory leaks.
Quality control will not stop memory leaking apps in no way shape or form, especially because the worse coded apps, from what I see, are actually the ones that come with your phone (ie: Sense, touchwiz, etc).
And please tell me why is facebook using static variables for anything.:x
That "memory leak" is someone adding an image to a cache and never removing it. It might slow down your application when the cache gets too big, but it should still get unloaded when the program exits (and ends up killed because of Android's architecture).
After my answer I actually looked for it and I found a way to do memory leaks in java, but I still think that wouldn't happen on android because of the constant load-unload scheme it has going on.
Please do tell how... Not only there is garbage collection, I was under the impression you couldn't even access the memory directly.
Furthermore, android loads/unloads apps to the memory all the time. If an application is consuming too much memory on the background and you need it, it'll be killed.
On the other hand, you should look into avoiding Sense, Touchwiz or anything like that. Those are the most likely culprits.
Never said it was, but because of youtube flash got installed pretty much everywhere.
You said they never took off, but have you ever seen, for example, a blockbuster movie website made in the last 10 years? It's all flash. Same with big companies like mcdonnalds or coca cola.
And you mention AJAX, do you know what it is? Javascript, yes, but AJAX was not a game changer at all.
Let me put it another way (And picking up on the flash example). You used to need flash to insert videos into web pages, but now there is a "video" tag. My gripe is not with RDF or OWL themselves (even though the fact that you can't compute the entirety of OWL kind of strikes me as a bit stupid - why go all out to then say "but you can only use # = 1"), but with SPARQL. They could have just added SPARQL like features to SQL and you'd only use it if you wanted... SQL uses tables, but isn't a table a matrix and aren't those one of the ways you can represent a graph?
Right now you need a specific setup to run things using semantic web, most of which I'd say are highly "unscalable", while requiring hacks to get simple functionality, for example, if you want to do a case insensitive queries, you need to either normalize your whole database to use lower/uppercase or use regular expressions to filter results (which, by my testing, makes it extremely slow).
Also, convincing your boss that you need to revolutionize their IT department for a non-specific gain is a lot harder than just using what you already have.
Flash had been around for over 5 years until it became the unofficial standard for rich internet applications (right around the time youtube showed up).
The idea behind the semantic web (context > statistics) is not a bad one, the biggest problem I see though is that everyone is trying to implement it using entirely new standards and with an utopic ideal. If they worked on how to get existing technologies to take advantage of all those ideas (for ex: altering SQL to accept the returning of relations instead of creating SPARQL) instead of pushing forward Turtle, RDF, OWL, SWIRL, and a whole bunch of stuff that only die hard techs will look at, maybe it'd go somewhere.
You can make horrible UI's no matter what the web version used. Their tech guys are trying moving forward, while the designers aren't. What's your point, really?
It actually mentions the use of semantic web technologies, so I highly doubt that was what they meant.
On the other hand, why does using RDF and semantic web makes journalists spend "more time creating content"? I'd say that has nothing to do with semantic web but with the publishing tools they use.
There was a nuclear disaster right next to them, so obviously they'll die, especially because the uranium won't settle instantly. But that kind of news disproves absolutely nothing about what he said. The long term effects won't be know (obviously) for a long long time.
Slashdot Mirror
Do you really think your GPS is accurate enough to detect a swerve? (:
Don't worry, I'm quite sure it isn't and that they won't be judging you by that kind of maneuver.
The GPS knows the speed and the place, they don't need the device itself to fire an alarm - if they receive data they can just post-process it.
On the other hand, I'm quite sure they will only want to know if you were speeding when you crashed.
Well, when you "people" say every single piece is abused by "the man", you're bound to be right someday.
In other news, I'm quite sure that if I turn off my "tom tom pro 3100" and use my Phone or any other gizmo, there will be no tracking.
Well, Siri works on the iPhone 4, you only need a 4S id to be granted access to the servers, so you remember it wrong (:
The problem here is not really the access, but the access in real time, according to the article.
If you request a communication you will still be able to get it.
The problem is the status quo. People got used to have access to something (and I'm sure some have a legitimate reason for it), so it is conisdered bad form to remove said feature. That's the way I see it, at least.
For a start, most (if not all) ICS phones guarantee some kind of spec pre-requisite, (512mb of ram, non-crappy cpu and gup, internal memory space) that I suppose will help delivering a good experience.
And second, and most importantly, every version of Android adds new features and ways to access them, who are you to say that chrome doesn't need them? If it turns out it doesn't, I'm quite sure an APK will turn out somewhere.
And you forget that google doesn't profit from android directly. There were no licencing fees, or even need by google to push ICS anywhere. Google gains nothing by limiting chrome to ICS... ... Unlike Apple that limited Siri to the iPhone 4S simply because they wanted to sell more phones. Siri's heavy lifting is not done on the phone and the old iPhone 4 was more than capable of playing the part. Actually, if you look at the iPhone 4S, 99% of the people buying it had no real need for it and I doubt that without Siri and all the marketing surrounding it Apple would have sold half the phones they did.
I honestly don't understand this kind of argument. Just because there is racism, what does it have to do with the argument at hand?
Nothing whatsoever.
No, it means that making the whole system run slowly is extremely hard because of the way android works.
Even the fact that each application seems to be limited to 16MB of heap memory (on some phones, not sure if in all of them, but quite sure they all implement a limit) makes that task of making the whole system need a reboot extremely hard.
The "lack" of quality of the apps on the Android market (actually, a myth, since more and more apps exist on both platforms - so you might have the shitty apps, but the good ones are still there) has nothing to do with memory leaks. Badly coded iOS apps will leak even worse than Android apps and I'm quite sure apple doesn't test memory leaks (if you were a programmer you'd know that is actually an extremely hard thing to debug, much less evaluate).
And yes, I am a programmer, I did study computer science, I own an Android Market account with apps. But please explain to me what does that have to do with anything (at all).
Oh, that would be true, but according to my research each application has a limited amount of heap memory they can use (on a G1 it was 16MB). So even if you're a service, it's still not that serious.
Especially not as serious as a possible objective-c memory leak (since the author seems to be implying that memory leaks happen very frequently on android unlike iOS). Quite sure apple doesn't test your app for memory leaks.
Quality control will not stop memory leaking apps in no way shape or form, especially because the worse coded apps, from what I see, are actually the ones that come with your phone (ie: Sense, touchwiz, etc).
And please tell me why is facebook using static variables for anything. :x
Actually, just read a bit more and my point stands (:
Does the scope of a static variable goes beyond the life cycle of an application?
disregard this answer, just noticed it was static. Not sure how android handles static variables, so nevermind.
That "memory leak" is someone adding an image to a cache and never removing it. It might slow down your application when the cache gets too big, but it should still get unloaded when the program exits (and ends up killed because of Android's architecture).
After my answer I actually looked for it and I found a way to do memory leaks in java, but I still think that wouldn't happen on android because of the constant load-unload scheme it has going on.
Memory leaks in java?
Please do tell how... Not only there is garbage collection, I was under the impression you couldn't even access the memory directly.
Furthermore, android loads/unloads apps to the memory all the time. If an application is consuming too much memory on the background and you need it, it'll be killed.
On the other hand, you should look into avoiding Sense, Touchwiz or anything like that. Those are the most likely culprits.
and on a sidenote, click where it says "major platforms"
http://en.wikipedia.org/wiki/Rich_Internet_application
Never said it was, but because of youtube flash got installed pretty much everywhere.
You said they never took off, but have you ever seen, for example, a blockbuster movie website made in the last 10 years? It's all flash. Same with big companies like mcdonnalds or coca cola.
And you mention AJAX, do you know what it is? Javascript, yes, but AJAX was not a game changer at all.
Let me put it another way (And picking up on the flash example). You used to need flash to insert videos into web pages, but now there is a "video" tag. My gripe is not with RDF or OWL themselves (even though the fact that you can't compute the entirety of OWL kind of strikes me as a bit stupid - why go all out to then say "but you can only use # = 1"), but with SPARQL. They could have just added SPARQL like features to SQL and you'd only use it if you wanted... SQL uses tables, but isn't a table a matrix and aren't those one of the ways you can represent a graph?
Right now you need a specific setup to run things using semantic web, most of which I'd say are highly "unscalable", while requiring hacks to get simple functionality, for example, if you want to do a case insensitive queries, you need to either normalize your whole database to use lower/uppercase or use regular expressions to filter results (which, by my testing, makes it extremely slow).
Also, convincing your boss that you need to revolutionize their IT department for a non-specific gain is a lot harder than just using what you already have.
Well, you're on slashdot, it is expected of you to either know or google it if you don't (:
Flash had been around for over 5 years until it became the unofficial standard for rich internet applications (right around the time youtube showed up).
The idea behind the semantic web (context > statistics) is not a bad one, the biggest problem I see though is that everyone is trying to implement it using entirely new standards and with an utopic ideal. If they worked on how to get existing technologies to take advantage of all those ideas (for ex: altering SQL to accept the returning of relations instead of creating SPARQL) instead of pushing forward Turtle, RDF, OWL, SWIRL, and a whole bunch of stuff that only die hard techs will look at, maybe it'd go somewhere.
You can make horrible UI's no matter what the web version used. Their tech guys are trying moving forward, while the designers aren't. What's your point, really?
It actually mentions the use of semantic web technologies, so I highly doubt that was what they meant.
On the other hand, why does using RDF and semantic web makes journalists spend "more time creating content"? I'd say that has nothing to do with semantic web but with the publishing tools they use.
further reading http://www.cl.cam.ac.uk/~mgk25/ih98-tempest.pdf
There was a nuclear disaster right next to them, so obviously they'll die, especially because the uranium won't settle instantly. But that kind of news disproves absolutely nothing about what he said. The long term effects won't be know (obviously) for a long long time.
http://theaviationist.com/2012/01/20/neuron-roll-out/ the europeans disagree with you