Having algorithms written in a form humans can understand is just as important in most cases. Someone who writes an unmaintainable implementation of an algorithm may be a good mathematician, but they're not a good programmer.
Basically, moving to a closed store model throws away one of the few things that are good about WinMo. Next to a phone running raw Linux (like the Nokia N900 *drool*) it's the most open phone. unfortunately, I find it slow, clunky, mildly unstable, and unusable without a stylus. I've recently switched to running a hacked in Android OS, and it's about as stable as WinMo, but is faster and much nicer to use. The XDA developers are doing great work, and when the last few features are working, I doubt I'll use WinMo again, and may move to the Nokia when I have the option.
I tried a beta of Fennec, and really, it needed a lot of work anyway.
Well in their defense, almost everything is made in China, including ties. I think their 'casual' dress policy is provides enough intent that the "Dont be evil" policy is still applicable.
It's very much like global warming. There's a very large group that don't seem to care because it doesn't affect them yet, and (if true) everyone is going to pay for it in the future.
You're defying prophesy. It has been said that in the future “There's only four things we do better than anyone else: music, movies, microcode, and high-speed pizza delivery”
Hardcore gamers generally want to play with a mouse and keyboard for immediate response in aiming, etc. This may be able to give that to them. The Xbox one worries me, as I'm unlikely to stand up for a 16 hour gaming session.
Entitled attitude? This guy is trying to save money or find an alternative solution to a problem, as he can't afford the options he's seen so far. We should frikkin' elect him to public office.
Lets see how it works out for them when they need to count on the trust of their American workers. This might be a good short term move for stock value, but long term its going to damage their reputation with workers, and the people that use their software and services.
It's an excellent opportunity for a company or government to extract itself from IBMs effective monopoly. No, it's not free, but it will generally save a lot of money in the mid to long term.
When programming in Java, I still resist breaking out of loops, or multiple returns, even in small methods. These things seem to be normal acceptable practice with most developers, and really are fine when used in the right places. Because of early exposure to BASIC (and badly written C) I avoid them more than most.
I think the BASIC of today is Javascript. You see more badly written javascript than any other language..
Is this an acceptable place to rant about the silly l/100km efficiency measurement? Why not use km/l? This numbers are still in a usable range, and it avoids use of an arbitrary or non-standard constant (100). What measurement do you use in Europe for 'mileage'?
It's also generally a bad idea to create a 'standard' on a proprietary, licenced technology as other companies will create competing 'standards'. If they offer the patents, connectors, etc, up for public domain, I'll start to be interested. Without an open standard, you'll have to have a pocket full of different electronic devices rather that a pocket full of keys.
As someone who is occasionally forced to write code that will be run on a large mainframe, option 2 might save a few million dollars a year in CPU costs. Admittedly this is one of the few cases where the "hardware is cheap, programmers are expensive" rule does not apply in all cases.
I'm still of the opinion that on occasion, the right framework is one you write yourself. Sometimes there's just too much of a compromise with all of the existing frameworks when you're dealing with an unusual case. Admittedly these cases are few and far between these days as most things tend to become 'solved problems'.
... and in those cases you should. There's nothing wrong with re-inventing the wheel in some cases, especially where you don't want to drag around a ridiculous framework that does way more than you need.
I'm not sure who was first, but the Google project has been around for a couple of years now. This is not really new 'news'.
into a form a computer can understand.
Having algorithms written in a form humans can understand is just as important in most cases. Someone who writes an unmaintainable implementation of an algorithm may be a good mathematician, but they're not a good programmer.
Exactly. That's why all drivers should be required to spend their first 2 years riding a motorcycle. If you live through it you can drive a car.
HTC phones, and a few others have had these features in North America for at least 3 years.
I was thinking it was more like "Dirty Rotten Scoundrels".
Especially since Palm is rumoured to be moving to Android.
Basically, moving to a closed store model throws away one of the few things that are good about WinMo. Next to a phone running raw Linux (like the Nokia N900 *drool*) it's the most open phone. unfortunately, I find it slow, clunky, mildly unstable, and unusable without a stylus. I've recently switched to running a hacked in Android OS, and it's about as stable as WinMo, but is faster and much nicer to use. The XDA developers are doing great work, and when the last few features are working, I doubt I'll use WinMo again, and may move to the Nokia when I have the option.
I tried a beta of Fennec, and really, it needed a lot of work anyway.
US Criticizes Google's 'Chinese Ties'
Well in their defense, almost everything is made in China, including ties. I think their 'casual' dress policy is provides enough intent that the "Dont be evil" policy is still applicable.
It's very much like global warming. There's a very large group that don't seem to care because it doesn't affect them yet, and (if true) everyone is going to pay for it in the future.
You're defying prophesy. It has been said that in the future “There's only four things we do better than anyone else: music, movies, microcode, and high-speed pizza delivery”
Hardcore gamers generally want to play with a mouse and keyboard for immediate response in aiming, etc. This may be able to give that to them. The Xbox one worries me, as I'm unlikely to stand up for a 16 hour gaming session.
Entitled attitude? This guy is trying to save money or find an alternative solution to a problem, as he can't afford the options he's seen so far. We should frikkin' elect him to public office.
The price will probably drop as demand increases, and based on how loud many have their MP3 players turned up, it will increase.
Lets see how it works out for them when they need to count on the trust of their American workers. This might be a good short term move for stock value, but long term its going to damage their reputation with workers, and the people that use their software and services.
It's an excellent opportunity for a company or government to extract itself from IBMs effective monopoly. No, it's not free, but it will generally save a lot of money in the mid to long term.
It's fairly simple. They're lying.
Yes they do. Their competition (PowerGig: Rise of the Six String) has a controller that is an actual electric guitar ...
When programming in Java, I still resist breaking out of loops, or multiple returns, even in small methods. These things seem to be normal acceptable practice with most developers, and really are fine when used in the right places. Because of early exposure to BASIC (and badly written C) I avoid them more than most.
I think the BASIC of today is Javascript. You see more badly written javascript than any other language..
Is this an acceptable place to rant about the silly l/100km efficiency measurement? Why not use km/l? This numbers are still in a usable range, and it avoids use of an arbitrary or non-standard constant (100). What measurement do you use in Europe for 'mileage'?
It's also generally a bad idea to create a 'standard' on a proprietary, licenced technology as other companies will create competing 'standards'. If they offer the patents, connectors, etc, up for public domain, I'll start to be interested. Without an open standard, you'll have to have a pocket full of different electronic devices rather that a pocket full of keys.
As someone who is occasionally forced to write code that will be run on a large mainframe, option 2 might save a few million dollars a year in CPU costs. Admittedly this is one of the few cases where the "hardware is cheap, programmers are expensive" rule does not apply in all cases.
I'm still of the opinion that on occasion, the right framework is one you write yourself. Sometimes there's just too much of a compromise with all of the existing frameworks when you're dealing with an unusual case. Admittedly these cases are few and far between these days as most things tend to become 'solved problems'.
Try reading it as William Shatner would.
I'm already at the gunpowder stage. My code has been blowing up for years.
... and in those cases you should. There's nothing wrong with re-inventing the wheel in some cases, especially where you don't want to drag around a ridiculous framework that does way more than you need.