Testing the 12-inch MacBook's Performance with Windows 10
alexvking.com
alexvking.com
So much this. I really admire how performance of Windows desktop is optimized. I can't compare it with OS X, but when compared to modern Linux DE's (Plasma, Gnome Shell, Cinnamon etc.), Windows desktop still has all the same modern bells and whistles (hw acceleration, effects etc.) yet it blows them out of water when it cames to both smoothness and resource consumption.
I say I admire the effort on optimization, because things weren't that good even on Windows 7. I remember constantly having slight stuttering here and there on Windows 7 but Windows 8+ is completely smooth on the very same machine (which is now getting close to its 6th year), and this anectode shows that they must have taken the optimization seriously.
P.S: I'm not complaining on Linux DE's, they just have different priorities, and they're good deals considering their price.
I'm not going to debate this, but I'll just try to assign blame. It goes one place: X.
As long as they all build on X, things will be suboptimal and I can't wait for initiatives and projects like Wayland and Mir gain more traction.
If you doubt anything I say about X, please watch this youtube video which has one of the key X-maintainers complain about how bad it really is:
I mainly use Firefox, the Terminal, Gimp and Libre Office. No performance problems whatsoever. And I have pretty old machines. An over 5 years old lenovo laptop and a similarely old desktop machine.
The obvious answer to experience those problems is to setup your system the same way as the people experiencing the problems, same h/w, s/w config, etc. You can look at the configs of people reporting problems on forums, in bug reports, etc.
Beryl and Compiz? I beg to differ. Besides a bitch to get running, and get running well, they were not at all comparable to Vista with regards to "resource consumption" and "hardware support".
At some point, "they" started to rewrite compiz, and it went downhill, until it was so slow I could not use compositing anymore.
It's the old CADT [0] monster still at work. Windows desktop is the same old explorer shell which has been there since 1995? Only addition is dwm, which provides the modern graphical facilities. And Windows team has been constantly improving this same codebase for 20 years now.
While on the FOSS side, desktop developers are busy with the sisyphean task of rewriting or porting desktop shells and base applications again and again. OH, they've released a new version of graphics toolkit and the old one is deprecated. We must port the desktop now. Oh we also have to port all the applications now. Some applications were so hard to port that we've abondoned them and rewrite them instead. Actually, why don't we also rewrite the desktop shell while we're at it? Promise it'll worth it. We ported old apps but they're not consistent with the new ux paradigms of the new desktop so we'll rewrite them also... And just few years later when things start to calm down, there's a new release of graphic toolkit which will eventually deprecate the old version, ... oh not again.
Notice that I'm not talking about fragmentation or lack of resources. I'm glad we have more than one major DE, and I don't think more resources or less fragmentation would change anything regarding the situation above. Even with lack of resources, linux desktops had long long time to create really high quality products but they can't, because the ground below them is always shaking. Windows team on the other hand has been vetting, fixing, improving the same codebase for 20 years. They don't change the underlying toolkit every 5 year. They don't rewrite basic applications or port them to new libraries over and over (except new metro things, but they're seperate so my point still stands). Imagine what we would have now, if Gnome devs continued to polish and improve Gnome 2 and KDE devs continued to polish and improve KDE 3, just by using the same resources they've poured into Gnome 3 and KDE 4/Plasma 5 and their applications, respectively.
Again I'll emphasize, I'm grateful for the efforts that went into linux DE's, and I don't blame their developers for shit they have to deal with (although some are partly responsible for it)
That was a long rant and thanks for listening.
Well, as far as I can tell, lots of Linux people are hipstery special little snowflakes and fork things because some small thing isn't exactly as they want it, and that's where most of the fragmentation comes from.
Assuming that's largely accurate, why would it not be a problem?
What if we had, say, three major Linux distros instead of dozens of half-assed ones? How many tinkerer-distros does the world need? -As many as it takes to prevent Linux from ever conquering the desktop, it seems.
But seriously.. Please stop.
My above statement was specifically about the desktop environments, and DEs actually fit into your scenario. There are only 2 major DEs which have most mindshare, followed by handful of smaller ones. So there is not a bad fragmentation in that area (at least historically, there is now more diversity compared to 5 years ago), and the major ones have been with us for many years, AFAIK since late 90's? That's not only plenty of time to turn both of them into kick ass desktops, but also create wonderful ecosystems around them with high quality applications. Yet all we see is rewriting or porting everything every few years.
PS: Linux is widely used everywhere except traditional 'desktops'. Existing mainstream DEs are pretty good (KDE5/Gnome 3.16/MATE 1.8) and provide a range of choice.
Safari on Mac OS is extremely smooth, from the looks of this blog it seems Microsoft has replicated that in Edge browser. Look forward to trying it.
Disclaimer: Microsoft employee working on the Windows 10 Start menu.
Sigh.
The start menu is great code but mom and pop dev shop doesn't have hundreds of top devs available :)
My current workaround is to lock the computer and unlock it again. This seems to work but it's really annoying.
It only occurs on my desktop PC and not my Surface (which has issues of its own).
Any clue if there's anything I can do here or should I just wait?
And just FYI, we do look at the stuff that gets submitted through the built-in Windows Feedback app.
They are all known issues but shell developers blame proprietary Nvidia driver, maybe that's why you are more happy with gnome shell than I am :) (Though I still can't get how cpu usage skyrockets when dragging windows.)
I know that gnome successfully offloads work to the GPU when I drag the windows [1] because I can hear it [2].
I don't have kwin installed, so I didn't compare.
[1] Yes, I also did move them wildly, too.
[2] My graphic cards has serious coil whine issues.
The overall user experience is smooth and pleasant. I doubt if Windows 8/10 would install on this machine (although it came with Windows 7). I have several Thinkpads of this vintage for the keyboards, not needing super powerful processors.
I'd say the same about a phone, but I don't spend my day staring at my phone.
Given the prevalence of touch devices these days, I'm surprised that I don't hear this complaint very often.
However on a serious note, its not as bad as you think. Just have to get used to it and once you do that, there won't be a going back. Think of it as something that is supposed to complement your existing workflow and not as something that would replace it. You know like have a voice assistant on your phone, you don't have to yell everything at it, just some quick look ups.
I want to be able to disable it entirely and not smudge the crap out of a screen I'm trying to work on, but it's effectively impossible and when you do disable it it all falls back to keyboard controls and leaves you with a garbage pen exeprience.
So that means by default high battery drain, heat issues, and having to manually switch on the discrete graphics card by hand every time you visit a 3D-utilising website.
People have been complaining about no auto-switch in Windows on Macbooks for years, yet they haven't fixed it. Tons of other laptops already support it (inc. Thinkpads).
Apple keep Windows "bad" on Macbooks on purpose. It is the only explanation for all the driver issues they have (but no other laptop manufacturer has).
1. The developer requires that you put windows into "test mode" (creating a non-removable desktop watermark) to install it at all, apparently to get around code signing restrictions
2. The developer requires that you install the completely useless "Power Plan Assistant" program in addition to Trackpad++
3. The software itself is terribly buggy, causing random 100% CPU usage spikes
I've heard good things about the new XPS trackpad, but haven't been able to try one in the wild yet.
So, just name one laptop whose trackpad is better than an rMBP, I'll go try it side by side.
So, it seems that in this case a beta version of Windows works best than MacOS
I don't use windows So I'll also have to ask, are these programs actually comparable in what they do ?
However, Win 10 runs quite inefficiently on Apple hardware in terms of battery life.
On a side note, I find Win10 as the first Windows that is usable on HiDPI machines.
An influence from its gaming heritage? I know that GPU companies definitely spend a lot more effort on improving their Windows drivers than on other OSs, because of gamers.
If I'm a bit cynical, Apple is deliberately refusing updates just so they'll be able to tout huge 20% performance improvement of their proprietary Metal when they bring it to OS X.
I have been using MacOS of various stripes since 1990 (I am a biologist by background and biologists were one of the few groups that stuck with macs through the late 90s). Other than 10.1 Yosemite is the buggiest OS 10 release to date in my experience.
The same kind of stories I've heard for every release since 10.4, about how the new one is so buggy, etc. Then, the next release comes and people wax nostalgically about how stable the previous one was.
It also is a memory hog compared to Maverick and earlier. 4GB machines are noticeably sluggish (to the point of user complaints).
I've not have had any crashes yet. I had a few in Mavericks and Mountain Lion (grey screen about needing to restart etc) -- like 1 or 2 a month.
a) Battery life on my macbook pro plummeted after the upgrade.
b) I get visual artifacts (black lines on screen and some flashing) when OSX auto switches between the intel gpu and the nvidia gpu.
c) Cannot get nfs transfers to work with acceptable speeds (they seem to top out at 2 MBPs)
d) Broke drag and drop in Qt because of some changes to the string supplied to the drop event.
e) Bottom of my macbook pro gets unacceptably warm. I dont recall it being this bad before the update.
b) Seen some occasional flashes. Not sure why it happens, but I think it's related to the color temperature mananging "Flux" app (they seem to stop when I don't use it).
c) Sure not some network problem? I've had succesful NFS transfers, but usually small files, so never bothered to check.
d) Shouldn't Qt fix it? If it didn't broke drag and drop in native apps, then Qt emulated it based on some assumptions that weren't guaranteed.
e) Never had this happen, even when using Compressor on all cores. Top left might get a little warm at those times.
That said, in Task View on Windows do the iconified windows still play live content? E.g., under mission control, a video window will continue playing video live in its preview texture. Does this happen on Windows too?
The Cortana feature is slick and I'm tempted to cancel my Amazon Echo order and get a Surface (which has a free Windows 10 upgrade).
I was never a fan of the OSX Dock. When switching between apps, I always misclick and startup a new program accidentally. I prefer the traditional windows dock. Two features I would surely miss if I switch back to Windows would be in-app window switching (cmd ~) and the placement of of the cmd key on the Mac keyboard versus the awkward stretching of my pinky finger to reach the control key on Windows.
That was what Windows 8/8.1 tried to do, but apparently people didn't like at all ( never understood that, to me is a fine OS)
I think the whole thing is very subjective. I have a way better UX with Windows 8/8.1 that I had with Win7 and with OSX.
The change resistance effect should not be dismissed too, people tend to be scared when a change is dramatic.
"People didn't like it because it wasn't adaptive to the present use. The tablet and desktop views were the same"
Isn't that more 'multiple similar UIs in a single executable' than 'same UI on tablet and desktop'?
If so, it seems the only difference with OS X/iOS is that Microsoft thinks a tablet now is powerful enough for desktop applications. Looking at size and weight of the latest MacBook, they probably are right.
This is the thing I and many other Windows users hate with passion, see rants like this:
https://www.reddit.com/r/windowsphone/comments/35zsgk/excuse...
https://windowsphone.uservoice.com/forums/101801-feature-sug...
https://windows.uservoice.com/forums/265757-windows-feature-...
https://windows.uservoice.com/forums/265757-windows-feature-...
Some people initially have strong negative reactions to something familiar changing but those tend go away quickly as the new version becomes familiar and then the same people will rant about the next version. Remember the “Fisher-Price My First OS” jokes when Windows XP came out? I'd bet you could find similar cracks at Windows 7 from some of the same people who are now saying the XP UI was the Platonic ideal of Windows.
ArsTechnica actually did the legwork looking through their forums when the now-staunchly-defended Windows XP was approaching EOL:
http://arstechnica.com/information-technology/2014/04 /memory-lane-before-everyone-loved-windows-xp-they-hated-it/
[1]: http://blogs.windows.com/bloggingwindows/2015/04/29/windows-...
Profile pictures I've used are a photo of my computer, a still from a movie, an animated GIF of a flying pig (alas no one I know of supports animated profile pictures), and yes even a photo of myself every once in a while.
That said, complaining about the shape of the profile picture is pure bikeshedding. Big deal. How much time on your computer do you spend staring at your own picture? (Please don't answer that.) Although if given the choice I'd prefer rectangular. My computer screen is a rectangle. The area reserved to display the picture is a rectangle. Does a click in the invisible rectangle register as part of the picture? And most of all, it's easier to crop a photo to appear circular when displayed in a rectangle than it is to show a rectangle inside a circle. So the "safe" default should be a rectangle.
Here's a quora thread from back in 2013 discussing it:
http://www.quora.com/Why-are-many-UI-designers-using-round-p...
windows 8 with touch enabled devices is another level. even if you only ever use touch so little. with touch and pen it's another level yet.
I've used Linux laptop with touch screen hacked in since 2006. had tons of tweaks. and win 8 still bowed me away. it is even integrated with a remote desktop (RDP) client on ios and android. when i connect to my HTPC in the living room (only place i have a reason to have windows installed) the touch input from the tablet just shine. i can use the remote device as if i was holding a surface 3 or something. there's no hacks and extra menus on the client to do anything. just touch solves all the needs you have to use the box
Step two: If on !Win10, use the chocolatey nu-get package manager (https://chocolatey.org/), but if on Win10, I _think_ the native package manager will be a drop-in, tho I'm not sure.
That is literally _all_ you have to do to get 90% of what I do on a linux terminal into a windows console.
[1] http://sourceforge.net/projects/pycmd/ [2] http://unxutils.sourceforge.net/
There is a performance hit because it has a an M-5Y10 instead of an M-5Y71.
Depends how much you want to pay to look "hipsterish". I would pay more to look non-hipsterish ;-)
More details: http://www.anandtech.com/show/9117/analyzing-intel-core-m-pe...
It's also driving a 34" screen right now, and not breaking a sweat. http://imgur.com/WvGwGo9
Also, I think he meant to say "Cmd+Shift+4" as the OS X screenshot shortcut or "Cmd+Shift+Ctrl+4" to copy screenshot to the clipboard.
I believe the shortcut you're looking for is Cmd+Shift+S. Courtesy of OneNote, it's the equivalent of Cmd+Shift+4 on Mac OS.
I use Windows for .Net development only. When it comes to programming Ruby, or just to surfing the web, I prefer Mac OS X. The UI/UX for Windows really sucks comparing to OS X. No gestures support, you'll need to use mouse instead of TrackPad.
You can tune your Windows (use third-party tools like trackpad++, write some autohotkey scripts), but you won't get this feeling that you're at home.
(FYI: I'm ~4 year Mac user and I've been using Windows/Linux since 1994).
Apple wants Windows to be worse than OS X on Apple's hardware. That's what it really boils down to. They're either apathetic or want people to believe that OS X is inherently better.
GDI+ is the culprit here more than any one company's driver. Windows won't have an as-nice-as-OS-X experience with touchpads until GDI+ is either overhauled or dead and buried. Which makes me sad, because there are really nice things going on with Windows right now, but the feel of using it is janky and weird to me.
For the longest time I just attributed it to software - I'm hopeful that the next version of OSX is able to optimize for HDPI displays.
I ask because out of the specs the gpu seems integrated and quite low-power (for the resolution it runs at.)
Otherwise, if you have a very busy webpage with a lot going on, (and ads going), scrolling might not be entirely smooth.
I suppose the author bought a Windows 8 (the articles claims that he did a clean Windows 10 install starting from Windows 8) license at some time in the past, since a Mac doesn't come with a Windows license.
If he wanted to have a nuanced conversation about OS architecture, he could talk about something specific rather than huge generalizations with terms which make it clear he doesn't know enough of the details to be qualified to make such broad statements.
Similarly, talking about one benchmark on one device for a feature which many people don't even use is not a good foundation for comparing the merits of entire operating systems. That's like saying you should buy a particular car because it has awesome door handles, as if there are no other possible factors which you need to consider.
In comparison, Windows 10 has its roots in the Windows NT lineage (starting with NT 3.1, and including Windows XP), which is separate from the DOS-derived Windows line that ended with Windows ME.
(That said, I agree that he was just trolling.)
Mach is not a Unix kernel and the Mach interfaces percolate up to the higher levels for many tasks which aren't covered by the POSIX layers.
The bigger difference, though, is higher up. While you certainly can compile POSIX code on OS X, most of the applications which people run use Cocoa and that owes far more to the NextStep side of its lineage than the Unix bits.
The better comparison might have been Win32 rather than DOS, where most of the interfaces were designed by the Win95 developers even though they were also implemented on top of the NT kernel. I've often wondered how much better things would have been in the late 90s/early 200s if David Cutler's team had been able to get the Win95 team to follow their generally much better instincts rather than the other way around. If nothing else, they wouldn't have needed to spend a decade duct-taping security onto a single-user design.
Microsoft has always been dominated by backwards compatibility constraints so there probably wasn't much scope for a massive redesign of the API, as it was in their best commercial interests for 16 and 32 bit Windows APIs to match as closely as possible, to ease porting of third party software.
http://blogs.msdn.com/b/oldnewthing/archive/2003/11/03/55532...
That's a bit silly but it also meant things like dutifully porting the real-mode Windows messaging system's feature which allowed any app to execute code in any other app:
http://en.wikipedia.org/wiki/Shatter_attack
Like, say, sending a message to the anti-virus software running as SYSTEM to get root…
The most entertaining bug I found was one of the times they failed at portability: one of the Win32 APIs to enumerate the contents of a directory worked 100% of the time on the Windows NT systems our development team used but returned no results on Windows 95 unless you had enabled network sharing (you didn't even need to share something; just starting the service was enough). This manifested in a very confused user wondering why our open dialog showed C:\ as empty when Explorer showed their files were still there.
OSX is a strange OS to use. It looks and feels good at first glance but when you have used it for a year, one really longs to return to a pure Windows environment. OSX has weird bugs like the beachball cursor which is something that simply shouldn't happen in a modern OS. The last Windows to have a global lock like that was 9x.
Mach is not an “old era Unix kernel” and OS X is not exactly a vanilla Mach:
http://osxbook.com/book/bonus/ancient/whatismacosx/arch_xnu....
It has a BSD subsystem but plenty of other different things, like a completely custom device driver model (IOKit).
Secondly, you just called everything above the level of the kernel a mod, when that's where most of the code and almost all of the significant differences live. Is Android also “just a mod” on top of Linux?
> OSX has weird bugs like the beachball cursor which is something that simply shouldn't happen in a modern OS. The last Windows to have a global lock like that was 9x.
Windows 10 and most X window managers have the same thing for the same reason: you see the busy cursor when an application stops responding to events within some defined timeout. It's not due to the Win95/Mac OS Classic-like “global lock” you're thinking about but rather access to an unresponsive shared resource. I most commonly see it due to either doing blocking network I/O in the main thread (e.g. Outlook) or making the mistake of assuming that the filesystem won't block which affects just about every app with a network home directory or flaky drive, but it's also common with things like web browsers using a large cache directory where the startup blocks for awhile while the file system churns through millions of files.
The beachball is a very infrequent occurrence on OS X, and if it does happen, it usually doesn't freeze the whole shell. If you're seeing it a lot, this is often an indicator of faulty hardware. That being said...
> This literally never happens on Windows.
Not true, the exact same thing can and does happen on Windows, with similar rarity.
> Also all IO on Windows is asynchronous. It doesn't support synchronous IO.
I'm not super-familiar with Windows IO, but at the very least it has blocking, synchronous C stdlib file I/O, and blocking, synchronous WinSock network I/O. Also, anything asynchronous can be trivially be made synchronous, whether it is a good idea or not.
On Windows it is extremely rare - maybe once a year, but you'd have to be a power user for sure. On Mac, it is usually a weekly occurrence. Hell, I had it happen last night in fact just by trying to mount a DMG file (a freshly downloaded TeamViewer DMG if you must know). It decided to go to the beach instead. After a full reboot it finally let me mount it. It really is a joke of an OS.
If you're not familiar with Windows IO then why try to cobble together a response? It is true that the Windows kernel does not support anything but asynchronous IO. It simply does not support it. Yes, user-mode land implements synchronous wrappers as a convenience for lazy developers or to aid in porting software from other lesser platforms.
As TazeTSchnitzel said, this happens on both and is quite rare. If you're not just trolling and actually see this on a regular basis, it's either a hardware problem, misconfiguration, or something like using an unreliable LDAP server (this was the last time I saw it, back somewhere around 10.5 and, surprise surprise, Windows clients also wedge solid with a slow/flaky domain controller – I see this every time I use a Windows 7 domain client on a VPN).
> Also all IO on Windows is asynchronous. It doesn't support synchronous IO.
Please contact the folks at Microsoft so they can correct the first hit on Google:
https://msdn.microsoft.com/en-us/library/windows/desktop/aa3...
Remember how we were talking about backwards compatibility? All of those traditional ReadFile/WriteFile/etc. calls aren't going away anytime soon. Even the teams at Microsoft who work on things like Outlook, Word, IE, etc. use synchronous I/O a lot since it's so much easier and there's no major downside on a local file system, particularly now that even a cheap computer can dispatch thousands of IOPs.
Finally, “merely a mod of components from Linux”? I don’t think anyone cared about the distinction between BSD and Linux or GNU user space tools. Things like a kernel with a multiuser system and different permissions are the types of improvements that were once difficult to handle on most consumer machines, yet they were also incorporated into Windows with NT. UNIX is part of the Mac OS being a modern operating system. Even if you lose the weasel word “merely”, OS X is not only a window manager or desktop environment, at a low level there are significant architectural distinctions between OS X and FreeBSD, and differences between OS X and FreeBSD compared to Linux that were developed at Apple.
The point is not that they cannot be compared, but that they have actual merits to compare rather than weaselly arguments as though we were in a 1990s chat room or forum.