JohnEdwa

They don't. But nevertheless, the progress they've made in a year is very impressive.

The question left to be seen is how it'll look in a year or two: hardly any improvement, or a beaten elite four?

Libel requires the claims to be published or broadcasted, so it isn't. A predictive text algorithm strung some random words together, and the guy got offended.
It's like suing because your phone keyboard autosuggested "is a murderer" as the next words after you wrote your name. Btw, I tried it a few times for lulz and managed to get it to write out "bluGill and the kids are going to get it on", so I guess you can sue Google now?

I spent a night in the ER, had some tests done, puked on the CT scan machine, got some meds, and the most expensive part of that trip was the taxi home.

Yes.

That's weird, it isn't for me.
Try https://archive.ph/iULP4 or https://web.archive.org/web/2/https://www.wired.com/2016/12/the-inside-story-behind-pebbles-demise/

The Pebble app was removed from the App store, so you have to manually sideload it every 7 days.

And:

Here are the things that are harder or impossible for 3rd party smartwatches (ie non Apple Watches) to do on iPhone:

• There’s no way for a smartwatch to send text messages or iMessages.
• You can’t reply to notifications or take ‘actions’ like marking something as done.
• It’s very difficult to enable other iOS apps to work with Pebble. Basically iOS does not have the concept of ‘interprocess communication’(IPC) like on Android. What we did before was publish an SDK that other apps (like Strava) could integrate to make their own BLE connection to Pebble. It was a clunky quasi-solution that other apps didn’t like, because it was hard to test (among other things)
• If you (accidentally) close our iOS app, then your watch can’t talk to app or internet
• Impossible for watch to detect if you are using your phone, so your watch will buzz and display a notification even if you are staring at your iPhone
• You can’t easily side load apps onto an iPhone. That means we have to publish the app on the iPhone appstore. This is a gigantic pain because Apple. Every update comes with the risk that a random app reviewer could make up some BS excuse and block the update.
• Because of iOS Appstore rules, it would be hard for us to enable 3rd party watchface/app developers to charge for their work (ie we can’t easily make an appstore within our app)
• Getting a Javascript engine to run in PebbleOS forced us to go through many hoops due to iOS — creating a compiler inside the Pebble iPhone app that in itself needed to be written in (cross-compiled to) JS to work with Apple's restriction on downloadable code can only be JS
• As a Pebble watch/app developer, using the iOS app as relay to the watch sucks since the "developer mode" terminates every few minutes
  https://ericmigi.com/blog/apple-restricts-pebble-from-being-awesome-with-iphones

There was/is a companion app called PebbleNav/NavMe that worked okay-ish, as long as you could survive with "Turn left in 100 metres to x street" type instructions with no map view (not really something you can do with 144x168 pixels).

Yet they are also the same - E Ink is an e-paper display.
Electronic paper is a category for any low energy display tech that looks kinda like paper, E Ink is a brand name for a "Microencapsulated electrophoretic display" from E Ink Corporation. Also just known as E-ink because IIRC they have the patent on it so nobody else can actually make them.

Pebble still works thanks to the Rebble project. Everything else is free, but the dictation and weather services require a monthly $3 subscription to use as those are the parts that have rather hefty API call costs.

Though the experience is miserable on iOS. That's entirely all thanks to Apple.

due to Pebble selling out to Fitbit.

Due to Pebble going bankrupt, and managing to sell its software assets to Fitbit to gain just enough money to refund the kickstarter pledges and pay off it's biggest debts.

That would require starting a database with the purpose of cataloguing every single part number in every single device that exists, which while technically possible, is rather unfeasible without extensive manufacturer cooperation.
What iFixit is doing is the other way around, they are telling what device a certain part number they carry fits in - as in their example, what Lenovo laptop that specific battery is compatible with. That's a problem multiple orders of magnitude smaller in scope.

In a perfect world though that information would be available in the repair manual and schematic that came with your device, as they usually did a few decades back. Alas, that's something that's never going to happen again because it hurts profit margins.