1. 3

    My screenshots

    Pretty basic stuff, not on a HiDPI screen so basically one screen for browsing, terminal and general stuff and one screen (actually external monitor) for coding. I’m not such a fan of the full screen on OS X mainly because I find quicker to switch between apps with a simple alt+tab, but on the coding screen I usually run the IDE/editor (IDEA shown) on full screen.

    Auto hiding of the Dock to get more useful space (resolution of only 1280x800 on an old 2011 Macbook pro) and chrome for browsing the web, and yes, I usually run that much tabs ;)

    1. 2

      I’m doing this! Also doing it on an ARM Chromebook like yours, with OpenVPN for the bonus insanity. :)

      I wound up, in no particular order 1) using mosh me@server -- screen -D -RR to log into servers, resume where I was, keep the session continuous across IP changes, mask some typing latency, etc, 2) opening crosh in a tab and having its ‘shell’ command drop me directly into crouton (by changing my .bashrc), 3) setting up aliases so it’s quick to log in, and keymappings on the other side so, e.g. Alt-W does ^W (since Chrome wants ^W for “close tab”). I do have some commands to quickly spin up an AWS t2.medium instance, but I don’t use it for many things.

      I do backend Web dev, mostly on a big old Django app (and I play with Go for fun). For what I do I think my client side just doesn’t matter that much–I want to squish my big annoyances, but don’t need to tweak it to be super amazing, if that makes sense. It’s been all the major OSes, very different kinds of editor, ThinkPads and netbooks etc.. Of all the environments, I guess full-fledged Linux feels a little more like home to me, but the hard part is always, you know, what to write and making it work once you’ve got it.

      1. 3

        Interesting setup. Is there a reason you use screen over tmux? I’m interested because I started using tmux because people always tell me it’s better than screen, but I never really compared them.

        I can’t agree more with your last paragraph. All I need is a terminal and vim, and I’ll be happy because I can code. I think it’s useful to not have too strong preferences when it comes to setup.

        1. 2

          Just started on screen before tmux was a thing. tmux is interesting, I’m just not that motivated to switch. Vertical panes (apparently also in new versions of screen) might be nice sometimes.

          1. 3

            I was really impressed by the configuration and command-line interface of tmux. It all feels so easy to control, which I never got with screen. Although maybe I just didn’t read the manual enough.

            1. 3

              I never get used to screen, but tmux gives me a lot of configurable options that makes my terminal use very “natural” specially when working with several servers over SSH, I guess there is no right or wrong choice here, is just a matter of how confortable the tool makes you feel.

        2. 2

          You should try the Secure Shell extension,, it doesn’t take keybindings like Crosh does, so CTRL+W works.

          Can also use >crosh as the host name to get access to localhost.

        1. 11

          This is my first post ever! I’ll spend this week working in storm-crawler, an Open Source “crawler” built around Apache Storm, basically I’m doing some work in the parse framework that will allow to split one URL into several documents in the storage (Elasticsearch for now) instead of the 1:1 relation that we have now between an URL and a document.

          1. 1

            I find the Trie to be an awesome data structure, although I kind of like HyperLogLog too.