rnmmrnm

this is cute but i imagined prompting the ai for a loop-di-loop roller coaster. If this could build complex ride it would be a game changer.

"So I deployed that hasty fix on friday..."

just my two cents that netfilter (for which iptables is a frontend) is a kernel subsystem and therefore global to all containers on host.

https://harmful.cat-v.org/software/GCC classic

Well here I tunneled multiple TCP connections traffic over a single input/output streams (the SSH shell IO stream).

Basically when you got a single communication channel and it's expensive to create more channels to tunnel multiple TCP streams where each connection get's its on channel, this is when you reach for the muxer.

i.e. here I probably could make it without yamux if instead I used SSH control port(socket? master?) and created many shell IO streams. but using yamux makes it cleaner. Also the server I'm working on is very buggy and you really get like 50% success rate logging in.

I suggest you download this `yamux` utility and play around with it really :)

reminds me how the other day I circumvented disabled SSH port forwarding by using https://github.com/nwtgck/yamux-cli + ncat already on the machine to do something like: yamux -l lport | ssh server -- <script: ncat --proxy-type=http -klp proxyport & and yamux localhost proxyport>.sh

good thing I needed HTTP access or else i had to find that socks5 server that's actually working again.

I also need elaboration on this. I presumed calling lua from c can be used to implement user-defined callbacks. Launching a thread for lua + locking seems even slower?

pretty fun though.

I didn't finish yet but I was thinking he's talking about memorizing the algorithm to calculate sines in your head.

obviously, but i'm not so keen to turn it into a pre-emptive scheduler either lol.

Terribly sorry!

Well the only thing that's really itching me is the fact that the whole lua debug.* section is documented as

>You should exert care when using this library. Several of its functions violate basic assumptions about Lua code (e.g., that variables local to a function cannot be accessed from outside; that userdata metatables cannot be changed by Lua code; that Lua programs do not crash) and therefore can compromise otherwise secure code (from the manual)

kinda creeps me out.

reading beyond the first paragraphs, I see this practically what he advocates to do :P

A bit off topic: I just wrote a bunch of lua C debug api code (lua_sethook) to pre-emptively run and context-switch multiple lua "coroutines" (well not so "co").

Is this library offering a lua implementation more well-designed for this use-case? I got all this code to unload the coroutine stack to store and and reload it before continuing it later. Does having C bindings to this library makes sense?

you wrap those properly. believe me waking up in the middle of the night because someone abused panic to throw state around, end up being called from a new goroutine, just enough to crash the entire pod, sucks even more.

tbh only like 50% of my `if err != nil { return err }` are mindless. rest of the time, the fact that error handling is explicit and in my face has helped me alot during my time with go.

sane error handling in go is more productive any day.

the day the go codebase throws random panics is the day I quit the company.

And he didn't even get into how mac docking stations fucking suck and full of graphics bugs (everybody in my company actually turned off chrome GPU accel. because the display sometimes went crazy while rendering.)

my company was too scared to roll X509 signing code on their own so here we are.

More than seeing it in main, I'm happy for the "python thread slow" meme officially going away now.

Thank you. HN stripping query params is funny.

I get hurt by managers messing with my scope every day. It is a struggle :). Because of it I also find solace in open source where I am the boss of everything.

But, I don't give up. I pitch my bosses research trails all of the time. 90% they don't hit the mark, mostly because I don't try to conform to the whatever roadmap the product team has laid out. But once in a while my ambition and their plan converge, and this is when I get to play out the really cool stuff I do at my job.

Indeed one of my favorites as well. Can't stop thinking about its modern angle where for example our industry is full of mediocre programmers that only really can do more of what they have already seen. I'm really longing for colleagues that actually put research effort into their code.

cool call me when they got one for go lol