reminder: computers can only do integers. everything else is a lie based on integers

The Modern Software Stack

Interesting fact: raylibtech tools fit in a single floppy disk. High-performant, single binary, beatiful multi-themed UI, powerful command-line, multiplatform, no external dependencies. Better software is still possible. #gamedev #toolsdev #raylib #raygui #uidesign #futureisnow

you can just render React with Raylib lol

raylib4Nintendo64 soon™ happy Andalucía 💚 day #raylib #libdragon #Nintendo64

The people who built this weren't motivated by profits.

Write your own game engine. Authors don't download a story template for their books then see how much they can be creative within those limits, they start from scratch. So can you. It's not difficult(*), and it makes for more interesting games. (* compared to making a game)

I met a founder today who said he writes 10,000 lines of code a day now thanks to AI. This is probably the limit case. He's a hotshot programmer, he knows AI tools very well, and he's talking about a 12 hour day. But he's not naive. This is not 10,000 lines of bug-filled crap.

who will own the square □ arc? @vercel owns △, @openai owns ○

Qt + Wayland are gone from openpilot! These were two of our nastiest dependencies. The immediate benefits so far: > 4s faster boot time > 500mW power savings while the car is off > more GPU available for the driving model > ~10k less LOC in openpilot > removes all the 32bit armhf dependencies from our custom SDM845 OS > removes the old, crusty closed-source Qualcomm Weston we were running > a graphics stack simple enough to reason about The new openpilot graphics stack is just Python bindings for @raylibtech. Let a little bit of complexity in, and it'll just keep growing!

George Hotz says that everyone should learn C and Assembly.

Our first video game, coming soon to a COMMA_CON near you.

the joy of coding is gone think about it for a second, if we actually go down this road of vibe coding we will absolutely kill the joy of coding i have worked in projects that the only thing driving me was the technical challenges vibe coding will force you to understand that the code was just the means to the end and that only developers care about it but in a possible future this care will be replaced by a sad feeling of not having the time, the priority of enjoying solving a technical challenge by yourself

I just realized that Python might be the last programming language we would ever need to build software. Most powerful tech stack today: • Python • English • Your favorite LLM

Interesting fact: raylibtech tools fit in a single floppy disk. High-performant, single binary, beatiful multi-themed UI, powerful command-line, multiplatform, no external dependencies. Better software is still possible. #gamedev #toolsdev #raylib #raygui #uidesign #futureisnow

Sometimes you just need to learn basics so you know what you're doing. Odin + Raylib, custom simple lighting and dithering shaders + Trenchbroom maps and basic sphere-to-triangle collisions for the player. Loads instantaneous. Runs on potato PC.

I read this article about software development, which I knew about because I saw Prime reacting to it: notashelf.dev/posts/curse-of… For the most part I think it is fine: a relatively young programmer is doing the healthy work of introspecting on what he should really be doing. But there's one part of the article that I think is a deep mistake, and the author doesn't know it's so wrong because he has never experienced the alternative: "Software doesn’t stay solved. Every solution you write starts to rot the moment it exists. Not now, not later, but eventually. Libraries deprecate. APIs change. Performance regressions creep in. Your once-perfect tool breaks silently because libfoo.so is now libfoo.so.2. 2 I have had scripts silently fail because a website changed its HTML layout. I have had configuration formats break because of upstream version bumps. I have had Docker containers die because Alpine Linux rotated a mirror URL. In each case, the immediate emotional response was not just inconvenience but something that moreso resembles guilt." Yes, this is true in much of the programming world. But there is another world in which people build things that last much longer. I have done it many times. I shipped a binary for this game Braid in 2009 that you can still download and play on Steam 16 years later. If you are pretty young (like 35), you can run binaries on Windows that were compiled before you were even born, which is amazing given how hard they have been trying to f up Windows lately. On an emulator like MAME, you can play arcade games programmed in 1979. If today's software "technology" is so much better, why does it fall apart like tissue paper? The author is not wrong about the cited decay. But this decay is not inherent to the practice of software. It's due to choices made, usually foolishly, by the people designing the systems being interacted with. And, it's due to a lack of knowing better, non-exposure to the sector of programmers who are very concerned with their code lasting a long time, actually. The way you make code last a long time is you minimize dependencies that are likely to change and, to the extent you must take such dependencies, you minimize the contact surface between your program and those dependencies. The actual algorithms you program, the actual functioning machinery you build, is a mathematical object defined by the semantics of your programming language, and mathematical objects are eternal, they will last far longer than your human life. The goal then is to avoid introducing decay into the system. You must build an oasis of peace that is insulated from this constant bombardment of horrible decisions, and only hesitantly interface into the outside world. This means, for example: If you are shipping on iOS, you only reluctantly use any functions iOS gives you, because when you use them, Tim Apple will come along and break your program next year for arbitrary pointless reasons, because Tim Apple does not respect you or anyone you know. This means a program cannot last forever on iOS, because Tim Apple likes breaking your things and watching you submissively clean them up. But the core of your program, which could be 95% of the code, is fine, and you can deploy it elsewhere. This means you have to insulate from Linux userspace, because of all the jackass decision making that introduces constant incompatibilities while somehow never making the system better. Using a library dependency to do font rendering or sparse matrix math? That dependency gets checked into your source tree, a copy of exactly the version you use. Ten years later you can pull down that source and recompile, and it works, because your program is a mathematical object. If you want to upgrade to something newer that has bug fixes and so forth, you are free to do so, but you are also free not to do so, and your program still works. (And how many of these bug fixes do you really need? Your program worked correctly when you shipped it to the greatest extent you could measure, because you are a skillful software engineer who wants to ship things of a high quality). Everyone who got into programming for the joy of it knows, at some level, that the magic of programs is that they represent complexity that is replicable over time (and thus they exist outside of time). But the trashy programmer culture of the past 20 years stopped aspiring to this, and now has forgotten it is even possible. And so long as people have forgotten, decisions will continue to be made that make the problem worse. There are programmers who only write glue code, and who think that's what programming is; to these people what I have written above will not make sense. But the good news for that contingent is, they can always just stop writing glue code and start doing something else! If today's software "technology" is so good, why do you think it needs so much glue? Maybe there is a stylistic problem. So if you are looking for what to do in the world of software that can represent a lasting contribution, maybe this is food for thought. @NotAShelf @ThePrimeagen

