From Mac to Linux: Web Development with Linux

Post by subway » Mon, Oct 17, 2016, 12:55 PM UTC

Post by se6 » Mon, Oct 17, 2016, 12:58 PM UTC

toxican wrote: post #35

rayalez wrote: post #30

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…

If Adobe supported linux, I could almost do my entire job without Windows. The only missing piece would be support for Exchange-based email. But for now I've got two machines, 3 monitors, and make great use of Synergy. I feel like a luddite though because I use and love linux, but have never taken the time to learn and use the workspaces feature. It would probably be cheaper to learn it than to keep throwing monitors…

Post by SunShiranui » Mon, Oct 17, 2016, 1:03 PM UTC

fdomig wrote: post #28

Honestly, nice if that works easy for you when using just developer tools on the terminal or a text editor. As a web developer, though, you might end up using more than that. A Mac offers so much more commercial applications that just do not exist on any Linux distribution. Gimp is no replacement for Photoshop and Inkscape is not replacement for Illustrator, ... Btw, mostly everything you install with `apt-get` can b…

Post by pjmlp » Mon, Oct 17, 2016, 1:09 PM UTC

mugsie wrote: post #57

pjmlp wrote: post #43

Earlier quoted context omitted.

> With "the cloud", these days that is not necessarily true. a t2.large / m2.large are 2 cores, 8GB RAM. - well within the reach of a basic laptop. Which is why we just connect to "cloud" and clone our own instance from a production server, if we really need to. > Never debug in production. No developer should have access to production. Maybe in a perfect world. On real life I have been in projects where developers w…

OK, the problems seem more culture based then. All of these issues tie together. Developers can't access production, so they start using production like environments, which allows for proper Ops work (Infrastructure as code - e.g. config management), which allows for easier setup of production like environments for developers ... and continue cycle. Its hard to move to that, and takes time, but it really helps. I kno…

Post by gravypod » Mon, Oct 17, 2016, 1:12 PM UTC

liuw wrote: post #63

gravypod wrote: post #51

The problem with most apt-based distributions is I've found that a lot of packages are out of date. Try out a pacman-based distribution some time. The idea of a rolling distro is great in my mind and most of the packages in the repo are up to date. If something is missing there is usually an AUR. If you use zsh with oh-my-zsh then you're going to have a much easier time finding whatever you need to install. Pacman ha…

> The problem with most apt-based distributions is I've found that a lot of packages are out of date. If you want APT based distro + rolling update, Debian testing is what you need. (Obviously if you're satisfied with Arch, there is no need to change.)