8 ms·
I am still waiting for a decent size e-ink screen (22"+) without backlight which should be enough for low-FPS stuff like backend coding, slack, terminal and tex
by imhoguy 6y ago
I am still waiting for a decent size e-ink screen (22"+) without backlight which should be enough for low-FPS stuff like backend coding, slack, terminal and text content web pages. Existing solutions are still too small - Dasung and Onyx Boox are 13.3" with HDMI.
- gmadsen 6y agoi have never heard of an e-ink screen with fast enough refresh to be viable for coding
- officialjunk 6y agowhat is your minimum refresh rate needed for coding?
- smusamashah 6y agoScrolling would be painful on e-ink
- nottorp 6y agoAlso programmers tend to type pretty fast after getting some experience. It's disconcerting enough when code completion slows down the editor, not sure i could stand a screen that can only refresh every full line.
- bee_rider 6y agoThis is why vim has multi-character movements. The problem here doesn't seem that different from coding over a slow network, something that's been possible for quite a while.
- nottorp 6y agoCoding over a slow network is the sole reason I know to use vi :) But i'd rather not do it daily.
- GekkePrutser 6y agoWhen I'm coding I'd usually do pgup/pgdn, don't think this would be a huge issue.
- imhoguy 6y agoI think both of these are usable https://www.youtube.com/watch?v=NozoRkE0DTo https://www.youtube.com/watch?v=NozoRkE0DTo they use various optimizations to avoid full panel refresh. Here is coding example with Dasung although it is hard to judge scrolling quality https://www.youtube.com/watch?v=OO0Qzuw18q8 https://www.youtube.com/watch?v=OO0Qzuw18q8
- tzs 6y agoHow about a display that had a large e-ink screen plus a small LCD of maybe 2-4 lines at the bottom? Go old school for editing. Use something like TECO or ed or Rob Pike, David Tilbrook, Hugh Redelmeier and Tom Duff's Unix version of QED [1]. The small LCD is for seeing the command you are currently typing and a little command history. With those editors you entered editing commands but did not see the results until you asked for them. You'd tell the editor to show you the current line plus say 10 lines before and after. Then you'd give it commands to edit the current line, such as telling it to change the text "float" to "double", or telling it to insert a new line before the current line, and so on. When you had done enough changes that you needed to refresh your notion of the current state of the file, you'd ask it to show you again. Even the older generation, slower e-ink screens would be fast enough for that kind of work. Maybe instead of putting the small LCD display at the bottom of the e-ink screen, make it a separate unit that can attach to the e-ink screen or attach to the top of your keyboard or stand alone somewhere if you prefer. [1] https://github.com/phonologus/QED https://github.com/phonologus/QED
- rthomas6 6y agoSyntax highlighting is too important to me to use this.
- imhoguy 6y agoIt is only color coding one may miss, although it is going to change with faster color eink panels. There is a still a lot of other ways to mark syntax: font, borders, underlines, cursive, grascale tones, background inversion.
- rrrrrrrrrrrryan 6y agoDecent color e-ink tech is finally here: https://gizmodo.com/the-first-color-e-ink-devices-are-finally-here-1844832864 https://gizmodo.com/the-first-color-e-ink-devices-are-finall... It's just a matter of time before a major brand (Amazon, Microsoft, etc.) decides to take a chance and use it to make a big multipurpose tablet.