Wow, this is a pretty great idea. However, I feel it would be difficult to track the thief down with only a fingerprint. Also someone is going to complain about the privacy/security implisecurity of sending fingerprint data through the internet.
Absolutely if there's a bug, there's a bug. By "overstate bugginess" I meant that some people speak as though the software is so buggy that it is difficult to use the computer (example: https://news.ycombinator.com/item?id=11895916). I personally have had a very smooth and pain-free experience with OS X/macOS 99% of the time, and many people I know have a similarly smooth experience.
In the past year since El Capitan I have had essentially zero major issues with the software. I feel that most of the time programmers tend to overstate the bugginess of Apple software - most users I know have a consistently smooth experience.
Green bubble = SMS. Blue bubble = iMessage (data only, doesn't count towards text limits). I would assume the app would only let you use the new features with other iMessage users.
While I understand your position, I'm not so sure that Google, Facebook, and Twitter would look the same today if they charged each user directly for access.
I'm currently a sophomore at Harriton High School in PA. Here's what my day looks like. Ideally wake up around 6:20, sometimes I oversleep to 6:40-6:50. Wake up, shower, breakfast if there's time (when I wake up too late, I'll grab some Clif bars on the way out). Run to bus stop, bus comes at 7:02. School starts at 7:30. 6 classes a day, an hour each. Lunch starts around 10:45. School ends at 2:40, sports start at 3:00. Sports normally go until 5:30, occasionally 4:30. I go to bed around 11:30-12.
I have been using https://www.spectacleapp.com/ for a while now, and it has performed like a champ. Easy window resizing and organization with keyboard shortcuts.
I was considering deploying Postgres (as a container) into a Kubernetes cluster. Kubernetes takes care of service discovery, networking, persistent disk mounting, moving the container if a server goes down, etc.
Wouldn't you have similar problems with Postgres without the container?