Not sure why this article made it to front page, but fwiw, I used to work as a research engineer in a role where using a confocal microscope in clinical trial settings was a regular part of my job. AMA :D
Meta: I submitted it ~2 months ago because I ran into the topic for work reasons. I found the connection to Minsky reason enough since I didn't know that, and also the technology itself is of course very cool and probably not well known outside the relevant fields.
The post did not get a lot of attention, but a couple of days ago I got what I think is my first offer to re-post from the admins, and since I still found the topic interesting I thought it was worth giving it a second chance.
Meta meta: it seems people are more inclined to question submissions' topicality these days, which I find a bit stressful. Submitting Wikipedia articles about cool/interesting/novel/unknown things (not only technical in nature, for sure) feels to me like a cornerstone of this place (and I've been here a while now).
FFS. I've been fighting uphill this past 5 years to get my colleagues, friends, and family onto Signal. This single decision will tank any hope I have of keeping them there. Literally the only reason I'm able to convince non-privacy advocate types to switch to Signal is because it is a drop-in replacement for their existing SMS application.
This decision is idiotic and will cause a mass migration off the platform. Why not take a better approach and work on a better UX to make it clearer when a message thread is secure or not?
I've been making tabletop game to enter into competitions (there are lots running!) and my significant other has been experimenting with making home-made ice-cream and sorbet :)
This is an intentional design decision in the language - not having lambda functions / functions as first-class citizens makes the code easier to optimize internally.
It also makes me feel like I'm programming in 1987.
LuaJIT does fine with lambdas and I'd bet good money chibi-scheme is faster than GDScript. Its not a really good excuse.
This is a very interesting idea and looks like a promising execution - I may try this with one of my repos. I have a question: it seems the only license options are IP-locked. What if a developer wants to issue non-IP locked licenses to paying users? This is a feature I would consider enabling - is that something you will support in the future?
