Stuff like constant folding won't take place until you hit an optimizing compiler tier. For the interpreter and baseline/template-compiler tiers, there's just not enough time to do that sort of dataflow optimization. So yes, it would help at least somewhat, esp. if you don't think the code is likely to tier up much for whatever reason (no one part is all that hot, or perhaps it's too polymorphic).
> No amount of baby cash, or white picket fences, or coercion, or lack of birth control, or whatever other set of schemes you can make, none of that matters.
This is a profoundly unscientific statement. All of these things matter, you just aren't willing (or rather think, correctly, that our society is not willing) to try them in earnest.
Per the studies that I have seen over on Fertility Twitter, none of them seem to really make much of a difference.
Right now they are on a meme where they want to turn large tracts of national parks into suburban developments because some study said that apartments are bad for families. I ... its ... yeah...
All the studies seem to contradict, meaning that likely they are having little to no measurable effects.
'Yeah, we just need to try harder though'.
I mean, yeah, we're mostly trying to exhaust those 80-20 effects right now and see if anything sticks. From the little I have seen: nope. It's the proper way to look at it. Go for the cheap stuff with big effects, then see.
But you're right, it may be more like a 99-100 thing, where you kinda have to get it all right before it kicks off. We don't seem to know right now and are still exploring the space.
Because beforehand engineers could be reasonably confident that their work would simply accelerate a the growth of a growing pie; today, most expect that further development will be used, first and foremost, to replace labor. Most sectors do not grow indefinitely, so there's no reason to assume software has to.
To put it gently, yes it feels different: for people who haven't already saved a lifetime of SWE wages, this is the first credible threat to the sector in which they're employed since the dot com bubble. People need to work to eat.
> iPhone and macOS are basically the same product technically
This seems hard to justify. They share a lot of code yes, but many many things are different (meaningfully so, from the perspective of both app developers and users)
Lockdown mode costs ~nothing for devices that don't have it enabled. GP is pointing out that the straightforward way to implement this feature would not have that same property.
You'd be surprised how many Apple engineers are fixing many bugs, of this caliber, on a semi-regular basis.
That "Human Hours Wasted" is not just sitting there because engineers don't care about it, it's because there are many many other opportunities to save similar amounts of time. Crashes waste time, perf bugs waste time -- and security bugs are much worse.
I really doubt everyone or even a tiny fraction of people at Apple are working on opportunities to save more time than fixing the repeated autocorrect issue. It affects everyone and it's been a meme since forever.
At this scale, some bugs become features. I think fixing the bugs would need lots of conceptual work, due to the fact that there are millions of users of these apps.
reply