federico3

Figma does not seem to tie into the OS UI primitives.

What is the experience for visually-impaired users that need high contrast UIs or braille terminals?

I always wondered why there aren't synchronous "audio conferencing" tools to allow play music and even improvise over the Internet.

Of course they would have to introduce a fixed delay of a phrase (or multiple) and people would have to play accordingly.

> It's not faster, that's a myth

This is false. There a plenty of statistics showing that Dvorak is faster (albeit it's true that the main benefits is around finger movement)

> native hardware keyboard layouts

Never been a problem: you don't need (or want) to look at the keys anyways.

> limits to the users ability to configure software keyboard layouts

Also not a problem: you cannot touch-type on a phone and also you type with thumbs.

Dvorak. I know 5 people, including myself, that switched to Dvorak and none of us regretted it or switched back.

It's not about speed, at least for me, but reducing stress on fingers and prevent inflammation and RSI.

Touch-typing comes easier with Dvorak. Even better if you use a Dvorak layout on a querty keyboard: there's no point in looking at the keys and this is also good for back/neck posture.

Please ignore all the people who insist on using qwerty without having had at least a year of Dvorak use experience.

> meant to be airtight rather than RF-tight

You are thinking about the wrong one.

Actually, VariableName != variable_name

You can write ClassesLikePython and variables_like_python in Nim.

Sometimes people end up having dangerously similar variable names in the same scope, e.g. username and user_name, where an incorrect tab-completion might introduce a bug. Nim would require the developer to choose better names.

Keep in mind that Nim is statically typed and the typing prevents ambiguity: foo.say_hi() and SayHi() are not the same.

Author here. Please be aware that the project has no releases, it's not on PyPI and it's little more than a proof of concept.

I have no intention to mislead any user into running it so I'll remove the repository for the time being.

> This looks like an enjoyable source for weird bugs

It's meant to prevent them: in Python applications it's not uncommon to see bugs introduced by an incorrect completion, e.g. updatePlayerstatus / updatePlayerStatus / update_player_status

With case/underscore insensitivity you know in advance that there can be only one "updateplayerstatus" in your codebase and write it according to your style, e.g. always update_player_status

> Many Secure Boot implementations let you load your own keys.

And there is no promise that this will not change.

> individual sessions are typically much shorter than route change intervals

True for web traffic, not true for large file transfers, many multiplayer games, VPNs.

> live connections can get rejected and closed immediately by the new server allowing for rapid recovery

...if the client protocol allows recovery.