I think the key there is display. The value of not having to switch software ecosystems is high imho. Basically once both isa's can operate for 8 hours or so on a single charge I suspect the less functional one will need a much bigger jump in hours per charge to make up for the functionality loss.
I don't often go more than 8 hours without easy access to power. Once I can do that and run windows an android tablet would have to last a week or more per charge to make up for it.
I don't think there were any good strategies. Having missed the iphone and android early leads and being linked at the hip to a power hungry x86 isa meant that any strategy was a lesser of several evils one.
That being said I'm sure they could have executed better. I don't have a problem with using the same brand since it emphasizes a break with the past level of mobility. Porting 25+ year old software to a new isa is NOT an easy thing to do.
Might still be valuable to keep around both as a hedge against future power efficiency changes. If arm devices can go a week om a single charge, or a month, then this cycle gets played out again.
Also good to get your high value software working well on more than one instruction set so you're not at the mercy of intel.
But it's a balancing act. And x86 doesn't have to be as efficient because they're way more functional (all that extra software you can run).
From a consumer viewpoint once you get to a certain amount of power efficiency more becomes less valuable. So if I can run a single light device for at least 6 - 8 hours on a single charge then being able to use a single stack (e.g., windows x86) increases in value.
If they get the surface down near android tablet thickness and weight then I wouldn't bother with an android tablet...
Amd's been dying since they went fabless imho... They've never matched intel in performance (not for long any way) and power on the desktop was less relevant (though still relevant in data centers).
The display angle was rational imho but the legacy jump (displayport) undermined that.
It's more than that though office is a big deal on the desktop sure.
Lots of internal it type apps target windows. And lots of utilities. Throw in enterprise concerna and fuggetaboutit - running full windows is a requirement, not an optional thing.
If the purpose of rt was to get intel to take power consumption seriously then it may well have worked. Battery life was a key differentiator and on ramp for non - windows (ios and android) devices. Getting rid of that advantage strikes me as pretty crucial for the windows camp.
The question is whether or not it's too late to restore hegemony to windows in the tablet space.
It's a free festival. Internet access was kind of all or nothing. At the main stage speed test over verizon 4g clocked in well north of 5mbps. Over near the shore, on the rocks and the like I got bupkus. No signal at all.
Not really a big deal to walk a few feet to get coverage but this is seattle, we tech hard so going the extra mile to have a weed festival with great coverage is important-ish.:)
Yeah but the first part sounds kinda interesting. Anyone who works at any of those tech companies next to the park could probably plug in to their wired network. That'd be a trunk line onto the public internet. Getting that out of the building... maybe run cat5 from the closest port near the roof then wifi it over to a main hotspot that relays to the rest.
Or wifi it through the windows to the nearest park hotspot.
They'd take a bump to their internet traffic but if it is mostly over a weekend and they're nowhere near their cap... hell put a donation cup in front of the parpark hotspot to pay em:)
Oh and microwave, wimax and COWs strike me as the most promising/practical so far. Even here in seattle it might be hard to get the tech companies to sponsor (though maybe 429 branded beers and the like might?)
Definitely interesting imho. I'm a hobbyist, 1st time at festival this year, and would have defaulted to using hotspots as wifi backhaul but maybe that's not the way to go.
then again I'm used to bringing in stuff from home to work (pc components mainly) but enterprise hardware is like a superset of home hardware. SAS, fibrechannel and the like.
I thought his question implied that they were going to use 4g hotspots to provide wifi. Not to extend 4g coverage but to use it as a backhaul for wifi. Why would he need the hotspots to move? The geography is fixed. Coverage sucked near the shore but was fine around the main stage. I thought he qas asking if there's a better way to position the hotspots to provide maximum wifi coverage...
Normally I'd say this was a bad for users kind of decision. But honestly office on a phone is mostly irrelevant. Now that OneNote on android and ios are tolerable I think they've hedged their bets well.
Coming from someone that thinks winphone is beautiful but because of network effects will not be a real contender (os/2 warp anyone?)
Typical reactionary FU. My kid will be 3 levels ahead of yours because he's been doing math, physics and biology since he was two. And more importantly having fun while doing it.
At this point I think tablets are mainly ideal for kids. I never use mine except when playing with my son (ultrabook is much more functional).
Lighten up. The kids love them, they'reunbelievably educational and they provide a great way to bond as you play together. Download zoodles and only let your kid play the educational stuff.
Zoodles is excellent. You can even lock the kid in zoodles "kid mode". I got it when my son turned 2 and still use it. Liked it so much I pay for it but it's fully functional for free.
They have hundreds of apps arranged by age. And you can add links to other apps (e.g. angry birds). They send you a weekly report card with more graphs and stats than anyone needs.
I worked for severals years as a programmer in the unix world (mainly solaris with the occasional linux development thrown in) then made the transition to the windows world.
In both worlds C is the common denominator language. I was suprised by how much of the Win32 API is plain old vanilla C. So whatever you've learned about procedural programming, memory management and pointers comes in handy in both worlds.
Next up is C++. The OO support makes it powerful but its hybrid roots and expansive ambitions make for many pitfalls. In the Win32 world much of the code/library sharing is done via COM. In the unix world you'll accomplish similar reuse via pipes, shared memory and shared bindings (e.g., using the same compiler or a compatible one as everyone else).
If you can master C and C++ then the world is your oyster - you will rarely encounter a problem that you can't solve better than most because of your understanding of what is really going on.
Lastly I'd pick up Java and/or C#. Both are excellent languages that incorporate many of the wonderful concepts you studied in your programming languages and constructs class (or whatever it's called at your school). They're both extremely productive languages with rich libraries, excellent documentation, concise syntax and great futures.
Along the way I'd grab PERL and at least one shell language (I'm partial to bash but ksh and tcsh are others). For many tasks they're more than adequate and mastery of them will make you more productive - you'll quickly automate things that others will waste time doing manually.
Which brings me to my last point. Be a fan of tools. Tools are your friend. If an IDE is available use it. They don't change the algorithms but they can dramatically increase your productivity by reducing the time it takes to do things that programmers do all the time. Learn keyboard shortcuts/combos. If you're an emacs-er then know your ctrl combos. If you're vi* fan, know your commands. Learn to use the debugger for all of the languages you learn (if they have one). Learn your.rc files and fill them with time saving aliases and settings.
The more languages you know the better you will be at writing code. You will see patterns emerge. I can't tell you how many times I've seen bad solutions to problems come about because the people involved didn't know about the features of their language or their language's libraries.
Use your downtime to browse through API documentation. When you're find -exec'ing in a huge directory pull up another xterm and skim through a header file or man page on a library call. Most of the time skimming is more than enough to set you apart from your peers - you'll be able to lookup the details when you need them while they'll be wasting time building it from scratch (and creating all the bugs that have already been fixed in the api you're using).
Slashdot Mirror
I think the key there is display. The value of not having to switch software ecosystems is high imho. Basically once both isa's can operate for 8 hours or so on a single charge I suspect the less functional one will need a much bigger jump in hours per charge to make up for the functionality loss.
I don't often go more than 8 hours without easy access to power. Once I can do that and run windows an android tablet would have to last a week or more per charge to make up for it.
I don't think there were any good strategies. Having missed the iphone and android early leads and being linked at the hip to a power hungry x86 isa meant that any strategy was a lesser of several evils one.
That being said I'm sure they could have executed better. I don't have a problem with using the same brand since it emphasizes a break with the past level of mobility. Porting 25+ year old software to a new isa is NOT an easy thing to do.
Might still be valuable to keep around both as a hedge against future power efficiency changes. If arm devices can go a week om a single charge, or a month, then this cycle gets played out again.
Also good to get your high value software working well on more than one instruction set so you're not at the mercy of intel.
But it's a balancing act. And x86 doesn't have to be as efficient because they're way more functional (all that extra software you can run).
From a consumer viewpoint once you get to a certain amount of power efficiency more becomes less valuable. So if I can run a single light device for at least 6 - 8 hours on a single charge then being able to use a single stack (e.g., windows x86) increases in value.
If they get the surface down near android tablet thickness and weight then I wouldn't bother with an android tablet...
Amd's been dying since they went fabless imho... They've never matched intel in performance (not for long any way) and power on the desktop was less relevant (though still relevant in data centers).
The display angle was rational imho but the legacy jump (displayport) undermined that.
It's more than that though office is a big deal on the desktop sure.
Lots of internal it type apps target windows. And lots of utilities. Throw in enterprise concerna and fuggetaboutit - running full windows is a requirement, not an optional thing.
If the purpose of rt was to get intel to take power consumption seriously then it may well have worked. Battery life was a key differentiator and on ramp for non - windows (ios and android) devices. Getting rid of that advantage strikes me as pretty crucial for the windows camp.
The question is whether or not it's too late to restore hegemony to windows in the tablet space.
Not scary at all to me but I have very low paranoia...
It's a free festival. Internet access was kind of all or nothing. At the main stage speed test over verizon 4g clocked in well north of 5mbps. Over near the shore, on the rocks and the like I got bupkus. No signal at all.
Not really a big deal to walk a few feet to get coverage but this is seattle, we tech hard so going the extra mile to have a weed festival with great coverage is important-ish. :)
Yeah but the first part sounds kinda interesting. Anyone who works at any of those tech companies next to the park could probably plug in to their wired network. That'd be a trunk line onto the public internet. Getting that out of the building ... maybe run cat5 from the closest port near the roof then wifi it over to a main hotspot that relays to the rest.
Or wifi it through the windows to the nearest park hotspot.
They'd take a bump to their internet traffic but if it is mostly over a weekend and they're nowhere near their cap... hell put a donation cup in front of the parpark hotspot to pay em :)
You still hang with your friends. You just have much cooler stuff to share than ripped up magazines or broken-spined books.
Nice, good linkage.
Damn sorry to hear that! Jkjkjk :)
Oh and microwave, wimax and COWs strike me as the most promising/practical so far. Even here in seattle it might be hard to get the tech companies to sponsor (though maybe 429 branded beers and the like might?)
Definitely interesting imho. I'm a hobbyist, 1st time at festival this year, and would have defaulted to using hotspots as wifi backhaul but maybe that's not the way to go.
then again I'm used to bringing in stuff from home to work (pc components mainly) but enterprise hardware is like a superset of home hardware. SAS, fibrechannel and the like.
I thought his question implied that they were going to use 4g hotspots to provide wifi. Not to extend 4g coverage but to use it as a backhaul for wifi. Why would he need the hotspots to move? The geography is fixed. Coverage sucked near the shore but was fine around the main stage. I thought he qas asking if there's a better way to position the hotspots to provide maximum wifi coverage...
Normally I'd say this was a bad for users kind of decision. But honestly office on a phone is mostly irrelevant. Now that OneNote on android and ios are tolerable I think they've hedged their bets well.
Coming from someone that thinks winphone is beautiful but because of network effects will not be a real contender (os/2 warp anyone?)
Typical reactionary FU. My kid will be 3 levels ahead of yours because he's been doing math, physics and biology since he was two. And more importantly having fun while doing it.
At this point I think tablets are mainly ideal for kids. I never use mine except when playing with my son (ultrabook is much more functional).
Lighten up. The kids love them, they'reunbelievably educational and they provide a great way to bond as you play together. Download zoodles and only let your kid play the educational stuff.
Zoodles is excellent. You can even lock the kid in zoodles "kid mode". I got it when my son turned 2 and still use it. Liked it so much I pay for it but it's fully functional for free.
They have hundreds of apps arranged by age. And you can add links to other apps (e.g. angry birds). They send you a weekly report card with more graphs and stats than anyone needs.
Zoodles is awesome.
You don't play an instrument? I thought it was quite a clever name...
I worked for severals years as a programmer in the unix world (mainly solaris with the occasional linux development thrown in) then made the transition to the windows world.
In both worlds C is the common denominator language. I was suprised by how much of the Win32 API is plain old vanilla C. So whatever you've learned about procedural programming, memory management and pointers comes in handy in both worlds.
Next up is C++. The OO support makes it powerful but its hybrid roots and expansive ambitions make for many pitfalls. In the Win32 world much of the code/library sharing is done via COM. In the unix world you'll accomplish similar reuse via pipes, shared memory and shared bindings (e.g., using the same compiler or a compatible one as everyone else).
If you can master C and C++ then the world is your oyster - you will rarely encounter a problem that you can't solve better than most because of your understanding of what is really going on.
Lastly I'd pick up Java and/or C#. Both are excellent languages that incorporate many of the wonderful concepts you studied in your programming languages and constructs class (or whatever it's called at your school). They're both extremely productive languages with rich libraries, excellent documentation, concise syntax and great futures.
Along the way I'd grab PERL and at least one shell language (I'm partial to bash but ksh and tcsh are others). For many tasks they're more than adequate and mastery of them will make you more productive - you'll quickly automate things that others will waste time doing manually.
Which brings me to my last point. Be a fan of tools. Tools are your friend. If an IDE is available use it. They don't change the algorithms but they can dramatically increase your productivity by reducing the time it takes to do things that programmers do all the time. Learn keyboard shortcuts/combos. If you're an emacs-er then know your ctrl combos. If you're vi* fan, know your commands. Learn to use the debugger for all of the languages you learn (if they have one). Learn your .rc files and fill them with time saving aliases and settings.
The more languages you know the better you will be at writing code. You will see patterns emerge. I can't tell you how many times I've seen bad solutions to problems come about because the people involved didn't know about the features of their language or their language's libraries.
Use your downtime to browse through API documentation. When you're find -exec'ing in a huge directory pull up another xterm and skim through a header file or man page on a library call. Most of the time skimming is more than enough to set you apart from your peers - you'll be able to lookup the details when you need them while they'll be wasting time building it from scratch (and creating all the bugs that have already been fixed in the api you're using).