It's not like Apple soldered some plain old DDR5 to a PCB to be difficult:
1. It's TSMC's InFO_POP, which has significant performance benefits.
2. There weren't even any modules that existed for LPDDR until very recently. (and while the A18 was being designed, it didn't exist)
3. The power/price/performance/thermals they are able to achieve with this configuration is not possible with socketed RAM. You are asking them to make the device worse
Go pop open a Framework with an Ryzen AI Max processor -- you won't find socketed RAM. Technology has moved on. Math coprocessors and CPU cache aren't separate modules anymore either. AMD has even said they studied the possibility of LPCAMM for Strix Halo and found that even it wasn't good enough for signal integrity.
I picked up a 15" Macbook Air (M3) for $849 — clearance @costco early 2025.
This model only has 8gb of RAM — which is fine for streaming videos/typing — it absolutely could not be my daily driver, but makes for good casual usage.
Machines probably should ship with more than that (or a lighter operating system?), particularly when the RAM isn't upgradeable. I'll recon Apple supports at least two more macOS on these 8GB configurations.
My favorite machine only has 4GB of RAM (Core2Duo Max, Win7Pro) and works good, albeit nothing modern.
That device was explicitly made with "not enough" memory, because if it had enough, it'd cannibalize a significant portion of their higher-margin products' sales.
I'd argue that if memory and storage were still customer-expendable, they wouldn't have even considered making this product.
> simp: be excessively attentive or submissive to a person in whom one is romantically or sexually interested.
This word does not appear to be in any way relevant. You do not have to buy a MacBook Neo, but approximately everyone else in the low-end laptop market will.
If you think it is a bad product, go buy some Acer stock.
> but approximately everyone else in the low-end laptop market will.
No, they won't. People repeat this, but Macs constitute a minority of the low-end market and will continue to for the foreseeable future.
This has been the case when $400 Retina Intel Macbooks were flooding the used market; it was the case when Costco sold $700 M1 MBAs. If you cannot extrapolate what will happen with the $600 laptop, then I don't think you have payed attention to what the market is buying.
> but approximately everyone else in the low-end laptop market will
This is delusion. The retail price point right now for comparable PC laptops is $429 and they ship with DOUBLE the RAM and storage (16GB, 512GB).
For the same specs as the Neo we are talking < $350.
There is NO market for this device. Apple is catering to the welfare crowd with this one, except anyone in that situation would opt for a PC at half the price.
Like trying to sell a Cadillac with a park bench for seats to save money. It makes no sense.
Bookmark this post, the Neo will be discontinued within two years. It will join the original MacBook on the scrap heap of Apple products that should have never been.
I have firsthand knowledge that at least one incumbent household name PC manufacturer is in a state of panic over the Neo. This is from an organization that would be predisposed to believing what you’re saying, but instead they’re revising internal forecasts and executives are freaking out.
I have no interest in arguing further, it benefits me nothing. But sure, let’s revisit it in two years.
Can’t say I’ve done this recently, but I think if I were doing this today I’d probably install it on the current machine and then boot into recovery mode and reinstall from there.
There is a Web client at https://winden.app (although it uses different servers than the defaults in the Python CLI, the latter can be easily configured to use the same servers).
However, see further discussion in this article about the difficulties of Web / JavaScript security in this context (i.e. you're depending on the people operating the Web server to not serve different JS on each and every visit).
Yes, because "a" is not an object, it is a reference to an object. This reference is passed by value.
This kind of thing is why I'd recommand everybody to know C: when you know pointers there's no magic anywhere anymore
Something like this, without any kind of error checking being done.
#include <stdlib.h>
// assume some hash table library, exercise for the reader
typedef struct{} *hashtable_t;
extern hashtable_t hashtable_init(void);
extern void hashtable_put(hashtable_t hashtable, const char* key, const char* value);
extern void hashtable_dump(hashtable_t hashtable);
typedef struct {
hashtable_t table;
} data_t;
void foo(data_t* a)
{
hashtable_put(a->table, "otherKey", "b");
}
int main(void)
{
// let a = {key: 'a'};
data_t* a = (data_t*) malloc(sizeof(data_t));
a->table = hashtable_init();
hashtable_put(a->table, "key", "a");
foo(a);
// console.log( a );
hashtable_dump(a->table);
return 0;
}
The function foo() gets the numeric value of the a pointer, thus a parameter inside foo() points to the same memory location.
If C had pass-by-reference, it would be possible to give (implicitly) the memory location of the local variable a in main() instead. For example, like in Pascal (var) or C++ (& in function declaration).
reply