I'll see you both in court.gravy wrote:For your cassandraesque warnings [...]
Microsoft Surface : their tablet
- Absolute_Zero
- Baaaaaa!

- Posts: 3564
- Joined: Wed May 18, 2005 4:11 pm 0
- Location: Hilbert Hotel, Heisenberg.
Re: Microsoft Surface : their tablet
- Portland
- Baaaaaaa!

- Posts: 8828
- Joined: Thu Apr 06, 2006 8:16 am 0
- Location: Swinton, South Yorkshire
Re: Microsoft Surface : their tablet
For mild amusement, search Amazon for Microsoft Surface
Portland 3.0.1.0 public release rolled out
Re: Microsoft Surface : their tablet
Portland wrote:For mild amusement, search Amazon for Microsoft Surface
- pogo
- Sheepie Whore

- Posts: 14180
- Joined: Tue Sep 10, 2002 8:28 pm 0
- Yahoo Messenger: BrassSparrow
- Location: County Durham
Re: Microsoft Surface : their tablet
More on memory: Ars digs deeper
Surface disk space: a bit better, and a bit worse, than Microsoft says
I don't get the headline though. They redo the calculations and confirm you get 46GB on the 64GB device, but add 1GB for 17GB free space on the 32GB model. This seems to be down to the confusing way MS reports free memory though, with GB meaning both 10^9 and 2^30, as well as rounding errors. So a bit better, or maybe no different just calculated differently.
But it's far worse the other way, e.g. once you start installing apps. Installing the Office update that patches it to the final version takes up to 1GB. Installing any other app then updating it fills up memory as it keeps old versions around which seems insane on a device with memory costing $100 per GB.
And adding an SD card doesn't help much: not only can you not put apps on there but content there can't normally be seen by apps:
Surface disk space: a bit better, and a bit worse, than Microsoft says
I don't get the headline though. They redo the calculations and confirm you get 46GB on the 64GB device, but add 1GB for 17GB free space on the 32GB model. This seems to be down to the confusing way MS reports free memory though, with GB meaning both 10^9 and 2^30, as well as rounding errors. So a bit better, or maybe no different just calculated differently.
But it's far worse the other way, e.g. once you start installing apps. Installing the Office update that patches it to the final version takes up to 1GB. Installing any other app then updating it fills up memory as it keeps old versions around which seems insane on a device with memory costing $100 per GB.
And adding an SD card doesn't help much: not only can you not put apps on there but content there can't normally be seen by apps:
But music and photos are precisely the sort of content you want to put there, as they tend to be the things that fill up a phone or tablet. Great for MS upselling the higher capacity version, not so good for users.Due to the sandboxing and security used in Windows RT, apps need special permission to use this removable storage. Apps that just have permission to access your music, picture, or document libraries can't use the SD card.
Re: Microsoft Surface : their tablet
So, the mistake Nintendo made (and later had to fix) years ago then.And adding an SD card doesn't help much: not only can you not put apps on there
-
want to read eye-wateringly bad stories? No? Ok.
want to read eye-wateringly bad stories? No? Ok.
Re: Microsoft Surface : their tablet
But it /is/ "no solution at all". Force the user to micromanage storage of data, and (usually) break in a horrible manner if stuff suddenly disappears.Dio wrote:The antiquated naming is certainly clumsy - but what's wrong with the paradigm? It seems likely to me to be far less confusing to the average user than, say, mount points, and seamless knit methods (as Windows does with local / roaming data, for example) suffer from the problem that it's hard to determine what's on what.tufty wrote:Hope, of course, but fully expect `D:\`...
In the absence of a perfect solution, it's still better than no solution at all.
Firstly, we're talking about storage space that might, or might not, be available at any given time. For SD cards, that's unlikely to be much of an issue (I can't speak for the majority of people, but I personally remove the SD card in my Android tablet approximately "never" - it might as well be a permanently attached piece of hardware), but there's also USB based storage, dropbox or other "cloud" based solutions, and so on.
So what's needed is a solution that can deal with anticipated (or, in the worst case, not) removal of a physical storage device.
Micromanagement of where to store stuff is something that can and should, in most cases, be left to the operating system, or rather, the file system layer of the operating system. OSX's file system, for example, handles the micromanagement of where on a device to store "hot" data, there's no reason that this couldn't be extended to handle multiple devices if we weren't so intent on sticking with the antiquated concept of a hierarchical filesystem. Newton got this almost right in the early '90s, as did BeOS, and I had high hopes for WinFS that was supposed to be coming with Longhorn. File systems should be journalled, should automatically union mount themselves, and they should be databases, not some arbitrary hierarchy of random crap.
In most cases, the user should simply say "store this", and the OS should store it in the most reasonable place. Obviously, the user should also be able to say "share this with the 'net", or "store this where I can use it on another machine", "store this where it will always be available" or "store this on this specific removable device", but the most common use case is, surely, "store this".
Dealing with (un)anticipated removal of devices is relatively easy to deal with as well. For small files (where "small" is below some configurable watershed), the system should make sure that the data is somewhere that's guaranteed to be available at all times, at the point where the file is opened. In short, if I'm opening a file in order to mutate it, it should be copied to "local" storage beforehand, "shadowing" any existing copy on removable storage, and then copied back (if possible, and perhaps only if necessary) when we're done.
There will always be edge cases, usually to do with sudden disappearance of storage, but they can be alleviated and certainly shouldn't cause crashage.
"massive retard™", "full of shit™", "tiny bitch™", "retarted™", "a bit of a one trick pony™", "petty™", "simple minded idealistic twat™", "miserable humourless fucker™"
Re: Microsoft Surface : their tablet
I don't think it's no solution, because a deficient model it may be but it's one that the average user has a conception of because it relates almost entirely to physical objects, which is certainly not true about merged folders or mount points.
I'm still unconvinced by the value of database storage versus hierarchical storage. I tend to believe that there's only one valuable piece of metadata about an arbitrary file, which is its identifying handle (including its location). Everything else is more likely to be wrong than right. Sure, you can have that as metadata in a database.
Of course, I'm an obsessive organiser so for me location is valuable information, which I'll concede probably isn't true for the majority.
Capturing all the corner cases with anything removable - not just storage - is extremely hard.
I'm still unconvinced by the value of database storage versus hierarchical storage. I tend to believe that there's only one valuable piece of metadata about an arbitrary file, which is its identifying handle (including its location). Everything else is more likely to be wrong than right. Sure, you can have that as metadata in a database.
Of course, I'm an obsessive organiser so for me location is valuable information, which I'll concede probably isn't true for the majority.
Capturing all the corner cases with anything removable - not just storage - is extremely hard.
- gilesgoat
- Sheepie Whore

- Posts: 27259
- Joined: Wed Sep 03, 2003 7:54 am 0
- Location: Monfalcone, Italy
- Contact:
Re: Microsoft Surface : their tablet
I would say there's no "one size fits all cases solution".Dio wrote:I don't think it's no solution, because a deficient model it may be but it's one that the average user has a conception of because it relates almost entirely to physical objects, which is certainly not true about merged folders or mount points.
I'm still unconvinced by the value of database storage versus hierarchical storage. I tend to believe that there's only one valuable piece of metadata about an arbitrary file, which is its identifying handle (including its location). Everything else is more likely to be wrong than right. Sure, you can have that as metadata in a database.
Of course, I'm an obsessive organiser so for me location is valuable information, which I'll concede probably isn't true for the majority.
Capturing all the corner cases with anything removable - not just storage - is extremely hard.
I think "data" is not only "data" it also depends a lot "what is data for you and the application that sees it", as in "it may
be data + metadata for ( some ) human users dealing with it, it may still be 'just data' for the OS working with it".
I am always a bit 'skeptical' when "things begins to be a bit too much complicated" at the point where "only a machine
can deal with them", I mean "get this file, copy it there" anyone can do it, "get this thing attached to a database/jounalling
system/etc. " only a machine can do it.
There one system or another can lead to more/less benefits depending on what you do and want to do.
I still find "an extreme feeling of joy" when all my data is simply copied into some big USB key somewhere and then
left into a safe place and that can be done very easily N times, away from the internet, away from a potentially crashing
machine, into a media that is cheap and store and easy to carry whenever needed.
The world can collapse, all the clouds can fail all the database servers can crash .. BUT .. I'll still be able to browse and
watch my huge MLP collection
Giles the billy goat
"Baa"
"Baa"
Re: Microsoft Surface : their tablet
Exactly what metadata do you currently have in your filesystem?Dio wrote:I tend to believe that there's only one valuable piece of metadata about an arbitrary file, which is its identifying handle (including its location). Everything else is more likely to be wrong than right. Sure, you can have that as metadata in a database.
File name - this encodes one and only one of a multitude of "handles" the user might want to attach to a file, along with an extremely poor representation of file type (which you can't necessarily rely on anyway - there's nothing stopping the user renaming, for example, "swap.avi" to "annual accounts.xls").
Location - "where the file is".
Owner / group and permissions.
That's it. Nothing else. In addition, this encoding is mixed up for system and user files - for user data, location and name are arbitrary bits of metadata - if you change them around you might have trouble finding your files or launching the right application to handle them, but for system data you can quite easily hose your entire installation, and there's very little that stops you actually doing it apart from convention. Further metadata /is/ available from within applications (think email clients that allow you to search on arbitrary fields, for example) but that's application-specific - we should be moving away from an application-centric approach and towards a data-centric one.
The situation as it stands is lamentable. Reinventing the file system could be one of the most important steps forward in productivity terms since - umm - I don't know - we seem to have pretty much stagnated in terms of business software since the late '90s anyway.
Indeed. But that doesn't mean we should just say "it's a hard problem, so let's ignore it".Dio wrote:Capturing all the corner cases with anything removable - not just storage - is extremely hard.
I'm a fervent believer that we should be making things better, not just making more of the same. Unfortunately, the industry seems tied to the idea of making more of the same.
"massive retard™", "full of shit™", "tiny bitch™", "retarted™", "a bit of a one trick pony™", "petty™", "simple minded idealistic twat™", "miserable humourless fucker™"
Re: Microsoft Surface : their tablet
You know, I think MS would agree with you right now but there are many people who would rather have Windows 7 but faster.tufty wrote:I'm a fervent believer that we should be making things better, not just making more of the same. Unfortunately, the industry seems tied to the idea of making more of the same.
- Deckard
- Sheepie Whore

- Posts: 10748
- Joined: Fri Jun 18, 2004 11:27 pm 0
- Location: Falmouth, Cornwall, UK
Re: Microsoft Surface : their tablet
So I'll take that no-one here has bought one as I asked earlier ? - Cant be a good sign for MS if us lot havent bought one between us......
Now with a new Mac Mini Pro so dont judge me !
- sack
- Baaaaaaa!

- Posts: 7077
- Joined: Fri May 10, 2002 4:13 pm 0
- XBL Gamertag: evilgopher
- PSN: sixFiveOhTwo
- Location: Rijswijk, The Netherlands
- Contact:
Re: Microsoft Surface : their tablet
it's interesting to see the performance figures on these tablets:
http://www.anandtech.com/show/6385/micr ... -review/10
It looks like the Intel Clovertrail outperforms the Tegra-based tablets and is the one to get
http://www.anandtech.com/show/6385/micr ... -review/10
It looks like the Intel Clovertrail outperforms the Tegra-based tablets and is the one to get
Re: Microsoft Surface : their tablet
That's closer (between Arm and x86) than I'd have expected.
Re: Microsoft Surface : their tablet
It's not, given how slow in-order x86 is
.
Re: Microsoft Surface : their tablet
Different is not the same as better though, especially when "different" is pretty much copying trends from the mobile market.venusian wrote:You know, I think MS would agree with you right now but there are many people who would rather have Windows 7 but faster.tufty wrote:I'm a fervent believer that we should be making things better, not just making more of the same. Unfortunately, the industry seems tied to the idea of making more of the same.
Very, very much agree.The situation as it stands is lamentable. Reinventing the file system could be one of the most important steps forward in productivity terms since - umm - I don't know - we seem to have pretty much stagnated in terms of business software since the late '90s anyway.
-
want to read eye-wateringly bad stories? No? Ok.
want to read eye-wateringly bad stories? No? Ok.