User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
Admin
Wyvern-shaped software developer and hobby vector artist. Also sometimes a fluffy werewolf alien creature (Areon).

Creator of the neofoxes, neocats and other emojis.
wvrnBox
Website
https://volpeon.ink/
Speaking German, English
Age 30s
Pronouns he / him
Backup Account @volpeon@goto.wyvern.rip
Bonus Content @areon@icy.wyvern.rip
User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
10mo
Fedi when AWS goes down: neofox_smug
Fedi when Hetzner goes down:
neofox_surprised_pika
User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
10mo
I was wondering why light themes for VSCode didn't make use of colored backgrounds for tokens. Turns out VSCode doesn't support it, and obviously all the AI features are more important than a fundamental part of the editor that's relevant to everyone all the time when working with it.
User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
10mo
HaaS (HTTP errors as a Service)
User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
10mo
1. AWS goes down and takes half the internet with it
2. Nobody does shit about it
3. GOTO 1
User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
10mo
I need to build a Docker container, but it says HTTP 503. Let me guess, that's also due to AWS?
User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
10mo
@finn Borb
User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
10mo
Ente's part
User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
10mo
AAAAAAAAA MONDAY
User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
10mo
tfw when eepy, but the cold turned my nose into the world's best sealed vault
User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
10mo
@karpour neofox_googly_shocked
User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
10mo
I can't unsee that VSCode places checkboxes not next to the label, but rather the description below. That's weird
User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
10mo
I found out that it wasn't my parser which blew up the stack. It was the string builder which pretty-prints the JSON. Isn't that the thing designed to lower resource usage? neofox_googly
User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
10mo
There won't be broken Unicode on MY watch 😤
User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
10mo
@hexaitos neofox_googly_shocked
User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
10mo
Well, that's not great
User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
10mo
@hexaitos neofox_googly_shocked
User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
10mo
@LilacJaybrdComfy
User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
10mo
I got a cold brdFlat
User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
10mo
Seems the real problem is passing around and accessing a string's backing storage.

This crashes:
val t = "null"

fun iter(b : bytes)
  trace(b.string.show)
  iter(b)

pub fun main()
  iter(t.bytes)




This runs:
val t = "null"

fun iter(b : bytes)
  trace(t.bytes.string.show)
  iter(b)

pub fun main()
  iter(t.bytes)
User avatar
privTri Volpeon areonNSmol @volpeon@icy.wyvern.rip
10mo
It's super baffling because a byte slice is just a cursor over bytes, and I don't see any mistakes. github.com/koka-lang/koka/pull/384/files#diff-e0e03146bd1172ddffe490fde15787b2e00d2072cad832122a2c2094363b336b