Live data from Hacker News

Time to Upgrade Your Monitor

tonsky.me

711–720 of 1001 posts

Re: Time to Upgrade Your Monitor

#711
post #76

The technical details are all right (or seem right to me, anyway), but this is too opinionated for my liking. No, you do not need a 4K monitor for software development. Some people might like them, some won't. [edit/clarification: someone rightfully pointed out that nobody will actively dislike a 4K monitor. I was unclear here: I meant "some people won't need them" more than "dislike them"] This sounds like when Jeff…

We used to write great code on the original Mac’s 512 by 384 screen, doesn’t mean we were very productive at it. A 5K monitor allows you to view an enormous set of workspaces and code, and sharply. It will cost you less than $300 a year, which for any decent developer is less than 1/2 of 1% of your annual revenues (and its tax deductible for contractors!). There is no way the increase on productivity doesn’t far outw…

What do you mean "we weren't very productive"? People were plenty productive with the original Mac.

I was plenty productive on PC XT clone with a tiny monochrome CRT monitor and an Hercules video card. (I wanted to say I was plenty productive with my C64, but that'd be stretching it :P )

What I want to fight is this notion that once tech N+1 arrives, then tech N must have been unproductive. That's demonstrably false, a form of magical thinking, and not a healthy mindset in my opinion.

Re: Time to Upgrade Your Monitor

#712
post #708

Earlier quoted context omitted.

>The best developers I've known wrote code with tiny laptops with poor 1366x768 displays. I'm sorry to say this but that is not a real argument.

It's not meant as an argument, but as an illustration: people who I respect more than the author of TFA, and whose skill and accomplishments I've witnessed first hand, weren't eager to upgrade from tiny screens. It's not that they would've refused a better screen if given one, it's just that they didn't ask for it and it wasn't a pressing issue. Indeed, for them it was not "time to upgrade the monitor". It taught me…

Why are you talking about screen size when the article is talking about pixel density? You can have a lot of pixels but low pixel density because your screen is huge, while my first 200+ PPI display was on an iPhone 4, my watch has a 200+ PPI display as well. I don't think many would accept phones or watches with lower pixel densities these days, but somehow the display we use for work is different?

You are right that there is a cargo culting going on, but it is going on both sides. There are a lot of strawmen out there as well.

Re: Time to Upgrade Your Monitor

#713
post #392

Earlier quoted context omitted.

If you are on macOS, all is good. Never had a problem with any of my 4 monitors (3x4K, 1x5K). I set the scaling to a size I like, and the text is super crisp. I don't see how any programmer can NOT like that.

How do you manage multiple monitors with MacOS? I was doing this until recently and every single login involved rearranging my windows because MacOS moves them all to whatever display woke up first. In my experience MacOS multi-monitor support is effectively non-existent. Recently I picked up a 49” ultra-ultra wide monitor (basically 2x27” panels). It is one monitor but MacOS can’t drive it. They just don’t detect th…

How do you manage multiple monitors with MacOS? I was doing this until recently and every single login involved rearranging my windows because MacOS moves them all to whatever display woke up first.

I finally got sick of this and wrote a Hammerspoon script to deal with this. The config looks like this:

      local dualLayout = {
          {"Firefox",       nil,         primary,   topLeft,             nil, nil},
          {"Preview",       nil,         primary,   topLeft,             nil, nil},
          {"Sublime Text",  nil,         secondary, topHalf,             nil, nil},
          {"Slack",         nil,         secondary, topRight,            nil, nil},
          {"Notes",         nil,         secondary, topRight,            nil, nil},
          {"iTerm2",        nil,         secondary, topRight,            nil, nil},
          {"Safari",        nil,         secondary, topRight,            nil, nil},
          {"IntelliJ IDEA", "cursive",   primary,   hs.layout.maximized, nil, nil},
          {"IntelliJ IDEA", "community", secondary, hs.layout.maximized, nil, nil},
      }
Now when I connect my two external monitors, a quick Ctrl-Alt-Cmd-R lays everything out. It's crap that I have to, but it saved my sanity.

Re: Time to Upgrade Your Monitor

#715

Earlier quoted context omitted.

> You lost me right here on line 1. I'm on Windows and can confirm 1. is an issue. Windows lets users scale UIs to be readable at high DPI on small screens. Doesn't work on all UIs (e.g. QGIS). So maybe not all OS's, but two important ones. > You could say the same for any arbitrary DPI; 96dpi isn't "Required", we got by fine with 72dpi. It's all about ergonomics as far as I'm concerned. I think the point the parent…

>I think the point the parent is making is that human vision has limited resolution. I.e. for a given screen size & distance from the screen, you cannot notice any difference in DPI past a point. The parent is suggesting that 1080p & 27" with a typical viewing distance is already higher resolution than the eye can resolve. Looking at my 1080p 27" screen from a metre away with 20/20 vision I am inclined to agree! Are…

MacOS does support subpixel rendering, has at least since the early to mid 2000s. One or two versions back though they turned it off by default since it isn't necessary on HiDPI "Retina" displays and they only ship HiDPI displays now.

You can still turn it on although it requires the command line.

Re: Time to Upgrade Your Monitor

#716
post #392

Earlier quoted context omitted.

How do you manage multiple monitors with MacOS? I was doing this until recently and every single login involved rearranging my windows because MacOS moves them all to whatever display woke up first. In my experience MacOS multi-monitor support is effectively non-existent. Recently I picked up a 49” ultra-ultra wide monitor (basically 2x27” panels). It is one monitor but MacOS can’t drive it. They just don’t detect th…

How do you manage multiple monitors with MacOS? I was doing this until recently and every single login involved rearranging my windows because MacOS moves them all to whatever display woke up first. I finally got sick of this and wrote a Hammerspoon script to deal with this. The config looks like this: local dualLayout = { {"Firefox", nil, primary, topLeft, nil, nil}, {"Preview", nil, primary, topLeft, nil, nil}, {"S…

This is really cool, thanks.

I tend to have one space per task and have at least a Firefox and an iTerm on every one.

Just running a single monitor is the way to go for me. The benefits of multiple monitors just doesn't make up for all the fiddling.

Re: Time to Upgrade Your Monitor

#717
post #708

Earlier quoted context omitted.

It's not meant as an argument, but as an illustration: people who I respect more than the author of TFA, and whose skill and accomplishments I've witnessed first hand, weren't eager to upgrade from tiny screens. It's not that they would've refused a better screen if given one, it's just that they didn't ask for it and it wasn't a pressing issue. Indeed, for them it was not "time to upgrade the monitor". It taught me…

Why are you talking about screen size when the article is talking about pixel density? You can have a lot of pixels but low pixel density because your screen is huge, while my first 200+ PPI display was on an iPhone 4, my watch has a 200+ PPI display as well. I don't think many would accept phones or watches with lower pixel densities these days, but somehow the display we use for work is different? You are right tha…

I'm talking about tiny screens and resolutions, so it's both. I don't see the strawmen.

Phones and watches are a different use case, so I'm not sure what you mean. I don't type code in either.

Re: Time to Upgrade Your Monitor

#718

Earlier quoted context omitted.

What if I gave you more vertical pixels? Would that be okay? 1280x1440 maybe? Just a few more.

Nope, bad aspect ratio. Let me know if you find a 1920x1536, though. (1600x1280 would also be nice, and a 2560x2048 would be a 4K monitor that's actually useful, although thomaslord's objections still apply.) Edit: actually, wouldn't 1440x1280 (aspect ratio 1.125, which is even less than my usual 1.25) be a better use of such a LCD panel, rather than a obviously-useless 1280x1440 (with a aspect ratio less than one)?

Why do you care about aspect ratio so much?

Re: Time to Upgrade Your Monitor

#719
The article is all based around this premise:

> Times of low-resolution displays are over. High-resolution displays are a commodity now.

I reject that premise. 4K is basically the maximum number of pixels you can get for less than $1K, and that's only a handful more pixels than a 16" MBP screen. It does not make sense for most people to shell out the $$$ just so that they can see the same number of pixels from slightly further away.

It is absolutely not the right time to upgrade your monitor. Wait until 5K+ becomes affordable again[1] so you can actually get the benefits of an external monitor (more usable screen space) without having to sacrifice the sharpness and quality of retina.

[1] https://tidbits.com/2018/11/16/what-happened-to-5k-displays/

Re: Time to Upgrade Your Monitor

#720
post #711

Earlier quoted context omitted.

We used to write great code on the original Mac’s 512 by 384 screen, doesn’t mean we were very productive at it. A 5K monitor allows you to view an enormous set of workspaces and code, and sharply. It will cost you less than $300 a year, which for any decent developer is less than 1/2 of 1% of your annual revenues (and its tax deductible for contractors!). There is no way the increase on productivity doesn’t far outw…

What do you mean "we weren't very productive"? People were plenty productive with the original Mac. I was plenty productive on PC XT clone with a tiny monochrome CRT monitor and an Hercules video card. (I wanted to say I was plenty productive with my C64, but that'd be stretching it :P ) What I want to fight is this notion that once tech N+1 arrives, then tech N must have been unproductive. That's demonstrably false,…

But it's true. Developing modern code on a Apple 2 is unproductive. It's suboptimal, and worse. Maybe you don't want to use the word "unproductive," and that's fine. But larger screens, faster computers, and more expressive programming languages all contribute to increased productivity over the older alternatives.
Post reply on HN