pandeiro

I really love the idea and style of this blog post and the project's README. I recognized the style from somewhere and then realized it was the same author as "Example Driven Development"[1], another one that showed up on HN a while back.

[1]: http://www.wilfred.me.uk/blog/2016/07/30/example-driven-deve...

Knowing where to use `subscribe` (vs pure components) is an art and something that gets easier/clearer as you understand the app better. I'm happy to take responsibility for that aspect of the architecture though; the library's role is to provide the operations and patterns I might want. And if further generalizable patterns evolve, those can be turned into a higher level library.

> there just wasn't a compelling reason to keep it over es6

- hiccup syntax / sexps are trees analogous to the HTML you're constantly generating, and first-class supported data structures supported by the language which need no pre-compilation/transformation step, unlike JSX

- syntax is a good 20-30% less verbose than JS (yes, even ES6), especially when the core lib is taken into account (things like partition, zipmap, threading macros)

- one extremely battle-tested dependency resolution story, not named NPM - it just works

- incredible development tooling innovation, best of class for frontend web development

- the sequence abstraction and dozens of functions that operate on it, rather than Object.assign, Array.map, etc

- best-of-breed dead code elimination via Google Closure Compiler, meaning much of third party libraries and development-specific code ends up weighing less / nothing in production builds

- sets and set operations built in, along with tree walking, diffing and string utility libraries, included with the distribution

- no more defensive copying, thanks to immutability everywhere

What about re-frame is "a mess"? Pretty tiny API surface, solely aimed at forcing the best practices of unidirectional data flow / single source of truth. Have you ever looked at what the same thing entails in JavaScript, ie Redux?

I don't think you can foster a culture of ownership and responsibility where developers are "protected" from decision-making and involvement in other activities. The code isn't written in a vacuum, but as a function of the larger functions of building a business and organization. Furthermore, for essential tasks like evaluating new team members, devs must be involved as they will often be the ones most affected by the eventual decisions.

I'll use a hackneyed sports metaphor b/c my creativity has atrophied over years of nothing but coding: on a basketball team, the shooting guard should definitely be taking a good percentage of jumpers and concentrate on delivering a high percentage of buckets, but they may also be a great passer, a leader in the locker room, mentor for younger players, etc (up to and including weighing in on personnel matters), if they have those capabilities and trust. Probably better than just shooting baskets in a gym their entire career, right?

"Government is the entertainment division of the military industrial complex." - Frank Zappa

Never truer than in 2016.

Load balancers often being a single point of failure in even fairly large org's, this is especially painful.

OP writes really well. Found myself reading the README of his Python web framework (which I'll never use) just because of the clarity, style and pedagogical approach.

Hope there's more on the way.

In what sense?

Thanks, this is exactly what I was hoping to hear. Curious if you dual boot Chrome/Arch or not; I plan to.

I've just purchased one, and to go along with it, I ordered a 128GB SD card and a 64GB USB C pen drive, bringing the total capacity to 256GB. The removable storage obviously won't be as fast, but I believe I can keep my daily work stuff and OS entirely on the SSD, and use the other storage for more extraneous things.

Obviously a 128GB SSD would've been preferable, but I think this strategy will work out.

I'm surprised no one has mentioned the Chromebook Pixel. It seems like a pretty ideal machine for anyone whose primary development OS would be Linux.

Is there really nobody that went for the 16GB RAM version who can speak about the experience?

toxi's thi-ng/geom[1] library deserves a mention in this space.

[1]: https://github.com/thi-ng/geom

I applaud trying to spread the news about these awesome technologies, but personally I think it would be much more helpful to _not_ hide what's going on behind a template generator. The build.boot file itself is easy enough to write[1], and that is really the huge value proposition with Boot vs. Leiningen plugins.

[1]: A simple example: https://github.com/pandeiro/jamal/blob/master/build.boot

It just amazes me that programmers would use anything else.

Aside from the pithy syntax compared to even the most futuristic ECMAScript, meaning frontend code is faster and easier to write (and throw away, if need be), there's another key element Clojure brings to solving this API proliferation problem, which is just how easy it is to do data transformations. The Clojure standard lib makes it trivial (dare I say, fun?) to carve up and reshape whatever data you're consuming to fit the model your application needs.

What's not stated in the article, re: "Why we use Om", is that much of Om's adoption was because of its high-profile creator and all the status/momentum that brings along.

But I think it's approaching a consensus already within the CLJS community that, on API alone, reagent is the React interface you want.

It's extremely elegant and performant; probably the best frontend library I've ever used in close to a decade of web development.

Umm, taking nothing away from his incredible stewardship and everything, but that's not true. I believe Rich Hickey et al did the first implementation. Not to mention that contributors have added hundreds of commits.

Many years later, as he faced the firing squad... http://www.learner.org/courses/worldlit/one-hundred-years-of...

Can a browser REPL-connected Cursive auto-complete based on the browser environment?

What ClojureScript-specific features does Cursive offer?

From the title, I thought there might be something insightful about the importance and difficulty of maintaining concentration when working with the large, complex, abstract and mostly invisible structures that software consists of.

Instead it was just another riff on "we're doing it wrong"...

Putting 'for Mac OS X/iOS' in title would be nice

I'm guessing it would package up Rhino and use that on Android.

Has anyone who's seen the actual code comment?

From what I understood on the video, this is going to be distributed via a repo that is essentially already an iOS or Android template?

There wasn't much talk about the compilation process. Maybe the details (for the open source version) haven't been ironed out?

tldr:

    git clone git://github.com/feature-expressions/clojurescript
    cd clojurescript/feature-macros-demo
    make deps
    make demo

Add some immutable data and sweet.js macros and you've nearly got ClojureScript!

s/solution/workaround

Text reflow was/is a killer feature of the original Android browser (which cyanogenmod still uses, fortunately).

Reading the HN front page is a PITA without it.

Hear, hear. I long for the day that lein and cljs tooling can replace bower/npm/grunt/gulp entirely. And I came to Clojure(Script) from JS, not Java, still have no clue what maven or pom.XML even means, but lein obviates all of that.

The main criticism I'd make, and this is something the boot (http://boot-clj.com) guys have mentioned (http://c2.com/cgi/wiki?CodeGenerationIsaDesignSmell), is that we are getting pretty dependent on code generation with lein templates, and they are getting increasingly larger and more complex just to handle our base scenarios (dev/prod builds, REPL, live reload). Maybe this is unavoidable, or not really an issue... I don't know.

+1

Besides being a prolific coder, he's a great writer with a knack for bridging the academic and the practical.

What's more, the Clojure community has a great number of similarly education-minded and highly talented and effective programmers.