Or like with the M1 chip: wait until the incumbent alienates so many experts in the field that you can scoop them up and they will succeed partially fueled on spite against their old employer.
From a financial market perspective, AAPL is the second highest valuation for a publicly traded company and #1 is in first place because of the AI bubble.
What people hate about Apple is that they ship things other people couldn't get to capital-W Work, and they're seen as 'stealing' the idea instead of perfecting them.
Your dismissive tone is really discouraging me from replying with a legitimate answer to your concerns.
So you only get: people have been predicting the imminent demise of Apple every year for the last 20 and they are still the most valuable non-bubble stock in existence by a country mile.
Keep whining, I'm going to retire early on your whining.
Hank Green mentioned in passing the other day how ungodly much money Apple is making off of airpods. I still have managed not to get one. But the watch and iPad definitely counts as something after the app store.
Which they didn't really invent the app store either. What they did was break the stranglehold cellphone carriers had on cellphone software, and we should kiss their butts every single week for that. Most people didn't work in mobile prior to the app store and holy shit.
I don't know why this is a surprise to anyone. Apple is famous for watching peanut butter and chocolate makers and swooping in with Reece's Peanut Butter cups while everyone scratches their head because they've had better chocolate and better peanut butter so what's the deal?
When and if Apple pulls the plug on AI, we can declare it dead for this cycle. See you all again in 2040.
I understand that turbines are very handy in power generation but we don't use gyroscopic power storage because the inertia gets scary at high RPMs. Turbines lake the momentum but make up for it by being entirely made of knives. You lose an engine mount or throw a blade and you're deep in the shit.
I don’t understand your point about UPS 2976. You make it sound as if people there were hurt by the engine parts hitting them. But in actuality it is the airplane crashing into them which killed those unfortunate.
Even aviation turbines are quite safe and uncontained engine mallfunctions are very rarely a problem. On top of that there is every reason to think that ground based power generating applications can be even safer. There weight is much less of a constraint, so you can easily armour the container to a much higher assurance level. The terrestrial turbine is not jostled around so you have less of a concern about gyroscopic effects. And finally you can install the power generating turbine with a much larger keep out zone. All three factors making terrestrial power generating jets safer than the aviation ones.
The plane suffered an engine mount failure, which tore a hole in the wing, sprayed shrapnel into engine 2, which caused a compressor stall reducing thrust past the survivable level. Then it crashed into a fuel recycling plant with a full load of jet fuel.
The scary part of the mount failure is that the mounts cracked in an unexposed part where visual inspection did not reveal the damage. It wasn't due for a teardown and inspection until it had traveled 25% (80% of the maintenance window) farther. That's why they grounded the entire fleet.
Takeoffs are dangerous because they run the engines hard, and parts are operating in the supersonic range.
I’m aware of the facts you say. But they have nothing to do with terrestial operations. If the same thing happened to an engine sitting next to a data center the worst thing which could happen is it knocks the neighbouring engines out too. And if you are worried about that you can add more armouring between the engines. Which you can do because they don’t need to fly. Heck you can put a row of hesco barriers between engines in a terrestial application. But either way the data center is not going to suddenly fall on a fuel recycling plant.
(A couple of decades ago I worked for a company that was a tenant at a datacenter that used these instead of batteries; it's not new or particularly exotic technology.)
The thing that has made me feel the oldest this week is that someone I used to mentor posted a holiday pictures with visible wrinkles. If people you think are young look old, then buddy, check the mirror.
But this is a close second. 10 years? That can't be right. Even accounting for Covid Time Dialation.
Until you get high memory contention from the rest of the code. Once eviction gets high you get some pretty counterintuitive improvements by fixing things that seem like they shouldn’t need to be fixed.
My best documented case was a 10x speed up from removing a double lookup that was killing caches.
My best improvment was just bit-interleaving both axes of a 2x32bit integer coordinate (aka z-curve). I obtained factor ~100x (yes factor not percent) throughput improvement over locality in only one dimension. All it took was ~10 lines of bit twiddling. The runtime went from a bit above 300ms to slightly less then 3ms.
End to end gets weird. I was asked to look at an admin page, nobody could figure out why it was 30s. Literally the first thing I tried got it under 4 and the second down to three. It was pulling the same list of rows twice, applying two filters and then looking at the intersection. I changed the signature to send the list as input instead of the query constraints. Then I changed them to avoid the intersect.
If you would have asked me to bet on which one would have had the bigger impact I would have split the difference.
My second favorite was similar. Two functions making a call instead of sharing the answer. Profiler said 10% cumulative. I removed half. Instead of 5% I got 20%. Which just demonstrates how much data a profiler cannot show you.
Profilers lie and some more than most. I’ve gotten 3x from code with a perfectly rectangular profile output.
Part of it comes down to a trick game devs steal from finance: give each task a budget and keep it to the budget even if it’s not the tall tent pole.
You should not spend 10% of your response time on telemetry and logging combined. Yet I pulled 10% TTFB out of just the logging and telemetry code on a project. It was a frog boiling situation. Every new epic used the new code and determining the cumulative cost wasn’t easy.
reply