From Apple: Memory prices finally hit Apple products, and the price increases are quite steep--much more than I assumed they would be. Was looking to upgrade my M1 Pro 14" to a 16" M5 Pro last...
From Apple:
We have never seen a component price increase this much, this quickly. We have shielded our customers from these increases so far, but we have now reached a point where we need to begin raising prices on a number of products, including today’s increases for iPad and Mac. We know this is not welcome news, and we are working tirelessly to find solutions.
Memory prices finally hit Apple products, and the price increases are quite steep--much more than I assumed they would be. Was looking to upgrade my M1 Pro 14" to a 16" M5 Pro last night, and in less than 24 hours it's gone up $300 (even with education discount). Makes me a little worried about how much more they could raise it given their open-ended statement about increases down the line...
To some extent it feels like we're experiencing the downside of companies trying to shield consumers from the increased cost of components. As we now see the bigger "shock" increase for the end...
To some extent it feels like we're experiencing the downside of companies trying to shield consumers from the increased cost of components. As we now see the bigger "shock" increase for the end product, compared to smaller more frequent increases.
Sadly I think may mean in future that companies will be faster to pass these increases on again in future, compared to absorbing short term ones like they have in the past.
The alternative is, in many ways, just as bad. If prices are adjusting on things like computers every quarter you wind up with all sorts of supply/demand shock issues as well. It's a screwy...
To some extent it feels like we're experiencing the downside of companies trying to shield consumers from the increased cost of components. As we now see the bigger "shock" increase for the end product, compared to smaller more frequent increases.
The alternative is, in many ways, just as bad. If prices are adjusting on things like computers every quarter you wind up with all sorts of supply/demand shock issues as well. It's a screwy situation all around.
It’s not gonna happen. I’m sorry. We just don’t have the technology to render text and images without uploading 500MB of JavaScript on the side. The people who knew how to do this retired long...
It’s not gonna happen. I’m sorry. We just don’t have the technology to render text and images without uploading 500MB of JavaScript on the side. The people who knew how to do this retired long ago, it’s like trying to find a COBOL developer.
It's not that we don't exist, it's that tech companies prioritize software quantity over software quality. It's why AI coding is actually a disaster for the industry as a whole, because it is...
It's not that we don't exist, it's that tech companies prioritize software quantity over software quality. It's why AI coding is actually a disaster for the industry as a whole, because it is almost exclusively being used to further prioritize quantity.
When is the last time a tech company put out a new piece of software that people actually love? It's all just crap users toloerate. I remember back when Adobe would launch a new version of Photoshop and people would actually get excited about dropping $500 on an upgrade, rather than feel resentful that their Creative Cloud subscription just go more expensive to justify some half-baked new feature nobody cares about.
Even worse than that sadly. There's plenty of engineers who can optimize such apps. But they are getting cut off in lieu of whoever can make it fastest and cheapest. It's simply not a parameter to...
Even worse than that sadly. There's plenty of engineers who can optimize such apps. But they are getting cut off in lieu of whoever can make it fastest and cheapest. It's simply not a parameter to consider on the sales end.
I think that's why there's hope this is a silver lining, because it might be. AAA games for example can't just buy a $4k GPU at the start of development and expect it to be available and...
I think that's why there's hope this is a silver lining, because it might be.
AAA games for example can't just buy a $4k GPU at the start of development and expect it to be available and affordable in 2-10 years when they finish. There's a small chance we see RAM sizes shrink due to costs and we're down to 8 and 4 as standards again, although hilariously one of the major bottlenecks there for consumers is windows.
JOKES ON YOU I REFUSE TO LEARN! But seriously coming from the business programming/mostly backend side, I have done damn near everything to avoid JS as it so often seems like a wild amount of...
JavaScript
JOKES ON YOU I REFUSE TO LEARN!
But seriously coming from the business programming/mostly backend side, I have done damn near everything to avoid JS as it so often seems like a wild amount of overhead (in my case, in obnoxious JS rules) for little gain.
I'm hopeful libraries like HTMX/Datastar can gain more popularity and the throttling of basically every part of the computer finally hitting will lead to better frontend development all around, because it's such a frustration if you aren't a JS programmer and then hit that point and people say "well just use react/whatever"
I don't think JavaScript itself is the problem so much as bloated React apps. They're often wildly inefficient, with no real structure to ease optimization.
I don't think JavaScript itself is the problem so much as bloated React apps. They're often wildly inefficient, with no real structure to ease optimization.
JS (assuming you are using tsc for static analysis) is a pretty nice language. The issues crop up when people see npm as a candy store and install packages without any consideration to how much...
JS (assuming you are using tsc for static analysis) is a pretty nice language. The issues crop up when people see npm as a candy store and install packages without any consideration to how much data they're sending to the client or how many extra cycles are getting wasted.
The problem is that for anything that runs on people's devices, developpers have almost no incentive to optimize anything beyond the absolute bare minimum of making it work on most low end devices...
The problem is that for anything that runs on people's devices, developpers have almost no incentive to optimize anything beyond the absolute bare minimum of making it work on most low end devices under favorable circumstances.
because of this, the only way for apps and websites to be well optimized is to have the devs working on them to be sufficiently knowledge, interrested and to have enough choice about what this can work on to be able to pick optimisation work insted of working on the next feature/app.
There's no money in that. We might see some great value cloud subscriptions though. Realistically I think the worst offenders have too much network effect to care. But maybe we'll see more...
There's no money in that. We might see some great value cloud subscriptions though.
Realistically I think the worst offenders have too much network effect to care. But maybe we'll see more migration to the smaller alternatives.
Well, it looks like I won’t be looking to upgrade my 2024 Mac anytime soon. Although to be completely honest, I really wasn’t looking to upgrade my Mac anytime soon anyway. These things are pretty...
Well, it looks like I won’t be looking to upgrade my 2024 Mac anytime soon. Although to be completely honest, I really wasn’t looking to upgrade my Mac anytime soon anyway. These things are pretty bulletproof. They run for decades if you take care of them.
I’ve actually been getting into the hobby of retro computing with 8 bit, 16 bit, and even 32 bit systems. If you count the Athlon as the first widely available consumer-grade 64 bit system, those are already vintage. If you count the 64 bit systems used by Sun Microsystems and some of the others in the 1990s they’re even older than that.
We used to get a lot more mileage out of our computers before manufacturers started touting huge ram chips, giant GPUs and more storage as the solutions, instead of better programming techniques and more thoughtful architecture and design of software.
I’ve never agreed with the concept of needing to improve over previous generations for minor iterations of speed. I’ve always been more of a proponent of doing more with what you have, learning the architecture that’s already in place and how to use much more thoroughly and efficiently. I’ve always called it using the entire buffalo.
From Apple:
Memory prices finally hit Apple products, and the price increases are quite steep--much more than I assumed they would be. Was looking to upgrade my M1 Pro 14" to a 16" M5 Pro last night, and in less than 24 hours it's gone up $300 (even with education discount). Makes me a little worried about how much more they could raise it given their open-ended statement about increases down the line...
To some extent it feels like we're experiencing the downside of companies trying to shield consumers from the increased cost of components. As we now see the bigger "shock" increase for the end product, compared to smaller more frequent increases.
Sadly I think may mean in future that companies will be faster to pass these increases on again in future, compared to absorbing short term ones like they have in the past.
The alternative is, in many ways, just as bad. If prices are adjusting on things like computers every quarter you wind up with all sorts of supply/demand shock issues as well. It's a screwy situation all around.
I really hope on the bright side of this price increase, we start to see more efficient, less memory-hungry apps.
It’s not gonna happen. I’m sorry. We just don’t have the technology to render text and images without uploading 500MB of JavaScript on the side. The people who knew how to do this retired long ago, it’s like trying to find a COBOL developer.
identification division.
program-id. hello.
procedure division.
a-main section.
move 'trim' to WS-DEVELOPER-NAME
display 'hello from ' WS-DEVELOPER-NAME upon syserr
stop run.
COBOL developer since 1994.
I like your funny words magic man
It's not that we don't exist, it's that tech companies prioritize software quantity over software quality. It's why AI coding is actually a disaster for the industry as a whole, because it is almost exclusively being used to further prioritize quantity.
When is the last time a tech company put out a new piece of software that people actually love? It's all just crap users toloerate. I remember back when Adobe would launch a new version of Photoshop and people would actually get excited about dropping $500 on an upgrade, rather than feel resentful that their Creative Cloud subscription just go more expensive to justify some half-baked new feature nobody cares about.
Even worse than that sadly. There's plenty of engineers who can optimize such apps. But they are getting cut off in lieu of whoever can make it fastest and cheapest. It's simply not a parameter to consider on the sales end.
I think that's why there's hope this is a silver lining, because it might be.
AAA games for example can't just buy a $4k GPU at the start of development and expect it to be available and affordable in 2-10 years when they finish. There's a small chance we see RAM sizes shrink due to costs and we're down to 8 and 4 as standards again, although hilariously one of the major bottlenecks there for consumers is windows.
JOKES ON YOU I REFUSE TO LEARN!
But seriously coming from the business programming/mostly backend side, I have done damn near everything to avoid JS as it so often seems like a wild amount of overhead (in my case, in obnoxious JS rules) for little gain.
I'm hopeful libraries like HTMX/Datastar can gain more popularity and the throttling of basically every part of the computer finally hitting will lead to better frontend development all around, because it's such a frustration if you aren't a JS programmer and then hit that point and people say "well just use react/whatever"
I don't think JavaScript itself is the problem so much as bloated React apps. They're often wildly inefficient, with no real structure to ease optimization.
JS (assuming you are using tsc for static analysis) is a pretty nice language. The issues crop up when people see npm as a candy store and install packages without any consideration to how much data they're sending to the client or how many extra cycles are getting wasted.
The problem is that for anything that runs on people's devices, developpers have almost no incentive to optimize anything beyond the absolute bare minimum of making it work on most low end devices under favorable circumstances.
because of this, the only way for apps and websites to be well optimized is to have the devs working on them to be sufficiently knowledge, interrested and to have enough choice about what this can work on to be able to pick optimisation work insted of working on the next feature/app.
There's no money in that. We might see some great value cloud subscriptions though.
Realistically I think the worst offenders have too much network effect to care. But maybe we'll see more migration to the smaller alternatives.
Well, it looks like I won’t be looking to upgrade my 2024 Mac anytime soon. Although to be completely honest, I really wasn’t looking to upgrade my Mac anytime soon anyway. These things are pretty bulletproof. They run for decades if you take care of them.
I’ve actually been getting into the hobby of retro computing with 8 bit, 16 bit, and even 32 bit systems. If you count the Athlon as the first widely available consumer-grade 64 bit system, those are already vintage. If you count the 64 bit systems used by Sun Microsystems and some of the others in the 1990s they’re even older than that.
We used to get a lot more mileage out of our computers before manufacturers started touting huge ram chips, giant GPUs and more storage as the solutions, instead of better programming techniques and more thoughtful architecture and design of software.
I’ve never agreed with the concept of needing to improve over previous generations for minor iterations of speed. I’ve always been more of a proponent of doing more with what you have, learning the architecture that’s already in place and how to use much more thoroughly and efficiently. I’ve always called it using the entire buffalo.