71–80 of 106 posts
Earlier quoted context omitted.
I'm using a Hackintosh for 4 years now. It's definitely not true that one is bound to Apple hardware.
Well, from a legal perspective you are bound to their hardware. A Hackintosh is a breach of the EULA, and no company should allow one to be used for their development, as it can create a potentially massive liability for them.
Earlier quoted context omitted.
* Package management isn't a train-wreck (I always have troubles with brew whenever I have to move to a mac that I never have with linux). * There are substantial subtle differences between Mac and Linux that will eventually trip you up when leaping the divide between development and deployment. * The Mac often has ridiculously old versions of tools because of its GPL allergy. But hey, Macs are shiny and popular.
> Package management isn't a train-wreck (I always have > troubles with brew Really? What? > The Mac often has ridiculously old versions of tools > because of its GPL allergy. Brew! :) I would actually love to ditch macOS - I used Arch on my MBA for some time, but in the end it was better drivers and brew that brought me back. I seriously miss i3wm though. Brew is the best package manager I've ever used - so simple t…
* Conflicts with other software installed causing all sorts of weirdness.
* Numerous packages not in the main repo that weirdly have to be installed by some other mechanism (pip, cask, etc.).
* Dependency on XCode. There's like a 5 step installation process to get it up and running!
* brew install rsync -> rsync [xyz] -> why isn't this working? -> oh wait, the version of rsync on the PATH is still the ancient system one for some reason.
* whatever brew doctor does. the fact that command even exists is a big red flag to me.
^^ This is just the stuff I've run into recently when I've had to debug stuff that was working just fine on linux but somehow broke on a somebody's mac.
To me a huge selling point of linux is i3wm. If you haven't used this thing yet, you absolutely have to try it out! It is the best tool that I have discovered since emacs. It allows me to easily and conveniently manage dozens of windows, and it's hard to describe how convenient that is until you get used to it. I usually have around 10 workspaces open: 1. Emacs with personal notes, goals, todo lists. 2. Emacs windows…
The killer feature for KDE is the "konsole" (KDE terminal) integration in their GUI tools. Their file manager (Dolphin) and text editors (Kwrite and Kate) have a CLI built in so I can leverage the best of both paradigms from a single interface. Couple that with Krunner (I know every DE and OS has a runner these days) and Yakuake (a Quake-style drop down terminal) and KDE is actually a surprisingly productive desktop environment even for people who are command line orientated or running on platforms with limited screen real estate (eg laptop screen).
But as much as we might intellectualise the productivity of different desktop environments and window managers, our personal preferences often just boil down to old habits. I've been using KDE since version 1 so when migrating to a tiling WM I was as much frustrated by having to rewrite muscle memory as I was by any personal preference with the UI design.
You can see the differences between linux and macOS when you consider your environment as a desktop workstation rather than a simple dev machine. I've switched from linux to macOS after 13+ years because, IMHO, the linux desktop overall experience sucks for everyday use.
That's interesting; what challenges did you run into most often?
1b) desktop apps availability/quality
2) drivers and support
3) With mac, I open my laptop and I can use it like a toaster, without thinking how to fix this or that issue after a software update
bonus) iphone/appletv/ipad smooth integration
PS (especially for downvoters): I've used linux since 1999, I have a sysadmin background, I used to build my desktop/servers from scratch or by using gentoo (that is almost the same), I wrote kernel modules. So I'm not afraid to tinker with a linux system down to the kernel details. Again I switched to macOS because I was tired of all those little issues that made my daily work a crappy experience (eg: why my Bluetooth device doesn't work today?)
I recently switched to using a Mac (for work) after 5-6 years only using Linux. Again and again the most painful aspect of the Apple ecosystem is that Apple have already decided what is going to be best for me. By default, it's impossible to use workspaces without frequent switches to the trackpad, which wouldn't be so bad, but without installing third party software it's not really possible to create shortcuts or st…
To me a huge selling point of linux is i3wm. If you haven't used this thing yet, you absolutely have to try it out! It is the best tool that I have discovered since emacs. It allows me to easily and conveniently manage dozens of windows, and it's hard to describe how convenient that is until you get used to it. I usually have around 10 workspaces open: 1. Emacs with personal notes, goals, todo lists. 2. Emacs windows…
Understand the sensation. 5 years ago I used to do something similar with xfce+compiz' "spin the cube" with a suitable hotkey (ctrl+alt+direction). I actually wound up preferring this greatly to the dual monitor thing as I didn't have to maintain my neck at unnatural angles, spend more money, or have a stupidly large desk. The last few years I have been mostly on console (similar alt+direction) or OSX (kinda fullscre…
Although, It'd be awesome if someone did an iOS port of Vim — I've always thought a modal interface like Vim's would be perfect for a tablet + keyboard combination.
The apt-get install for damn near anything is a big one (for Debian based distros obviously) in my opinion. I think the access to build tools and packages is big too. I had case recently where I needed to make a one line change to an Apache module; wget the source, make the change, configure, make, make install, exactly the same as on the prod server. Unfortunately the author delves into text editors, which can be fl…
Homebrew comes pretty close to apt-get on Mac. Of course the whole OS being open source & community driven (sans driver blobs) is nice thing, althought benefits are mostly idealogical than practical. The argument "dev env == production env" is overrated IMO, because you typically want more conservative/controlled production environment anyway and/or you may prefer different distro for workstation use. For serious use…
Earlier quoted context omitted.
> Package management isn't a train-wreck (I always have > troubles with brew Really? What? > The Mac often has ridiculously old versions of tools > because of its GPL allergy. Brew! :) I would actually love to ditch macOS - I used Arch on my MBA for some time, but in the end it was better drivers and brew that brought me back. I seriously miss i3wm though. Brew is the best package manager I've ever used - so simple t…
>Really? What? * Conflicts with other software installed causing all sorts of weirdness. * Numerous packages not in the main repo that weirdly have to be installed by some other mechanism (pip, cask, etc.). * Dependency on XCode. There's like a 5 step installation process to get it up and running! * brew install rsync -> rsync [xyz] -> why isn't this working? -> oh wait, the version of rsync on the PATH is still the…
> Conflicts with other software installed causing all
> sorts of weirdness.
> Numerous packages not in the main repo that weirdly have
> to be installed by some other mechanism (pip, cask,
> etc.)
> Dependency on XCode. There's like a 5 step installation
> process to get it up and running!
I think the only way around this would be for brew to ship a compiled binary, and then mandate that you install either XCode Command-Line Tools, or gcc. (Some formulae will need to compile.)
> brew install rsync -> rsync [xyz] -> why isn't this
> working? -> oh wait, the version of rsync on the PATH is
> still the ancient system one for some reason.
> whatever brew doctor does. the fact that command even
> exists is a big red flag to me.
> Please note that these warnings are just used to help
> the Homebrew maintainers with debugging if you file an
> issue. If everything you use Homebrew for is working
> fine: please don't worry and just ignore them. Thanks!Earlier quoted context omitted.
Understand the sensation. 5 years ago I used to do something similar with xfce+compiz' "spin the cube" with a suitable hotkey (ctrl+alt+direction). I actually wound up preferring this greatly to the dual monitor thing as I didn't have to maintain my neck at unnatural angles, spend more money, or have a stupidly large desk. The last few years I have been mostly on console (similar alt+direction) or OSX (kinda fullscre…
How are you using a tablet for dev work? I know there are some good terminal apps on iOS (Prompt), but I've never really found that a convenient way to go. Although, It'd be awesome if someone did an iOS port of Vim — I've always thought a modal interface like Vim's would be perfect for a tablet + keyboard combination.