I'm hoping that Apple releases a new mini on a 3 year cadence. Maybe there wasn't enough demand to continue the line every year, but they'll bring it back occasionally?
I would enjoy this as well, but they need to be transparent about the plans, so people who want small phones can get them. On several occasions I bought something new (that I hated), because I thought the line I liked was dead. Then a year later they release something new to fill the gap.
I bought an iPhone 13 mini the day the iPhone 15 was released and the 13 mini was discounted, with plans to keep it until it was pried from my cold dead hands. Now, less than a year later, I’m not sure how that’s going to go. While I love the size, and have hated every other iPhone since the 5/5S/SE, the lack of RAM on this thing is a real problem. The browser can’t handle some pages, things constantly reload causing me to lose stuff. It’s not great. Some developers have also seemed to stop caring about making sure things work well on the smaller screen. I sent 1Password a bug report, they tested and confirmed it was an issue and said they do still support the Mini, yet the issue remains a year later, last I noticed.
I’ve also wanted the Pro camera setup for years, but it’s only on larger phones, so I didn’t get it. There is this misguided idea that people want small phones because they’re cheaper. I’d pay a premium for a small Pro phone. If they need to make it thicker to fit everything in and give it the same size battery, I’m good with that… it would eliminate the camera bump, which would be great.
I buy my phones through work, so my next upgrade opportunity isn’t for another 14 months. When the time comes, I’m not sure if I’ll be as excited to hold onto the mini. I want to make my point, but also want a usable phone. Not to mention probably wanting some of those Apple Intelligence features. I’m troubled by the whole situation.
I just posted the same thing. I think there are more of us than Apple thinks, at least I like to believe that. I think Steve Jobs was in that camp as well.
When the 12 mini was released I bought it and Apple sent me a survey. It seemed like have the questions were asking if I bought the mini because it was cheaper. It seemed like that was the assumption they were going with. I answered over and over again that I didn’t care about price, and if there were comments I wrote that I was price insensitive and cared about the size, not the price.
I get steep discounts on phone hardware through work, but if they released an iPhone 16 mini Pro tomorrow, I’d pay full price out of pocket, no questions asked.
I'm in the same boat. Want a small phone with premium features. My hope is that the next generation of iphone SE is at least on par with the 13 mini that I currently have. Otherwise, not sure what I'll do when my mini dies since the current SE is a pretty big step down from the 13 mini.
`let` has a performance benefit, which is why they are encouraged. They are only executed if called - but if you setup all the ivars in a `before` block, and all those ivars aren't used in every test they waste time - it can be significant if you are using factories for example.
Instance variables, you mean those beloved things in Ruby that cannot be distinguished between not having been defined versus having being assigned the value `nil`? :p
> but if you are using something before defining it you are going to crash so that's definitely one way of distinguishing it.
Would you clarify? Like that was my point, casually using something where `nil` is a possible assigned value, or maybe the variable hasn't been defined, makes possible the (sadly common) category of bugs where the program does not crash, but proceeds as though the variable was assigned `nil`, but actually the variable was never defined.
In contrast to local variables where the program will crash if you reference the variable but it hasn't been defined.
My comment meant "bare instance variables in Ruby are not great [and we might not want to recommend them as a solution to people complaining about Ruby/Rails quirks]". Do you disagree and actually love the behavior of Ruby instance variables? Or are you simply technically correcting me? (which, again, I appreciate)
> Do you disagree and actually love the behavior of Ruby instance variables
yeah I wouldn't say i love it and i'm not sure why they did that but i imagine they had a reason for it originally. i would say it should have crashed instead of return nil as a default. they did tend to try to make the programmer happier and maybe they did it to that end but i don't see a large upside to it... not too much we can do about not using instance variables though... at the end of the day you just have to be a little more careful.
tests are a pretty good thing to have though and can catch this kind of error.
100% this. We have an L-shaped sofa from them that has lasted through 4 different apartments. One side of the L is longer, and we can easily change the orientation to fit the aspect of the apartment living room.
Owned one. It was a damn good phone, had a great UI that remains unsurpassed to this day, but it clearly came at least two years too late to gain the critical mass needed for a thriving ecosystem.
I loved the UX on it too, but the crappy locked-down web browser killed it for me.. I don't even use apps, but since I couldn't load Firefox with uBlock on there, and there weren't any single-purpose apps, it was really rough
I think the software was loved. It was years before Apple and Android did their own 'natively digital' designs which echoed Metro and Zune's design aesthetic.
> The software was not loved and the app store was lacking.
The app store was definitely lacking. In my own circle of real life users I did not meet one person that did not really like the phone (software included). Granted this is just my own experience so very limited but its also a group of non-technical people just sharing with me. I never heard one complaint in fact it was usually more accolades.
The phone had great software and could run on incredibly low-end hardware like the Nokia 520. I had that phone and it was functional, fast and far better designed than any of the Android equivalent low-ends at the time.
Biggest flaw at the time was Google's shady nonsense involving banning Google Maps/Youtube on Windows Phone without a native app.
Alternately, I found Tiny Habits by BJ Fogg to be more actionable and was able to stick a number of new habits using the recommendations from the book.
What new habits have you picked up? I've picked up a few handy ones, but I am running out of ideas, and some were very 'fragile' in that a shift in routine (e.g. a vacation) completely broke the new habit.
I use profile triggers to change the color scheme of the shell when I SSH to a production server. The color I chose is different from my regular scheme so that it reminds me I am in production and things can break if I'm not careful.
As someone who uses Stripe for a SaaS product, this is an amazing feature. It means not having to email/call the client just because they got a new card, and instead billing keeps going as if nothing changed.
