I love how the Onion hits so many nails on the head (It's kinda hard not to hit a nail while wielding a hammer) but in the same, I'm distraught by how many people manage to completely miss the honest satire it provides.
Python with PyGTK or C++ with g++. Just for the name of all that is structural and logical, don't expose the kids to the horrid habits of Visual Basic -- Once you learn a way of doing things, it sticks with you.
I still don't see how that justifies him having raunchy photographs of himself on his phone in the first place, unless the iPhone was responsible for that too. (In which case, I would like to exempt from the iStalk features.)
I'll be the first (albeit a little late) to admit I thought Google was pulling a MS for a moment.
So what would call for revising the standards? Well let's say you have a lemonade stand. What if your normal set-up doesn't provide all the things you (and your customers) would like out of your lemonade stand? That's where you go out and implement these features.
Google would find out what the users would like and then make it happen. MS would start selling orange juice.
Now wait, that's not what NORMAL lemonade stands do! Well you're right. If a standard itself is causing problems for the user and the operator than there's more than likely a problem with the standard. (Or you have really bad operators.) If the changes were for the better, other stands of the like will do the same. Eventually, you bring forth better standards. This, like the lot of things is a double edged sword as we also end up with a lot more orange juice stands.
They haven't wronged (me) us yet, anyhow.
I love how the Onion hits so many nails on the head (It's kinda hard not to hit a nail while wielding a hammer) but in the same, I'm distraught by how many people manage to completely miss the honest satire it provides.
break?
Python with PyGTK or C++ with g++. Just for the name of all that is structural and logical, don't expose the kids to the horrid habits of Visual Basic -- Once you learn a way of doing things, it sticks with you.
I personally own a .net TLD and use it for nothing but the finest of shenanigans.
I still don't see how that justifies him having raunchy photographs of himself on his phone in the first place, unless the iPhone was responsible for that too. (In which case, I would like to exempt from the iStalk features.)
We're being forced to feel the siren, it's rape.
The image is from this webcomic's author's flickr, he just so happens to like redbull a lot.
The irony of this situation is absolutely baffling.
I'll be the first (albeit a little late) to admit I thought Google was pulling a MS for a moment. So what would call for revising the standards? Well let's say you have a lemonade stand. What if your normal set-up doesn't provide all the things you (and your customers) would like out of your lemonade stand? That's where you go out and implement these features. Google would find out what the users would like and then make it happen. MS would start selling orange juice. Now wait, that's not what NORMAL lemonade stands do! Well you're right. If a standard itself is causing problems for the user and the operator than there's more than likely a problem with the standard. (Or you have really bad operators.) If the changes were for the better, other stands of the like will do the same. Eventually, you bring forth better standards. This, like the lot of things is a double edged sword as we also end up with a lot more orange juice stands. They haven't wronged (me) us yet, anyhow.