I have an iPhone 5 (4 year old phone) running the latest OS and it works fine. No, it's not as fast as the latest devices, but it works adequately if one desires to keep using their 4-year-old device.
While I agree that's been the case in the past, supported devices are fast enough now that it really doesn't slow them down anymore. Even the lowest supported device runs well on iOS 10, and it has gotten official updates years longer than all android devices I know of.
Sure, one could install an updated and more secure rom (assuming it exists for your device). But, the vast majority of users don't care or won't bother to go through that process, rendering it a completely ineffective solution for the general consumer market.
But even if Apple may be better than most android manufacturers, Apple still doesn't support devices it considers "Obsolete"...and there is nothing you can do about it other than buy a new phone since the bootloader is locked down. According to https://en.wikipedia.org/wiki/List_of_iOS_devices anything before iPhone 5 is considered "Oboslete" and they don't seem to be releasing updates. On the other hand, I've been happily using my Samsung S3 which cyanogenmod has been pushing latest android updates to nightly...and that is likely to continue as long as there are enough of us who care, even if cyanogen and samsung goes away.
For the record, the Galaxy S III was released in the same year as the iPhone 5 (2012), so for now your device hasn't lasted any longer than an iPhone. But I don't doubt that it will.
You're probably better off using a stock Android derivative built for OPO. There's always a nice variety of them on xda-developers.
I used to use CM on everything but over the last few years I've been plenty happy with pure stock Android (+ root). Didn't end up using most of CM's extra features and found that it was often unstable and/or leaving lots of things just sort of half-working.
If you have a popular device, that idea is fine. If you don't, I'm not sure if you're going to have much of an option moving forward. Less common devices frequently have phone-specific builds of popular distributions like CM published by a developer-user on xda as their only non-default option.
Even CM's support for a wide range of hardware was mostly bankrolled by Cyanogen Inc, which will now no longer be funding them as they rebrand under LineageOS. It's unclear whether any but the most popular phones will continue to see support from a group that has "actual reputation" on the line or not.
OnePlus (One) hasn't been really updated well at all, Both Cyanogen and Oxygen OS builds were late and filled with problems.
That was true pretty much out of the gate.
The newer phones come with Oxygen OS or w/e they call it now and at least get some sort of periodic update.
The AOSP fork for bacon is still quite well supported. I'm sure the community support would be enough for security patches and updates given how massive it still is.
Most, if not all, languages that work on the server side eventually develop a "minimalist" "web framework" in reaction to the "bloat" of some popular fully-feature one. Particularly coordinated languages even eventually develop a barebones server backend that allows you to potentially even plug them together, like Python's WSGI.
Generally these frameworks are met with general acclamation on HN. (Followed by a lot of replies generally defending the larger frameworks, which then devolve into a couple of threads about how hard it is to pack resources together, the importance of a "blessed" ORM, and the security implications of requiring people to assemble their own security stack for things like CSRF, etc.)
Are they less worthy if they're simply built into the language from day one? A lot of recent languages are taking such a tack, after all.
When I go to a supermarket, I have to deal with finding the stuff I need, way too many people in the store, etc. but at least I can take my stuff home immediately.
When I buy online I have to wait for delivery, but at least I don't have to go looking for stuff in 20 different isles only to find out the thing I needed is in a completely illogical place, or deal with all the people there.
This concept combines all the disadvantages of physically going to a supermarket with all the disadvantages of buying online. Amazon's concept actually improves the physical buying experience.
Going to a (small) supermarket is not a disadvantage, I find it a nice experience, because you can see/smell/touch) the products you want. I wouldn't buy fruits, vegetables, meat, fish, cheese, etc. online.
Not being able to take your stuff home is a little annoying, but depending on where you live it can be almost necessary to have groceries delivered. In Paris many buildings don't have elevators at all, or very small ones that can hold at most two people and not many bags. If you live on the 5th floor you're happy to get someone bring the bags up the stairs for you.
For me, it really depends on how reliable the market is. If I know produce and fish are going to be reliably high quality and fresh, I'd be more inclined to use an online service. However, that's not really the case with the average supermarket and therefore I prefer shopping in person. (If it were available where I live, I'd probably use Instacart with Whole Foods from time to time, but I'm lukewarm on using Peapod which is available for me.)
Is going to the store such a big disadvantage? I work from home, I spend most of the time physically away from people. I do enjoy my shopping. You know, a little bit of interaction with people. I have tried online shopping with delivery when living in the UK. Very often, at the door, it turned out that X, Y and Z was not in stock and I had to go to another shop and find the missing bits myself. Waste of time...
That was pretty much what I found while I was using grocery delivery (Peapod) because I was on crutches. This was a while back and there are generally more options today (though not where I live fr the most part). I'd get substitutions I didn't care for and random common items I absolutely needed for a recipe would be out of stock.
I could imagine using a reliable service again but, so long as driving to the store and shopping is straightforward, ordering online for delivery isn't something I really need.
Depends how much time the physical delivery takes. From my experience Monoprix picks high-rise locations (not like WallMart). Most of its customers should be at walking distance.
I don't want to speculate but it would help if a french gentleman tells us his experience.
You're right, every city I used to live in France, I had at least 1 Monoprix within a short walk distance. Where I currently live, I can get to 3 different Monoprix in less than 10 minutes by walk.
Never seen a Monoprix outside of a city anyway:)
What Amazon ad didn't show is a huge cart full of items which will have to be unloaded into the car then again from the car to the house. That's not negligible when the weather is cold.
Until you need a solid search that spans across the nested directories then you start wasting significant time with regular expression and complex commands.
Because he had "considerable problems" with his Apple products? Basically Apple release unfinished product and let users test it - and it shows in the software quality.
(Don't even ask about the quality of any of their "1.0" products - full of bugs every time, newest example is the touch bar.)
