Nick Smith

I agree. This font is bolder than all of the other monospace fonts I've used before. IMO, it's not really usable at this level of boldness. When using a dark...

I'm encountering this issue too. In particular, functions that accept a `...` parameter seem to cause line-breaking for some inexplicable reason: ``` let foo = (pattern: Pattern) => () =>...

@Brian-M-J I've looked into the senders and receivers proposal. I see people promising big things ("a global solution to concurrency"), but notably, they don't seem to be able to back...

> I guess talks like [this](https://youtu.be/XaNajUp-sGY) would be good demonstrations at least. That's another toy example. All he's done is create an event loop that spawns asynchronous tasks one-at-a-time. This...

At the risk of stating the obvious, there are a lot of projects out there developed by well-meaning, passionate people, who promise that they have created something important. But most...

Getting rid of function coloring is a worthy goal, no doubt about that. But that is orthogonal to S&R. The reason most PLs have colored functions is because the thread-based...

I've seen that. The idea is that if you can **statically** identify all of the places in your codebase where a variable is being accessed by multiple tasks—and if at...

Actually, I'd only read the second article you linked, but the [first article](https://accu.org/journals/overload/28/158/teodorescu/) is more interesting IMO, because it actually discusses the "program restructuring" problem I'm referring to: > Let’s...

Beyond special-casing the `+` function, I'm not sure that it even makes sense for functions to appear in types. At least, not in a programming language that has untracked side-effects....

> 1+2 is a function call @Mogball Yes, sorry, I amended my post with a bit more discussion about `+` shortly before you replied. I appreciate that it's a function...