no way fable did this. It would have stopped after the words "command and conquer" and nerfed you to opus (while also landing you on some nsa watch list)
I’ve been using it to use Ghidra to do reverse engineering for modding Zelda: Tears of the Kingdom. Pre-ban it would flag immediately, post-ban it _rarely_ flagged anything and when it did I realized I could just make a memory telling it to convert reverse engineering speech into game development speech, not mentioning pointers, memory, addresses and decompiling. Then the flags mostly went away. You can sidestep flag…
Command and Conquer Generals natively ported to macOS, iPhone, iPad using Fable
161–170 of 302 posts
Re: Command and Conquer Generals natively ported to macOS, iPhone, iPad using Fable
#162I wonder if we’ll get to a situation where a new game is reversed in the first few months by a team effort. Right now it’s mostly solo devs, but a technical team that’s capable without LLMs is unstoppable with them, and given the nature of modding communities, the only thing they are missing is an LLM to grind away at the details of the game that would otherwise take years to find out.
Re: Command and Conquer Generals natively ported to macOS, iPhone, iPad using Fable
#163> Built on EA's GPL v3 source release via fbraz3/GeneralsX (which did the heavy lifting of the macOS/Linux port — this fork adds the iOS/iPadOS port and a set of engine fixes).
Right? All Fable did was a ported an already cross platform project to ios. Does not look like any sort of heavy lifting there, opus 4.6 would do just fine
Re: Command and Conquer Generals natively ported to macOS, iPhone, iPad using Fable
#164> (tap-select, drag-box, long-press deselect, two-finger scroll, pinch zoom) This is another "AI-ism" I noticed, mostly in coding agents - they seem to be very fond of making up new "compound nouns" (and occasionally verbs) to sum up relatively complex and specific concepts into single noun phrases. I wasn't sure if it's to save tokens or if the AI uses this to get a concise "identifier" for a concept that it can ref…
Yes! It's infuriating. I've tried prohibiting them in my AGENTS.md but it's not 100% effective. --- AGENTS.md --- ## Plain words, not jargon Don't use jargon-as-shorthand. Say what you actually mean. - Don't say "load-bearing assumptions". Say "the assumptions the xyz depends on". - Don't say "cross-service". Name both services, e.g. "whether the X service can derive duration without calling the Y service". "Cross-X"…
And if you manage to do this automatically before committing, you’ve built the backpressure everybody is talking about.
Re: Command and Conquer Generals natively ported to macOS, iPhone, iPad using Fable
#165Earlier quoted context omitted.
I’m (sorry for the lack of humbleness) a very fluent non-native speaker and writer, and this is by far my biggest challenge with Claude. It stitches together 2-4 advanced concepts into one or two words and I always have to ask it to “unpack”. I don’t think it’s easy on native speakers when it happens, but it’s even harder when you’re not.
Its hard for native speakers. Information density makes for rough reading.
Re: Command and Conquer Generals natively ported to macOS, iPhone, iPad using Fable
#166> Built on EA's GPL v3 source release via fbraz3/GeneralsX (which did the heavy lifting of the macOS/Linux port — this fork adds the iOS/iPadOS port and a set of engine fixes).
I have a Renegade one going that does all of this from scratch (different engine) so it's def more than capable!
Re: Command and Conquer Generals natively ported to macOS, iPhone, iPad using Fable
#167Earlier quoted context omitted.
Some people, myself included, think that announcing a conversion from Rust to Zig as an experiment then jumping to putting it in the alpha train for public testing/consumption without any real explanation in the span of around 2 weeks is irresponsible and reckless. Blogposts were promised, details were hinted, but no, it’s just full steam ahead because the AI worked so well. The converted unit tests all worked, all t…
They are looking for a different human buy-in. "Yes, the AI rewrote the code. No, we do not pretend that we've scrutinized the code, or that we understand it. It works, tests pass, so we don't care, and so shouldn't you. " The "recklessness" is offered as the new normal. Because it kinda, well, works for them.
Re: Command and Conquer Generals natively ported to macOS, iPhone, iPad using Fable
#168Earlier quoted context omitted.
> - I don't think Claude Code is using the Rust version yet in their official build No, I'm pretty sure it is, actually, since June 17: https://code.claude.com/docs/en/changelog#2-1-181 >> Upgraded the bundled Bun runtime to 1.4 Now, Bun 1.4 doesn't seem to officially exist on https://bun.com/blog or https://github.com/oven-sh/bun/releases , so I can't be 100% sure this is the Rust version. However, I have to do some…
https://news.ycombinator.com/item?id=48609168 https://grigio.org/bun-1-4-the-controversial-ai-driven-rewri... > 13,044 unsafe blocks in the resulting Rust code (hand-written Rust projects of similar size average ~73) Grok is this true? I've heard the meme that AI written rust code is absurdly full and safe blocks but... that's pretty funny. Hang on. A claim like that can be verified with a single grep! Give me a minu…
If I understand what happened here correctly this isn't really a case of any such meme, but the result of the porters (heh) telling the LLM to directly convert zig code using unsafe to match the previous code "exactly".
I.e. more like using the LLM as a fancy version of c2rust [1] (which would result in just as much unsafe) than a result of LLMs reaching for escape hatches too liberally.
Re: Command and Conquer Generals natively ported to macOS, iPhone, iPad using Fable
#169Re: Command and Conquer Generals natively ported to macOS, iPhone, iPad using Fable
#170Earlier quoted context omitted.
They are looking for a different human buy-in. "Yes, the AI rewrote the code. No, we do not pretend that we've scrutinized the code, or that we understand it. It works, tests pass, so we don't care, and so shouldn't you. " The "recklessness" is offered as the new normal. Because it kinda, well, works for them.
What's working for them is having a huge amount of resources and very good people to design a cutting edge agent harness, RLHF the hell out of their models, and build out a tremendous amount of inference capacity. I'm sure their process for making code changes in any of their client apps is very fast, but a TUI built around a chatbot is also not a particularly complicated application. So yes it's working for them, bu…