Betelgeuse90

Honestly I used to think the same way about JS, because not having types allowed for very concise code sometimes. But the more I used Swift I realized how powerful type inference can be, and the difference in conciseness shrunk to basically nothing.

I feel you. There’s so much good stuff out there.

But you’re only capable of handling so much. You’re under no obligation to process every piece of information you think you might like, and moreover - you shouldn’t. You’d be setting yourself up for disappointment.

The way I work is I acknowledge my limits and follow my gut. Sounds vague but that’s what I got.

IIRC the main appeal of CoffeeScript was syntactic sugar like lambda expressions etc that were missing in ECMAScript 5. I think ECMAScript 6 made most of the appeal of CoffeeScript obsolete

Waiting to see if people on new ATX 3.0 PSUs suffer the same issues.

It looks like the 12VHPWR cables don't bend very much close to the connection itself.

The Swift code that's generated is pretty good, but I found myself pretty much immediately wanting to edit it.

I now maintain a separate copy of the templates that implemented some missing features of the spec that I needed, and adjusted access control etc to suit my needs. And I also feel like checking the generated code into source control is the way to go, if only for the build time improvements. I mean it doesn't change often enough to warrant being rebuilt all the time.

Exactly. This is why I got into indoor boulder climbing. It's hella fun, and as long as it is I'll push myself without even trying.

Wikipedia says the iPhone 5S was released in September 2013, So that's about 6-7 years of updates. The chart you linked seems wrong to me. Am I missing something?

But the existence of competition or lack thereof can have its own effects, some of which are actually desirable and make the iPhone have the draw that it does.

If Facebook had a worthy competitor for example, surely you'll agree Facebook would be a considerably different product now. You might say that doesn't help my case, because it would actually be a better product, but it's not an inevitable outcome in every comparable scenario.

I'll quote another guy from this thread:

"I like that TrueCaller on my iOS device works for most features without getting any permission from me, while on Android it refuses to buzz from the splash screen unless you give it every permission - including full contact access and phone.

I like that on iOS a famous payment app from India (PhonePe) works flawlessly with zero permissions but on Android? It needs both location and contacts to even function - neither of these are mandatory for their functioning but still they do and can get away with that.

You know WhatsApp doesn't let you use "Status" feature unless you provide Storage permission to it on Android (I doubt they need it just to shows those images, videos, and texts)."

I think it's important to note that the mere existence of controls, i.e buttons that do a thing, don't actually end up achieving their goal of improving user privacy unless there's also enforcement of usage patterns. You can't get away with stuff like this on iOS, and it's clear by these accounts that the same companies would do the same on iOS if they could.

Worth noting that WebP support was added to Safari 14 in Big Sur and iOS 14.

Wow man I'm really feeling that. I also have a great 16" and I'm experiencing similar issues with it. The new M1 MacBook Air is already as fast as my machine and costs less than half. It's bonkers. I use two external monitors however and the Air doesn't support that, so that's one thing keeping me away from the new M1. I imagine the new 16" MacBook Pros will support more than one external monitor, and I don't think I'd be able to stop myself from getting one.

I don't see what's stopping these developers from lowering prices for users in less developed countries.

YouTube shows a monkey for me in Israel