3 ms·
> Future work > • Support unicode It's 2016. Virtually every operating system and programming language in use supports Unicode. How is it still so hard to sup
by ygra 10y ago
> Future work
> • Support unicode
It's 2016. Virtually every operating system and programming language in use supports Unicode. How is it still so hard to support it (especially in this case where the data being copied should not matter at all to the actual routines doing the save/restore). Am I missing something fundamental here?
- kevingadd 10y agoThe problem is that they wrote this in JS/node so it's using some sort of horrible bodged hack that interacts with the clipboard using ancient ASCIItext-only compatibility clipboard APIs. It's also polling the clipboard on a timer instead of using clipboard change notifications, which has some relatively obvious implications for power efficiency on laptops, along with the ability for it to miss history entries. This is also a very dangerous behavior for applications that add virtual clipboard data - clipboard data is not guaranteed to be resident, so by trying to capture it as text you may be performing an RPC to the application that put the data on the clipboard and asking it to produce text for you. If the text lives across the network on another machine (this can happen :-D) you may be waiting a while.
- teknologist 10y agoRegarding power efficiency: I've profiled this method. Its impact on battery power is negligible. I guess the best way to ease this concern will be to make the interval variable. Polling is often the only way to access clipboard data (it's that way on OS X, by the way.) Regarding RPC / complex data: This does not happen. Only simple text in immediate memory is captured.
- teknologist 10y agoRemoved from the readme - that's old and no longer applicable. Thanks for flagging it.