Interactive programming Flappy Bird in ClojureScript

What Hacker News said

Strong rec nprescott · 2016-07 · on “Fun vs. Computer Science”

I don't disagree with the article, but I also don't know that pushing the boundaries of interactivity and "fun" are relegated to academia. Iterating on what makes things fun is (probably) highly unscientific and might be better left to people more focused on it directly, such as game programmers. As far as interactive development of games goes, I still marvel at Bruce Hauman's demo[1] of "Interactive programming Flappy Bird in ClojureScript". I think the best hope of achieving what the author is suggesting is in the development of something similar, either direct REPL access to the game environment or DSLs embedded in the game engines (which already exist I'm sure). Outside of the big name e

Recommends dustingetz · 2015-04 · on “Myself – v1.0.3”

This is called interactive development; if you liked this, check these out: * Interactive programming Flappy Bird in ClojureScript: [this video] * Live-editing React app without refresh: [LINK] These demos aren't smoke and mirrors, I and many others do interactive development, 8 hours a day, writing regular web apps.

Recommends base698 · 2015-09 · on “Lisp is still a secret weapon”

If you're starting from from scratch it looks really awesome. No callback hell and in believable tooling. Watch these talks to see what I mean about tooling: Few minutes [this video] Longer [LINK]

Recommends freshhawk · 2017-07 · on “Show HN: Mesh IDE – a code editor that feels like a spreadsheet”

I'm not sure if the parent did, but I followed what you were looking for and the answer is still "try clojure", perhaps more specifically it is "Try the Clojure libraries figwheel and devcards to do web stuff" but the push for immediate feedback and "interactive programming" is central for everyone. It's a community that took Bret Victor's Inventing on Principle talk to heart, already agreeing due to the REPL centric workflows that most people used. Bruce Hauman has some good talks about his tools, which are GUI application-centric and a joy to use [1][2][3] If you aren't doing web or native mobile GUI stuff then the default tools have immediate unit test/linting/spec compliance feedback tri

Recommends LandR · 2019-11 · on “Learn ClojureScript: Functional Programming Concepts”

One of the best things about ClojureScript is figwheel and realtime programming. You can see it in action here [this video]

Recommends Nihilartikel · 2020-07 · on “Nubank acquires Cognitect”

From my standpoint as a one man show, it's invaluable to be able to write the web client and backend in the same language, to share code between them... and have that one language NOT be JS. Clojurescript with Rum/Citrus or Reagent/Reframe deliver on the promise of React/Redux with much less fuss and overhead. Editing JSX is a pain in comparison to the Hiccup syntax used more often in CLJS, e.g. [:div {:class shiny} "some stuff" [:button "OK"]] - with the structural editing in any good Clojure editor you can cut, paste, entire blocks of tags, or slurp a tag from outside your div into it, or spit one out, all with a few keystrokes, never stopping to find some closing </div> tag.. I guess some

Cites lambdadmitry · 2017-01 · on “Re-Frame: a Reagent Framework for Writing SPAs, in ClojureScript”

Well, the CLJS->JS side of story is very polished, Figwheel [1] makes things work smoothly (in-browser errors and warnings, sourcemaps, hot reload all work from the box). You can check out [2] if you are interested. There are two areas that still can be improved in my opinion: * the asset story. Right now I use a gulp task that prepares my assets and outputs CSS into a folder known to Figwheel, which makes hotreloading work automagically. However, if you need a complicated interaction between JS, HTML and CSS (i.e. you use CSS Modules), it can be a bit more involved. * the NPM deps story. AFAIK it's gonna be solved in CLJS core soon, but right now your best bet is to pack all NPM deps using

Cites Jach · 2019-01 · on “Porting 30K lines of code from Flow to TypeScript”

Does TypeScript let you build a program interactively as a living thing? Example of what dynamic languages for the browser (ClojureScript) have been doing for 5 years now: [this video] Given that frontend work is so often an endless series of tweaks I don't know how people stand doing anything big for a long duration the classic way of edit -> compile (refresh) -> rebuild runtime state to look at what changed/play around/test -> repeat.