chrisoakman
You can play online here: http://t3tr0s.com/
Battle Mode is especially fun with a group :) You can see everyone's board in real-time on this page: http://t3tr0s.com/#/spectate
The build process is defined by the compiler (using Google Closure tooling under the hood) and has not significantly changed since the introduction of ClojureScript in 2011.
Since all CLJS projects use the same compiler, the build process works the same everywhere, regardless of which actual build program is being used (Leiningen, shadow-cljs, etc).
I opened a PR to add it to your list
For most serious usage and projects you will want to use the JVM though.
I maintain an up-to-date fork of Parinfer JS here: https://github.com/oakmac/parinfer
The Rust implementation is also popular and actively maintained: https://github.com/eraserhd/parinfer-rust
The team at Luminare (https://luminaremed.com) has been working with epidemiologists and doctors from Harris County and the City of Houston to build out a screening tool to help prioritize public testing. We are doing about ~10k screenings per day and ready to ramp up as more testing becomes available: https://checkforcorona.com/harris-county
We are providing this tool free for any hospital or public health organization that needs it. Please reach out if you have any connections!
A few years ago some friends and I wrote a tetris clone to celebrate the 30th anniversary of tetris and learn ClojureScript in the process. Really fun group project.
Playable here: http://t3tr0s.com/
The only problem is working on a shared code base where people don't bother to indent code properly.
Parlinter was designed for this purpose. Maybe you could suggest it to your team? https://github.com/shaunlebron/parlinter
I feel your pain here and just wanted to let you know how common this is for programmers who initially try out Lisp for the first time. As others have alluded to, I promise this initial "parenthesis shock" goes away rather quickly as you read and write Lisp code. In my direct experience, I have hired junior developers straight out of a coding bootcamp who were able to pick up ClojureScript in their first week using Sublime Text with no editor extensions. In other words: you can definitely do this; it's not magic.
I would strongly encourage you to check out Parinfer [1]. Parinfer makes indentation "significant" so you never have to worry about "closing the parens". Basically, if you can handle Python or CoffeeScript indentation, you can handle Lisp. There are no hotkeys to learn and it is available in most common editors today.
For a first project I would recommend rewriting something you have already written and are familiar with. That way you can focus on just the language and not worry about the problem domain or "how to solve it". Just do a 1-to-1 port of something you've already done and compare how the two solutions are the same or different.
I'm sorry you are being downvoted and being told to "just use emacs" or "use the REPL more". IMO, these are not helpful suggestions for someone new to the language.
Good luck. You won't regret learning Clojure. One of the best things I have ever done for my career.
If you've found a bug with the port, please report it here: https://github.com/oakmac/parinfer-viml/issues/new
Thanks :)
One of the design goals of Parinfer[1] is to help reduce the cognitive load of Lisp syntax for newcomers. Hopefully more introductory texts adopt it as part of their environment setup.
I'm biased, but I think ClojureScript is the best way to use the JavaScript platform today. Awesome core library, consistent build process, best of breed tooling, persistent data structures, flexible syntax (JSX is madness compared to hiccups); I could go on.
JavaScript the platform may have it's warts, but ClojureScript is all beauty :)
In other words, CLJS users don't have to do anything special to benefit from the power of Google Closure. It just works :)
Parinfer will infer the closing brackets.
You could borrow the idea of indentation inferring function scope structure and make a plugin that would modify JavaScript syntax accordingly, but I'm not sure that would even be desirable when writing JavaScript.
Parinfer is made possible by Lisp's unique syntax.
they have to make the indentation part of the syntax
shifts cognitive load from managing parenthesis to managing indentation
I'm glad it "just works"!
There can potentially be a "big diff" when you run Paren Mode on a file for the first time, but that's typically a one-time event. The beauty of Parinfer is that most Lisp code already uses these conventions.
Once you start using Parinfer's Indent Mode regularly it feels crazy to write or edit lisp without it.
One of my plans for atom-parinfer[0] is to have a comment flag in a file that will automatically signal "use Parinfer on this file". Similar to JSHint inline configurations [1].
[0] https://github.com/oakmac/atom-parinfer [1] http://jshint.com/docs/#inline-configuration
That sentence is an oversimplification to give context to the rest of the content in that section. Should probably have an asterisk to clarify.
Have an early prototype of Parinfer working with the Atom editor here: https://github.com/oakmac/atom-parinfer
It's pretty early software, but feedback appreciated :)
https://github.com/clojure/clojurescript/wiki/Rationale#goog...
I remember writing this example and being mesmerized watching the games progress. I think I made an alternate version that speed up the time and opened a handful of browser tabs to watch the games. Most of them do end up in insufficient piece draws or the 50-move rule.
Glad to see others are enjoying it :)
I do not use statically typed languages and I have nothing against MSFT; I was solely commenting on TypeScript as a language.