eudox

23 ms·

181.
by eudox 12y ago
I'd love a write up of your setup, and I think other people here would as well. Did you build this all from what you thought you'd rather use, or have you tried Lisp machines like Genera?
182.
by eudox 12y ago
> it falls extremely short for lack of community and open-source libraries/frameworks. This is one area I'm hoping to improve. I've already built the ORM, auth system and template engine. Now I'm doing the web framewo
183.
by eudox 12y ago
And I love the CSS thing that mimics the Symbolics interface (Putting a border around links on hover). But people want "CSS they can trust", as I like to put it. Startuppy Silicon Valley CSS. It may be just marketing, but marketin
184.
by eudox 12y ago
>I'd really like to figure out how to build more of a Common Lisp community. I think the low-hanging fruit is web design. Just touching up the CSS of library documentation would be very useful. Presentation is a lot more important t
185.
by eudox 12y ago
I love Common Lisp[0], that's why I'm trying to improve it. [0] https://github.com/eudoxia0
186.
by eudox 12y ago
>I think you have to find that out yourself. This won't really do anything to bring people closer to Common Lisp. This is a bad thing btw.
187.
by eudox 12y ago
That's an old article that only discusses intrinsic language features, and doesn't even try to sell people on Common Lisp's ecosystem. I imagine most people who explicitly choose Clojure over Common Lisp do so because of conc
188.
by eudox 12y ago
Common Lisp has all those tools, what it does lack is a well-designed website that says "Here's how you start". The closest thing to that is probably the common-lisp.net website, and that's just an unfinished barebones B
189.
by eudox 12y ago
>The issue is that the Common Lisp Community is not just sending signals that most of the potential market ignores, it's that it is sending signals that turn the potential market off. Absolutely agree. The Lisp community could attra
190.
by eudox 12y ago
Or a magnetic sail to slow down. For that you might need a longer runway than Sol-Alpha Centauri though.
191.
by eudox 12y ago
Missing: Project Valkyrie https://en.wikipedia.org/wiki/Project_Valkyrie http://www.projectrho.com/public_html/rocket/slowerlight.php
192.
by eudox 12y ago
>(decades? centuries? millennia? forever?) All equivalent. >expecting a spontaneous reboot Nobody actually expects this. You can't just thaw someone and reperfuse them. Extensive repair work has to be done at the nanoscale. In an
193.
by eudox 12y ago
Thankfully the fact that people have come back just fine from minutes of total EEG silence (Often involving hypothermia) shows that the immediate state of the brain does not matter nearly as much as its structure.
194.
by eudox 12y ago
IIRC, that was in 1983, when three TransTime patients were transferred to Alcor thanks to donations. There's a very interesting article written about it: http://www.alcor.org/Library/html/postmortemexamination
195.
by eudox 12y ago
>Early applications of cryonics didn't take the tissue destruction of freezing into account. What other problems are being completely missed in the process? Literally everyone knows about ice formation. Robert Ettinger wrote about i
196.
by eudox 12y ago
Liquid Nitrogen is one of the cheapest fluids on the planet. Dewars are refilled every week. If the supply of LN was cut, the LN on each dewar would take months to evaporate -- And the patients are stored upside-down, so the head is the las
197.
by eudox 12y ago
Since you specifically mentioned kidneys: >In the summer of 2005, where he was a keynote speaker at the annual Society for Cryobiology meeting, Fahy announced that Twenty-First Century Medicine had successfully cryopreserved a rabbit kid
198.
by eudox 12y ago
Electron micrography of cryopreserved tissue shows pretty good preservation[0][1], and since every aspect of the mind is dependent on physical properties of the brain, the possibility of revival exists as long as structure and context are p
199.
by eudox 12y ago
People have come back from minutes of electrocerebral silence with intact memories and personalities.
200.
by eudox 12y ago
By the time we have the technology to revive cryopatients, that question will likely be "why not?".
201.
by eudox 12y ago
Active shutdown is certainly preferable, but to the best of my knowledge is only legal in Switzerland.
202.
Getting Started in *Lisp (1991) [pdf](people.csail.mit.edu)
75 points by eudox 12y ago|19 comments
203.
by eudox 12y ago
They may not little about their users now , but this valuation could well be based on the (reasonable) expectation that they will know more in the future.
204.
by eudox 12y ago
> It's a language designed by committee, and it looks like it. This means nothing. When a design succeeds, we say it was designed by the community; when it fails, by committee. You can produce examples for any language: In Common Li
205.
by eudox 12y ago
Well, you can add ADT's to C/C++ with a macro system: https://github.com/eudoxia0/cmacro/blob/master/t/good-macros...
206.
by eudox 12y ago
The article hits rather close to home, as someone who, for better or worse, is committed to improving Common Lisp's ecosystem. I often feel this existential dread of "Is it worth it? Whose lives will it change? Will I spend years
207.
by eudox 12y ago
I do acknowledge (Or try to) that Common Lisp has plenty of problems. But aside from some design flaws, I think the majority of these problems are social, which in a way is a good thing: Fundamental characteristics of a language cannot be c
208.
by eudox 12y ago
The reason I have stuck with Common Lisp, rather than bailed to Clojure or something else, is that the language is so fundamentally good -- Mature, robust, standarized, performant, compiled, gradually-typed -- that it is worth sticking with
209.
by eudox 12y ago
Framework: Caveman2[0] or Ningle[1], which run on Clack[2] (like Rack/WSGI), which supports five backend servers. Templates: Djula[3], closure-template[4]. ORM: Crane[5], Postmodern[6]. [0] https://github.com/fukamachi&
210.
by eudox 12y ago
Yes, Common Lisp. Gradually-typed, fast, compiled, standarized, stable, and with multiple mature implementations.

More ›