And buy now page with tech specs: http://www.microsoftstore.com/store/msusa/en_US/pdp/productI...
Looks like $499 for 64GB storage and 2GB RAM, $599 for 128GB storage and 4GB of RAM (WiFi models; 4G LTE model pricing wasn't showing for me).
And buy now page with tech specs: http://www.microsoftstore.com/store/msusa/en_US/pdp/productI...
Looks like $499 for 64GB storage and 2GB RAM, $599 for 128GB storage and 4GB of RAM (WiFi models; 4G LTE model pricing wasn't showing for me).
4 GB is the minimum I'd run anything newer than Windows XP on. The SSD's speed might be able to "save" the 2 GB from being completely unusable, but it is still going to be damn slow with the amount of paging that's going to occur.
Honestly, I get that Microsoft wants to hit that magical $500 figure, but that device is going to give a really poor use experience in my opinion.
http://blogs.windows.com/bloggingwindows/2015/03/16/how-wind...
I'm hoping 10 comes out with a more refined understanding of modern OS expectations, especially when your OS is both a desktop and mobile OS. I find it amusing that 8 came out with this large install size when SSDs were becoming the norm. I guess Redmond can't move fast enough to avoid this outcome. They saw 1TB drives being the norm in 2009-2010-ish when they started this project and couldn't pivot fast enough to stop it. Now things like the sxs folder being 20gb is the norm. Or still defaulting to a 1996-like "make your swap file twice 2x your RAM size" mentality. I have 16gb of RAM. I sure as hell don't need a 32gb swap file.
The only reason I have a swap file is because DirectX seems to expect one for many games, so I have a token 512mb one just for gaming. No other application expects one. MS really needs to contemporize with Win10. There's just way too much legacy cruft in 7 and 8. Win8 on that sexy Surface hardware is like driving your Ferarri on a dirt road.
On Windows, every allocation gets reserved by actual memory, so it's easier to run into a situation where you would start failing malloc. So having swap is more important.
Also, I think that anonymous mmap is backed by the pagefile. So anything using mmap without specifying a file is going to increase your pagefile needs.
I'm curious: does anybody besides OS developers want this to be the case? I don't want the way I interact with a tablet to be the way I interact with a laptop or a desktop.
I run Chrome with a lot of tabs open on my Asus Vivotab Note and I don't really feel the pain of having only 2GB. I'm one of those guys with bad habits about closing tabs.
The thing you have to remember -- Atoms are serviceable CPUs, but they're nothing like the Core series. If you're looking to do heavy lifting, you should probably go for a Surface Pro anyways.
Have you considered switching to Firefox, which is a bit more conservative with memory usage? :)
iOS is extremely memory efficient but it comes at a cost which can be quite high for some.
Now, granted, the OS does use more RAM has availability increases (I have 16 GB) however Chrome is a beast no matter what.
But 2 GB? And maximum 4 ? Just kills me inside. Way to ruin the device.
My home workstation has 32GB and I can remote into that anytime I want from every device that I own, so I tend to lean on that.
But of course, the sad reality is that the only reason there is a 2 GB version is so that they can have a ridiculous premium for the 4 GB version yet still lure customers with the low starting price point.
I wonder if, when the market has matured enough, that there will be honest companies making products that tries to make good mainstream products rather than trying to get away with whatever they can. There is no reason what so ever that there should be any high-end smartphone available for purchase with less than 64 GB of storage. But now we have 16 GB and, for a $100 GB premium you get, gasp, 32 GB!
Phone storage has not gone up, in many cases down, in the last five years... And that's like 120 years in the tech world.
But hey, 2 GB of ram is certainly enough for the 5 min demo you get in the store...
I love having full control on a tablet that lasts 10 hours and fits in most of my pants and jacket pockets.
I've found 2gb to be perfectly usable with Win7 and 8, Chrome's voracious appetite for memory would be a sticking point, except I've noticed that it does a better job of managing itself when RAM is limited. Chrome runs just fine on 1gb Chromebooks despite having just 768-512mb available most of the time. I will say that the Atom processor is a concern with Chrome even though I know the latest versions are roughly 2-3x more powerful than the Pineview dual core I had in my old Dell netbook. Chrome routinely maxed out the processor on every page load while Firefox and IE never needed more than 25% of the available CPU horsepower. Tripling the available power would eliminate the 5 second lockups I experienced but it could still be a slow, stuttery user experience.
Nope. Windows grows over time. So a Windows install that fit into 40 GB would grow to over 100 GB over a two or three years.
Heck we had to pull an entire rack of servers because the idiots that set them up partitioned the drive into a 100 GB C: and a massive D:, and Windows consumed all the space on C: just through Windows Update and then started falling over.
We had to rebuilds the machines with a 200 GB C: and they have been running fine ever since.
Obviously user folders can grow quickly, but I wouldn't put the blame on Windows for that.
Windows installs themselves or with other software installed? The latter makes sense but I've never seen anywhere close in the former. 32GB would be a bad idea but 64GB I think is fine for the majority of people.
I just don't think 32GB is big enough in general minus some space for the OS but I don't think I've had the same type of issue as you. The majority of my OS installs have been roughly 10GB which isn't far off from iOS and might include some restore stuff. But it's also been a while since I checked.
That really depends on your use case.
I've been using the Asus Vivotab Note 8 for several months (2gb/64gb), and I haven't even come close to feeling a need to put an SD card in it yet. I use it as a complement to my laptop. Mostly for consumption, communication and note-taking with OneNote. I don't think you'd want to do any heavy lifting on an Atom-based machine -- you'd be better off with a Pro in that case.
I'd love to see Microsoft release a Surface Mini with that Surface Pen. Having a Wacom pen on my Vivotab is great, except at the edges.
I may end up replacing my t100 with the 128 GB surface 3, especially given the small price difference.
If you're a Pro, then buy a Pro or get a MacBook Pro and VM Windows.
But as just a tablet, this is _close_ to a great deal (I think they can do better and probably will drop the price by the holidays).
Like Dell XPS 11
2560 x 1440 display
4GB RAM
128GB SSD
http://www.officedepot.com/a/products/665236/Dell-XPS-11-XPS...
http://www.dell.com/us/p/xps-11-9p33/pd?p=xps-11-9p33&view=p...
Photoshop (since it was also mentioned) has very limited support for real scaling (beyond the OS's default of render as if on a low-dpi screen and then bitmap scale the UI up, which looks horrible, especially when combined with an app you are using to do precise bitmap editing) -- the only meaningful option it gives you is to scale everything in the UI up 200%, which is better than nothing (and what I have to do on my 3840x2160 Toshiba laptop to get a usable UI), but not a really flexible solution and even this is considered an "expirmental feature" in the very latest version.
Adobe Lightroom, on the other hand, has effortless scaling and just works great on screens at any DPI.
The point being there is plenty of support in the OS for apps that effectively scale, it is just that there are a lot of Win32 legacy apps out there which would require a near rewrite of the UI layer to scale well, it is by no means something the OS handles for you automatically (beyond the clumsy bitmap scaling default) if your code targets the older UI APIs, and there are (still) plenty of gotchas you do actually run into when running Windows apps on high DPI screens, though things are certainly improving in this regard.
Even in Windows 10, the new update has issues with scaling. It now caps out correctly (1920 x 1200), but it is blurry as hell.
Edit: It was about 3 pro ... ignore.