Please create an account to participate in the Slashdot moderation system


Forgot your password?

Comment Re:Closed Ecosystem (Score 1) 54 54

I can update a proper linux system. apt-get update (etc etc) and I'm good. it could be a 5 yr old linux install, 10 yr even more. it will still get security and major bugfixes.

android? yeah, right. my nexus one (go ahead, laugh at the old guy with the ancient phone) has not had an update for over 3 years now; probably more than that. 2.x distro from cyan and even they stopped doing updates. I have no time in my schedule to learn android internals well enough to do this myself (I could do it for linux, but I have no desire to waste time on phone crap, too many other things to get done). and so, I am running quite old software on a mobile computer and unless I pay for new hardware (my old hw works fine, still) I can't get updates.

this is the main reason why I hate google so much. they totally messed up on the whole android build/deploy/update system. its not linux, its not separatable (gfx and kernel and ip stack all are comingled, like a college-hire might design, sigh) and you can't update just the parts you need. its a whole update or nothing at all. HOW UTTERLY STUPID.

I wish I could get to love apple gear. then again, they EOL their old products, too, and so I'd have to keep rebuying hardware just like android guys are forced to do.

I may just go back to dumb phones again. this is ridiculous. a mobile computer with wireless access, a lot of my personal info on it and yet no update mechanism at all. essentially its abandonware. hundreds of dollars and I have a device that won't ever get updated even though there's not a single good reason for that.

what I can't figure out is: was google stupid or smart when they planned this? I tend to think they were both; stupid due to having too many kids onboard who don't understand the longevity of embedded systems in the real world; and smart since they force people to keep re-re-rebuying things and that must make their hardware partners very happy. they also can ignore older hardware and save time on multiple forks and build trees. but it was all the wrong design for END USERS. we are the ones who get screwed by this.

I cannot ever forgive google. they could have kept linux clean on the phone and allowed users to update ip-stack, kernel, etc. but they put a lot of effort into NOT allowing this and we all pay for it with security problems; and ones that we won't ever be able to fix, either, unless we do the work ourselves (which is not acceptable for an embedded system).

Comment Not practical (Score 1) 302 302

It's not practical any more than everyone learning to be lawyers or plumbers or electricians. Get experience and master your art rather than try to be a jack of all trades. Newbie programmers usually do poor work for a while (or are slow), just like newbie plumbers.

Comment Re:funny I should see this right now (Score 1) 113 113

mongodb? Use something that's been tried and true for at least 10 years. Go with MySql or PostGresql and screw the noSql toys until they mature and have decent docs.

Let pioneers take the arrows, the rest of us stay in proverbial Boston, which has infrastructure and seasoned specialists, and get shit done. And we have nice lawns to kick fanboys off of.

Comment Re:Here's the list (Score 1) 113 113

The problem with most software isn't that it can't be modelling and rely on basic physical principles, it's that many projects fail to take specs and testing seriously

Most requesters (users) don't really know what they want UNTIL they actually see something concrete, and then realize it didn't fit what they had in mind. We don't need engineering, we need mind-readers. If users had enough time to sit and be thoroughly interviewed about needs and preferences, they wouldn't need automation to begin with.

And further, how to make software maintainable in the longer run is highly disputed largely because it depends on "wetware" and unknowns, such as developer perception of code, and unknowable future domain changes.

It's more akin to writing technical documentation than to building a bridge: how do you write documentation that's clear to the audience, but flexible enough that it doesn't have to be largely reworked for every change.

There is no magic modularity formula: domain issues inherently intertwine (or can intertwine in the future even if not at original launch.) You can't hide intertwining, you have to find a way to manage it well.

Comment Humans (Score 1) 113 113

Software development seems to be riddled with arrogant know nothings who think they can cut corners or reinvent the wheel...

That's a problem with human nature, not just devs. We are not Vulcans. Humans are impatient, egotistical, fixate on the wrong factors, and often just plain random; and most don't know it or care.

I know some well-educated people who are complete idiots outside of their narrow specialty. I'm probably an idiot also in ways I don't even realize (please don't educate me in replies). My head-model of the world is perfectly logical and consistent to me, but it's probably highly lossy against the real world.

Gee, it's almost as if we are merely upright apes who happen to be able to talk and write. (I would have said "hairless", but I'm hairier than the orangutans I see in the zoo.) They fling poo, we fling nukes.

Comment Re:Jury Nullification (Score 5, Informative) 533 533

and in most of the US, its borderline illegal to even MENTION JN in court. judges will kick you out, lock you up, threaten you, try to scare you. voire dire does all it can to try to reject jurors that even KNOW what JN is. and if you tell them during VD that you don't know what JN is and then later, they find out you do, you are in contempt.

its all neatly stacked up so that your CONSTITUTIONAL RIGHTS are not vocalized or listed or communicated to you.

"nice liberty you got there; would be a shame if something were to happen to it"

"There is such a fine line between genius and stupidity." - David St. Hubbins, "Spinal Tap"