Actually you don't need any third party software to do this, Apple does provide a way of doing it, and if you have a look at the code of this program, it seems to be just a wrapper of this functionality: https://support.apple.com/en-us/HT201372
Seriously. They have a neat project, but this is one of those cases where they need to seriously seek out constructive criticism because that is just terrible. The narrator is trying to sound almost carnivalesque but the result is a slurred monotone of barely decipherable words.
Doesn't work.. Chrome on mac. Which browser did you actually tested it on? :P
It doesn't look like a good idea to show it to the public before testing it on a few of the most popular browsers... It isn't so hard to do..
That said, the bar to creating plugins these days is much higher. It needs to be testable, and I'd implore the author to add unit tests.
Aside from that, it's quite a bit of page weight for this lil feature. I really would like to not have to add jQuery-ui and store.js to get it to work.
Well he said he posted it to find out in which browsers the plugin has issues. I just said it is a better idea to test it himself, that it isn't so hard to do. I don't see why I'm being a dick, and I spoke with respect.
I'm tired of people overreacting over this kind of things, we don't need to be extremely polite all the time, it's tedious.
That being said, I hope he gets it to work properly, seems like it could be a very useful plugin...
Seems like this is testing 101. the guy is right, he should have tested it on major browsers before showing it. Getting excited and posting it is no excuse for not doing some preliminary testing. So please refrain from being a dick by calling someone else a dick. Thanks
It's sometimes said that if you aren't embarrassed by your product at launch then you've waited too long. It's important to get early feedback, and build on early reactions and responses.
Likewise, by making ideas like this, along with an early investigation, perhaps someone can build on it, or throw out another idea, and perhaps people can work together to find a good solution to the mess that is current user identification.
Or would you rather people beavered away in secret, never sharing ideas, never sharing their results, and never working together?
And it differs quite a bit based on _what_ I am typing, too. Plus the tactivity(?) of the keyboard factors in, because as soon as I have feedback that the key was registered, I am on to the next one.
Especially if a Dvorak user is forced to use Qwerty on another person's computer. At that point, they become completely unable to log in via this method.
