Guess I won't bother after all.

If you prefer markdown and don't need a massive set of features, I highly recommend notable.

I seriously can't believe they don't have at least an EPIRB. If they had one, the entire "they might be on the surface" idea could pretty much be ruled out.

I might be in the minority here, but I feel this is actually a step back.

In the 5 years I've had my phone, there have been two times I've ever really needed to pull the battery, and still the hard reset sequence still eventually worked in both cases.

Anyone remember how some phones had issues with the battery door becoming somewhat loose over time, causing any slight bump to turn the phone off? Many have already commented on how they explode into multiple pieces when dropped. Traditionally the battery covers are incredibly flimsy plastic, even on flagship devices (cough Samsung). Waterproofing is a common concern too, however it actually can be done with a removable battery (e.g. Galaxy S5).

What really needed to be addressed here was how cumbersome it is to get into these devices to replace the battery, and how often people are price gouged to replace them. I believe this could have been better written to allow for either a removable battery, or a standardized and affordable built-in battery replacement process.

Yeesh I hope not.

These are garbage collected languages and come with the overhead of such a process. Rust has no GC process and instead relies on reference counters to statically track live memory.

Wow this is neat!

How can I tell that a post is from another instance when browsing on Kbin? Just scanning the card for this thread, it isn't apparent that it's federated content.