optymizer1

4 ms·

1.
by optymizer1 13y ago
You could even go further and assume all user resources are logical extensions of sleepy.Resource: type HelloResource struct { sleepy.Resource } This makes it clear that you're inheriting everything from sleepy.Resource, s
2.
by optymizer1 13y ago
Russian first names (not Cyrillic) are very strange: "Innocent Korovin" - really? Russian (cyrillic) seem more realistic though.
3.
by optymizer1 13y ago
So.. it's like prefetching.
4.
by optymizer1 13y ago
Here's an advice: browse for job posts you'd be interested in. Look at required/preferred qualifications. Start learning those. When ready, apply for those kinds of jobs. Also, find out what other libraries/API they migh
5.
by optymizer1 13y ago
In C, variables have function-level storage. I don't recall the actual term from the C standard, but the storage for _all_ variables declared in any blocks inside a function is allocated at the beginning of the function, when the stack
6.
by optymizer1 13y ago
That's the obvious next step, but it's not valid C89 and that may or may not be relevant for people doing embedded programming. Personally, I'm all for using newer standards and declaring variables locally when it makes sense
7.
by optymizer1 13y ago
I'm not completely on board with #4 (initialization of variables). I agree that 'declaring and then assigning a value' _within the same block_ vs 'initialized declaration' has no speed gains, only downsides. However
8.
by optymizer1 13y ago
I hate to be that guy, but what's the big deal? Where's the full disclosure? It looks like they're just documenting the API, which is not really disclosing much. Anyone can fire up burpsuite proxy and inspect HTTP requests an
9.
by optymizer1 13y ago
On a related note, 10 years ago, I was asked to go to MIT and take a math exam instead of a student. Obviously, I said no, but I did not expect an MIT student to do that. He was more of the business type though.
10.
by optymizer1 13y ago
I find the JSON benchmark misleading a bit. I posted this before, but I'll say it again: JSON serialization in Go is slow (2.5x slower than Node.js for example [1]). The web server, however, is very fast. When they measure webserver+js
11.
by optymizer1 13y ago
This is pretty neat. Functions that read from or write to http.Request.Body should be able to accept a Context object, assuming they take a Reader/Writer. If they take an http.Request, you're going to pass in Context.req, similar
12.
by optymizer1 13y ago
Interesting. Now, what does SetUser(r, "dave") do? Since you're passing in 'r', it must keep a map of all requests and their data, i.e. map[*http.Request]string ("dave" being the string in this case). This
13.
by optymizer1 13y ago
I'm not saying that having a bug is something to be ashamed of. I am pointing out that the page is making a big deal out of a small issue, in order to argue a bigger point: operating system development is hard. The whole page screams w