4 ms·
I'm generally more productive with a split screen view for code, with either different files on each side, or different parts of the same file on each side. Thi
by lewisl9029 11y ago
I'm generally more productive with a split screen view for code, with either different files on each side, or different parts of the same file on each side. This kind of workflow needs quite a bit of horizontal resolution to work well.
- jameshart 11y agoInteresting - a 16:9 screen splits into two 8:9 screens - almost squares. A 3:2 screen splits into two 3:4 screens, much more useful document-style aspect ratios. That said, with the surface/surfacebook, we're talking about small 12-13 inch screens anyway, not enough physical real estate for that kind of work. You'll likely connect to a larger external screen if you're looking for a splitscreen workspace.
- e12e 11y agoReading this now in a roughly 2:1 split on my Thinkpad t420s (16:9, 1600px:900px). On the right, i have a terminal window, with no margins, and no window decorations. On the left Firefox with HN open, which because of the "forced" margins set by stylesheets, end up being a squarish "page", with a regularish (portrait) text block in the middle... -FF---------Term-- mmm mm |mmmmmm mmm mm |mmmmmm mmm mm |mmmmmm |mmmmmm mmm mm |mmmmmm |mmmmmm |mmmmmm So while some people probably prefer a 1:1 split, I usually end up with a 2:1 or maybe even closer to 3:1.