5 ms·

Ubuntu on a ThinkPad X1 Carbon is my workstation. As a Go developer I only need Chrome, a terminal, and Go itself (which I install from the official tarball bin

Ubuntu on a ThinkPad X1 Carbon is my workstation. As a Go developer I only need Chrome, a terminal, and Go itself (which I install from the official tarball binaries). Now that I have Google Fi I'm kicking myself for not getting the cell radio builtin as Google will send you a data only SIM for free! I would never have to deal with another terrible airport or hotel captive portal again! My coworkers are all Macbook Pro users and ask why I don't get one too. I just don't see the point. I think MBP's build quality is nicer but otherwise I get twice the machine for the same price and get to develop on the same OS as my project primarily targets (Linux).

mjolk 10y ago
> Now that I have Google Fi I'm kicking myself for not getting the cell radio builtin as Google will send you a data only SIM for free! Oh, I forgot Fi would send us this, thanks! > I think MBP's build quality is nicer but otherwise I get twice the machine for the same price and get to develop on the same OS as my project primarily targets (Linux). I just looked at the X1 carbon specs and my 3 year old MacBook Air is faster than the base model carbon and I spent about the same amount of money. The build quality is huge for me as I spend 50+ hours a week directly-on or with peripherals cabled to my laptop. If I wanted, I could install a Linux on it, but really, OS X just works without having to fuss with it (e.g. trying to get the touchpad feel anywhere near as nice). As for writing Go, isn't cross-compilation pretty good? I spend most of my time writing in VHLLs (js, python, etc) and OS X is (still, even after some iOS-direction changes) quite good as a dev environment -- spinning up a VM for when I need to compile something lower-level and test on a target OS is trivial.
- schmichael 10y ago
  > As for writing Go, isn't cross-compilation pretty good? Go's cross-compilation is near perfection unless you use cgo which needs to use a C compiler to link against native libraries. Then you need all of the normal tools and libraries for cross-compiling C; Go just puts a decent on it.
  - mjolk 10y ago
    Ah, cool. My workflow is essentially "write Python until it's too slow, then profile and write C," so maybe it's time I move to a Go/C approach.

mjolk 10y ago

> Now that I have Google Fi I'm kicking myself for not getting the cell radio builtin as Google will send you a data only SIM for free! Oh, I forgot Fi would send us this, thanks! > I think MBP's build quality is nicer but otherwise I get twice the machine for the same price and get to develop on the same OS as my project primarily targets (Linux). I just looked at the X1 carbon specs and my 3 year old MacBook Air is faster than the base model carbon and I spent about the same amount of money. The build quality is huge for me as I spend 50+ hours a week directly-on or with peripherals cabled to my laptop. If I wanted, I could install a Linux on it, but really, OS X just works without having to fuss with it (e.g. trying to get the touchpad feel anywhere near as nice). As for writing Go, isn't cross-compilation pretty good? I spend most of my time writing in VHLLs (js, python, etc) and OS X is (still, even after some iOS-direction changes) quite good as a dev environment -- spinning up a VM for when I need to compile something lower-level and test on a target OS is trivial.

schmichael 10y ago
> As for writing Go, isn't cross-compilation pretty good? Go's cross-compilation is near perfection unless you use cgo which needs to use a C compiler to link against native libraries. Then you need all of the normal tools and libraries for cross-compiling C; Go just puts a decent on it.
- mjolk 10y ago
  Ah, cool. My workflow is essentially "write Python until it's too slow, then profile and write C," so maybe it's time I move to a Go/C approach.