catern

5 ms·

1.
by catern 1y ago
>What would be the syntax for promise pipelining, if you aren't using promises to start with? Oh, great point! That does seem really hard, maybe even intractable. That's definitely a reason to like cooperative concurrency, hu
2.
by catern 1y ago
I totally agree with your framing of the value of async/await, but could you elaborate more on why you think that this behavior (which I would call "cooperative concurrency") is important for (ocap?) RPC systems? It seems to
3.
by catern 1y ago
Rationalists and EAs spend far more time praising the Catholic Church and other religious groups than criticizing them - since they spend essentially no time criticizing them, and do occasionally praise them.
4.
by catern 1y ago
>If you take enough steps back and really think about it, the only synchronization primitive that exists is a futex (and maybe atomics). Everything else is an abstraction of some kind. You're going to be surprised when you learn tha
5.
by catern 2y ago
Emacs 30 has a native graphical port to Android, maybe you can just use that on any Android device.
6.
by catern 3y ago
Well, that's not fundamental. There are plenty of projects that support generating typed bindings for libraries in one language for use by programs in another language. You could do the same thing here.
7.
by catern 3y ago
Is stackfulness required for what the grandparent describes? It seems possible to do this stacklessly: all functions implicitly compile down to a state machine, but futures are never visible.
8.
by catern 3y ago
What do you suggest as an alternative way to express these concepts? Colloquially, "library" and "service" have 95% of the correct connotations.
9.
by catern 3y ago
Ultimately, it can't. Proprietary software has fundamental limitations that force proprietary software developers to choose technically inferior designs. It's why in the long run proprietary software is doomed.
10.
by catern 3y ago
Do you have better suggestions for what words/phrases to use to refer to these two categories?
11.
by catern 3y ago
If you predictably do that then the pilots won't speak truthfully in therapy in the first place. The only way to get the lesser benefit of therapy is to precommit to not report suicidal thoughts. The greater benefit of "pilots hon
12.
by catern 3y ago
I think you may have misunderstood the problem that this article is solving. You've implemented something which kills all your child processes when you exit cleanly, but which leaks child processes if you exit uncleanly. This is, frank
13.
by catern 3y ago
It is unfortunate that there are poorly-managed projects with poorly-managed mailing lists (just like there are poorly-managed projects on Github), but sourcehut at least requires a properly-managed mailing list, and I think you should eval
14.
by catern 3y ago
You don't have to subscribe to send a patch to a mailing list.
15.
by catern 3y ago
That specific workflow precludes reviewing the patch via quoting and making inline comments, which is the normal way to review patches when sending them via email.
16.
by catern 3y ago
When a process does, its children are reparented to init, not to its parent. So the grandparent can do nothing.
17.
by catern 3y ago
It requires a bit of annoying machinery since you have to dedicate a process to being a subreaper. Still it's probably the best option, I made https://github.com/catern/supervise with it, see also https:/&#
18.
by catern 3y ago
An important thing omitted in this post, which makes work-stealing less attractive, is that one core being idle can actually improve performance of other cores. Today's CPUs basically have a fixed energy budget, and if one core is idl
19.
by catern 3y ago
The problem is setuid. Just get rid of that and this becomes irrelevant.
20.
by catern 3y ago
That's actually a git issue - git is notoriously slow on OS X, and magit uses git heavily in a way that is correspondingly slow.
21.
by catern 3y ago
I didn't know 9p had promise pipelining! Or more specifically, it seems to have client-chosen file descriptors, so the client can open a file, then immediately send a read on that file, and if the open fails, the read will also fail (w
22.
by catern 3y ago
I respect the attempt to shift perspective very much, but you only engaged at a surface level with the reasons I listed. >The first is that it's not easy; but `docker run` or `podman run` is easy. I was referring to easy use from a
23.
by catern 4y ago
People worry about Net Neutrality because it was a fantastically successful astroturfing campaign by internet media companies. No similar campaign against FOSTA-SESTA succeeded.
24.
by catern 4y ago
Just as one data point, I have never used straight.el, package.el as it exists in even Emacs 26 is sufficient for me for all my packages. I think this is true for the majority of Emacs users that use packages.
25.
by catern 4y ago
I do this, I host my website on my desktop. It's nice to have just a single computer instead of many. http://catern.com/computers.html
26.
by catern 4y ago
Confounded by health. No mention of this or any confounds in the paper. Which leads me to believe this paper is clickbait "science".
27.
by catern 4y ago
Yes, I came here to say this, these are not command line games. I'm tempted to make some kind of gimmick website or Twitter account, "Not Command Line", which posts examples of this confusion...
28.
by catern 4y ago
Fascinating take! I've never heard this view before, thank you for sharing it!
29.
by catern 4y ago
One can embrace this philosophy for one's personal computing too http://catern.com/computers.html although it's not for everyone
30.
by catern 4y ago
>Bell Lab's Plan 9, for example, did so in part in the late 1980s. Plan 9 did not support forking to remote machines and was not a single system image system. Its support for running a program on a remote machine was a completely us

More ›