If you're not willing to pay a 20% premium for upgradability/fixability, then you don't _really_ want it. And that's fine!
The Neo is an example of how this tradeoff should work: You lose flexibility but gain a lower price. For other Apple laptops, the price is on the high end and also you lose flexibility. This seeming contradiction is what helped open up the market opportunity for Framework.
(To complicate my argument a bit, it happens to be the case that the Neo is actually, for a Macbook, highly repairable, but the original article doesn't actually mention this so presumably they didn't think much about that. https://www.ifixit.com/News/116152/macbook-neo-is-the-most-r... )
(Also, I'm not putting down the overall value of pricier Macbooks. You get other things in return for those prices, they are still a good value and I own some Macbooks, I'm just looking at the price <-> repairability axis here... The Neo is a particularly clear example of price vs repairability)
> If you're not willing to pay a 20% premium for upgradability/fixability, then you don't _really_ want it. And that's fine!
$799 versus $499 is a 60% premium.
The best case numbers are buying used RAM and SSD for the Framework like Jeff did in the article ($749 total, if you can find the RAM at those prices) and comparing against the non-EDU MacBook Neo at $599. That's still a 25% premium.
> and actually want the extended warranty/applecare
The Framework warranty is only 1 year, same as the MacBook Neo.
If you add AppleCare+ to the MacBook Neo you could get a 3-year warranty laptop for $739 that performs better than the $799 Framework 12
> Now pretend you want to bump up to 16gb of ram so you can run a VM.
I don't think the students shopping for a MacBook Neo are going to be heavy VM users on their little laptop, but if I do this on their website the price bumps to $1049
$1049 is within $50 of a MacBook Air with 16GB of RAM and much better CPU, display, build quality, and battery life.
But bumping to 16gb ram means buying new hardware, moving over your profile/configuration and then trying to sell your old hardware, losing money on the trade... vs just upgrading the ram.
I'm not saying don't buy a Neo... I'm just saying there are objective reasons why you might not want to... for me, it's that I would prefer to run a Linux distro on whatever I buy. I might just go for a Lenovo IdeaPad and save a little over the Framework and the Neo at that point... they aren't the only two options on the market.
> If you're not willing to pay a 20% premium for upgradability/fixability, then you don't _really_ want it. And that's fine!
This is a completely sensible take, but many on this forum believe upgradability/fixability should be mandated by law in spite of posts like this where consumers choose against this option in spite of what the repairability activists say. It's likely that the EU will in fact pass some laws to mandate this because of this vocal minority and because it's popular to stand up to Big Tech.
Much like peter thiel’s lawsuits against Gawker, which included funding a guy who dubiously claimed to have invented email and sued Gawker for pointing out this was absurd.
Oh we have to worship our ex presidents like kings? It’s possible to criticize both Trump and Obama.
For example my top criticism of Obama is that he killed a 15 year old American child without trial. His press secretary was not only was unapologetic he said “ I would suggest that you should have a far more responsible father if they are truly concerned about the well-being of their children.”
> Oh we have to worship our ex presidents like kings?
No, but we shouldn't excuse wrongdoing by one by reference to something vaguely related by the other. It's fine to criticize both Trump and Obama. It's not fine, as the upthread commenter did and which you are defending, to criticize the Obama administration for actions taken by the Trump administration.
Drone strikes would be my top Obama criticism, followed by not closing Guantanamo, but I can use the man's name without some clever nickname. That's just not worthy of the actual conversation. It a very Trumpian thing to do
Oh I see a unilateral execution program does not warrant a vaguely rude nickname. A bridge too far. Glad you’re concerning yourself with the important issues (while Gitmo remains open and holds people)
You are wrong and the drought attribution is correct: Winter wheat is the dominant variety in the U.S. and is (and is projected to be further) down due to drought.
"a severe drought in the U.S. Plains has curbed production of hard red winter wheat, the largest variety grown in the U.S... The USDA projected U.S. wheat production in the 2026/27 season at 1.561 billion bushels, down from 1.985 billion in 2025/26, as a severe drought in the U.S. Plains was likely to slash the hard red winter wheat crop by 25% from a year earlier."
"The USDA rated just 28% of the U.S. winter wheat crop in good-to-excellent condition in a weekly crop conditions report on Monday, the lowest rating for this point in the growing season in four years."
This was mentioned in the very first sentence, it's the very first attribution of falling wheat harvest.
Yes Hormuz and rising oil costs are also a factor, a secondary one since they are impacting spring wheat planting decisions as you mention.
> Winter wheat is the dominant variety in the U.S. and is (and is projected to be further) down due to drought.
Both drought and the fertilizer shortage (which, as the article notes, was too late to effect planting decisions but DID impact the costs, and thereby decisions on the applied quantities, of nutrients for the winter wheat crop this year) are impacting winter wheat yields.
Do you have a single link or other piece of evidence to substantiate this? I’ve never seen, nor can I find in a search, any evidence the ICP license scheme in place for that past 26 years in China has ever related to children in any meaningful sense.
It has the ring of BS. Why would an authoritarian government in a country with no free press or free elections feel any need to justify a speech regulation with a fig leaf? They openly restrict speech.
An authoritarian government needs excuses too. China even claims to be a democratic country. North Korea even has the word Democratic in its name. "Protecting children" is a common excuse China uses. https://en.wikipedia.org/wiki/Very_erotic_very_violent is a famous example of them trying to justify internet censorship under the name of "protecting children".
Self glorifying nonsense. Gorbachev ALLOWED Poland to not get crushed. You think Poles were any braver in 1989 than the Chinese people who laid down their lives in Tiananmen? You think your solidarity was in any way superior to what they did, what the Hungarians and Czechs did decades earlier? You succeeded due to good timing and because Gorby was your ultimate overlord rather than Deng Xiaopong. Poles should go thank him.
People didn't go towards "it mostly works", people go towards "it works at all". A lot of people tried to use xhtml, and it didn't work, broken content was pervasive and the experience when facing broken content was irredeemable.
All async systems have pitfalls, I'd say core.async's are pretty minor compared to most other systems. You're right that `go` can encourage bloated functions and it would be better if it, for example, handled exception propagation (I would guess every serious core.async user has written their own go-but-with-exception-handing macro, it's not hard but it is unfortunate duplication of effort).
(I've never had to think about the state machine code when debugging and I've done a lot of core async debugging. That part really does seem to just work.)
To be more clear, I didn't mean debugging the generated state machine itself.
What I meant was, the use of the go state machine renders certain debugging techniques useless. E.g., stacktraces are less helpful, and js-debugger is pointless, since you can't guarantee the (js-debugger) will get grouped with the state you're trying to debug.
Frequently print/tap is sufficient, but core.async/go narrows your options.
This was actually detectable in the calls to the providers if they went as described. The credit card company tells them the perk subscription is active and the streamer says it has been cancelled. ("There was a valid activation of the streaming perk, and a confirmation from the provider" vs "The subscription had been activated, then cancelled in an orderly fashion about 5 minutes later.")
This is perfectly in line with the actual async problem, but differs from what they put in the summary ("Support on both sides saw an orderly activation followed by an orderly cancellation, with no errors").
As a digital pedant I am very sympathetic to what prompted the creation of Atom. RSS2 for example under-specifies item "description" and "title," in particular how to put HTML in there, and using the most once-most-common technique (entity escaping HTML) makes it tricky to reliably do more basic things (encode/decode left angle brackets and ampersands, because now you don't know whether to do so singly or doubly).
But the undeniable victory of RSS shows the importance of being first and "easy" (even when "easy" means sweeping edge case problems under the rug). And of humans: Major publishers like the New York Times had adopted RSS and saw no need to switch to Atom because it was good enough. I'd argue the (also underspecified) CSV format is another example of this phenomenon.
(As for the entity escaping dilemma, people mostly just moved to using CDATA for their feed-embeded HTML, although I imagine people who write RSS readers still need to come up with semantics for figuring out if a title or description payload contains encoded html or not.)
The Neo is an example of how this tradeoff should work: You lose flexibility but gain a lower price. For other Apple laptops, the price is on the high end and also you lose flexibility. This seeming contradiction is what helped open up the market opportunity for Framework.
(To complicate my argument a bit, it happens to be the case that the Neo is actually, for a Macbook, highly repairable, but the original article doesn't actually mention this so presumably they didn't think much about that. https://www.ifixit.com/News/116152/macbook-neo-is-the-most-r... )
(Also, I'm not putting down the overall value of pricier Macbooks. You get other things in return for those prices, they are still a good value and I own some Macbooks, I'm just looking at the price <-> repairability axis here... The Neo is a particularly clear example of price vs repairability)
reply