It's an information appliance, nothing more. I don't think most people need or care to jailbreak it. The only interesting thing I could do with my jailbroken iphone was tether it, but there are contractual reasons why I shouldn't be doing that.
I'm saying that the summary misses the important point that Google isn't at all interested in not doing business in or with China which many people would like to hear. It's clearly misleading fellow commenters here if you scroll up or down which is why I posted my original comment early on.
There's an accessory that is a dock/keyboard for the iPad. Actually I thought it was clever to have a way to both prop up the iPad and have a real keyboard at the same time.
If a spokesperson for my government said "of course we have to censor the Internet for stability reasons" my ears would perk up and I'd have to ask "exactly what are you censoring from me?"
Rewriting history like China's massacre at Tiananmen Square is truly evil. The only saving grace is that China's dependance on technology is only going to make it harder to control information.
There's a little bit more info in the article, albeit not a lot. Seems very odd that they would spend 4 years trying to hack an interface onto a Linux base to make it sort of look like Windows (what a role model for UI design!).
For that matter, why not just hack Windows to begin with? I guess maybe the answer is that they probably already do and it's not as newsworthy as a 'New' OS which actually isn't new after all.... And, Perhaps with an open-source base to work from they can put in their own controls for restricting/monitoring what the user does. The Russian student should release disc images of what he has so people can pour through the code to see what's going on under the hood.
Every business I've ever worked for has had that one dusty 8086 off in a corner. It would run a single batch file every few hours. No one would touch it, because no one knew what it did-- just that whatever it did do was mission critical.
Ha ha, yeah, there's the real rub. Consolidating servers sounds like a good idea, but some of those servers are running some funky old proprietary services that were set up by folks who have moved on, or are maintained by an IT guy who wants people to believe that "it's just too complicated, you won't understand what it does or how it works".
They shouldn't be auditing servers, they should be auditing services. Phase out the old and take those servers out of service over time.
I find it odd that they think the energy savings would offset a pita consolidation effort.
Something that comes up over and over again is that it doesn't come with a keyboard. Well, Apple will sell a dock/keyboard for it: http://images.apple.com/ipad/specs/images/keyboard_dock_1_20100127.jpg
I'm not saying I wouldn't feel like a dork using it at a coffee shop, just saying that for those who find not having a physical keyboard a deal-breaker, then take a look.
"When doctors disassembled the board, they found the accelerometers..."
They did? I couldn't find any information stating that the balance board had motion sensing. Everything I've read says it just has four pressure sensors, one for each corner and that's it.
Silly monkey, did you actually think Psystar was fighting Apple on some idealogical grounds other than justifying making money by ripping Apple off? The irony is thick. Psystar's infrastructure, which was to protect their profits, takes you down with them on the ship when things go south. Nice.
But, who knows, maybe somebody will start a company reverse engineering Psystar's DRM so for a small fee you can get your computer working again?;')
At my work we had a problem with people putting on headphones and tuning out completely. We resorted to throwing pens at each other to get the others' attention. It's especially irritating when you walk up to tap somebody on the shoulder and you see that they aren't even working but surfing the web.
We solved that issue (and more) by making it a requirement to have an IM client going at all times. For those times where people really did need to focus, it was accepted to set your status to 'away', as long as it wasn't set that way a majority of the time.
I've been a long time Perl 5 developer, and have been doing a lot of Ruby since RoR was in beta. I haven't had a lot of issues with Ruby, to be honest. Most of the important CPAN modules have been ported to RubyGems and most of the serious Ruby bugs have been fixed.
Some things which make Ruby great: It's a very nice OO language. Rails is basically the standard web framework used (Perl 5 has many to choose from, so inheriting a Perl web project can be a pita).
Some things which make Ruby not so great: It's sooo slow to start and requires mod_rails/fastCGI/Mongrel or some other special environment to be fast enough for production web-apps. The community (sorry) has a lot of n00bs that make it difficult to find truly talented programmers.
BTW- I think it's a little cheap to compare Ruby with Perl 6. Ruby reached 1.0 in 1996, and Perl 6 hasn't reached production yet.
And toner doesn't dry up or clog like ink cartridges. I'm nursing a toner cartridge that's over 10 years old and it still prints with the same quality as it did when it was new.
Right-o. I meant more specifically that it play through the alert to me in real-time instead of only recording it for me to stumble upon later when it doesn't matter any more.
I was watching my TiVo a few years ago and 'EMERGENCY!' There was a tornado watch in effect. Sadly, it ruined the program I was watching which was recorded over a week before. So, when will DVRs recognize the alert tones and play them through to whatever (potentially recorded) program you are *currently* watching?
The nice thing about standards is that there are so many to choose from!
Why in the world implement a new standard whose purpose is to speed up the web yet only do it 2x under certain conditions? To be taken seriously, it would have to be orders of magnitude faster, but that's a huge hurdle because the root of the problem isn't the HTTP protocol, but what's happening on the web server (no pipelined connections? slow DB? uncompressed content? sloppy, inefficient coding?) and the end users' bandwidth. The one thing SPDY has going for it is compressing headers and eliminating redundant headers, but that's a small gain really.
In any case, you could simply wait and things will get naturally faster w/o new protocols because servers generally get faster and users' bandwidth increases. And by the same token the benefits of a new in-between protocol would diminish.
Sad but true, I watched somebody give some mockups/samples with real sounding but bogus data to an exec. The executive later used that data in a presentation as if it were real data (*face palm*). Apparently he remembered seeing the mockups and needed that sort of data and forgot it was bogus.
Put giant watermarking saying "SAMPLE DATA ONLY!" or something like that on it, or it could come back to bite your butt.
This has everything to do business planning of funding and timely rollout of redundancy and backup systems (including staff). The tech, tools, good IT staff hires, procedures, and strategies are out there and are pretty well known. I don't have to know about their infrastructure or staffing to tell you that they didn't invest in the infrastructure and/or training for staff to prevent exactly this sort of disaster.
I can think of three possible reasons why they didn't have such an infrastructure in place:
1) When M$ bought Danger, they scaled back to maximize profits
2) The risk/cost analysis (odds of failure, cost, and cost to prevent) of such a disaster was out of date, incorrect, or simply accepted
3) Funding was available but rollout of redundancy/backup was taking longer than expected
I doubt #3 since Danger has been around for a while and their customer base probably isn't growing exceedingly quickly. #2 is mildly possible, IMHO, if they simply accepted the risk. But, a class-action after a disaster like this has to be really expensive unless they think they can dodge the legal obligation of backing up user data. #1 is fairly typical of take overs, especially if profit is more important than safeguarding user data.
If you are lying to a company in order to satisfy some requirement of theirs you think might be silly, then they probably aren't a good fit for you anyway.
Overselling yourself is just going to make life hard for yourself. We've hired a number of people who have oversold themselves and I think some do so because they are cocky (blah, how hard could it be?), or because they are simply ignorant of what the job entails. They flounder and eventually get let go.
Find companies that share your sensibilities and be honest with them about what you can do and where you want to go in the long term.
This reminds me of an article at the Consumerist web site about Nigerian internet scams. It's not a particularly enlightening article, so I was confused at first why Stumble Upon took me there.
And then I started to read the comments and realized why the page was of interest. You see, the article included an image of a black man holding a box. Surely a Nigerian holding stolen goods! Nope. It was a Getty stock photo. At Getty the caption is 'delivery man holding a package'. While I was looking at the image at Getty a live-chat box popped up asking if I needed help, so what the heck, I asked them if it was OK to use Getty stock photos like that. They said, No, that it is actually a crime and that the model can sue the Consumerist if they want for portraying them as a criminal.
Anyways, I'm sure fashion models have signed away all rights against making them look deformed, but as these PS disasters pile up there has got to be some sort of push back from the models.
Here's the next meme: Can I haz a sammich? A site with photoshoped women like this with lolcats-style captions.
A CS professor years ago used to tell us as students, "When you graduate, you'll spend the first year of your career trying to get Root, and the rest of it trying to get rid of it."
How true. My first year at a small but growing media company was exciting with colocations, T1s to set up, phone systems, strutting around with key-code cards, etc. I was important!
The novelty quickly wears off after, for example, a server doesn't come up after a scheduled night time reboot. Driving in the middle of the night to the co-location center just to see "Keyboard error, press F1 to continue" because the last person there borrowed the keyboard for another server and forgot to plug it back in.
Like many other posters have mentioned, when things go smooth, you get taken for granted ("what do you do here, again?"). And when things blow up, you've suddenly lost credibility because you 'forgot' to keep an extra spare of that proprietary power supply on hand. Or, get razzed for not better preparing for when a bathroom in an apartment upstairs over the server room has flooded and is making it 'rain' in the server room. (Yes, it happened!)
Rock on, AMD! AMD's can handle anything. To prove it, I've got some videos and stuff running right now (loading the CPU), and I will take the side off the case and remove the heatsink... (ouch! it's hot!..)
Slashdot Mirror
It's an information appliance, nothing more. I don't think most people need or care to jailbreak it. The only interesting thing I could do with my jailbroken iphone was tether it, but there are contractual reasons why I shouldn't be doing that.
Checked. Works fine! (thumbs up!)
I'm saying that the summary misses the important point that Google isn't at all interested in not doing business in or with China which many people would like to hear. It's clearly misleading fellow commenters here if you scroll up or down which is why I posted my original comment early on.
I RTFA! So sue me! Shesh.
From the article:
"It’s very important to know we are not pulling out of China"
At most, it appears they would stop offering search services.
What gives the iPad its strengths is the software it runs. It's otherwise a fairly simple device (a touchscreen, yay).
There's an accessory that is a dock/keyboard for the iPad. Actually I thought it was clever to have a way to both prop up the iPad and have a real keyboard at the same time.
If a spokesperson for my government said "of course we have to censor the Internet for stability reasons" my ears would perk up and I'd have to ask "exactly what are you censoring from me?"
Rewriting history like China's massacre at Tiananmen Square is truly evil. The only saving grace is that China's dependance on technology is only going to make it harder to control information.
There's a little bit more info in the article, albeit not a lot. Seems very odd that they would spend 4 years trying to hack an interface onto a Linux base to make it sort of look like Windows (what a role model for UI design!).
For that matter, why not just hack Windows to begin with? I guess maybe the answer is that they probably already do and it's not as newsworthy as a 'New' OS which actually isn't new after all. ... And, Perhaps with an open-source base to work from they can put in their own controls for restricting/monitoring what the user does. The Russian student should release disc images of what he has so people can pour through the code to see what's going on under the hood.
press F1 to continue.
I'll shoot anyone in the face who says that I'm violent.
I love the fact that this is (currently) modded as "Informative".
Every business I've ever worked for has had that one dusty 8086 off in a corner. It would run a single batch file every few hours. No one would touch it, because no one knew what it did-- just that whatever it did do was mission critical.
Ha ha, yeah, there's the real rub. Consolidating servers sounds like a good idea, but some of those servers are running some funky old proprietary services that were set up by folks who have moved on, or are maintained by an IT guy who wants people to believe that "it's just too complicated, you won't understand what it does or how it works".
They shouldn't be auditing servers, they should be auditing services. Phase out the old and take those servers out of service over time.
I find it odd that they think the energy savings would offset a pita consolidation effort.
Something that comes up over and over again is that it doesn't come with a keyboard. Well, Apple will sell a dock/keyboard for it: http://images.apple.com/ipad/specs/images/keyboard_dock_1_20100127.jpg
I'm not saying I wouldn't feel like a dork using it at a coffee shop, just saying that for those who find not having a physical keyboard a deal-breaker, then take a look.
"When doctors disassembled the board, they found the accelerometers..."
They did? I couldn't find any information stating that the balance board had motion sensing. Everything I've read says it just has four pressure sensors, one for each corner and that's it.
Silly monkey, did you actually think Psystar was fighting Apple on some idealogical grounds other than justifying making money by ripping Apple off? The irony is thick. Psystar's infrastructure, which was to protect their profits, takes you down with them on the ship when things go south. Nice.
But, who knows, maybe somebody will start a company reverse engineering Psystar's DRM so for a small fee you can get your computer working again? ;')
Ask your boss what the REAL reason is.
At my work we had a problem with people putting on headphones and tuning out completely. We resorted to throwing pens at each other to get the others' attention. It's especially irritating when you walk up to tap somebody on the shoulder and you see that they aren't even working but surfing the web.
We solved that issue (and more) by making it a requirement to have an IM client going at all times. For those times where people really did need to focus, it was accepted to set your status to 'away', as long as it wasn't set that way a majority of the time.
I've been a long time Perl 5 developer, and have been doing a lot of Ruby since RoR was in beta. I haven't had a lot of issues with Ruby, to be honest. Most of the important CPAN modules have been ported to RubyGems and most of the serious Ruby bugs have been fixed.
Some things which make Ruby great: It's a very nice OO language. Rails is basically the standard web framework used (Perl 5 has many to choose from, so inheriting a Perl web project can be a pita).
Some things which make Ruby not so great: It's sooo slow to start and requires mod_rails/fastCGI/Mongrel or some other special environment to be fast enough for production web-apps. The community (sorry) has a lot of n00bs that make it difficult to find truly talented programmers.
BTW- I think it's a little cheap to compare Ruby with Perl 6. Ruby reached 1.0 in 1996, and Perl 6 hasn't reached production yet.
And toner doesn't dry up or clog like ink cartridges. I'm nursing a toner cartridge that's over 10 years old and it still prints with the same quality as it did when it was new.
Right-o. I meant more specifically that it play through the alert to me in real-time instead of only recording it for me to stumble upon later when it doesn't matter any more.
I was watching my TiVo a few years ago and 'EMERGENCY!' There was a tornado watch in effect. Sadly, it ruined the program I was watching which was recorded over a week before. So, when will DVRs recognize the alert tones and play them through to whatever (potentially recorded) program you are *currently* watching?
The nice thing about standards is that there are so many to choose from!
Why in the world implement a new standard whose purpose is to speed up the web yet only do it 2x under certain conditions? To be taken seriously, it would have to be orders of magnitude faster, but that's a huge hurdle because the root of the problem isn't the HTTP protocol, but what's happening on the web server (no pipelined connections? slow DB? uncompressed content? sloppy, inefficient coding?) and the end users' bandwidth. The one thing SPDY has going for it is compressing headers and eliminating redundant headers, but that's a small gain really.
In any case, you could simply wait and things will get naturally faster w/o new protocols because servers generally get faster and users' bandwidth increases. And by the same token the benefits of a new in-between protocol would diminish.
Sad but true, I watched somebody give some mockups/samples with real sounding but bogus data to an exec. The executive later used that data in a presentation as if it were real data (*face palm*). Apparently he remembered seeing the mockups and needed that sort of data and forgot it was bogus.
Put giant watermarking saying "SAMPLE DATA ONLY!" or something like that on it, or it could come back to bite your butt.
This has everything to do business planning of funding and timely rollout of redundancy and backup systems (including staff). The tech, tools, good IT staff hires, procedures, and strategies are out there and are pretty well known. I don't have to know about their infrastructure or staffing to tell you that they didn't invest in the infrastructure and/or training for staff to prevent exactly this sort of disaster.
I can think of three possible reasons why they didn't have such an infrastructure in place:
1) When M$ bought Danger, they scaled back to maximize profits
2) The risk/cost analysis (odds of failure, cost, and cost to prevent) of such a disaster was out of date, incorrect, or simply accepted
3) Funding was available but rollout of redundancy/backup was taking longer than expected
I doubt #3 since Danger has been around for a while and their customer base probably isn't growing exceedingly quickly. #2 is mildly possible, IMHO, if they simply accepted the risk. But, a class-action after a disaster like this has to be really expensive unless they think they can dodge the legal obligation of backing up user data. #1 is fairly typical of take overs, especially if profit is more important than safeguarding user data.
If you are lying to a company in order to satisfy some requirement of theirs you think might be silly, then they probably aren't a good fit for you anyway.
Overselling yourself is just going to make life hard for yourself. We've hired a number of people who have oversold themselves and I think some do so because they are cocky (blah, how hard could it be?), or because they are simply ignorant of what the job entails. They flounder and eventually get let go.
Find companies that share your sensibilities and be honest with them about what you can do and where you want to go in the long term.
This reminds me of an article at the Consumerist web site about Nigerian internet scams. It's not a particularly enlightening article, so I was confused at first why Stumble Upon took me there.
And then I started to read the comments and realized why the page was of interest. You see, the article included an image of a black man holding a box. Surely a Nigerian holding stolen goods! Nope. It was a Getty stock photo. At Getty the caption is 'delivery man holding a package'. While I was looking at the image at Getty a live-chat box popped up asking if I needed help, so what the heck, I asked them if it was OK to use Getty stock photos like that. They said, No, that it is actually a crime and that the model can sue the Consumerist if they want for portraying them as a criminal.
Anyways, I'm sure fashion models have signed away all rights against making them look deformed, but as these PS disasters pile up there has got to be some sort of push back from the models.
Here's the next meme: Can I haz a sammich? A site with photoshoped women like this with lolcats-style captions.
A CS professor years ago used to tell us as students, "When you graduate, you'll spend the first year of your career trying to get Root, and the rest of it trying to get rid of it."
How true. My first year at a small but growing media company was exciting with colocations, T1s to set up, phone systems, strutting around with key-code cards, etc. I was important!
The novelty quickly wears off after, for example, a server doesn't come up after a scheduled night time reboot. Driving in the middle of the night to the co-location center just to see "Keyboard error, press F1 to continue" because the last person there borrowed the keyboard for another server and forgot to plug it back in.
Like many other posters have mentioned, when things go smooth, you get taken for granted ("what do you do here, again?"). And when things blow up, you've suddenly lost credibility because you 'forgot' to keep an extra spare of that proprietary power supply on hand. Or, get razzed for not better preparing for when a bathroom in an apartment upstairs over the server room has flooded and is making it 'rain' in the server room. (Yes, it happened!)
Rock on, AMD! AMD's can handle anything. To prove it, I've got some videos and stuff running right now (loading the CPU), and I will take the side off the case and remove the heatsink... (ouch! it's hot!..)
See!