Made a chrome://dino game replica using raylib. After 10 years in game dev, raylib indeed brings me back the joy of programming #gamedev #raylib

Hello, openpilot user. It's release time. Go hit that update button to grab openpilot 0.10.1.

Putting a coat of paint on the new debug tools for clay. It's a similar idea to the chrome inspector - just gives you a window into your UI hierarchy and its configuration. Still all just one .h file - it just injects the debug view as additional draw commands. Out in a few days.

Today #raylib is the #2 world trending C project of the week on GitHub! 🤯🚀 Source: github.com/trending/c?since=…

Built with C and raylib, 100k enemies + 5k bullets, its not just enemy-bullet collision, theres also some enemy-enemy separation that happens, it uses a spatial grid internally, i havent made all the optimizations yet, not even render culling, i think i can push it more

Python is the best language in the world. Yes, Python is slower than other languages, but I don't care because most of my work doesn't require it to be faster. Python is fast enough for what I need, and fast enough for most people out there. On top of that, over 90% of the Python code you interact with uses C/Rust/Fast-thing behind the scenes anyway. The speed at which you can write good Python code is way more important in most situations than the speed at which that code must run. And no other programming language can match Python in code clarity and readability. Except English, maybe.

Hey! I made a simple Space Invaders/Breakout game in COBOL using raylib! Very fun project :) 🧵

Did you know Assembly language has overtaken Rust in popularity?

Within 5 years I predict a UI trend emphasizing sharp corners, no animation whatsoever, and sub-millisecond snappiness of all controls

So 6400 at 60fps wasn't enough huh ? 42000 now with instancing. #gamedev #raylib naturally there's nothing else going on.

I am always bemused by programmers that don’t use debuggers. It isn’t just about breakpoints and examining variables, but also being able to break into a process that has been running for an hour and issue something like: (observation_ring*255).to(dtype=torch.uint8).view(128,16,4,3,128,128).permute(1,0,2,4,5,3).cpu().numpy().tofile('results/ring_128x128.rgb')

Hey! Just published rFXGen 5.0, a simple and easy-to-use fx sounds generator!! 🔊 Free and open-source! Use it online, download multi-platform desktop version or compile it for your favorite OS!😄 Get it here: raylibtech.itch.io/rfxgen Powered by: #raylib #raygui @raylibtech

Have you ever compiled a single source file named `game3d.cs` that was 32510 lines long. Me neither, until today! ``` $ wc game3d.cs -l 32510 game3d.cs ``` The game is matty77.itch.io/conflict-304…, and uses Raylib.

Hey GAMEDEVS! Which game engine are you using, and why exactly this? #indiedev #gamedevelopment #gamedev #IndieGameDev #indiedevelope

Procedural walk cycle test. Are there bugs - yes, but do I love it - of course, I can't stop playing with making it move now. Made it in #raylib, because I didn't implement all the loading yet, and #raylib is an amazing library y'all should try!

I published my path finding code guide on my personal web page and on itch.io. It runs in the browser and is (hopefully) compatible with all devices and browsers. #raylib

Thrilled to announce that A Little Perspective, a puzzler where perception and reality are one and the same, now has a trailer and a store page! 🟥👁 Wishlists/reposts appreciated, link in the replies :) #indiegames #puzzle