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.

You can totally feel any delay above 5-10ms so that rules out quite a lot of things. I hear people still do it in some fashion.

I have trouble getting local latency below that at times with recording and live playback. Trying to sync together multiple people and keeping it below that is still a bit a ways off most current networks.

It takes about 134 ms for a signal moving at the speed of light to go around the Earth. You can do no better if you have to cross such distances (unless you want to bore through the earth somehow).

So making it possible for people to jam together across such distances is an interesting challenge indeed. Such a delay makes a naive approach incredibly awkward! Good musicians can get around it with practice and using drones, for example.

However, if you're synced to a shared reference /background track, you could play in time to that. The problem is that you can't hear any of the contributions of the other players while you're playing -- the signal is too far away.

But you could imagine sort of controlling an AI mimic which would stand in for you in the ears of the other players, and your contribution would be patched in to the final mix. As a minimal step you could just represent your playing with a couple of loops (A and B pieces) and your improvisations can get auditioned and patched in for later contributions later on in the song.

Some things to think about. It's easier to imagine doing it all in the same area! And you can do in in real space, so that's a plus :D

This has existed (at scale, not just experimental prototypes) for over 10 years. I can't recommend anything in particular as I don't use it myself, but the very first search term I tried ("online jamming") turned up some useful leads. Direct integration with DAWs seems quite easy to set up nowadays.

> 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.

Studies often show Dvorak is faster, but when you dig you discover they are not comparing equivalent. People who learn Dvorak are more likely to be better typists. When you compare equals you discover that the speed of the mind is the limit not the speed of the fingers and so it makes no difference.

As I recall there is one exception: if you are just copying something without having to think about it dvorak is faster. This isn't a common job, but it does exist.

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.

Two identifiers are considered equal if the following algorithm returns true:

    proc sameIdentifier(a, b: string): bool =
      a[0] == b[0] and
        a.replace(re"_|–", "").toLower == b.replace(re"_|–", "").toLower

So, right, looks like it is case sensitive for the first character allowing the same convention from Python. Still, I find it dangerous:

    m_insensitive == min_sensitive

This would be caught by the compiler. If you have m_insensitive declared in current scope you won't be able to define min_sensitive in this scope, the compiler would throw an error.

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