This monitor is listed as $999 on Amazon, following the very link he posted in the article. Is there somewhere else you can buy it for $500?
[deleted]
4K is for programmers
61–70 of 342 posts
Re: 4K is for programmers
#62This seems like flaunting your budget more than improving your environment. Maybe I just need to get my eyes checked again, but for some reason my code just doesn't perform any better or write itself any faster with more screen real estate and I'm as productive on my laptop as I am on my big screen. 4K is not for programmers, code is for programmers.
I've always felt the same. A huge monitor has never felt any better or more productive than my Macbook Air -- just bigger.
I mean, I just never need to be looking at more than one window at once. And when I need to interact with multiple windows (editor, browser, e-mail, docs, whatever), then I need to shift the focus to each of them anyways to reload the browser, change the code, highlight a new email, etc. -- so I always have to cmd+tab to the window no matter what.
After all, you can only look at a single window at a time, and I never need to keep things open for constant monitoring or anything.
(I do a little 'trick' with OSX, however, which is to always resize every application to use the full screen area, and keep it on its own desktop, so I never have to deal with the clutter and confusion of overlapping windows. And remember, dragging and dropping files etc. works between desktops just fine!)
Re: 4K is for programmers
#63Earlier quoted context omitted.
I do all these things in a terminal. I used not to. But once I started doing things the CLI-way, I never looked back and have yet to discover a tool offering even half the productivity gained from keeping my fingers firmly planted on the home row. However, if you are locked into using an environment where doing the things you've said requires mousing or multiple windows with tons of resolution, then you have my sympa…
While I do a lot on the terminal, not everything is faster there. Jumping between symbols in your IDE is not going to happen faster on the command line because it's a spatial operation. You've located the symbol visually, clicking it to jump to definition is far faster than keyboard-navigating to it, or even typing it. Merging is better with a dedicated merge tool than a command line merge. I have to resolve conflict…
"Merging is better with a dedicated merge tool than a command line merge. I have to resolve conflicts one to three times per day and I couldn't imagine a non-visual merge interface for complex files where manual edits from both sides are necessary. Being able to see it all at once helps."
Being able to see it all at once absolutely helps, but on a big enough console you can see it all just fine. Vimdiff is great. A large monitor definitely adds value there, GUI or TUI.
Re: 4K is for programmers
#64This monitor is listed as $999 on Amazon, following the very link he posted in the article. Is there somewhere else you can buy it for $500?
He's talking about the 39 inch, which is $500. When you go to Amazon, it defaults to displaying the 50 inch. Click 39 inch button to the right of the product image and you'll get the $500.
Re: 4K is for programmers
#65Part of the problem might be gamers not having powerful enough machines and not wanting a blurry image from scaling.
I think PC gamers would find the 30Hz much more of a disincentive. I think most console games are used to 24 fps anyway, but they don't even have the option to reach that resolution (yet?)
Yup, 30hz would be a no go. And I am pretty sure Sony has said the ps4 is able to play video at 4k, but has no intentions for games at that resolution. Hell games for both systems aren't even 1080p across the board.
Re: 4K is for programmers
#6630Hz is a dealbreaker. I will keep my 1920x1200 until I can have a proper 4K display. I really am surprised there are people who can tolerate that refresh rate on a desktop.
Re: 4K is for programmers
#67Earlier quoted context omitted.
While I do a lot on the terminal, not everything is faster there. Jumping between symbols in your IDE is not going to happen faster on the command line because it's a spatial operation. You've located the symbol visually, clicking it to jump to definition is far faster than keyboard-navigating to it, or even typing it. Merging is better with a dedicated merge tool than a command line merge. I have to resolve conflict…
"Jumping between symbols in your IDE is not going to happen faster on the command line because it's a spatial operation. You've located the symbol visually, clicking it to jump to definition is far faster than keyboard-navigating to it, or even typing it." When the lab I worked in moved between buildings, we each broke down our work stations and set them up in the new spot. I went through a good week of getting work…
Most of the time when I'm coding I use the keyboard to jump to symbols. But when you are getting acquainted with a large codebase, reading through and clicking to jump to symbol can be a more efficient way to parse the code and understand its interdependencies.
It may depend on what you use to position the cursor as well — I haven't used anything but a trackpad in the last five years, and even on that mostly I use gestures to navigate UI. Since the trackpad is almost part of the keyboard it feels very seamless to scroll/tap and type.
Re: 4K is for programmers
#68Whatever. It’s not the number of pixels, it’s the pixel density that’s important. Higher density is what is going to make text and pictures better. At 39″, that’s 113 ppi. Anyone can rig up a multi-monitor display setup with higher ppi. The only advancement is one physical screen that a good number of GPUs can’t take advantage of.
For comparison, my Retina 13″ MacBook Pro has 2560x1440, 2.5K (or really ⅔ 4K) but at 227 ppi.
Re: 4K is for programmers
#69Earlier quoted context omitted.
"Jumping between symbols in your IDE is not going to happen faster on the command line because it's a spatial operation. You've located the symbol visually, clicking it to jump to definition is far faster than keyboard-navigating to it, or even typing it." When the lab I worked in moved between buildings, we each broke down our work stations and set them up in the new spot. I went through a good week of getting work…
Most of the time when I'm coding I use the keyboard to jump to symbols. But when you are getting acquainted with a large codebase, reading through and clicking to jump to symbol can be a more efficient way to parse the code and understand its interdependencies. It may depend on what you use to position the cursor as well — I haven't used anything but a trackpad in the last five years, and even on that mostly I use ge…
Yeah, I'm much more likely to bump a trackpad than reach for a mouse, even when the mouse gives me much more control (I always find trackpads a little finicky), just because of the distance. My hands don't need to actually go anywhere.
Of course, I also bump the trackpad accidentally sometimes, but that's a separate issue...
Re: 4K is for programmers
#70Earlier quoted context omitted.
That would be a deal breaker, but lenovo and asus make nearly identical IPS displays.
AFAIK all 28'' 4k screens are TN, that's why they are so cheap. If you want IPS, it's $1300 for 24 (dell), or $3500 (dell, asus).
And the 32" inch $3500 ones are IPS on IGZO instead of traditional amorphous silicon.