Im still running Win2003 here, hence classic GUI (Win2000 like). Works like a charm :) I do some hacking (programing, reverse engineering) and playing games (old of course) on it.
The relative resource consumption of meat vs. plants is well established. Chicken is much more resource efficient than beef if you want to eat meat but consume less resources, and mussels are even more efficient.
That part I'm well aware of, I wanna know how the parent reached the figure 17000. What does count as a request even nowadays? When I tell an agent to make the button blue, how many requests is that? And how about when I tell it to throw together a whole website? Or rewrite the codebase in Rust?
“A typical request to the open model Kimi K3 emits about 0.4 grams of CO₂ in Sweden, 1.6 grams in Ireland, 2.5 grams in Germany and 3.2 grams in Texas, on identical hardware — 8.5 times more in Texas than in Sweden.”
0.4 x 17,000 = 6,800g, a fairly typical estimate for the co2 emissions of a burger.
Thanks. My next question would be what's a typical request. The article defines it as "production-typical request of 5,000 input and 387 output tokens, weighted by a typical day's traffic" for the Kimi K3 model. Not sure how that translates to my scale of the blue button to RIIR.
Yes they are. We just had a workshop where the managers previewed our “software factory”. A big pile of skills, hooks, CLAUDE.md files, an elaborate spec and test system based on many markdown files.
All features should now be created via this workflow. It’s basically a ticket going in, a few rounds of questions back and forth with the LLM, then waiting for an hour until it finishes.
Then having to read/review 2k lines of AI-generated code. It’s terrible.
Isn't it tiring to keep up with considering the speed of the generated code? And if you want to be careful with the review you lose a significant part of the speed advantage.
It's the same as any other PR. Keep the changes small and contained to that feature. AI can do this if you instruct it to, there is no need to vibe code some 40k line monstrosity.
If dev approaches zero, but you review at the same pace as you always have, are you in a better position? Yes.
Will you potentially have a backlog of code waiting for review? Also yes.
Would you prefer to be waiting for the dev team for all of the time instead, then still have the same amount of reviewing to do at the end of it? Absolutely not.
Yes, but it's the only option if you want to retain a maintainable code base. And you can always slow down. You'll probably still be a bit faster than you were before.
Do you mean leave if they don't have an alternative?
I'm not religiously opposed to QR-code linked menus myself, but it just so happens that the last restaurant I ate at, the QR menu was broken and I was forced to ask for a paper menu anyway.
Now if a restaurant puts a lot of care and curation into a web based menu (and posibly ordering system!), and lovingly craft a complementary QR code to point to it, then why not?
A lot of the time the caring is the important part.
I certainly would, unless it was something I was doing for someone else's sake (like a birthday dinner for someone). Why would I do business with a restaurant that can't be bothered to provide a good experience for customers?
I personally do not use QR codes. I suppose there could come a time where I could benefit from scanning one but I still have access to restaurants where you can order manually from humans and they cook the food themselves also.
If they wouldn't find another to help me? Absolutely. I can't imagine I couldn't just ask the server a question like "what's cheap and good?" or "I'll take the soup of the day."
Restaurants have thin enough margins already. They aren't turning away a customer for not bringing a phone. There's one tiny burger place just around the corner from me that's delivery/pickup only, not even a QR code, but they have a sign outside saying 10€ combos and they're 15€ on the website... I just asked them. They have very good halloumi burgers and perfectly cooked fries. They were happy to accept my cash, too.
Depending on what type of computer (if not smartphone) you have at hand, you can probably use a search engine to find the same menu. Or ask somebody at your table. Or ask the server. Or point at somebody else's food and say you want what they're having. Or eschew the menu entirely and ask to be surprised. Chef's choice can be fun.
Or leave yeah, I think that's valid. TFA is predicated on the notion of pretty-much-lying to people by telling them you don't have a smartphone even if you do. Leaving a restaurant if you can't find a menu seems like it'd be on similar ideological footing.
The idea is you shouldn't have to have any sort of computer on your person to participate in public life. If a proper eat-in restaurant can't maintain a paper menu then it's an indication of the level of service that's sure to follow.
Perhaps that's the grandparent commenter's idea but I don't think it's the point the article is making:
> So, seriously, I do really like the smartphone idea. It’s just that I don’t have any browser or "social" app on it. And I don’t want anything else than what I have.
> I wish I could say it is all I have, that I’m a true minimalist.
He defines true minimalism as having an _ideologically conformant_ computer, not no computer at all.
How are you running the classic GUI?
reply