The comment tone isnt great but they have a point. I really dont think having an idea and getting Claude to implement it counts as being a "doer". The barrier to entry for doing something like this with an LLM is so low now. It seems obvious to me that these vibe coded projects are worth much less attention than a pre LLM equivalent that you know took the author a lot of time and effort. All these posts are basically now "I had an idea and wrote a prompt". It's great if folk have fun with this but it seems pointless sharing this stuff if anyone can do it in literally less than 10 minutes with a 20 USD sub.
Not everyone. I found that if you want quality, you need to spend a lot of time ironing out issues.
Sure, prototype works in 20 minutes. Then, 10 nights later I still can't get my game to have really good ai opponent. Even with MCTS, genetic algorithm, a lot of prototypes and 30 cores for the game to use.
Who are you to decide how much effort counts as doing? The parent comment was gatekeeping, and so is this.
> worth much less attention
Prove it. Vote with your wallet, err, attention? You don't get to decide for me or anyone else on this site how much attention this post is worth. Unless your charge is that OP is buying votes, or Claude magics votes into existence, the fact that it got popular is proof enough.
If you don't like it, don't read it, and if you get conned into that, don't upvote or comment.
Any language? Like what? C++ has terrible metaprogramming and build times. Rust has terrible build times and you need to wrap your head around it. C# has GC. C is barebones.
I firmly believe that you should settle your approach to metaprogramming first, on any major project, and for me none of the off-the-shelf solutions ever were preferable to "just generate the code" (JAI probably won't be any different here). Then, once you build all the tooling to be able to iterate as quickly, you basically have your own language and standard library anyway.
Yes, C#, C++, Rust. Even Javascript. They may not be perfect, they have flaws... but the game could certainly have been built in any of them. Blown just didnt want to, for ideological reasons, which is his decision. Look at the complexity and sophistication of modern AAA games... none of them "needed" a language built from scratch.
> but the game could certainly have been built in any of them.
Of course it could, after all, it could be built in any Turing-complete programming language. But you wouldn't say that he could do it in assembler, right?
Have you played The Order of the Sinking Star? Pretty much the first thing I did in the game was inspecting how the game operates and wondering why would he need a new programming language to make it. Making something in a new programming language is by default harder, because you have no existing ecosystem (unless you can make bindings or otherwise easily port something to your language), so why even make a new programming language?
While I can imagine a piece of software where this is more clear, the ridiculous complexity of the Order of the Sinking Star is a huge hint: perhaps his language is so much better at iterative development, or level design (e.g. a level editor or a fast compilation time), or debugging, or some kind of structure defining, that achieving the same result in another, existing programming language, would only be possible theoretically, but in reality it would take more time, more workforce, or the complexity of the design, multiplied by the complexity of implementation in another programming language would produce an overall complexity too big for a single human to comprehend, requiring separating the game world into isolated parts with clearly defined, simple and boring portals between them.
I may be exaggerating, but the idea is, he was making a video game, he was annoyed with the programming language he was using, so he made a new programming language to deal with the annoyances so that the programming language helps more and gets in the way less.
You mentioned Rust, well JAI has already better game portfolio than Rust...
"Better game portfolio" is a bit vague but >1,000 reviews on Steam is a common bar applied to indie games for what constitutes commercial success.
By that measure, I know of two successful Rust games (Tiny Glade and Gnorp Apologue) and one successful JAI game.
To be fair, JAI has not hit 1.0 yet, while Rust has been 1.0 for 11 years. The meme of "Rust has 5 games and 50 game engines" is still accurate, but it will be interesting to see if anyone other than Blow will ship a successful game in JAI.
Jon has talked multiple times on his stream addressing the "it could have been made in any other language crowd". Gist is they have no idea what they are talking about.
wdym he said it would have been delivered sooner had he used C++
> If we had just used C++ in the engine from The Witness and done this game, how long would it have taken? The answer is less than 10 years. I can’t tell you how much less, because it was also a big game design-wise. Lots of stuff overlaps. It probably could have gone at least two years faster. Maybe four years faster. Somewhere in there.
It’s about feasibility not speed. If he believes the game could have been made faster with C++ then why is he a visionary for having created Jai? And why then do the people who say the game could have been made with another language have no idea what they’re talking about?
Because in the future he believes he will have more velocity and better UX making games in this language. It's an upfront investment and you are missing the forest for the trees. Also being a visionary or having a vision does not imply success.
But what's the evidence it can do this where other languages cannot? And if it's just about speeding up the game dev process in the future, why isn't a framework or engine sufficient?
And again, why do those who said the game could have been made in other languages have no idea what they are talking about, because it seems like they do. Can you link to where he explains that or explain it yourself?
> being a visionary or having a vision does not imply success.
If having a vision and working on it is enough to be a visionary, probably most people on HN are visionaries.
> But what's the evidence it can do this where other languages cannot? And if it's just about speeding up the game dev process in the future
You are asking for evidence when we are talking about vision? "What's the evidence cars are needed?? We have horses!". His vision is "C++ sucks for game development, most people are using it out of inertia, let's make a programming language that caters better to game development". A lot of people in the games industry agree on the former (that C++ sucks and we need something better). Not only he is doing something about it, but he already delivered a successful game using his language. Whether other people will adopt it remains to be seen when it gets out of beta.
> why isn't a framework or engine sufficient? And again, why do those who said the game could have been made in other languages have no idea what they are talking about, because it seems like they do. Can you link to where he explains that or explain it yourself?
> You are asking for evidence when we are talking about vision?
The vision was laid out 10 years ago. I think it's fair to be asking for evidence at this point. The existence of a game is evidence that Jai can make games, but the vision was about making game making better.
> One of the videos he's talking about it:
Thanks for digging that up. I'm a bit surprised because I didn't expect that to be the argument he'd make, it seems kind of flat.
And in the course of explaining he basically concedes that those people who say it could be written in another language are actually correct, just that the end result wouldn't have looked as good as it does (obviously his opinion, and he doesn't provide a technical reason for this assertion).
So anyway, that's what I was getting at as I disagreed with your generalization that those people don't know what they're talking about. They actually do.
Whether Jai is a thing or not remains to be seen. FWIW Odin seems to have taken a lot of the ideas Blow originally laid our for Jai and released them years ago in a working project, while Jai is still locked away.
That's why people are asking the question about what makes this language visionary beyond whether he's simply executing on a vision. If the vision is better game development, how does this do it? And if it does do it, why does it need to be a language rather than an engine or a framework or even a preprocessor or something else?
A far worse version of that game concept could have been built in Javascript (which you can't even run at speed on consoles because they don't allow JIT), but that's not this game.
Modern "AAA games" cost 100 million dollars or more. Of course if you have an army of developers paid by the hour, maybe iteration speed doesn't matter, maybe the subjective experience of software development doesn't matter. But "AAA gaming" would never produce a game like this in the first place, so it's a moot point.
It's the same with AWS, Cloudflare. There is also this weird effect, often commented on here, where if half the Internet is down, everyone understands when you are down. If I use some random new start up for my infrastructure or services, and it goes down, customers and executives are furious. So it seems we are stuck here.
Something I've been thinking about with the last few major outages is that as there is more and more consolidation (fewer large companies running a higher share of the world's infrastructure and critical services) is that we become increasingly exposed to massive disruption like this. Would some sort of mandated maximum occupancy per instance resolve this? So Outlook.com is allowed to support 100m accounts per instance. Then you are required to spin up Outlook2.com. You are not allowed to have any shared infrastructure. Yes it's wasteful and expensive, but these are companies with billions in revenue, so that's the price you pay. It just seems that keeping these huge, incredibly complex services running is turning in to an impossible task. Very much a hot take so interested in the opinions of peope who have worked at this scale.
They could (and should, and clearly don’t) architect the services like this internally. There will always be some single-points-of-failure, but minimizing those should be a top priority. Just from reading their status updates it’s clear most everything is sharing way too much in terms of infrastructure and configuration.
But even this requires someone high up in the organization to have the insight that reliability requires some level of “inefficiency” — ie retaining certain highly paid staff, duplication of effort, over provisioning of resources, etc.
The irony is that the execs who could make those decisions are convinced that LLM tools obviate those needs, and shift all spare resources in that direction. But without heavy constraints from experienced humans, LLM tools will only multiply the complexity at the root cause of these sorts of outages.
I am positive there are bare-metal, no shared tenancy, customers of MS already. Unclear if they are down too. While yes, these companies are massive, not being allowed to share infrastructure defeats the entire revenue-purpose of offering a cloud. The hardware in these servers is unbelievably expensive. You'd go back to everyone having an IT department and a few racks of servers for hardware configurations that meet their specific needs (which I'm totally okay with, and even rooting for!)
I'm an outsider who used to work at a different cloud provider, so take this with a grain of salt, but this doesn't smell like a limits and provisioning problem, per se. It's not necessarily like they just had 1 too many emails tip the scales for the entire world. Until today stuff was running okay. This was a monitoring and fail-over problem, at a comically tragic scale - a cascade failure. Architecturally they obviously did not design for a world where they could damage control failure at this scale. Failure should be expected and designed for at literally every layer. They cheaped-out on careful design in order to play catch-up building a public cloud offering and here we are.
Yes but someone who knows what they are doing with years of experience i the field probably slows down, is more thorough, and goes through a peer review process before rushing to announce to the world their new discovery.
If you're a Google SWE with 7 figure comp, doing experiments with agent swarms you don't need to pay for, with healthy case of Dunning-Kruger... then maybe it is.
Ideally, tank your hole with a membrane and pump. Only a noob garden-plane-in-hole owner would crane it in without one! Bit late now.
On the up-side, it looks like it's going into a concrete clad hole so may have a cavity not be buried in soil. It won't be permeable like basement walls that suck water out of the ground. I guess it's aluminium/titanium so won't be red dust by spring but can still corrode in some fashion depending on ph/oxygen. Could there be steel in things like fasteners?
Oh, and it's a tube... no idea how they've sealed the ends.
My intro to game dev as an 10 year old was learning to use my cousins C64, writing some BASIC text based games. It was pure joy discovering programming that way.
It is utterly depressing to think that kids will never take that path again. Instead, we will get pulling the slot machine lever, zero skill, zero effort, nothing gained.
"Creating something" now means typing a few text sentences in to some prompt and paying money to these companies that want to essentially make humanity redundant. Instant gratification, no hard earned skills at the end. Compare this to the kid building something themselves with scratch, improving on it, moving on to Godot etc.
The AI boosters in here saying how amazing this is are being incredibly short sighted.
Anyone doing this with their kids: please take a moment to think about the implications of what you are doing. Even explain to your kids what an LLM is, the moral implications (massivley capital funded companies have stolen so much content to make this possible and now want to sell it back to us) and the importance of effort and learning real skills.
Creating something that other people will want to play is going to be hardly ‘zero skill’ going forward. I would argue the level of skill that’s going to be required to do this is going to be either at the same level or even much much higher…
Skills that, unfortunately, are likely to become obsolete very soon.
Taking the logical conclusion of your argument - we should also be teaching our kids how to fashion stone tools, because by moving straight to machined tools they are also missing out on "actual" skills...
Ironically, a kid that does fashion a tool out of stone will learn the skill of toolmaking deeper (in some respects, all other things being equal) than a kid that doesn't. A few years ago I created my own computer out of logic chips, this taught me a heck of a lot as well about how computer hardware and low level software works under the hood, more so than most of my software engineer peers, but I am under no illusions that doing this was required to be productive in the modern conception of this role, or society at large...
You can produce the same level of output with several magnitudes less effort, or you can produce output of several magnitudes greater quality with the same amount of effort. Or anywhere in between, or beyond.
And if you're putting in effort, you're going to end up learning skills, though they're certainly not the same as for doing everything by hand.
It takes effort, skill, and dedication to make something that's better than the flood of cheap stuff (slop) available out there. That's going to remain true with AI, it just plays out differently.
reply