Request done! Thank you !!!
Request done! Thank you !!!
Spider Teto
#้้ณใใ #KasaneTeto
you're not her
#signalis
drawing of priestess from arknights lean-sitting on terra (earth)
you'll always come back to me
Sporty Fluorite ~ ๐
เธเธฒเธชเนเธกเธงเธชเนเธก
White Monster Energy Girl sketch:
Redbull only gives you wings ๐ชฝ with white monster energy you get so much more ๐
Daily #1975 - Swift & Uncomplicated
๐ฅฑ
#Inehoda #Mekaberry
mori calliope!? ๐โค๏ธ#callillust
Dante
#DevilMayCry
CHAINSAW MAN !!!!!!!!!!!!!!!!!!!!!!โ๏ธ
#chainsawman
tea
ใณใผใใใใใจใใใใใพใใฎ็ตต
ใณใผใใผใงๅทฎใใคใใ
kiraraa
searching through log files in disbelief. @grep is this true?
sodashi uma fandesign from 2025 #original
everytime someone whines about gpl vs mit an angel looses its wings
fair, but i'm not sure if that's worse than a scenario in c/c++ where the *codebase* is the one making these assumptions, and there's no mechanisms to enforce that those assumptions are even consistent or followed. At least in rust you know any safe code will always play by a consistent set of rules
ใขใใฏใญ็ทด็ฟใใใจใ่จใฃใฆใชใใฃใใฃใๅ...
similarly, I hate the opinion people parrot of unsafe rust being somehow harder than doing the same thing in c or c++. It literally isn't. the article that said it basically boiled down to
- unsafe is hard because you need to match rusts own assumptions
- rust doesnt have -> syntax (who cares)
IWY
79/100 Lighting Practice