robertknight

6 ms·

31.
by robertknight 5y ago
> added anti-features like preventing export of the DB (or something like that, I don't remember exactly what it was anymore) The application's internal SQLite database was encrypted. The user-facing export functionality is sti
32.
by robertknight 6y ago
An option in some languages is to simply create an alternate mock/fake version of the actual class or function that is depended upon and monkey-patch the code under test to use it for the duration of the test. This is commonly done in
33.
by robertknight 10y ago
> But actually most FW has AOT already then. I'm not sure about "most", its relatively new amongst currently popular frameworks. Assuming I understand correctly that the script execution time figures he provides are for th
34.
by robertknight 11y ago
What problems do you have with the architecture?
35.
by robertknight 11y ago
> Dart + "Unfortunately, due to iOS restrictions, updating your Flutter app over the network is not possible" means 100% no thanks from me. Indeed. One of _the_ biggest selling points of React Native is the promise of near-ins
36.
by robertknight 12y ago
Indeed - I've documented what I've learned thus far at https://github.com/robertknight/passcards/blob/master/lib/ag... I did create a test vault with every item that 1Password v4.x support
37.
by robertknight 12y ago
I've been working on a pure-JS browser extension for Chrome/Firefox which supports two-way sync with existing 1Password vaults via Dropbox that has the ability to add and edit items: http://robertknight.github.io/p
38.
by robertknight 12y ago
The more general name for this approach is structural typing - http://en.wikipedia.org/wiki/Structural_type_system
39.
by robertknight 12y ago
> The README says 'Better security now that you > can have a different password for every server > if you'd like'. Can you explain a bit more about your situation? I'd expect most people managing a lot of server
40.
by robertknight 12y ago
How far do you have data going back? It would be interesting to see whether user attitudes towards social logins have changed over the past 3-4 years.