freenode/#sicl - IRC Chatlog
Search
3:02:25
beach
YAY! The paper on call-site optimization was accepted. 1 strong accept, 1 accept, 1 reject.
3:04:54
beach
I seem to have established a new terminology item, namely "snippet". I kind of like it myself.
3:07:12
beach
Corrections are to be expected. The less experienced as a technical writer you are, the more corrections will likely be required.
3:09:56
beach
Referee number 1 clearly understood the idea and suggested another paper to read and cite. That's the kind of referee report I like.
3:13:22
beach
It can happen that some referees on some conferences are not that great. Some of them are not qualified to read and understand the papers they referee, and their reports can be infuriating. But the list of members of the program committee for ELS2021 seemed pretty good. No doubt because Marco knows how to choose them.
3:17:13
beach
Even the "reject" is not bad. The main reason for the reject is that the technique has not been tested. That's fair, I guess.
3:22:52
beach
ELS is not a very prestigious forum, and it may not be as tough about the quality of the articles as some of the more prestigious ones, but it's a serious academic conference, so your accepted article counts.
4:22:01
no-defun-allowed
The feedback from the reviewers was very insightful. One thing though: is "abstraction inversion" a well-established term? The term has a Wikipedia page, so I was hoping it would be understood without a definition.
4:24:20
beach
It might not be something that is fresh in memory of every referee. You might as well explain it briefly.
4:49:05
splittist
This discussion of abstraction inversion leads me to wonder whether it has any meaning at all https://wiki.c2.com/?AbstractionInversion
4:51:44
no-defun-allowed
The definition I know is loosely "building a low-level abstraction on top of a high-level abstraction", which can appear if one wants to use features which are not provided by the high-level abstraction.
4:54:49
no-defun-allowed
(For example, phoe's implementation of Common Lisp control flow forms using Java's exception system. And in the paper, I argue that the "room" protocol provided by Matrix [the communication platform] forces too many design decisions, limiting reuse.)