There is a difference between nullish coalescing and the or operator. The or operator will return the right value if the left operand is a falsey value. however the nullish coalescing syntax will only return the right value if the left operand is null or undefined. So "" || "a" returns "a", but "" ?? "a" returns "" Edit: I paused and commented before watching the next 5 seconds. Oops.

Bit of context on the touch one; if nothing handles the touch event the browser converts to a mouse event and refires so that older sites can work on mobile. It's pretty common to handle only mouse even for touch events if theres nothing specific to touch you're trying to do

This session is super cool! Seeing the maintainer's side and some git usage is very interesting. Thank you so much!

Hi Zozin! I recently played with WASM in Go and I liked the approach proposed there, I think it’s quite interesting because having just once written a wrapper for calling functions from Go on the JS, you can then use the language of the project itself, in this case C, to create an API for raylib And thanks for the streams, I highlighted a lot of useful things from them :3

git blame is good thing to blame other people git bisect is good thing to blame other people before figuring out that you are blaming urself

Congratz with 100k!!!!!!

I had no idea about that git bisect command. thats so useful

As a relative novice, it is very interesting to see live the process of open source collaboration.

23:40 As a Visual Studio user this was pure magic! Generally, I enjoy your navigation through your system.

46:35 king

In regards to ?? vs ||, ?? is the null coalescing operator, it takes the first unless it's null, then it takes the second; || will give the first if it's a "truthy" value, so anything that's falsey except null or undefined will be rejected by || but accepted by ?? As an example: "", false, and 0 will all yield to the alternative with ||, but be accepted by ??

Didn't know about git bisect, very cool

I love your stream ❤

my uber after 20 minutes of silence: looks like we arrived

To "The Browser Should Be Simpler ..." (around 41:00 + "Support for worker execution context. No. 22" Pull Request). I totally agree! The browser should simply be the X-Server of the "Web", an engine to display Scheisse! Now it is a -playground- -for- dumpster fire of all kind of internal frameworks and wannabe features like VRML and CSS( hehehe, hate me for that:P). Absolutely BLOATED BS! When did we take the wrong turn? (Hint: "The Browser Wars", Microsoft, Google, Mozilla. There are no angels in this club!:))) )

I suspect the ?? is inspired by PHP.... There you initially just had ?: which was later followed by ?? What is funny is that in PHP these are actually 2 operators (each) so you may put whitespace between them. (These are the ternary operators.) ?: is the same as || in JavaScript

asyncify

Javascript operators' easter eggs.

About browsers should beocme "Distribution programs", aren't they already? I get what you mean, server send html which says button there, and the browser actually renders the button natively on any device. That was the original thought. Why do you think URLs are called Universal Resource Locators? A browser simply asks for a resource from a location!? The only added part is, instead of downloading everything to a file on your system, it can instead display some types of content. Like an Video file, MP3 file, etc. most have players built-in, with native controls written by whatevery UI library the browsers using. Then it can also render HTML. HTML is a markup language, in which you describe layout as "bullet-points" for the browser to render how it wants to on any given device natively. Now, HTML can also link to other content... uiuiui So it recoursively resolves fetch requests... then renders all content. And also scripts! oh oh! So it also fetches unsafe code and has to ship a interpreter + a standard library. But then people said, we actually want client-side interaction, and don't want to leave it up to the browser how the button looks like. So we enter CSS and JS. JS was to provide client-side interactivity together with CSS. And to provide a way to layout your page. But soon people started building apps and ""browser-native"" apps, instead of distributing it through the browser. They are now using the browser AS their application. But then still ship in MB of javascript their own "Virtual" UI Frameworks that transpile/translate it to browser renderer html and css. Your point of why not, at this point, ship your own application, which just happens to run inside the browser window. But isn't run using the browser, but your own renderer code etc. That was always possible. Not everything the browser displays has to be HTML. But now they are making it even easier, by having WASM "Assembly for Web", as a supported "native" filetype a browser. Instead of rendering the html, showing the mp3 player or video player. It begins executing the send-over binaries. Within the browser natively. Why people use an html doc and render to a canvas element? And pretend its the only way? No idea.

When you fixed the text y offset you added fontsize separately when it is already there in the parentheses, multiplied by the line number. What the commit author did is make an off by one error as the loop starts from zero so the first line was never offset. Adding fontsize twice looks very bad.

This subject has potential for a series of videos. Don't you think?

Adding a js dependency to a zozzin project, rookie mistake kiddo

1:31:23 This is why you use a linter and force formatting.

Pog

Whenever I see you faffing around in chromium, I am reminded that I do actually prefer firefox for dev tools, because they are more accessible. Which is kinda unexpected. (like the buttons for dark mode preference are right there in the inspector for ex.)

If you go out of your way to contribute to a project that is not yours, you have to expect anything. It doesn't mean that any reaction by the devs in charge, as shitty as it can be, will be good or just, because shittiness is just shittiness. But you have to expect anything and if you value your time too much, maybe you shouldn't work for free.

49:19 I am literally crying from laughter. Why does it copy the name?

1:20:00 this is http query params being stupid, not JS, lol.

why don't you do odin? come on man I don't wanna die before you do odin

First try!

I'd expect the double pipe (||, a.k.a. logical OR) would return boolean (e.g. `'hello' || 69 === true`) and the double question mark to be as shortened ternary operator (`('hello' ?? 69) === ('hello' ? 'hello' : 69)`) 🤦‍♂

Alternative stream name: shitoberfest

Some devs really need to grow a spine. A maintainer shouldn't have to waste their time explaining why a PR gets rejected. It's almost like dealing with children. Anyone else have to put up with that kind of behavior running a team, especially from fresh graduates that have inflated egos?

Multiple cursors work best in editors like Helix.

31:31

Zozinnnnnnnnn

24:15 Of course my vim can do that: qq/{ait,at}ayyptwct_wasm/"buildct_wasm/",ea/wasmG:normal! @q