Show HN: Lambda speech
b2b3.free.fr
b2b3.free.fr
No snark here, I just try to understand how do different people read and understand a copy like this.
It is now taken offline due to too many "stupid people", as the last line says, apparently due to them vandalizing it :(
The menu which is shown now is much less helpful indeed.
post tldr - The terrible thing was this was painful to use and early on wikis had almost no structured data. So you have incredible amounts of useful information that mostly cannot be leveraged or processed efficiently because it’s a living nightmare to parse.
Over time things have improved. They added a wysiwyg editor so you don’t have to look at it. They’ve incrementally added ways to allow for documents and data to be more structured and parsable.
Not sure how far along everything is at present.
Similar work:
* James Gosling of Java made something called "Mock Lisp" in the 1980's to support an Emacs editor: Now deleted Wikipedia page: https://en.wikipedia.org/wiki/Mocklisp
* Lisp in Sed: https://github.com/shinh/sedlisp
The implementation is ~20kb gzipped js.
It’s said on the site that html and coding are often too complex of an abstraction for a wiki because so many less technically oriented folks have use for editing them.
This audience I would guess doesn’t want to hear lambda anything, I doubt they could ever fully understand the concepts. Not because they are dumb, but because they have other specialties and by definition are not investing time to learn the theory.
It’s probably been a while for many people here since they first learned about lambda calculus, functional programming, or other concepts. But try to think back to when it first hit your brain. You may have started to do some things quickly but even for many in the field it only really sinks in over time and with some continued investment.
I love how there are some undergrad theorems that someone with a middle school understanding of math can grok and learn to prove and derive the result themselves in a matter of hours. The simplicity can be so beautiful for what someone might have thought was scary.
But that doesn’t apply here. This stuff would be scary to lots of people, it’s made my brain hurt before. Now after however many years I have the luxury of reading the paper, appreciating the elegant aspects, and even enjoying thinking off all the connections to other cool concepts. But even for me is this really the most efficient abstraction?
So I like the design and theoretical aspects, nice work on all of it. I just have trouble seeing any mainstream use cases as described on the site that don’t have better potential solutions.
Some people prefer a feature-laden word processor, some, a complex language like LaTeX, and some, the distraction-free notepad.exe. For each group, for their subject tasks and mental habits, their chosen solution feels best.
I don't see why this approach can't be best for some niche.
And maybe I will have had a few useful feedbacks on this work...
We've experienced many issues on HN about content that was hosted on Free.
EDIT: as expected, website's is down.
No website is still alive, even if the "save" function has been disabled for a while. I was stupid enough to believe in people respecting a defenseless site. Destroying such a site is in no way an exploit. The exploit would be to understand how such a small language could be funny to use in a wiki.
I'm afraid it's hopeless.
- it looks like a mobile design (text way to big on desktop) - needs more room to breathe - the picture takes up the whole screen (while still displaying the h1 below the fold)
It would be good to have a single clear statement describing the aim and purpose (what and why) of lambda speech, followed by a description of how to use it. Otherwise people will give up in confusion