You just had to come and shit all over Microsoft and make the same point that you already made up thread because uhhh, you call it like you see it...right?
Bullshit. More like you can't deal with opinions that don't match your own, especially when it comes to Microsoft and Apple. You're nothing more than an pro-Apple, anti-Microsoft fanboi.
There are actually multiple lap modes that both work great.
1) Like a regular laptop.
2) Fold the keyboard back and open the stand so it makes a right angle. Place the right angle so that the keyboard is parallel with your stomach and the Surface is perpendicular. Now the Surface is floating above your lap near the bottom of your chest where it's easy to read and write on.
3) Completely remove the keyboard.
I feel sorry for people who are using products from Apple's sterile and completely un-innovative product lines that are all moving closer and closer to the locked-down anti-consumer, anti-developer iOS business model.
Admittedly I haven't used one aside from once briefly in a store, but seeing people balance them on their laps using the keyboard just looks awkward. Like they are top heavy? Or just too small for that purpose, necessitating one to keep their knees close together.
Works fine for me, but I can imagine issues for people with short legs. If the kickstand needs to be out past the end of your knees you're going to have a problem.
Good. One less locked-down, anti-competitive player to deal with.
I'm sticking with Android for now since it offends me the least and I'll never, ever, ever use iOS (ever) since Apple is such an asshole to their customers and developers that I hate them with a passion. As a matter of fact, I hope Apple spends and loses all of their money on their car project. (Fingers crossed!)
Give me a phone where I have complete control please and stop trying to "protect" me. Until that time comes, I'll continue using only the most basic features of my so-called "smart" phone.
Funny story: I tried to install Microsoft's Exchange client for Android, and before it let me connect my account, it warned me that my organization would take control of my phone's security policy. The iOS version doesn't do that.
On iOS typically your organization does take control of your phone's security policy to connect to Exchange. I would personally prefer not to have 6 number passcode.
TouchDown also does this, but it's by Symantec and it's expensive as heck ($29.99). But it works well, and the container it stores your data in is encrypted and follows Exchange policy.
I need to look at Nine though, the big downside of TouchDown is it only lets you have one Exchange account on it per phone, and I have two different domains I need to connect to.
Ah, TouchDown is quite older yeah. Nine offers multiple accounts, costs 9.99$ now and is updated regularly with new features. For the cherry on top it also looks great.
It does the same on iOS, except silently. If you were already complying with the Exchange rules (i.e. PIN or password, as required by your sysadmin), you might not notice anything.
If you want a license to implement ActiveSync, enforcing Exchange policies is a mandatory part. Some licensees sidestep that by giving you option of enforcing Exchange policies at the app level, instead of device level, but they have to enforce it nonetheless.
I think you missed the point of the post you're replying to. What's the reason that you feel that you want to understand the "real technologies" that run the web? So that you can build better apps with those technologies, right?
So, what you really want to do is just build some apps, not learn CSS. See the difference?
If we had been talking about means vs. ends, I would agree.
However, we were talking about knowing HTML and CSS vs. knowing abstractions built on top of them. In that context I didn't interpret the post I replied to the same way that you did.
The person you were replying to did emphasized "wants to" vs "have to" though - so I think they were trying to insert the point about means vs ends. Anyway, whoever was trying to make that point - I think it's been made (however painfully).
Did you even read the article? The arguments still hold up. It's clearly the case that it's not worth the effort to move VS to 64-bit.
- "First, from a performance perspective the pointers get larger, so data structures get larger, and the processor cache stays the same size. That basically results in a raw speed hit..."
- "The cost of a full port [due to the amount of code involved, not the quality of the code] of that much native code is going to be quite high and of course all known extensions would break and we’d basically have to create a 64 bit ecosystem pretty much like you do for drivers. Ouch."
- "A 64 bit address space for the process isn’t going to help you with page faults except in maybe indirect ways, and it will definitely hurt you in direct ways because your data is bigger...32 bit processes accrue all these benefits just as surely as 64 bit ones."
You just had to come and shit all over Microsoft and make the same point that you already made up thread because uhhh, you call it like you see it...right?
Bullshit. More like you can't deal with opinions that don't match your own, especially when it comes to Microsoft and Apple. You're nothing more than an pro-Apple, anti-Microsoft fanboi.