“AI” text prediction runs locally. Microphone is for voice to text functionality.
As for the keyboard itself. Ehhhhh. It’s lacking UX features to make it actually usable. I dailied it for a month and had far more typos, text prediction broke whenever a number or symbol was fat fingered into the string. Finding symbols you need was worse than gboard & SwiftKey.
I really want there to be a great open-source keyboard, but none actually deliver on UX atm.
The way Python is implemented, almost all objects in the language are dicts and can be accessed with the
__dict__
dunder. Which has some useful applications when transforming data.But in the case, the interviewer was likely looking for knowledge that one is structured and maintained by indicies vs defined keys. And that searching through a dictionary is O[1] vs list that is O[N] but are inverted for deletion. So if you are doing a lot of inserts and seaeching, use a dict, but if you have something that has tons of deletions, use a list. However, there’s tricks to improve the deletion speed downside that can be used with a slight memory tradeoff.