1
point
kuekacang
Joined 16 karma
- kuekacangexperiencing how text renders differently, slowly, with my potato battleship
- One other angle yet mentioned: JS is browser native. No matter how slow it is, browser is now the LCD. Similar server-client codebase, while ugly, is another plus.
- I think the hack is to store html height/width locally and restore it as early as possible so the content will then load under the scrolled view
- Oh hey, a fellow noticing person!
- Now ui libraries does its own reset. The no-nonsense blogger just use a few styling, and yeah, the default now is good enough.
- Surely. First time I used clipboard management was long time ago somewhen in windows xp era. But growing older make me not really incentivized on trying myself to relearn clipboard history gestures. I might do that someday though.
The difference is now I know git and text editor with hot-save support; with mostly textual clipboard, the texts usually just land in either git/editor.
- I'm aware of that gesture, but I think it shows the point that it requires extra intention from the user to do select+copy on an input-looking field with copy button attached, instead of being part if the default ctc button experience.
Not that I am searching, but I wonder if there's already tog/nielson/other ux research on this specific interaction.
- Maybe weird behavior on my end? Or perhaps you need to select part of <a>'s content to trigger it?
- Back in the day I requested chrome feature "copy text" in addition to "copy link" on <a> context menu. Now I tried it it's no longer there.
- Recently I've been considering simple click-to-copy button is a bad ux since it can destroy one's clipboard (granted, I'm not using clipboard manager). This might be mitigated with a confirmation before actually replacing the clipboard, but I haven't encountered such implementation. Maybe due to ctc more often appear in tech-related websites.
- Another part are malleable memory. Something I imagine we as humans are accumulating context daily and doing reinforcement training while we sleep.
- It seems like it would be more stable to run windows office under wine instead.
- I think it is due to java already featured the threadlocal mechanism so the ecosystem get used to it. I just recently rediscovering java (w/o framework) when virtual thread landed and I gravitated towards context passing. Even more recently I started reading golang code only to then seeing they were doing the same thing.
- Also many are still using the og 1987 version
- In mobile (at least in mine, firefox) the input become buferred autocomplete and when accepted via return, the typed word gets duplicated before entered. Workaround is to accept via space and delete as necessary
- sftp? That's too modern. We had 3 or 4 vendors that only do ftp via vpn. Also ops and and networking/vpn is on different departments.
> [1] am currently heading to a similar path
- In this regard, chrome refers to the ui, say outside the <html> tag. The browser ui, native context menu, etc.
- To add, octane does a trick that, frow what i grasp from reading the source, it cap for a total of n request (200?) and kill the worker to preemptively free up ram
- Another missed mark is that "dream" needs knowledge. If you don't ever know/experience what's possible, you may not be able to dream about it.