Live data from Hacker News

It's Playtime - Light Table Playground released

chris-granger.com

101–110 of 132 posts

Re: It's Playtime - Light Table Playground released

#101
post #99
post #66

Java being required means this is a complete non-starter for me.

How would you like them to run clojure, a JVM based language?

There is an official, up-to-date ("within a week or so of milestones on Clojure main") .NET port at https://github.com/clojure/clojure-clr

Maybe once Light Table is somewhat stable, someone can hack it to use ClojureCLR for the benefit of the security-conscious Windows users :)

I really should get involved in open source projects.

Re: It's Playtime - Light Table Playground released

#102

Hi, I'm a beginner programmer, I've played around with learning Lisp various time & just started the 4clojure problems. I was having issues getting a nice workflow going & getting diverted with IDE issues etc. This is wonderful. Thanks.

I recommend trying Clooj, it's a simple editor and REPL that requires virtually no setup or configuration, and it provides enough functionality to be useful when working on the 4clojure projects.

https://github.com/arthuredelstein/clooj/

Re: It's Playtime - Light Table Playground released

#103
post #86

Earlier quoted context omitted.

Seems like you can use any browser you'd like by going to: http://localhost:8833/ once the server is up and running.

Thank you, that's cool! How can I kill the server, though?

  light server stop
if you look through the script file, it has a series of options.

  light table
  light server start | stop | restart
  light update [version]
but as far as I can tell it always checks for updates first and will install them before it checks any of the arguments passed.

Re: It's Playtime - Light Table Playground released

#104
post #99

Earlier quoted context omitted.

How would you like them to run clojure, a JVM based language?

There is an official, up-to-date ("within a week or so of milestones on Clojure main") .NET port at https://github.com/clojure/clojure-clr Maybe once Light Table is somewhat stable, someone can hack it to use ClojureCLR for the benefit of the security-conscious Windows users :) I really should get involved in open source projects.

I think the issue will be compiling it for the CLR and then distributing it. The current script gets and runs a JAR, but I 'd imagine it would be relatively trivial to modify the script to run the CLR instead - but you'd have to build from the source included in the JAR (if it's all there...)

Haven't had much experience with it myself, it has been a while since I've played with Clojure.

Re: It's Playtime - Light Table Playground released

#106
post #36

Who thought "It's Playtime" was a better title for this than "Light Table Playground released"? Why does this keep happening to Light Table posts? Edit: Now "It's playtime - Light Table Playground released", after ibdknox altered the blog title. So... success? I still think it's ridiculous, though.

The new title is definitely better, imho. I hate titles that keep me guessing about what the article is actually about.

"It's Playtime" has zero informative value. At least with the edit I now know it's about Light Table, and can click or skip as necessary and not waste any cycles guessing, or clicking and finding it's something I'm not interested in.

Uninformative titles are a plague. Concrete titles (and concrete language in general, but that's a whole nother blog post) are always better than vague ones, no matter how catchy, cutesy, or kitschy you may think it is.

Re: It's Playtime - Light Table Playground released

#107
post #39
post #36

Who thought "It's Playtime" was a better title for this than "Light Table Playground released"? Why does this keep happening to Light Table posts? Edit: Now "It's playtime - Light Table Playground released", after ibdknox altered the blog title. So... success? I still think it's ridiculous, though.

I don't know, but it's starting to make me sad. It doesn't seem to fall under the "editorial spin" guidelines - if anything it was clarification. Hopefully the mystery will bring more people in? haha ;)

>Hopefully the mystery will bring more people in? haha ;)

I know that's why people use mysterious titles, but trust me - that's done, it's over, it's the old and busted of social news.

It's one of those things that may have worked when social news was new and interesting and still a novelty, and people would click all sorts of stuff wily-nily just to see what neat treasure lies underneath.

But we're all over that, and now what we're dealing with is information overload - how to manage the signal:noise ratio in the information we consume and maximize the signal.

The expectation of informative titles is a key part of that, so all mysterious titles do now now is piss people off for making them click to see what the article was about, instead of just telling them in the submission title, which is what it's for.

You as a submitter (or advertiser, I've seen studies on this for SEM) are much better served writing a concrete, informative title. You may have less clickthroughs (but sometimes more - specifics are very effective), but every single one of them will be someone interested in whatever you linked to (or are selling, in the latter case), more likely to read, buy, participate, etc., and less likely to close the window annoyed at having been tricked into wasting a few seconds and attention on something they don't care about.

Re: It's Playtime - Light Table Playground released

#109
post #22

Is there any interesting piece of code that might help me see this working to its true potential? I tried the factorial function expecting it to show all the recursive calls. What can I expect to see here? Call trace over multiple functions? EDIT: Just tried this , atleast this shows the last calls made to the functions (defn my-add [a b] (+ a b)) (defn fact[x] (if ( (my-add (fact (my-add 3 3)) (fact (my-add 2 5))) -…

A little example I've come up with is writing a bunch of tests for a function you are implementing and seeing them automatically executed.

Try to fix fib by changing a, b and i values:

  (defn fib [n]
    (loop [a 1, b 1, i 1]
      (if (= i n)
        a
        (recur b (+ a b) (inc i)))))

  (= (fib 0) 0)
  (= (fib 1) 1)
  (= (fib 2) 1)
  (= (fib 3) 2)
  (= (fib 4) 3)
  (= (fib 10) 55)
Post reply on HN