From a value proposition, it seems good. Our group definitely goes through keyboards and mainboards from spilled tea at least annually it seems, but AppleCare is just a no-brainer, and away we go.
I still drive on my original M1 at home without complaint, and use my M3 at work. Anyone have the early Frameworks still in daily use? How are they?
The battery life is good enough that I never worry/think about it. The keyboard is fantastic. The trackpad is meh, not terrible but not MacBook great—use a mouse or vim :)
Deleted Comment
The green threads are very interesting since you can create 1000s of them at a low cost and that makes different designs possible.
I think this complaining about defer is a bit trivial. The actual major problem for me is the way imports work. The fact that it knows about github and the way that it's difficult to replace a dependency there with some other one including a local one. The forced layout of files, cmd directories etc etc.
I can live with it all but modules are the things which I have wasted the most time and struggled the most.
Use `replace` in `go.mod`, or `go.work` if you're hacking on it locally?
If this is how you think LLMs and Coding Agents are going about writing code, you haven't been using the right tools. Things happen, sure, but also mostly don't. Nobody is arguing that LLM-written code should be pushed directly into production, or that they'll solve every task.
LLMs are tools, and everyone eventually figures out a process that works best for them. For me, it was strongs specs/docs, strict types, and lots of tests. And then of course the reviews if it's serious work.
And the moment the context is compacted, it forgets this instruction “fix the problems, don’t delete the file,” and tries to delete it again. I need to watch it like a hawk.
The gap between what a minimum wage job pays and what it costs to scrape by is covered by government or charity, if they didn't do that the workers would die, which means the jobs don't get done, so that means the resource spent by governments or charities as a result of a low minimum wage is a subsidy for the employer. Instead of paying what it costs they get it for cheaper to create a fiction of "employment".
If anything we should be subsidizing small businesses to give a more level playing field against companies with global economies of scale.
- protein to fat (which is roughly 1.4 in Beyond Meat (20g protein / 14g fat in 100g) versus 2.5-3.5 in beef (30±5g protein / 12.5±2.5g fat in 100g)) - protein to mass (20% vs ~30%) - micro-nutrients to mass (a very wide variety of minerals, vitamins, and other unknown nutrients present in beef) - carbohydrates (not present in substantial amounts in meat and around the same amounts in tofu/tempeh as in Beyond Meat; but I don't think it's as major a statistic as previous ratios)
I eat chiefly vegetarian, and refuse to see why Beyond Meat exists beyond 'we can do it and it may get more people to eat vegetarian.'
The industrial overhead of producing Beyond Meat and all the effort that went into creating it simply doesn't make sense to me compared to beans and plant-based protein friends like tempeh/tofu/seitan. Latter are an order of magnitude more scalable than both Beyond Meat and Regular Meat.
All the processing plants and factories built to make this ultra-processing possible, the logistics and supply chains set up to bring all the necessary additives and components together, the grandiose packaging and marketing efforts... I don't get it. It's not a product made for a real audience.
That's a noble goal in and of itself. Every step to reduce environmental impact and animal cruelty has value.
Beyond and Impossible were my "off-ramp" from eating meat every meal to exploring vegetarianism and veganism. I'm sure I'm not the only one.
Unrelated to cheese but MyBacon is fantastic if you can get it near you.