maxpolun

6 ms·

1.
by maxpolun 9y ago
I don't tend to believe people who say that everyone working in a particular field are crazy and stupid. Wrong maybe. Whole fields are wrong all the time. But not because they're all crazy and stupid.
2.
by maxpolun 9y ago
You can have multiple threads with coroutines. However you generally only have one thread per CPU/hardware thread, and use async io within that thread. This is the general architecture of nginx for example (though it doesn't use c
3.
by maxpolun 10y ago
I wonder what the performance difference is when you're actually handling the errors though. I'd imagine that try { doThing(); } catch (Exception1 e) { handleError1(); } catch (Exception2 e) {
4.
by maxpolun 10y ago
A lot of people will recommend reading great code -- well known open-source libraries etc. That's good, but one thing I think is useful is to read your dependencies. Then you can get a better picture of what "regular" code is
5.
by maxpolun 10y ago
I think they're just being very strict about what counts as breaking. They gave the example of upgrading the typescript compiler they use as breaking.
6.
by maxpolun 10y ago
Rust has overflow checking in debug mode, but release mode does not have any overflow checking. The thinking here is that you'll hopefully catch most of your overflows while testing the app, but get no performance penalty in production
7.
by maxpolun 10y ago
Modern JS does allow you to send large buffers from one worker to another with just a pointer copy (because it stops being accessible from the sender).
8.
by maxpolun 10y ago
Sounds like a similar process to hand-pulled cotton candy, just with pasta instead of sugar. here's how to make that: https://www.youtube.com/watch?v=auRNHI2nkIU
9.
by maxpolun 14y ago
for migrations in go, check out goose ( https://bitbucket.org/liamstask/goose ). I've used it, and it's pretty simple, but works pretty well. You can write migrations either in plain SQL (my preferred method) or in go.