In regards to the output noise in your serialization of 0.5, I believe that 0.5 is a machine number so should be representable exactly as a float/double which might indicate that you have a bug in converting strings to floats
Cool. Welcome back. Good simple fixed. For hsl, I think you can move normalization, from parsing, to actual usage (and also to_string() for it). Normalization here means doing 'mod 360' (and probably ensuring it is non-negative).
I'm so incredibly glad you're back with programming videos! I truely love them (I started late with the whole browser playlist and just consumed them one after the other)
Yes! Browser hacking is back! I guess now that Ladybird announcements have their own TH-cam channel and you're not much involved in SerenityOS any more, it really makes sense to use this channel for things like these without having to worry about the algorithm too much.
I love this type of videos, actual coding is so much fun to watch, not like this tech influencers that only talk about it... Anyway, I love the premisis of the WPT test, simple fixes, that are easy for beginners and I have finally a good reason to dig into the code and start contributing 🥳
Hey @Andreas, Glad to see you back streaming again. Sorry to be forward, but may i ask you which font you are using in CLion ? seems monospaced font but coudn't find the name
I think the faces in the new style of thumbnails don’t feel like they match the vibes of your videos. Maybe you could just have the WPT graph, the number of tests now passing, and a screenshot of the failing test or something if the goal is to appeal to a broader audience not already familiar with your content while still accurately representing the content. I don’t think there’s any actual downside to the current thumbnails, just throwing my thoughts in lol P.S. loving the return of actual coding/hacking videos :^)
I am not a full-time programmer, but I have to ask: Why are you using auto as the type of every variable? This makes the code way less readable for someone without a bloated IDE written in electron and javascript.
Many reasons but chief among them, it's safer to use auto since you know you're getting the exact same type on both sides of the binding. If you don't use auto then you may end up with an implicit conversion either now or in the future.
You don't need a bloated ide, you need well named code which makes it obvious what's going to be returned. I use an editor without anything except goto definition and don't have issue with auto.
I still use type inference (both in C++ and Rust) despite not having inline hints! In particular, if it's obvious what the return type is going to be (especially if I have to explicitly type it out as a generic parameter later in the statement), and/or if there is no risk of type-safety pitfalls (which is 99% of safe Rust)
Andreas has said before that it should be clear what type something is from the code. When it's clear what type something is, specifying the type manually is just noise. If you feel the need to rely on specifying the type manually, your code is not clear enough. Plus it has other benefits as previously mentioned, like avoiding nasty implicit conversions.
am i the only one that thinks the copilot suggestions are SUPER distracting ? they weren't turned on in the previous video, and it was much easier to focus on the code without it 😢
It brings me joy that you're doing these again.
WHF glad to see you're back! ❤
Oh, thank you. These debugging videos are awesome.
This makes me unbelievably happy. Been missing these coding videos of yours a LOT, Andreas!
An hour and a bit, fantastic!
I certainly missed these. They're a joy to watch and learn about ladybird and the standards!
Welcome back
In regards to the output noise in your serialization of 0.5, I believe that 0.5 is a machine number so should be representable exactly as a float/double which might indicate that you have a bug in converting strings to floats
What appears to be happening is that 0.5 is being store as 128 (255*0.5, rounded to even), and them converted back as float (128/255 = 0.50196078431).
@@Rodrigo-xf2oe ah yeah that makes sense
I have very much missed these!
WHF! I missed your programming videos
I'm so glad to see these again! You're the only channel that can just sit down, hit record and code and I don't get bored.
Cool. Welcome back. Good simple fixed. For hsl, I think you can move normalization, from parsing, to actual usage (and also to_string() for it). Normalization here means doing 'mod 360' (and probably ensuring it is non-negative).
rebaseline doesn't take an argument, if you want to filter which tests are run, you need to pass -f or --filter :)
Two days in the row, unbelievable!❤
I'm so incredibly glad you're back with programming videos! I truely love them (I started late with the whole browser playlist and just consumed them one after the other)
What a gift! A second video the next day. What a time to be alive 😊
Thanks for doing these videos! They make it so much easier to become a contributor on the project 😸
So happy to have a video! Thanks Andreas!
Yes! Browser hacking is back! I guess now that Ladybird announcements have their own TH-cam channel and you're not much involved in SerenityOS any more, it really makes sense to use this channel for things like these without having to worry about the algorithm too much.
These sessions are really comforting... :) Especially with such a nice view of macOS!
Just saw the video came out, I just know it's going to be amazing!
Very happy to see number go up!
whk! You are spoiling us, thank you for uploading again!
I love this type of videos, actual coding is so much fun to watch, not like this tech influencers that only talk about it... Anyway, I love the premisis of the WPT test, simple fixes, that are easy for beginners and I have finally a good reason to dig into the code and start contributing 🥳
Thank you Andreas. Amazing videos 💎.
Is this an early Halloween video? No glasses, and... is that a Mac ?
...seriously great to have a new hacking video, yay!
Whatching the macos dock oscillate is kinda fun
Yay! Missed these.
Yes, thank you ❤ also thumbnail looks very cool :^)
Hey @Andreas,
Glad to see you back streaming again.
Sorry to be forward, but may i ask you which font you are using in CLion ? seems monospaced font but coudn't find the name
Missed these :^)
that broken-rgba-string parsing one is just... lol
great improvements
we're so back
It's so fascinating!
I love you! (brotherly)
thanks so much for this content!
Photosensitive epilepsy trigger warning @ 1:04:00 (heavy flickering)
that's why he's the GOAT
Have you considered doing coding livestreams?
What happened to qncvs? :^(
He's retired in the countryside :^)
Missed those coding sessions
Is Yes/No enum a new generation of bool?
You should get a shock mount for your mic boom 😊
Yess, just got one :D
@@awesomekling ❤️
We are so back!!!
My depression is instantly cured.
I think the faces in the new style of thumbnails don’t feel like they match the vibes of your videos. Maybe you could just have the WPT graph, the number of tests now passing, and a screenshot of the failing test or something if the goal is to appeal to a broader audience not already familiar with your content while still accurately representing the content. I don’t think there’s any actual downside to the current thumbnails, just throwing my thoughts in lol
P.S. loving the return of actual coding/hacking videos :^)
hey andreas, would it be too much to ask you to not have the drawing of the bug in the background? i know its art but it really creeps me out
make graph go up!
I really would like to find some time to hack ladybird!! It seems a lot of fun!!!!
I think this is a unique format, try to live code more
Good luck to you but the complexity of modern web standards is insane and the pace is increasing.
WHF!
I am not a full-time programmer, but I have to ask: Why are you using auto as the type of every variable? This makes the code way less readable for someone without a bloated IDE written in electron and javascript.
many editors can do type annotations, for example neovim. you can get better tools
Many reasons but chief among them, it's safer to use auto since you know you're getting the exact same type on both sides of the binding. If you don't use auto then you may end up with an implicit conversion either now or in the future.
You don't need a bloated ide, you need well named code which makes it obvious what's going to be returned. I use an editor without anything except goto definition and don't have issue with auto.
I still use type inference (both in C++ and Rust) despite not having inline hints! In particular, if it's obvious what the return type is going to be (especially if I have to explicitly type it out as a generic parameter later in the statement), and/or if there is no risk of type-safety pitfalls (which is 99% of safe Rust)
Andreas has said before that it should be clear what type something is from the code. When it's clear what type something is, specifying the type manually is just noise. If you feel the need to rely on specifying the type manually, your code is not clear enough.
Plus it has other benefits as previously mentioned, like avoiding nasty implicit conversions.
am i the only one that thinks the copilot suggestions are SUPER distracting ? they weren't turned on in the previous video, and it was much easier to focus on the code without it 😢
Ew macOS