If you prefer markdown and don’t need a massive set of features, I highly recommend notable.
If you prefer markdown and don’t need a massive set of features, I highly recommend notable.
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.
Yeah, I’m probably going to bite the bullet and start working on Kbin too. I’ve avoided PHP for my entire career just by chance, so all I know are the memes and what I’ve read of (usually older) codebases. From what everyone says, modern PHP isn’t really that bad, and from what I can tell when perusing the Kbin source, the implementation is pretty clean.
This exactly. I’m a software engineer and I’m itching to contribute to one of these systems, but I do not agree with some of the stuff I’ve seen posted by one of the developers of Lemmy. It just leaves a sour taste in my mouth about the whole thing.
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.
Guess I won’t bother after all.