#Mission control plus alternative windows

Does the amount of time I spend managing windows outweigh the configuration time for the Linux box? I doubt it. On my Mac, I have to spend time resizing and rearranging windows because I have to click a window to type there, and clicking raises it to the foreground, obscuring my other windows.

On my Linux machines, I can type in one window while interacting with another, and I use that ability fairly often. What you consider 'busy-work admin issues', many people consider tier-1 features.įor instance, take sloppy focus. But whether or not you do or don't like systemd, you'd be crazy to say that it fits in with that unix principle I mentioned above. Yes, the anti-syslog commentary went too far, but there were a lot of problems with it, especially before it had been battle-hardened. Only the IPU knows why they would make a new journaling system for a primarily-server OS, and keep kicking the 'centralisation' can down the road. In the same vein, do we have centralised logging in systemd yet? Or do we still have to run another syslog tool to ship them? Last I looked half a year ago, the consensus was still 'ship them through rsyslog/syslog-ng', so you still have to run your old syslog in parallel. > Here you go, all your old logs in the place you expect them.Ĭool. One of the definite problems was the core developers' disdain for other people's use cases - even Torvalds said he was ambivalent about systemd itself, but the developers were pretty user-hostile and that was a problem. Of course, I'm not going to tell you the winners that's my secret!ĭid you get onto the systemd stuff late? I got in midway along and found a few things that were iffy. There's an invisible pink unicorn who knows the winners of every horse race, but only I can see and hear her. And no, no one of them is found in the regular systemd-hate sites. > I only read one or two solid (technical) arguments against systemd. They work much better than trying to write a shell script or parse something. While some people may not like systemd, I find tools like timedatectl, localectl and hostnamectl to be quite useful. The last time I had a issue with setting date or time in Gnome was pre-systemd days.

Gnome nowadays use timedatectl AFAIK to set time too. GNOME assumed glibc did it right, which was a reasonable assumption.but an incorrect one, but with i3 I could control this. > Unfortunately the Linux desktops were actually worse than the barebones window managers like i3: there was some sort of glibc bug that screwed up clock display on GNOME for at least a year. No more fiddling with consolekit and dbus just to get working external drives (logind solves the problem of local authentication), no more fiddling with symlinks to set time (timedatectl to the rescue).

#Mission control plus alternative mac

I switched from Linux to Mac because I was too well acquainted with making symlinks to /usr/share/ somewhere just to change my clock when I traveled, and then figuring out just how few processes I had to restart so it would take effect. i3 is great, until you try to do something simple like change the time zone for your desktop clock or add some wallpaper.