Sean Bohan

@phoboslab Nope, but I was thinking about making a new one with Zig and open source, sadly too busy to have time for that. BTW. I've completely switched from C to Zig now, even on my daily job, fantastic experience.

@PixelPicoSean That's amazing! I'm currently in the process of adapting ye old editor to local file support (no more PHP API). Not quite ready to rewrite _that_ in C yet :] Did you make the source available?

I'm rewriting my 14 year old "Impact" JavaScript game engine... in C. No reason. Just a lot of fun.

You either concieve of programming as data processing, or you concieve of it as the stitching together of black boxes (libraries and services). Programming education should teach you how to make behavior emerge via data processing. BUT, as you begin learn to program, you can't help but also learn about libraries. That's because most people need some starting point. You need to have a window open where you can make things happen. Often times, the window is "just there". You don't know why it's there, or how to make it appear, except by calling a library function (or an OS API). Most people start way higher on the abstraction ladder: you already have a library or framework that does a lot of things for you. If you start with games, you have a framework that can draw characters and animations and play sounds and handle all kinds of things. If you start with web, you already have a framework that handles http connections and routing requests to functions and rendering html from templates, etc. From here, you have two divergent paths: A) You internalize that programming is about stitching libraries together, and you keep climbing the ladder of abstraction higher and higher until you have no idea how anything works. B) You focus on learning the essence of programming at your abstraction level (how to make computers do things), and as you gain familiarity with things at your level, you begin to go lower down the ladder and learn about how the lower layers work. After you spend several years down either path, the attitudes and mindsets of people who went down the other route will be mind blowingly absurd. I find it absurd that people put so much effort to _avoid_ doing actual programming (data processing) and instead spend so much effort stitching things together (configurations, libraries, frameworks). Most people go down the black boxes path. That's why everything sucks. Instead of programming, you spend 90% of the time confuring tools, frameworks, databases, build tools, containers, orchestrations, external services, etc.

Play with some 3D pixel characters #pixelart #gamedev

Jolt Physics is fast, actively maintained, MIT licensed physics engine written in C++ (github.com/jrouwe/JoltPhy…). I'm considering creating the C API for it in order to use it from other langs (#ziglang). The task is huge. Would you "github sponsor" this work? Please RT. Thanks.

The teaser for youtube.com/watch?v=BFld4E…

@hiulit - DPI: 256 - 14" 3024x1964 - macOS Monterey (12.3)

Hey, #GodotEngine people! I have a favour to ask of you. Could you run "print(OS.get_screen_dpi())" and tell me: - Which number does it print. - What is the size and resolution of your monitor. - What OS are you using. Thank you very much!

@NoelFB @Polywogphony now we have `zig cc` as alternative to both compiler and build script, you may want to try (spoiler altert: a 60mb file download is enough, and you get cross-compiling support as well) ziglang.org

@reduzio Tiny size for web is the reason I made github.com/pixelpicosean/… How I wish I can one click export from Godot

Do the thing! The world was built by people who did the thing. While not all who tried doing the thing succeeded, all successful thing doers tried.

After seeing this bug so many times, I start to think it probably is very stylish art #webgl #javascript

@umutkarakoc Glad to see someone going similar approach, I've been making a Godot to HTML5 converter (scripts not compiled to JavaScript, but I'd like to try after seen this). Bundle size is hugely improved but performance sometimes worse. my repo github.com/pixelpicosean/…

Did not expect the crafting system get done so quickly, but it's also so exciting and encourage :) #GodotEngine #madewithgodot #indiedev

"is-land" development day ONE, at least day-night cycle works #Godot #GodotEngine #madewithgodot #indiedev

@dittomat omg, such a coincidence, I was making similar procedural leg animation the same time as you do, but in 3D! twitter.com/PixelPicoSean/…

the one at the bottom looks so damn determined haha i love it.

Eventually got the procedural leg animation done. #GODOT #indiedev #screenshotsaturday

@picontier @skipmore Cute, the character and tank remind me the NES game called Metal Max.

Here are a few recent screens as shared by @skipmore. Just when you think you fully grasp the world of Picontier there's a tank overgrown with weeds and a giant teddy bear. Don't worry, it'll make sense...

@Polycode Is that EnTT?

Adding final touches on the new reworked API! Here's an example of a simple ECS setup of a scene with a threaded renderer in C++. gist.github.com/ivansafrin/e8b…

2000 white circles in a JavaScript engine vs 20000 white circles in a C++ engine built with emscripten, both running in the latest chrome. My mac is pretty old but reality still shows. Hmmm #javascript

IMO the hardest step for aspiring (commercial) indie game developers is learning to finish games consistently and efficiently - to move past game jams and prototypes but also avoid getting mired in a single project for years without end. It's a tiny sweet spot that's hard to hit.