tunaoftheland

9 ms·

31.
by tunaoftheland 10y ago
Agreed! The author mentioned Smalltalk and it instantly clicked for me. Having a live programming environment sounds awesome, it sounds like it will fit my thinking pattern better. Then, for production deploy, you drop the editor library fr
32.
by tunaoftheland 10y ago
Maybe a Clojure equivalent to NPM's "devDependencies" can manage something like this, so that it gets excluded from the final deployment JAR. It's been a while since I'd done Java/JVM development, but the dev-t
33.
by tunaoftheland 10y ago
Decent-looking, free themes to get started with: http://themes.gohugo.io/ . This probably doesn't make a big difference for you, since you already have sites made with Jekyll. I haven't used Jekyll, but I know of a
34.
by tunaoftheland 10y ago
I've found that settling on a fairly narrow set of tools that will cover most use cases is a good start. "Best tools for the job" is not a good advice in the JS app development... Rather, "Good-enough tools for most situ
35.
by tunaoftheland 10y ago
Agreed! While I do tell myself "right lang for the right job", I've come to the conclusion that I am lazy. :) So if Elm can run on Erlang/OTP like Elixir, that would be an interesting option for the webdev space. I don&#
36.
by tunaoftheland 10y ago
I don't blame you, the linter/editor integration is not quite mature yet, but thankfully getting better. And I don't believe React is necessarily the right JS view library for all situations, though it's often one of man
37.
by tunaoftheland 10y ago
Many have already added excellent comments, and here's mine, as someone who's recently worked on a project with React + Redux + ES6 (Babel5 -> 6) + WebPack, etc.: Start simple and refactor the application as you add the other l