Top tier reference

@netikras Yo check out my new site I built: https://127.0.0.1:8080/cool.php

Obligatory xkcd

@atheist Should be ltr else it would be layed out rtl (actually start from the right side of the element)

@jestdotty You can run a dynamic site but your files are wiped on each build I believe

@atheist God dayum their always free tier is juicy

Check out netlify. They have free hosting for dynamic sites, though it's more like a CI/CD thing so no persistence by default

But they do seem to offer a db service too

@lorentz Yeah I think that makes the most sense. For some reason I was worried about branch misprediction on the two consecutive loops but the remaining size of your buffer will literally be in L1 if not a register

In regards to SIMD, I haven't had a good idea for an efficient implementation yet. One major hurdle in utf8 decoding is that you have to smash the lower 6 bits of each of the up to 3 continuation bytes together. The only good ways i've found are the pext insn (which is microcoded and gigaslow on zen2 so I can't use it) and an unrolled loop

I've used the latter and it's surprisingly fast with a few other tricks (LUT for the first byte + fast path for 1 byte sequences)

Not a go dev but I heard := is preferred because it allows rebinding which you always use for errors, I so guess keep the style the same *shrug*

@jestdotty It's useful when you're running some wide algorithm over variable length data, e.g. utf 8 decoding where instead of reading each byte on its own you read the entire (potential) 4 bytes as one uint. Obviously for the last 3 bytes this would require reading past the end of the allocation

Though I think it's easier to just have both functions, one for the interior of the buffer and then one that handles the tail...

@kiki Yeah yeah I understand that, just sounded kinda funny how you phrased it

I recently tried vibe coding and my god was it terrible. Not really surprising though that it had the same quality/performance as chatbot llms (which isn't that great) considering that's exactly what it uses

@kiki The implication that it's only rape if the girl was underage is bit sussy though

@jestdotty "don't murder people"

uhhmmmm slippery slope 🤓👆

Please actually just kill yourself

@AlgoRythm You're only thinking emotionally

Because if you start justifying murders of people *you* dislike, the next person is gonna justify murder of people *they* dislike. And in response the next person is gonna justify murder of people *they* dislike. And...

It's an extremely dangerous game. I understand if you're angry. But don't be fucking stupid

Reads like assembly for a really questionable architecture

@kiki Understandable

Anger at the system is justified but cold blooded murder in the city streets is certainly not

@Lensflare I think it's just weirdo narcissists trying to get attention. Same goes for ostream

When they create new accounts you are forced to reevaluate who that is, whether to take him serious, etc. which means they can feel good about people thinking about them

@Lensflare In about 5 seconds some other bot will come in to save the day with some scam ass openai phishing website

I really wish I wasn't downvote banned

@antigermanist Yeah it was very funny

Just to be clear, the democrats also massively oppose releasing the epstein files because it's not about right or left but about protecting the globalists

@BordedDev Sure but you can still enjoy a bad concert with enough alcohol lol

@Alice omg alice is back

@YourMom llvm is literal black magic

But why did you go then in the first place

(And if you're cringing at a concert you definitely didn't drink enough alcohol :P )

@lorentz Ah I think I understand now

Yeah that's the beauty of the extremely efficient async implementation in Rust. It's a challenge of who dies first: You or the compiler :P

It's not really clear where the problem is in that snippet

@AvatarOfKaine "You ain't gonna need it"

Basically the idea that you shouldn't over engineer and over abstract your code. Only write what you actually need