vfaronov

5 ms·

1.
by vfaronov 5y ago
But doesn’t this apply to “normal” panics as well? When unwinding the stack of a panicking goroutine, any deferred call might panic again, in which case Go keeps walking up the stack with the new panic. In a typical server situation, it wil
2.
by vfaronov 5y ago
> While that sounds like a strange implementation detail, the philosophy of the .Net team has always been "how do you reasonably recover from an stack overflow?" Can you expand on this or link to any further reading? I just r
3.
by vfaronov 7y ago
The title of this HN post is completely out of context, and the discussion here is unrelated to the article. The author is not at all arguing against types or Haskell, nor is he bashing QuickCheck (he’s developed a QuickCheck-like framework
4.
by vfaronov 8y ago
How much of this applies to 1~100KB responses?
5.
by vfaronov 8y ago
HTTP is an inherently complex protocol, which has over time accrued many idiosyncratic, non-orthogonal features to support various use cases of the growing Web. Just consider that there exists an entire class, entire design space of librari
6.
by vfaronov 8y ago
Case in point: CacheControl [1]. Plug it in and you get flexible caching — interoperable with NGINX, the browser, and everybody else — for very little. But it relies on the protocol. If you respond to GET /stars/98765 with 200 (OK
7.
by vfaronov 8y ago
RFC 7540 also defines an optional way for the client to signal whether it wishes the request to be processed asynchronously: https://tools.ietf.org/html/rfc7240#section-4.1
8.
by vfaronov 8y ago
https://tools.ietf.org/html/rfc7231#section-6.5.9 > It is not necessary to mark all permanently unavailable resources as "gone" or to keep the mark for any length of time -- that is left to the discretion
9.
by vfaronov 8y ago
Outstanding explanation. I would like to emphasize one point: > If you have multiple systems with data, and you want to merge the data together into a unified whole for some reason This isn’t just about “big data” or “data warehousing”
10.
by vfaronov 8y ago
This article does not have a valid argument against using JSON-LD. It may be read as an argument against making namespaces a ubiquitous part of JSON, in the same way as they are ubiquitous in XML (even though not part of the base XML spec
11.
by vfaronov 8y ago
RDF was not designed for arbitrary graphs. It was specifically designed for resource descriptions on the Semantic Web. > reliance on the web infrastructure (IRI, DNS, web servers, ...) This is the whole point of RDF. It is what enabl
12.
by vfaronov 8y ago
> async/await are a step ahead to give you the best of both worlds here: You can write your programs as if your requests block Are you thinking of “green”/M:N threading (as found e.g. in Go)? Async/await (as found e.g.
13.
by vfaronov 8y ago
The article isn’t merely arguing that users prefer rich content, other things being equal. It is arguing that users prefer paywalled rich content to free plain content. This is not the kind of thing typically measured by A/B testing.
14.
by vfaronov 9y ago
Not to worry, it’s “just” 5–10% for “well tuned servers using all of [performance-saving] techniques”.
15.
by vfaronov 9y ago
I have a hunch that the era of side-channel attacks is only now dawning, and that we should expect many more painful exploits and cumbersome mitigations in the coming years. What do people more knowledgeable in the field think about this?
16.
by vfaronov 9y ago
> In most cases it is clearer to simply adopt a payload format that includes application specific error codes Absolutely. This is a common practice and there’s even a proposed standard for it (RFC 7807). But such a payload need not be
17.
by vfaronov 9y ago
Here’s the standard for 422: https://tools.ietf.org/html/rfc4918#section-11.2 . It’s not a WebDAV-specific error condition. People are right to see the similarity and reuse the status code. This is not “overloading”.
18.
by vfaronov 9y ago
> WebDAV spec, which is not HTTP HTTP is not a closed protocol. There will never be a single document defining all HTTP methods, status codes and such. Nothing in the definition of status code 422 makes it inapplicable to non-WebDAV ap
19.
by vfaronov 9y ago
Worth remembering that essentially the same issue exists at a lower level: the “%Cpu” number as shown by top includes not just the share of time spent actually executing your instructions, but also the share of time waiting on memory access
20.
by vfaronov 9y ago
> No option to disable automatic updates, or even reduce the check's frequency. Currently, it runs every hour, even though they can go weeks without a release! Why is this a problem? Is the check heavy somehow? An hour between qui
21.
by vfaronov 9y ago
I don’t think they are for “open ended discussion” though? From https://softwareengineering.stackexchange.com/help/dont-ask : > You should only ask practical, answerable questions based on actual problems that you f
22.
by vfaronov 9y ago
Or just seed the PRNG with some digest of the relevant source code (perhaps as simple as the version number). Doesn’t solve the problem that your tests can suddenly break on unrelated changes, but does solve the problem that your tests can
23.
by vfaronov 9y ago
Are you familiar with modern electronic dance music? There’s definitely no “authentic voice of another human being” in regular trance music, for example. It’s hours upon hours of repetitive structural patterns overlaid on similar timbres. N
24.
by vfaronov 9y ago
The actual software seems to be https://github.com/alan-luo/planetprocedural On a related note, I’m quietly amazed why there isn’t yet a working generator of electronic music. I mean something that I can download, run,
25.
by vfaronov 9y ago
https://www.browserling.com/#pricing says “Internet Explorer 9 only”, “Windows Vista only” — must be out of date?
26.
by vfaronov 9y ago
> Required TLS would also increase security. TLS is not inherently required for HTTP/2 on the backend. TLS is sort of required on the frontend mainly because browser vendors don’t want to deal with broken middleware that expects
27.
by vfaronov 9y ago
“Your own web server” here doesn’t mean “your own program that reads from sockets and parses HTTP” — that is taken care of by Go’s standard library. “Your own web server” here means “your own program that serves HTTP requests”, and yes, peo
28.
by vfaronov 9y ago
Looking at Linux’s sendfile [1], it should be possible to use it like that in principle (but not with the standard http.FileServer, I guess). [1] http://man7.org/linux/man-pages/man2/sendfile.2.html
29.
by vfaronov 9y ago
> So what are the servers behind nginx? 9 times out of 10 it is Apache httpd, and numerous instances of it at that. Can you cite a source for this? In my practice, the servers behind nginx are usually platform-specific application serv
30.
by vfaronov 9y ago
Server push sends responses to requests, only these requests are “promised” by the server. So, for every event pushed, the server would have to send at least three frames: promise (the synthesized request), response headers, and response da

More ›