tonyg

32 ms·

391.
by tonyg 8y ago
It's often said that a tail call is a "goto with arguments" [1]. It's also often said that "lambda is the ultimate X," for many different X [2]. Just adding proper tail calls to WebAssembly would do wonders for
392.
by tonyg 8y ago
Symmetric Microsoft Basic Optical Mouse, configured for right-handed use but on the other side of the keyboard. I left-click with my left middle finger, and scroll and right-click with my left index finger. It's great having the mouse
393.
by tonyg 8y ago
I view it as more of a consequence of "fail closed" thinking than a lack of versioning. As we've seen recently with TLS [1], even protocols with explicit versioning suffer from middlebox brittleness. [1] https://ne
394.
by tonyg 8y ago
Query opcodes 3 and 6 through 15 are unassigned [1]. Middlebox brokenness aside [2], a completely new payload could be placed behind a header 0000 7800 0000 0000 0000 0000 Public DNS installations already have to deal with getting un
395.
by tonyg 8y ago
Unfortunately RFC 1459 is just the shallow end. It both includes features that no-one uses anymore, and excludes widely-deployed features that everyone relies on. Lots of the de-facto IRC protocol isn't written down anywhere outside va
396.
An Updated Lead-Crime Roundup for 2018(motherjones.com)
1 points by tonyg 8y ago|0 comments
397.
by tonyg 8y ago
The author of this piece just recently published an update, also in Mother Jones: "An Updated Lead-Crime Roundup for 2018", Kevin Drum, Mother Jones, 1 Feb 2018. https://www.motherjones.com/kevin-drum/2018&#x2
398.
by tonyg 8y ago
Hi Phil, One thing you might find interesting - a small, crude experiment suggests that changing maxBlocking.erl to use process hibernation for those dormant processes could almost double the max number of processes Erlang can support. I
399.
by tonyg 8y ago
Not in general, though of course lots of production language runtimes do involve a certain amount of GC-related jitter. But even where such jitter is introduced, it might not be a very big deal for something like TCP/IP.
400.
by tonyg 8y ago
> GC will always introduce jitter. Hard real-time garbage collectors (including real-time reference counting approaches) can be used in such a way as to eliminate memory-management jitter. Region allocation - a form of GC - can be used i
401.
Mendeley encrypts your data so you can't access it(eighty-twenty.org)
1 points by tonyg 8y ago|0 comments
402.
by tonyg 8y ago
Yes, that's exactly what I mean. It's like saying "we use JSON as our file format", but worse. > "So this program saves its data as 'S-expressions'." > "Oh, cool. Which dialect?" >
403.
by tonyg 8y ago
Even that's not enough to save you in general. JSON deliberately (!) permits duplicate keys . It leaves it up to the implementation to decide how to handle them. And there are two (sensible) ways to add key/value pairs to a map
404.
by tonyg 8y ago
Both ASN.1 and XML are standardized (with extensive, lengthy and detailed specifications!). The term "S-expression" covers a very broad family of vaguely related not-very-interoperable surface syntaxes.
405.
by tonyg 8y ago
Do you want remote code execution? Because that's how you get remote code execution. http://docs.couchdb.org/en/2.1.1/cve/2017-12635.html Map and set values are important for many applications. The fac
406.
by tonyg 8y ago
Rob Pike, in his own words, claims that programmers at google are "not capable of understanding a brilliant language", and that this is the reason why Go is designed the way it is. The full quote: > The key point here is our pr
407.
by tonyg 8y ago
Amazingly, this gives an answer within not too many tens of seconds of full CPU usage. (I interrupted it before it finished searching the full space, though.)
408.
by tonyg 8y ago
Your claim is revisionist and, in my view, nonsense. Scheme is most certainly a Lisp. I mean, you can think what you like, and of course postmodernism is a thing, "the author is dead" and so forth, but if you look at the history,
409.
by tonyg 8y ago
It's fascinating! It looks like there's no C or unix-assembly code in there at all: it could be very close to self-supporting!
410.
by tonyg 9y ago
Previous discussion: https://news.ycombinator.com/item?id=8826060 https://news.ycombinator.com/item?id=11611661
411.
by tonyg 9y ago
Interpreted as a Rivest S-expression, the example given above conforms to the "advanced transport representation" [1], and so can automatically and straightforwardly be converted to the "canonical representation" [2]. In
412.
by tonyg 9y ago
It's experimental, but supports things like the interactive shell I mentioned in this comment: https://news.ycombinator.com/item?id=16879995 Example of a use of the shell library with the special syntax: https:/&
413.
Indentation-Based Racket Syntax with Macros and Infix Operators(github.com)
2 points by tonyg 9y ago|1 comments
414.
by tonyg 9y ago
You might be interested in an experiment of mine, https://github.com/tonyg/racket-something/blob/master/src/so... , which combines an indentation-based reader with a handler for unbound variables to
415.
by tonyg 9y ago
The page on syntax and semantics says "To learn more about the details of memory management, check out Memory.md", linking to https://github.com/carp-lang/Carp/blob/master/docs/Memory.md
416.
by tonyg 9y ago
> Mankind has done perfectly well without a "right to be forgotten" for hundreds of thousands of years. On the other hand, mankind has done perfectly well without computers, an internet, or indeed indoor plumbing for hundreds o
417.
by tonyg 9y ago
I got a lot out of "Essentials of Programming Languages" (2nd edition, at the time) by Friedman, Wand and Haynes. It has a great quote from Hal Abelson in the foreword, too: > Perhaps the whole distinction between program and p
418.
by tonyg 9y ago
Are you saying that the only people who care about POSIX are those saddled with legacy systems that they can't get rid of? That actually sounds about right to me.
419.
by tonyg 9y ago
There's such a strong connection between the idea of "programming language runtime" and "operating system" (resource management, I/O management, task scheduling, package management, upgrade management, lifecycl
420.
Reasoning with Types in Rust(aaronweiss.us)
3 points by tonyg 9y ago|0 comments

More ›