Google had the opportunity to create a truly free device, where developers could create software they wanted, accessing all the services the device provide, and users were free to install it. Without the signing crap, central repository, and restrictions of such sort. After all, people pays and own their own devices, so they should be free to do whatever they want with them.
But no, they decided to mimic Apple.
I really hope Obama will keep up on what he promised during the campaign, and take proper action towards companies the privilege outsourcing their jobs.
Once again, Microsoft invented the... drum roll... wheel!
Fuzzy data injection is used by ages in the security world. By both bad and good guys.
Oh, and the Address Space Layout Randomization thing, Linux had it long before them, so I guess that according to their very same rules, they invested that too.
Oh, absolutely. Ballmer statement was that you spend five hundred bucks for a logo, that isn't quite true.
You get a little bit more than a logo, if you really look into it.
You might not care of spending that extra money to get these features, but you can't say an Apple is built like your typical PC.
Take a MacPro, open it, and compare it with stuff like Dell or Sony or HP.
Is it a little more expensive? Yes. It is worth it? Hell, yeah.
There is no match as far as how clean and robust is the build, compared to other top-brand PCs. Absolute absence of flying around cables, top of the line electronic components, maximum care down to the very little details.
But this is a known thing to everyone that actually opened an Apple and other brand-name PCs.
Ballmer,... God's gift to every person in the world that does not really love Microsoft. Or for people, like myself, that could happily live even w/out them.
He has been able to drag Microsoft, once perceived as technology source with fairly large following, down to the nobody-cared status, as far as all the new technologies being introduced.
One failure after another, with Microsoft not being able to push new technologies even in their own niche (see Vista fiasco for one).
If you like programming (otherwise I got bad news for you), learn all three. With preference to C/C++.
But the fact that you're asking the question, kind of reveal that you've not much passion for CS, and that you'll likely be just another 9-5, into software development just to get a job, average programmer.
In which case I'd rather focus more on Java, and whatever language-of-the-day is now current at Microsoft.
It's managers job to give the right amount of freedom to talented individuals. Individuals with well over the average IQ, with passion for the job, and that are no afraid to spend extra hours on the task. If it were for me, I'd give up ten of the 9-to-5, dumb, lazy a$$es, weasels, that are unfortunately the fabric of most of US companies, for one talented engineer. You wonder and cry because he has extra privileges than you? Meritocracy, comes not only in form of extra salary, my friend.
No, I have the recipe for Nokia. Throw Symbian in the trashcan, since it's $hit from the kernel source, architecture, and external API. Lay off all of the internal, Symbian-backing, dinosaurs. Use Linux as kernel, and QT as UI interface.
Then, only then, Nokia might succeed in gaining some share in the mobile development world.
Yes, I know, there's still the fact that Nokia just hasn't the kool-factor that Apple and Google have.
Android code bad? I guess you're not a Symbian DevKit subscriber, do you?
Have you actually SEEN the Symbian OS core code? Compared to Linux it's a Pile Of $hit, same as compared to WM.
Thanks God is disappearing very fast on the eve of saner OSs and development environments (note the -21% on Q4 2008)
Funny how they go proud of their market share, when they lost 21% of it only in the last year. My bet, in 2009, they'll lose even more. My brokers give Symbian at 10% market share in 2010.
Great outline of the Symbian shortcomings!
Things comes in my mind slowly, because my brain actually tried to delete them ASAP. About their strings. They have these TDes and TDesC that should clearly have been made pure virtual, since you can't have a working instance in the way they're designed. But, they are not.
So someone could be tempted to create a function that accepts an object of type TDes/TDesC, with EPIC fails due to the TDes/TDesC members trying to access an unexisting data member of an unexisting parent class.
All nice things to debug, given the added crapola of their terrible debugging facilities.
Guys, Symbian API is NOT C++. Is a pseudo C++ written by people that were learning C++ along the way. Can you spell TRAPD() and CleanupStack?
And how about their imports by ordinals, whose number change magically and break ABI among minor OS releases?
How about the bare "Install Failed!" coming from an SIS install attempt, with no friggin' clue on the real problem?
How about their development chain? A clusterfsck of PE binaries, glued together with batch files, glued together with Perl scripts.
How about errors coming from the development chain, that gives no absolute clue of what happened (hiding real GCC errors)?
How about build binaries results being scattered God knows where, under a 34 levels deep structure?
How about their documentation? The missing of, that is.
There are way better and friendlier development environments to work with, in the mobile space. Don't waste your time with Symbian, you'll thank me for this suggestion.
I agree. Let's make a poll. Myself, and ALL the developers that had the bad luck to touch Symbian in a way or another, consider it the most developer-hostile environment to work with.
If you think that your job sucks, and the development environment you're currently working with, is bad, try Symbian. You'll look at your current job under an whole another light!
And what about that joke of the Symbian Foundation, whose spokesman attached Google on the basis that Android is not open? While, their "open" idea, is to have you pay $1500 to get a VERY LIMITED source code access, with ability to customize and build your own.
Get rid of any trace of MS in your resume, and you'll have a better chance to land a nice, challenging and rewarding job.
As soon as I dropped the very first years of my experience (I know!! I didn't know back then) from the resume, offers started flowing in. Do it, it works every time!
Slashdot Mirror
Google had the opportunity to create a truly free device, where developers could create software they wanted, accessing all the services the device provide, and users were free to install it. Without the signing crap, central repository, and restrictions of such sort.
After all, people pays and own their own devices, so they should be free to do whatever they want with them.
But no, they decided to mimic Apple.
I really hope Obama will keep up on what he promised during the campaign, and take proper action towards companies the privilege outsourcing their jobs.
One question. WHY?!?
Sometime, environmentalists push it a little bit too far, and become Environmental Talibans.
Yes it is indeed. The MS funny-boy above must have missed the obvious point. But that isn't in any way a surprise, is it?
Do the tinfoil hats come with the enrolling package in the Microsoft funny-boys club, or you've to build them by yourself?
Once again, Microsoft invented the ... drum roll ... wheel!
Fuzzy data injection is used by ages in the security world. By both bad and good guys.
Oh, and the Address Space Layout Randomization thing, Linux had it long before them, so I guess that according to their very same rules, they invested that too.
Oh, absolutely. Ballmer statement was that you spend five hundred bucks for a logo, that isn't quite true.
You get a little bit more than a logo, if you really look into it.
You might not care of spending that extra money to get these features, but you can't say an Apple is built like your typical PC.
IBM?!? That's a joke, right?
http://www.architosh.com/features/2006/reviews/macpro/images/macpro_inside-lg.jpg
Take a MacPro, open it, and compare it with stuff like Dell or Sony or HP. Is it a little more expensive? Yes. It is worth it? Hell, yeah. ... God's gift to every person in the world that does not really love Microsoft. Or for people, like myself, that could happily live even w/out them.
There is no match as far as how clean and robust is the build, compared to other top-brand PCs. Absolute absence of flying around cables, top of the line electronic components, maximum care down to the very little details.
But this is a known thing to everyone that actually opened an Apple and other brand-name PCs.
Ballmer,
He has been able to drag Microsoft, once perceived as technology source with fairly large following, down to the nobody-cared status, as far as all the new technologies being introduced.
One failure after another, with Microsoft not being able to push new technologies even in their own niche (see Vista fiasco for one).
If you like programming (otherwise I got bad news for you), learn all three. With preference to C/C++. But the fact that you're asking the question, kind of reveal that you've not much passion for CS, and that you'll likely be just another 9-5, into software development just to get a job, average programmer.
In which case I'd rather focus more on Java, and whatever language-of-the-day is now current at Microsoft.
We should set a new rule. When a company asks for .gov money to be bailed out, the top 5 layers of the company should be fired. No exceptions.
This is just beyond belief.
It's managers job to give the right amount of freedom to talented individuals. Individuals with well over the average IQ, with passion for the job, and that are no afraid to spend extra hours on the task. If it were for me, I'd give up ten of the 9-to-5, dumb, lazy a$$es, weasels, that are unfortunately the fabric of most of US companies, for one talented engineer. You wonder and cry because he has extra privileges than you? Meritocracy, comes not only in form of extra salary, my friend.
No, I have the recipe for Nokia. Throw Symbian in the trashcan, since it's $hit from the kernel source, architecture, and external API. Lay off all of the internal, Symbian-backing, dinosaurs. Use Linux as kernel, and QT as UI interface. Then, only then, Nokia might succeed in gaining some share in the mobile development world. Yes, I know, there's still the fact that Nokia just hasn't the kool-factor that Apple and Google have.
Android code bad? I guess you're not a Symbian DevKit subscriber, do you? Have you actually SEEN the Symbian OS core code? Compared to Linux it's a Pile Of $hit, same as compared to WM. Thanks God is disappearing very fast on the eve of saner OSs and development environments (note the -21% on Q4 2008)
http://symbianfoundation.files.wordpress.com/2009/03/table-3-gartner1.jpg
Funny how they go proud of their market share, when they lost 21% of it only in the last year. My bet, in 2009, they'll lose even more. My brokers give Symbian at 10% market share in 2010.
Great outline of the Symbian shortcomings! Things comes in my mind slowly, because my brain actually tried to delete them ASAP. About their strings. They have these TDes and TDesC that should clearly have been made pure virtual, since you can't have a working instance in the way they're designed. But, they are not. So someone could be tempted to create a function that accepts an object of type TDes/TDesC, with EPIC fails due to the TDes/TDesC members trying to access an unexisting data member of an unexisting parent class. All nice things to debug, given the added crapola of their terrible debugging facilities.
3. Robustness
You kidding, right?
Guys, Symbian API is NOT C++. Is a pseudo C++ written by people that were learning C++ along the way. Can you spell TRAPD() and CleanupStack? And how about their imports by ordinals, whose number change magically and break ABI among minor OS releases? How about the bare "Install Failed!" coming from an SIS install attempt, with no friggin' clue on the real problem? How about their development chain? A clusterfsck of PE binaries, glued together with batch files, glued together with Perl scripts. How about errors coming from the development chain, that gives no absolute clue of what happened (hiding real GCC errors)? How about build binaries results being scattered God knows where, under a 34 levels deep structure? How about their documentation? The missing of, that is. There are way better and friendlier development environments to work with, in the mobile space. Don't waste your time with Symbian, you'll thank me for this suggestion.
I agree. Let's make a poll. Myself, and ALL the developers that had the bad luck to touch Symbian in a way or another, consider it the most developer-hostile environment to work with. If you think that your job sucks, and the development environment you're currently working with, is bad, try Symbian. You'll look at your current job under an whole another light!
... with NO ability ...
And what about that joke of the Symbian Foundation, whose spokesman attached Google on the basis that Android is not open? While, their "open" idea, is to have you pay $1500 to get a VERY LIMITED source code access, with ability to customize and build your own.
Life is always nice at Google, relentlessly baking useless code 24h/day 7days/week.
So, you close fabs in USA and you make us even more dependent on oversee production. Way to go Intel!
... (a big bank) ...
See, I told ya it always work. It just filters out unwanted jobs, and lets you focus on the interesting ones.
Get rid of any trace of MS in your resume, and you'll have a better chance to land a nice, challenging and rewarding job. As soon as I dropped the very first years of my experience (I know!! I didn't know back then) from the resume, offers started flowing in. Do it, it works every time!