there's another interesting issue on OSX which I've got a patch for in my homebrew version: on OS X, sleeping in a thread can hang, which causes LSP issues for me (through the `lsp-auto-install` package, since it downloads in a thread). The bug thread is interesting, but seems to have petered out; the patch works for me though!
This is racket's [rhombus], which might be an interesting second link here; it's a scheme, underneath, with the full power of Racket libs available.
[`shrubbery`], the replacement for s-exprs, is pretty interesting, expanding s-expr simply with grouping, and then a separate infix-pass on top. I've been playing with using it as the basis for a separate language; it's in an interesting place in the AST space, especially given the forethought put into macros.
A while back I had made my own alternative to s-exprs that works with Racket. I have no idea if it still works, but I still think it looks nice, and at a glance I feel it's "purer" than shrubbery: http://breuleux.net/blog/liso.html
I really wish they had kept the old C-like Honu syntax rather that the Python-like Shrubbery. If Rhombus is supposed to be an educational language, copy-pasting and trying out new code is going to be a important part of ecosystem, and indentation based syntax is not ideal for that.
I guess. Truth be told I've taught hundreds, bordering on thousands of undergraduate intro courses in python, and students mostly figure it out after they configure tabs and spaces.
There is a long history of identifying the problems and risks of copy-pasting, and trying to reduce it. I remember it was a selling point of Java in the early days. For all the efforts it doesn't seem to be going away. (all the boilerplate in Java probably didn't help)
C-parsing is still built-in [0], so whilst I don't think the standard library has a C-language, it's either really simple, or there'll be a few on the package manager.
The talk goes line by line through this code [1]; I've been transcribing and taking notes on this for the last week, for a somewhat similar project actually.
If you're interested, I've got a huge pile of papers and links collected here [2] that you might enjoy. I've read everything, but right now it's still a big ol' mush; there's a _ton_ of prior art!
I'll add my 2c, and say that even with a really fluid password manager flow, "signin with X" is usually a 1-click entry (possibly 2 for scope authorization), rather than a signup form + leaving the site to click through an email verification.
I'd much prefer 1password to do it's "you last signed in with github here" popup, than just have easy new passwords created.
in this tool (and others I've seen, maybe zulip does this), you can mark threads as "done", and mark messages as canonical.
with slack, it's easy to have a thread with 15 different answers which are all slightly different.
The "knowledge retention" features I'm looking for is being able to mark a thread as "this is the decision made", have that highlighted in metadata and archival, maybe be able to link off to a notion page, and have the thread closed to finalize the decision.
EDIT: the number of times I've had to kick people off a thread because they're adding bad info during a crisis reallllly drives my desire for marking canonical messages lol
Ah, highlighting specific messages would be a neat feature to have in Slack! It aligns with their official acronym: Searchable Log of All Conversation and Knowledge.
the adblock "endgame" will be a self-hosted DNS system that blocks requests to ad-server urls (or return benign responses).
Then the game will switch to encrypted proxied traffic that you cannot block.
Then the adblocking software will switch to the GPU layer, and use machine learning and AI to wipe the region of memory in the GPU containing the ads (and replace it with something benign).
Then the next logical step from likes of google is a fully trusted computing environment - aka, you as an end user no longer control your own machine.
The browser... or the javascript running in it, served from the primary domain you are browsing will just do DNS over HTTP from within the browser, completely avoiding your dns filter
[bug]: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=75275#83 [brew]: https://github.com/d12frosted/homebrew-emacs-plus/compare/ma...