dailyanchovy

Yes, and “genuine question” or “am i missing something?”

Oh that’s not a limitation, it was a choice. You can remove that restriction by changing the appropriate line to scan ~ instead of ~/Documents.

I see. While making this I found that if you hide the Finder sidebar and toolbar (both are options in the menu), then your scenario plays out. In a way it’s nicer than the video on my github.

You can just choose not to use this. Nothing bad about having the choice, so no need to be negative.

I happened to have just finished writing a thesis on such a combination. The size of the little droplets is determined by the chemical wavelength of the reaction-diffusion subsystem. There’s a nice video and a pdf here: https://maximzuriel.nl/dynamics-and-pattern-formation-in-act...

Ah yes, that may be an issue. But that is solved by not installing the "window_title_changed" hook, so that the scripts only take effect when new Finder windows are opened. In that case, windows never move around. All the points you mentioned are issues with the default behaviour of Finder (e.g. when opening a new Finder window as is, you cannot predict where it will open and so it may block other elements).

* coral shaped rock

Math books are only static on your size scale

I found this rule in notes of Feynman's lecture given in the 70's. The rule is extremely valuable if you are in need of doing calculus regularly. Enjoy!

What a spectacularly poor take, it's clearly a joke. Where's my $0.50?

The amount of effort this must have taken is obscene. The creator made a physically accurate pin-hole camera and film inside Blender. I hadn't realised that this is even possible with existing off-the-shelf renderers, let alone open source software. What a blast to watch also.

That is, the fact that the whole package (Blender + the author's work) emulates a physical camera inside an existing renderer is amazing to me.

Unless this is my mistake, and I added all those sites manually in the past (I find it unlikely). Would anyone care to check?

While at my previous work, my manager deleted a message in such a way that it would make the conversation appear hostile from my part.

We were already not in good terms, and it was a small company so there was little to be done. But having seen the message and knowing the intention, and not being able to prove it felt horrible.

I since left (after discussing with the boss).

Yes! But intuition tells me that suspended particles moving past each other make a more fragile system than solid state devices.

Also take into account the difference in refreshes between reading a book (0.05 HZ) and writing (30 HZ). That is, using the display as a general purpose monitor necessitates 600 times as many partial refreshes. I approximate full screen refreshes occur 6000 times more often.

If degradation goes linearly with usage then the lifespan of the display would decrease significantly if used as a monitor. It would be good if someone in the industry could comment on this.

Apologies for the late reply @IshKebab, I read into your recommendations and they are very interesting.

If you wish you could copy your comment verbatim as an issue over here, so we can discuss it further: https://github.com/everydayanchovies/eink-vnc/issues

I will have a chance to test the ping tonight, possibly.

Yes, with his permission.

It is on ubuntu, for sure.

There is a lot of room to play with there, I code monochrome on colour displays too.

Try experimenting with font weight, italics, and combinations. I find that less distracting.

The degradation is speculation on my part. I haven't ever experienced it.

Yes, the 30 fps rate is for small updates. A full screen update (scrolling) is commonly less than ~200 ms, and there are still ways to bring that number down.

I agree, the Libra 2 is great :) Try koreader, it's noticeably faster than the stock reader application.

Off-topic comment ahead.

I'm trying to reconnect with my sister with whom I lost contact while we were kids. I link to this page containing both our names and a way to contact me, for search engines and archives to index: https://zmarshall.nl/static/orian-marshall.html .

Orian (Oriyan / Oryan, Marshall), if you're reading this, please get in touch.

Max

P.S. parent was right in doubting the claim, as a parallel connection from a client on a regular desktop refreshes at 30 HZ regardless of the size of the update.

The explanation is that I take end-to-end network measurements (from request of update to a full buffer of pixel bytes). That delay might be due to the slow processor on device, or an inefficiency in the networking code in my application.

The pixels are classical mechanical, as opposed to LEDs (electrical) or other solid state devices.

The particles in a pixel could deform/burst or clamp together over time, as they move around. Both scenarios lead to decreased contrast.

The less they move the longer the screen will last. I've no experience with the manufacture of those displays but I reason with physics.

I measured and split the latency between the main tasks of a single frame draw.

The main culprit was network delay as I am transmitting raw pixels (one u8 per pixel) compressed with zlib. That's a hit of ~140ms for half a screen.

Next in line is the screen refresh (unmeasured, perceived).

Then the optional post processing (~20ms for half a screen), and housekeeping, like keeping track of dirty regions (about as long).

Lastly writing to the framebuffer (less than 20ms, I don't remember exactly how long).

I took great care to optimise the process, and my next step was to transmit multiple pixels as a single u8 int, the physical display cannot render 255 distinct shades of gray.