8,773 karma · joined July 12, 2010
I sporadically rant at http://masonmark.com and usually see email sent to mason at that domain.
There were't any $4 healthy bowls of anything, but there were $2 "red hot beef & bean" (& fake soy filler) burritos which hit the spot if you'd failed to find a way to eat real food...
The problem with the microwave solution, I think, is that pretty much only burritos and pasta can be packaged in a microwavable way that still tastes good? And maybe like a few kinds of vegetable side dishes.
Unless you use it at 4K, but macOS isn't really usable that way (everything way too small).
But yeah, it's 60Hz. Which has sucked ever since I accidentally got a 120Hz display, so now 60 Hz looks like 30Hz used to...
Monitor Resolution PPI
─────────────────────────────────────────────────────────
31.5" 8K 7680 × 4320 280
27" 5K 5120 × 2880 218
31.5" 6K 5760 × 3240 210
23" 4K 3840 × 2160 192
27" 4K 3840 × 2160 163
34" 5K ultrawide 5120 × 2160 163
31.5" 4K 3840 × 2160 140
39.7" 5K ultrawide 5120 × 2160 140
44.5" 5K ultrawide (LG 45GX950A-B) 5120 × 2160 125
P.S.I had a chance to try that LG 45GX950A-B at Yodobashi Camera in Akihbara the other day, and... that measly 125ppi might overperform at the distance you have to put it at. But then again my 50-year-old eyeballs are starting to be like "anyway you need your glasses bro" so... YMMV
I haven't used a low-DPI monitor for like... not sure, but more than a decade, I'm pretty sure, so for me the weird blocker I have with Zed is the "OMG YOU HAVE NO GPU!!!! THIS WILL NOT END WELL!" warning (I run a lot of Incus containers via RDP, and they mostly have no GPU available).
But what kind of monitors are you low-DPI people using? Some kind of classic Sony Trinitron CRTs, or what? I'm actually curious. Or is it not the display itself, but some kind of OS thing?
But if you actually have any form of diabetes... definitely do not do that. Unless you are also rocking some other brand. ¯\\_(ಠ_ಠ)_/¯
It's objectively worse for me on every possible axis than Claude Code. I even wondered if maybe I was on some kind of shadow-ban nerf-list for making fun of Sam Altman's WWDC outfit in a tweet 20 years ago. (^_^)
I don't love Claude's over-exuberant personality, and prefer Codex's terse (arguably sullen) responses.
But they both fuck up often (as they all do), and unlike Claude Code (Opus, always), Codex has been net-negative for me. I'm not speed-sensitive, I round-robin among a bunch of sessions, so I use the max thinking option at all times, but Codex 5.1 and 5.2 for me are just worse code, and worse than that, worse at code review to the point that it negated whatever gains I had gotten from it.
While all of them miss a ton of stuff (of course), and LLM code review just really isn't good unless the PR is tiny — Claude just misses stuff (fine; expected), while Codex comes up with plausible edge-case database query concurrency bugs that I have to look at, and squint at, and then think hmm fuck and manually google with kagi.com for 30 minutes (LIKE AN ANIMAL) only to conclude yeah, not true, you're hallucinating bud, to which Codex is just like. "Noted; you are correct. If you want, I can add a comment to that effect, to avoid confusion in future."
So for me, head-to-head, Claude murders Codex — and yet I know that isn't true for everybody, so it's weird.
What I do like Codex for is reviewing Claude's work (and of course I have all of them review my own work, why not?). Even there, though, Codex sometimes flags nonexistent bugs in Claude's code — less annoying, though, since I just let them duke it out, writing tests that prove it one way or the other, and don't have to manually get involved.
If you can't use LLMs to generate placeholder graphics that don't ship in the actual game, then why can you use coding editors that let you use LLMs to generate code?
I'm a programmer, and I enjoyed the sort of "craftsman" aspect of writing code, from the 1990s until... maybe last year. But it's over. Writing code manually is already the exception, not the rule. I am not an artist, and I also really do understand that artists have a more legitimate grievance (about stealing prior art) than we programmers do.
As a practical matter, though, that's irrelevant. I suspect being an "artist" working in games, movies, ads, etc will become much like coding already is: you produce some great work manually, as an example, and then tell the bots "Now do it like this ... all 100 of you."
But banning using AI at all while developing the game is... obviously insane on its face. It's literally equivalent to saying "you may not use Photoshop while developing your game" or "you may not use VS Code or Zed or Cursor or Windsurf or Jetbrains while developing your game" or "you may not have a smartphone while developing your game".
COSMIC isn't yet close to a solution for remote desktop, so I expect to have to wait a few more years. (T_T)
[1]: https://blog.simos.info/how-to-install-and-setup-the-incus-w...
Sorry, but I bought Proxmox 7, but it is not comparable. Incus does everything (and more) with better interface, WAY better reliability, and also not like a hundred EUR or whatever. (100 EUR is fine with me if better, but not if not better...)
I run instances I need to interact with (e.g., do development in containers via SSH and remote-editors, with occasional Remote Desktop) on my very-fast Linux workstation — that also does other stuff like local development, web browsing, etc., but most instances that don't need power run on my old 56-core Xeon enterprise server (used, they are roughly as cheap as a Mac Mini).
Incus makes it super easy to move instances around, and from a skim of the announcement it looks like you could just put Incus OS on some machine you have lying around and drop it into an existing config like that with minimal effort.
I look forward to trying it out, even if my "main" Incus will probably remain on my actual manually-curated Linux desktop.
However, I'm confident that if that is what you want, this is probably fantastic — Incus, including the old LXD (which was mainly built by the same core developers, until Canonical behaved in ways they didn't like, and they hard-forked LXD to create Incus) has been one of my favorite open-source projects for several years.
Fantastic software, steady stream of reliable releases, helpful community... Incus is great.
The main reason work visas are required is not to prevent foreigners from doing work, it's to restrict and control their ability to live in the country, send their kids to school, receive medical care or whatever other social services might be available to residents, or do whatever kind of activity that the government doesn't want people to do and believes foreigners might do (discussing Tiananmen Square, disparaging Charlie Cook, advocating for gay rights, petty crime — whatever it is).
Hiring a foreign company, or foreign contractor, to perform work in their own country is almost always allowed. This is fundamentally not any different than a company having people answer customer phone calls in a call center in Bangalore.
Additionally: it seems likely that it was the result of gas station pump skimmers, just because the card in question had never been used for any other kind of transaction.
If our service goes down for any reason, uh... wait until Monday afternoon, then try again. (Sorry!)
Like, who would die if AOL was down for 36 hours?
Also, when you're 35, you will likely have a much better understanding of what really matters to you, and what kind of partner you really want for the long haul.
It's often said that "60 is the new 50" — and it is, if you do it right — the corollary is something like, "25 is the new 19". That's a gift! Take advantage.
They are doing the work elsewhere, and it would be suicidal for any economy to mandate only using domestic contractors to do all work. (Also, just a side note, even though logically irrelevant: it's not at all the case that these foreigner+robot combos are taking local jobs; I live in Tokyo and have seen that the convenience stores are desperately seeking staff, even 1 day a week, and paying more for it... they just can't find enough (yes, partly because immigration is pretty difficult here).)
For me, though, it's not remotely close. Codex has fucked up 95% of the 50-or-so tasks I asked it to do, while Claude Code fucks up only maybe 60%.
I'm big on asking LLMs to do the first major step of something, and then coming back later, and if it looks like it kinda sucks, just Ctrl-C and git revert that container/folder. And I also explicitly set up "here are the commands you need to run to self-check your work" every time. (Which Codex somewhat weirdly sometimes ignores with the explicit (false) claim that it skipped that step because it wasn't requested... hmm.)
So, those kinds of workflow preferences might be a factor, but I haven't seen Codex ever be good yet, and I regret the time I invested trying it too early.
But not for semantic document structure — recognizing that the grammatically incomplete phrase in a larger font is a heading, recognizing subheadings and bullet lists, tables, etc.
Also not for handwritten text, text inside of images (signage and so forth), or damaged source material (old photocopies and scans created in the old days).
Those areas all seem to me where an LLM-based approach could narrow the gap between machine recognition and humans. You have to sort of reason about it from the context as a human to figure it out, too.