731–740 of 1001 posts
Earlier quoted context omitted.
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?
Earlier quoted context omitted.
I love my 3 monitor setup. In 20 years of coding, I finally reached peak productivity in my workspace. No switching between windows, ease of throwing a window aside for monitoring, laying out information and tools side to side. It’s incredible once you readjust your habits and learn to use that new space. I compare it to having a large, wide desk when you’re working on something. Who wouldn’t want that? I was one of…
I got a 6 monitor stand for my home office, filled it with 22-24" screens, and never looked back. It is phenomenal.
Earlier quoted context omitted.
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.
Are we talking about developing modern code on an Apple 2 now? If so I misunderstood the parent post, because they were using the past tense.
In any case, consider this: how do you feel about your current suboptimal, unproductive hardware & software of choice right now? Your current programming language and monitor resolution cannot be used to code. It's simply not possible to be productive with them.
Think I'm exaggerating? Ok. Fast forward a few years and let's talk about this again. Maybe you'll understand my frustration...
Earlier quoted context omitted.
You can do that just fine at 60 Hz, if there is no tearing (all screen updates appear during vertical sync). You can read scrolling movie credits just fine at 24 FPS.
>You can read scrolling movie credits just fine at 24 FPS Honestly I actually struggle with that. But working and gaming at 60hz is still perfectly fine with me. I even purposely run my Valve Index VR headset at 90hz instead of 120hz because I don't need the extra frames
Earlier quoted context omitted.
Guess I never thought about that. Is the difference noticable. I always thought High refresh rate was for gaming.
High refresh rate has to do with reaction times in competitive multi-player gaming. You absolutely don't need 120 Hz in any single player video game produced between 1978 and 2020. Games at 15 FPS (even less) used to be perfectly playable and fun. At 30 FPS things are smooth well past giving a damn.
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…
In the last 3 months I went from 1 screen to 2 to 3 as I progressed through particular stages of development. When we 'go live' I'll easily be using all 3, but I don't _really_ need them, it's a nice to have.
You can pry my cheap A- panel Korean no-name brand 8+ year old monitor with one working button (thankfully the power button!) and a bunch of stuck pixels from my cold, dead, miserly hands.
Earlier quoted context omitted.
> 1. No matter what operating system you're on, you'll eventually run into an application that doesn't render in high dpi mode You lost me right here on line 1. If there are apps on MacOS that can't handle high dpi mode, I haven't run into them as a developer (or doing photo editing, video editing, plus whatever other hobbies I do). Also, I don't have any trouble with plugging my highDPI MacBook into a crappy 1080p d…
> If there are apps on MacOS that can't handle high dpi mode, I haven't run into them as a developer (or doing photo editing, video editing, plus whatever other hobbies I do). Also, I don't have any trouble with plugging my highDPI MacBook into a crappy 1080p display at work. PyCharm had high CPU consumption issues with a Macbook connected to a 4k display running in a scaled resolution. Native 4k was fine, using the…
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…
After trying virtually every display setup imaginable over the years, I've settled on a single, large, high-resolution display as the optimal setup. While I have written a lot of code on small, low-resolution displays, there are definitely disadvantages to that. I don't understand the value of multiple displays for code work. Just about everything that I could do with multiple displays can be more ergonomically achie…
When I code I notice a few things about the multimonitor setup. My cursor can travel 10 physical feet of screen space and it's literally inefficient to point. The ergonomics are terrible. The entire setup basically feeds inattention and an ever-sprawling amount of crap being opened. More than that I think having multiple large rectangles shooting light into your eyeballs kind of screws with your circadian rhythms.
When I code I use a laptop and enjoy how briefly my hands leave the keyboard before returning because what little pointing i'm doing can be done extremely quickly because of the small size of my workflow. Bigger is better is oversold - a workspace should match the work - too small is just more common than too big.
A great e-ink monitor - that would be my dream monitor.