Welcome! I'm the same but also a lot of Java lovers surrounding me. I wish he could do some Java-bashing as well, but it might be like kicking a dead dog... 😆

Yeah I also heard ALIVE instead of LIVE

I've been following Tsoding for years. Always thought he says 'alive' 😂

Amista Azozing saying Alive? Maybe you misheard... 😆

Yeah, its the main thing that holds me back from using cpp for wasm target. wasmbindgen makes emscripten look like a joke in comparison. not even comparable.

atom and proton taken, however atom is discontinued sooo..

*positron, i.e. an antielecton en.wikipedia.org/wiki/Positron

well it already kinda exists. it's called tauri

​@@CoolestPossibleName sadly, Tauri still uses a web browser. What Tsoding wants to do is more like Flutter or Avalonia but with C.

@@charliegnu at least it doesn't ship with one

Same, but this stream comes very close to showing all the puzzle pieces necessary to understand how the snake game was implemented

You need to define a very simple interface (like the one Tsoding describe around 4:00) and implement it in C and in WASI. I tried that - it is fun and kinda easy. I had a lot of issues trying to find online help - looks like Tsoding is the only one who cares about not using Emscript. It is really cool for simple 2D games, but the complexity of that API outgrew its benefits for me when I started more complex things like resource management.

Good luck on having fun with memory allocation/freeing (or with wasi if you want to use standard library)

@@NyanCoder Is it really that much more difficult than using C normally? If so I'll just mark all my large memory buffers as static, so I don't have to dynamically allocate/free anything. Or I'll just allocated from a big global static char array/arena, and turn strict aliasing off.

@@theevilcottonball well, some people really rely on standard library. If you do too, I'd recommend emscripten or wasi, if you not - I think you will not face any difficulties

@@theevilcottonball well, some people really rely on standard library. If you do too, I'd recommend emscripten or wasi, if you not - then I think you will not face any difficulties )

@@theevilcottonball idk why moderators or yt deletes my comments (I'm pretty sure there wasn't any insults or hate speech) All I wanted to say: if you use standard library you'll need wasi or emsdk (it basically only wraps wasi if other libs wasn't used), if you write code without libc functions - the experience would be pretty much the same as native

Your assertions that it's possible and even more sensible to just code your program platform-agnostically and then fairly easily code some wrappers for the minimum system-calling functionality you need for each platform is a breath of fresh air! It gives me hope that just maybe we can move things towards a little more efficiency and simplicity again, without making things impossibly difficult lol. I've known a little of a handful of code languages for a number of years, but I am just recently getting into learning how to really *make* an application or game. So starting that freshly, my principle is develop any real project I make to be as cross platform or extremely portable as possible from the start... but I've avoided Electron at all costs because I hate the idea of packaging a whole web browser with my 1000 lines of code and whatever script kiddie libraries I admittedly rely on lol. Electron apps just suck ime, but that could be partially due to the low barrier of entry (and so even big companies cut costs by putting the minimum effort into their Electron port 🤦‍♂️). I started learning Javascript through the game bitburner, the steam version, so that's the only Electron app I love lol. Again, all that means this video gives me great encouragement lol. The part about 64bit web assembly being difficult because it's javascript and would need to be the bignums type to address 64 bits was hilarious 😂

IMO it's more that they made the mistake of going with the callback by default method of calling back to js, instead of a more flexible coroutine style. Though that one is a lot more convoluted to use api-wise instead of calling into the instance and having it callback, instead it will return an object containing the information about the callback (name and parameters) and then you have to call again with the new result

im kind of surprised mr zozin doesnt pieces of the suckless suite like dwm and st

Yes but have you considered that js bad? Js monkey poopoo language? Did you know? Js is toy scripting language for children, flies, and fleas? /j btw

lol. the microphone (and maybe compression) make it sound like an actual drum set

Probably once a stream he does a little beatbox.

continued at 1:05:04

further continued at 2:11:04

TBF he demonstrates the easy way in the snake game and then tries to figure out Raylib's approach, but nobody knows how long the snake game really took to figure out either

I think clang even had some sort of intrinsic to directly emit the instruction but I was just too lazy to figure that out :P

It took me a long time, but you can get it to work in the end.

He mentioned it was because he reinstalled his OS and hadn't installed clang yet -_-

yeah but its cross platform

i dont think he'll do that lol

What's really funny to me is that every time someone makes something interesting with programming, someone will definitely ask to make some kind of tutorials and full courses.

Nobody learns C anymore, it's an obsolete language. Learn HTML and VisualBasic the languages of the future.

Learning C is the easy part. You need to learn programming using C.

he's already doing that

Emscripten is worse (supposedly). Porting the whole of raylib to JavaScript is better (supposedly).

​@@edhahaz The result of the "proof of concept" is - we need to reinvent raylib in JavaScript. An example for fail "proof of concept"

Are you saying you made a programming language ? (with a compiler ?)

And what is your language? Does it have a name?

have you considered writing a non-shitty rust compiler instead of inventing a 123th language

@@shrddr why would you write non-shitty compiler for a shitty language?

What is the issue about LLVM as "fix" for shitty compilers? Does it matter how the code gets optimised? I'm not sure what is the use case for a 1~2% improvement, but I gladly accept that loss whenever I write a new compiler on top of LLVM - I favour investing my time into language/compiler features and testing.