quail.wtf
A cursed quail. I think too much about databases.
FYI if you follow and have no posts I will block you :)
108 posts
90 followers
79 following
Regular Contributor
Active Commenter
comment in response to
post
Their... Data centers? A data center? In a nuclear apocalypse?
comment in response to
post
When I switched to the moonlander it was... about 2-3 weeks before I felt like I was good at typing again. During a few incidents I got frustrated and had to pull out the old keyboard.
Stick with it! It's worth it and your wrists will thank you :)
comment in response to
post
Have I recommended Severance to you yet? It's a pretty heavy novel, very nihilism, but it was the best novel I read last year by far
comment in response to
post
It's all going according to plan
comment in response to
post
Honestly I kinda love this one. The rabbit especially almost has a plastic feel to it.
comment in response to
post
I swear to god this is the bug that will never go away. Thank god I have a deterministic renderer
comment in response to
post
I suspect the sheer number of users is where this starts to get annoying - the size of the key space keeps growing and growing
comment in response to
post
They're the worst bugs to track down (imo) because all of your invariants throughout the program are held, it's just that the results are wrong
comment in response to
post
Yeah you really have to start upping the difficulty for yourself at some point. Despite initial appearances the game is actually very easy by default - with enough skill you can get to the "e's" with any seed. (Check out balatro University on yt)
comment in response to
post
I do think it's important to have some way to reliably test the behavior of a system from the "outside". At some point "running the system locally" needs to become "running the test suite" and IMO it's best to start with that mindset
comment in response to
post
Good news: the mirror is closer to being correct. I was previously including contributions from light samples for specular bounces, which is.... not how light works.
Bad news: diffuse surfaces are still not correct :(
comment in response to
post
Right it's because I wasn't renormalizing the light range back to 0,1. That's also why upping the sample count would fix it
comment in response to
post
honestly that looks better than I expected for 8 samples.
BUT IT COULD BE BETTER
comment in response to
post
I suspect this is abouuuuut as far as I can go before I'm forced to add randomness into the renderer. Actual materials, here we come!
comment in response to
post
I suspect if you don't have experience with production outside of "does it work or not" it can be hard to imagine what the point of otel even is. Logging works perfectly fine for them
comment in response to
post
I suspect there is a wide range of experiences for software devs. There are so many people who are "write web apps with a backend and a database" and yet who will never go oncall
comment in response to
post
That was my thinking at the time, but I feel like the ergonomics of the nushell aren't quite there for 90% of shell-y tasks.
comment in response to
post
If that's nushell good luck, I bounced off of it pretty hard 😔
comment in response to
post
Next step is probably.... UV mapping maybe? although I should probably get these light calculations correct :P
comment in response to
post
Honestly I feel like more things on the Internet would have fine grained pricing on how much I cost them. Paying per tweet for bsky? I wouldn't be opposed.
No I do not want crypto, fuck off with that
comment in response to
post
For various reasons this is gonna be a huge pain in the behind to get performant again. It's one data copy michael, how bad could it be?
Whatever, I wanna work on the raytracer itself. Maybe it's.... texture/uv mapping time??
comment in response to
post
👀 it shouldn't be working that way - importc in zig is a wrapper around `zig translate-c`, and the build system should be properly caching all that
comment in response to
post
Dying to see how the code for this works, my understanding of all things sound is "here be dragons".
comment in response to
post
Oh yeah I think that's pretty common with other terminals? I think it's called quake mode or pulldown mode or something similar. I've uhhhh never managed to build a workflow around it? Maybe if I combine that with zellij/tmux hmmmm
comment in response to
post
Lol I mean, I'm coming from alacrity so anything beyond a very basic terminal emulator is 100% new. I actually had to turn off stuff like tabs and window decorations because I didn't like how it meshed with i3wm 😅
comment in response to
post
All switched over! I'm coming from alacritty, which is pretty fast already, but I feel like certain things like scrolling in nvim is juuuust a bit more responsive, _and_ seems to have less tearing which is nice :)
comment in response to
post
(the bug in it is an annoying one, and I decided not to half ass the fix)