131–140 of 342 posts
NeXT's adoption of UNIX was just a way to fulfill expectations of the newly created workstation market.
No serious NeXT application was a pure UNIX one, just like on Mac OS X.
I never saw a NeXT full of xterms and vi, rather with applications that took full advantage of the desktop frameworks, including the devtools.
> Removing the Esc key you can switch back to default F1... keys > Removing all legacy ports necessitating the use of dongles for everything Somewhere have to start the transition > Prioritising thinness and weight over everything else Batterylife is the same Worst thing on the new rMBPs: No silent trackpad click option m( I use OS X just as an client.
> you can switch back to default F1... keys Why not just set Caps Lock to Esc? Works well with Vim and you don't wanna use Caps Lock anyway. I use Karabiner Elements to set it that way. Karabiner doesn't work with Sierra.
Earlier quoted context omitted.
I'm thinking about trying it, but a friend of mine said that he could crash it easily by just doing the examples from Mastering the Linux Command Line . I think a Surface might make a decent piece of hardware but either WSL (i.e. the horrendously named Bash on Ubuntu on Windows) has to get a lot more stable or Linux support will have to improve. I hear Linux support for the Surface Pro 3 is basically there, but SP4 s…
a friend of mine said that he could crash it easily by just doing the examples from Mastering the Linux Command Line Not really surprising (dev version, comes with warnings about compatibility, ...). But why would you let that hold you back for trying it out for what you are going to use it for? Counter-anecdote: I've ran gui apps like SublimeText, gcc, ... without crashing; also see other comments. tldr; try it firs…
People worry too much about what they use to host text editors and terminal windows...
Sure, except that OSX's iterm2+Karabiner is so much better than any terminal on Linux. Awesome full-screen switching (⌘-Enter), easy shortcuts to create subwindows, natural clipboard support, great keyboard compatibility with Emacs (after futzing with keyboard settings and Karabiner mappings). On Ubuntu, all of these have been lacking. Hell, I can't even use the terminal for a single session without accidentally trig…
Except for "natural clipboard support" (dunno what you mean) and "Emacs" (I am a vim user, so I set up vim shortcuts) I have everything you said in my i3 setup, however for every application instead only for terminal.
People worry too much about what they use to host text editors and terminal windows...
Sure, except that OSX's iterm2+Karabiner is so much better than any terminal on Linux. Awesome full-screen switching (⌘-Enter), easy shortcuts to create subwindows, natural clipboard support, great keyboard compatibility with Emacs (after futzing with keyboard settings and Karabiner mappings). On Ubuntu, all of these have been lacking. Hell, I can't even use the terminal for a single session without accidentally trig…
I don't have the nerve to learn all the other features anyway...
> The first option I tried was an i3 based desktop. However whilst I wanted to like tiling window managers I decided it wasn’t for me. It took me a week or so to get used to i3, but once I did I can't see myself ever going back. I've been using i3 at work and at home for about year now, and every time I get on my (Mac Book) laptop it's a frustrating experience: I feel like I spend more time trying to figure out how t…
i3 is great, until you try to do something simple like change the time zone for your desktop clock or add some wallpaper. 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. Unfortunately the Linux desktops were actually worse than the…
Systemd makes using i3 so much easier. 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).
> 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. GNOME assumed glibc did it right, which was a reasonable assumption...but an incorrect one, but with i3 I could control this.
Gnome nowadays use timedatectl AFAIK to set time too. The last time I had a issue with setting date or time in Gnome was pre-systemd days.
While some people may not like systemd, I find tools like timedatectl, localectl and hostnamectl to be quite useful. They work much better than trying to write a shell script or parse something.