Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Grok Build is open source

github.com

Post reply on HN
Print view View original

351–360 of 730 posts

Re: Grok Build is open source

#351

Post by lovich »

alex1138 wrote: post #142
lovich wrote: post #125

Earlier quoted context omitted.

> I was willing to give him a pass (still am) in a vacuum regarding the Twitter thing given the mass censorship of the old regime (sorry - no, it wasn't acceptable, in any way shape or form)… Why give him the benefit of the doubt when he censors worse than the previous management? Just look at all the grok lobotomies he gave it because he didn’t like how liberal coded the answers it was giving.

I was just trying to say old Twitter had a serious problem but apparently that goes against the hivemind so I accrue mass downvotes despite posting my comment in good faith

No man, I’d you had just said

> I was willing to give him a pass…

That could be logically consistent given how he is more censorious than the previous management, but you said

> I was willing to give him a pass (still am)…

That means you are giving him a pass on having more censorious behavior than what the group you disliked did. That just comes off like you’re biased and trying to hide it.

I don’t think you’re getting downvotes despite commenting in good faith, but because you aren’t commenting in good faith, and I say this as someone who hasn’t downvoted you.

Re: Grok Build is open source

#352

Post by brokencode »

jimmygrapes wrote: post #303
this_user wrote: post #223

Earlier quoted context omitted.

You misunderstand Musk's motivation. This was never about money for him, but about control over a key technology. One of the main reasons he exited OpenAI was the fact that the other co-founders wanted to create a structure where no one, Musk included, would be able to seize full control of the company. That was the thing that prompted him to leave, which tells you a lot about what he really wanted in the first place…

What happened to the rule about steelmanning? I know it's chic to post super hot takes about what we assume a persons intentions are, and I know there are plenty of "if you can't see how bad they are you're the problem" type justifications; I know the supposed goal of empathy is tossed aside at first hint of disagreement whether real or perceived, and I know there is "evidence" of justification for hatred/dismissal.…

What rule about steelmanning? We’re commenting online, not writing peer reviewed research.

And yeah, some people lose the benefit of the doubt. Sorry, but actions have consequences.

Elon doesn’t just get to kill hundreds of thousands of poor people by eliminating USAID and expect everyone to treat him the same way.

He’s made enemies for life, and he deserves it.

Re: Grok Build is open source

#353

Post by tbrownaw »

m4rtink wrote: post #305
Gigachad wrote: post #263

Earlier quoted context omitted.

The rocket business is hardly profitable. The whole valuation is based around grok and space datacenters. He needs to keep pumping the hype or else we are in for the worlds biggest crash.

Well, in the long run expansion into space is the only profitable thing.

That's a much longer long run than Keynes' "in the long run we are all dead".

Re: Grok Build is open source

#354

Post by smegger001 »

marcus_holmes wrote: post #315
sohrob wrote: post #274

[flagged]

I have friends who use it and rate it. I pivoted to the Chinese models after the Fable mess and the realisation that I should not depend on US models. But others just pivoted away from Claude. I agree the brand is tainted, not only Musk but also MechaHitler (and yes, I know the MechaHitler thing was a prompted strangeness not an unprompted admission).

Yeah I would prefer not to use models whoes the owner has a habbit of altering them to push white replacement/genocide conspiracy talking points on we he gets board

Re: Grok Build is open source

#356

Post by thrdbndndn »

simonw wrote: post #304
simonw wrote: post #299

There's some surprising stuff in this codebase. For example, https://github.com/xai-org/grok-build/blob/b189869b7755d2b48... is a "self-contained terminal renderer for Mermaid diagrams", which renders a subset of Mermaid chart types using Unicode box-drawing.

I had Fable 5 compile that Rust code to WebAssembly and build a browser-based playground for it, so you can try it out with Mermaid diagrams here: https://tools.simonwillison.net/grok-mermaid A few more notes on my Grok code explorations on my blog: https://simonwillison.net/2026/Jul/15/grok-build/

I love this kind of stuff (ASCII art, if you will), but it just breaks down too easily as soon as Unicode characters (mainly CJK, as I'm Chinese) and fonts are involved.

For example, on your website, any chart or plot involving horizontal arrows breaks down because the assigned font-family (`ui-monospace, SFMono-Regular, Menlo, Consolas, monospace`, which ends up as Consolas on my machine) has no such glyph. Thus, it falls back to Segoe UI Symbol, which does not have the same fixed width (or is not fixed-width at all) as other characters: https://i.imgur.com/d2DPGHE.png

Re: Grok Build is open source

#357

Post by skissane »

afavour wrote: post #257
skissane wrote: post #221

Earlier quoted context omitted.

> If a shovel manufacturer was notified numerous times that their shovel was being used for murder and they had the capability to disable using the shovel for murder while retaining all legitimate uses wouldn’t people question why they didn’t do it? This is impossible-nobody can possibly block all illegitimate uses without also blocking some legitimate ones as collateral damage. Any moderation process (whether automa…

I didn’t say block all illegitimate uses, though. We’re talking very specifically about disabling the production of CSAM. Which is something Grok seems to be able to do now! So I’m curious what legitimate uses had to be sacrificed in order to do so.

> I didn’t say block all illegitimate uses, though. We’re talking very specifically about disabling the production of CSAM

But what is “CSAM”? If by it you mean illegal material-different jurisdictions worldwide have different laws on that topic, so material which is illegal in one jurisdiction can be legal in another.

Re: Grok Build is open source

#358

Post by Grombobulous »

CobrastanJorji wrote: post #133
GodelNumbering wrote: post #114

This is not the right thing, this is the tactical thing. If you have an LLM with less than 1% of the share to begin with, you suffer from bad rep and you got caught uploading user data, one of the very few remaining tactical moves to try to climb out of it is this.

Another tactical move is to just stop. You're allowed to exit the AI business. Nobody's forcing you to keep throwing money into the furnace. Just be a rocket company. All of the xAI founders left. Your product's brand name is mud. Just stop doing that and build spaceships.

This is what a normal company might say.

xAI is not a company, it’s a financial instrument. The growth potential as perceived by investors is there to prop up the stock price.

Re: Grok Build is open source

#359

Post by Pannoniae »

stusmall wrote: post #197
gidellav wrote: post #161

What a bunch of slop: 182 top-level external dependencies (so, without considering nested dependencies) and 1318853 lines of code in Rust. Building efficient agents is doable (I did it myself, github.com/gi-dellav/zerostack), companies just want to tokenmaxx, and as a by-product, produce and publish slop.

It looks like some of that high LoC is because they are vendoring some deps. There readme gives the reason to vendor some but not others as: > These crates sit on the path that renders untrusted model output (diagram source → SVG). Vendoring gives a full audit surface, pins exact source, and avoids crates.io yanks. Local patches and upgrade checklists live in each crate’s Cargo.toml header comments — treat those as t…

It's kind of full circle... dependency management was invented because consuming libraries or common code was hard, everyone kept reinventing the wheel and if you had some vendored code, updating it was a nightmare due to the build integration and source customisation. So people don't update much.

Proper dependency managers changed that and it became much easier to consume libraries, just declare what you went, the build framework handles the rest.

But we now have problems with consistent versioning, churn, breaking API changes and supply-chain attacks.... and looks like "just vendor everything in" might be a thing again?

Post reply on HN