5 ms·
Beware Apple, Google: Microsoft is starting to get it.
by r00fus 13y ago
Beware Apple, Google: Microsoft is starting to get it.
- _random_ 13y agoGoogle has universal apps? When will they get 'it'?
- shashwatak 13y agoChrome, and thereby all Google webapps, run on every major OS.
- _random_ 13y agoWhat about their tablet and phone OS - Android? Is there an app-store for those 'webapps' (not the Chrome app store)?
- hayksaakian 13y agocoming soon TM so far they've been working with phonegap to allow porting packaged apps to phonegap (to then package for specific platforms) http://phonegap.com/blog/2013/11/21/chrome-apps-pgdayeu/ http://phonegap.com/blog/2013/11/21/chrome-apps-pgdayeu/
- dragontamer 13y agohttp://tctechcrunch2011.files.wordpress.com/2014/04/img_20140402_104055.jpg?w=738 http://tctechcrunch2011.files.wordpress.com/2014/04/img_2014... Yes they are. Windowed Metro-apps, and legitimate Start Menu with decent Metro live tile integration (and a shutdown button) I was hoping that they'd have jumplists back on the startmenu, but lets see what they come up with...
- taiki 13y agoWhat about the internals? Is it still kind of a mess under the hood? I heard they rebuilt the TCP/IP stack so it's not user land 32 bit driver anymore. Any ideas if/when they'll modernize NTFS? Right now it's a race to the bottom to who has the worse FS, HFS+ or NTFS. WinFS or ZFS on OS X would be a godsend. What about the registry? Any idea if they'll make that easier to manage for regular people? Am I still fucked if it corrupts? What about sunsetting Win32? Or improving the driver model? They're starting to get it on the UI side, but the reason why I use Mavericks as my personal machine and work on a LAMP stack has less to do with how useful or pretty the start menu is, and more to do with the godawful internals of Windows. Or have we just resigned ourselves to a crappy OS internally that we've all just gotten used to?
- chokolad 13y ago> Any ideas if/when they'll modernize NTFS? Right now it's a race to the bottom to who has the worse FS, HFS+ or NTFS. WinFS or ZFS on OS X would be a godsend. http://blogs.msdn.com/b/b8/archive/2012/01/16/building-the-next-generation-file-system-for-windows-refs.aspx http://blogs.msdn.com/b/b8/archive/2012/01/16/building-the-n...
- taiki 13y agoYou mean like WinFS? I'll believe it when they ship it. EDIT: Retracted. Looks like it's actually going to ship with Win8.1
- bananas 13y agoNo it's rock solid underneath. The TCP stack hasn't been a 32-bit driver since XP. NTFS has been modernised already: http://en.wikipedia.org/wiki/ReFS http://en.wikipedia.org/wiki/ReFS The registry is fine - it's people pissing around in it that break it. Win32 - haven't touched it for years. Driver model: not my problem. Mavericks is a crime compared to windows 8.1. I use both, regularly. It's virtually impossible to use efficiently with a keyboard unless you have twisted mutilated hands to hit meta keys galore and half the apps don't actually survive more than 2 minutes without crashing.
- taiki 13y agoI should've been way more clear about my gripe with the Windows TCP/IP stack. Why the hell does the TCP/IP stack eat itself? No other OS I've ever used has the nuttiness that is netsh winsock reset as a regular troubleshooting step when diagnosing network connectivity issues. I was long under the impression that the reason why that kept happening was that the NT kernel didn't have a robust TCP/IP stack of its own and was reimplementing the BSD sockets via a translation layer that was easily hooked into by godawful apps that felt like putting whatever it wanted there. ReFS wasn't on my radar, and that's my fault. The registry isn't fine. As of Windows 8 it can still hose a machine by going corrupt. The concept of having a centralized application database for application state and other metadata isn't a bad one, the current implementation absolutely sucks. It goes corrupt and the entire machine is rendered useless. Granted, the current solution is to just back it up and hope none of the backups corrupt either. Corruption doesn't happen from just people manually messing with it, corruption happens from a lot of apps reading and writing from it at the same time. A lot of apps not even bothering with good practices in how to handle it either. As far as Win32 and the driver model not being your problem... When crappy apps written in 20 year old APIs and devices using crappy drivers crash your machine, then it absolutely IS your problem. I can't speak to your use of OSX with a keyboard. However, given my choices, I'll take weird metakey combos over, "Is my TCP/IP stack going to eat itself this week?" Besides, emacs uses nothing but crappy and bizarre meta key combos and it's still a thing. So.