31–40 of 61 posts
Has anyone used these to write interrupt service routines? Seems like there's an opportunity here. You can take your existing synchronous code and not have to rewrite it into something like continuation-passing style. This is a source of a lot of bugs.
Earlier quoted context omitted.
You probably shouldn't have your browser in full screen mode on a 27" screen
why?
I have a 24" (16:9) screen turned 90°, which works wonders for full screen web pages.
Earlier quoted context omitted.
You probably shouldn't have your browser in full screen mode on a 27" screen
why?
Admittedly we would all lose this habit quicker if resizing windows wasn't such a finicky process in most OSs
I guess one of the applications of Coroutines could be WebAssembly. When you run WebAssembly on a website which needs 100% of the CPU for more than a few ms, you have to use the "setTimeout(fn, 0)" trick to prevent the "this website stopped responding" message. That means you have to store the current state at some point and continue in the function fn (after waiting 0 ms). Languages which support coroutines out of t…
Earlier quoted context omitted.
The only issue of these websites is the width: using the full width of the screen is just too much for reading. If you add {max-width: 60em; margin: auto;} to the body tag it looks much better.
Back in the day, we had multiple windows on the screen at one time, so this wasn't a problem. I think it was Windows which defaulted to full-screen, and led to the plague of sites assuming that the browser would be full-width on a landscape screen, but I could be wrong. Although I love using a tiling window manager now, I kinda miss my old System 8 Macintosh setup, with Netscape open in one window & Think C (or was i…
I haven't found something similar for Windows, but I'm sure there is one.
Earlier quoted context omitted.
You probably shouldn't have your browser in full screen mode on a 27" screen
why?
That way it's easy for everyone to make their own choices. If you want 27" wide lines of text, go ahead and full-screen that browser and have at it. If you want the text you're reading to take up less horizontal real estate than that, then you can easily make the browser itself as wide or narrow as you like.
Earlier quoted context omitted.
> easy to read. Not on 27" with browser in full screen.
CTRL and + to zoom in on Windows/Linux CMD and + to zoom in on Mac or CTRL/CMD and scroll wheel to zoom in/out depending on direction scrolled. Or are you using an ancient browser without zoom?
Earlier quoted context omitted.
You probably shouldn't have your browser in full screen mode on a 27" screen
why?
If you're viewing documents, they're typically more vertically than horizontally oriented. That is, the parts you need to see more of are above/below of the viewable portion, not left/right of the viewable portion. So a browser being used for reading is often more useful when it takes up maybe half the screen on a high-res/large monitor.
If you're accessing webapps, that have more objects arranged horizontally, then going fullscreen may be more useful (think Trello boards and other things).
That page uses very simple HTML. Just paragraphs of text divided into sections with headings. Some code examples laid out side-by-side with a table. Tiny stylesheet. No JS. Loads quickly, easy to read. Warms the cockles of my heart.
The only issue of these websites is the width: using the full width of the screen is just too much for reading. If you add {max-width: 60em; margin: auto;} to the body tag it looks much better.