swannodette

7 ms·

31.
by swannodette 5y ago
No App Store issues as far as I know.
32.
by swannodette 5y ago
To be fair there were definitely still bugs in Om as well as om.next (and both were marked as being experimental and of alpha quality) - however Fulcro came along and more less took the ideas and took them further and far as I know is activ
33.
by swannodette 5y ago
Some technical points about Krell. It leverages the ClojureScript `:bundle` target which was released last year https://clojurescript.org/news/2020-04-24-bundle-target . By simply producing output that is JS bundler fri
34.
by swannodette 5y ago
Mostly a maintenance release, but the and/or compiler pass thing is somewhat neat. First, it might seem that such an optimization would not be that useful, but actually it's one of the most critical ones - we want to write the per
35.
Developing mobile digital key applications with ClojureScript(vouch.io)
101 points by swannodette 5y ago|12 comments
36.
by swannodette 6y ago
Honestly not sure, I'm not a Webpack expert and have no wish to be :) But again, as I've said elsewhere, there is no specific integration with Webpack. The bundle feature makes no choices so it's easier for users to fully con
37.
by swannodette 6y ago
We have no specific integration with Webpack, so you can consider anything since we haven't chosen for you :)
38.
by swannodette 6y ago
Yep. But having this feature only in shadow-cljs doesn't do much for the ecosystem as a whole since non-portable. With this change, many tools, cljsbuild, Figwheel, etc. have the same capabilities. It also opens the door for creating C
39.
by swannodette 6y ago
1. NPM is analogous to Maven for Java. Yes the ClojureScript bundler target lets you use anything you've installed from NPM into your project's `node_modules` directory. Not many limitations because we wash our hands of dealing wi
40.
At Dynamicland, the Building Is the Computer(tashian.com)
132 points by swannodette 7y ago|31 comments
41.
Deploy ClojureScript to GitHub Pages(betweentwoparens.com)
3 points by swannodette 7y ago|0 comments
42.
Tech Workers vs. The Pentagon(jacobinmag.com)
3 points by swannodette 8y ago|0 comments
43.
Suggestive Drawing Among Humans and AIs(nono.ma)
124 points by swannodette 8y ago|25 comments
44.
by swannodette 8y ago
We don't really compete with PureScript, BuckleScript, ReasonML or even Elm and this is heavily reflected in our surveys. The only real competition at this point is Scala/Scala.js or full stack JavaScript.
45.
by swannodette 8y ago
New users (and experts as well) do not find Leinginen and templates easy to use. The response to the Quick Start has been overwhelmingly positive from new and experienced users.
46.
by swannodette 8y ago
Lead developer of ClojureScript here. Agreed, we take Windows support quite seriously.
47.
by swannodette 9y ago
The whole point of passing everything through Closure is to avoid needing externs. However there are caveats, see me comment above about building React.js directly from sources.
48.
by swannodette 9y ago
Using NPM for client libraries required using Webpack to bundle those things. If you were targeting Node.js then we just didn't support idiomatic usage of those libraries (users could just call require themselves directly).
49.
by swannodette 9y ago
Nothing has changed about ClojureScript interop in 6 years so I don't really know what you're getting at. We believe ClojureScript interop is pretty good and our users pretty consistently agree.
50.
by swannodette 9y ago
I fail to see how Closure Complier is any more complicated, more painful, and has any more caveats than Babel/Webpack. With Closure Compiler at 8 years old and building some of the most sophisticated JS properties on the web (GDocs any
51.
by swannodette 9y ago
I would say you are in a distinct minority here with that viewpoint :) I've been using / working on ClojureScript since the very beginning and the halfway integration with Node and NPM never seemed particularly desirable to me.
52.
by swannodette 9y ago
There's no extern inference required here as all the original sources are passed directly through Google Closure Compiler. As a benchmark for feasibility when we started we chose React.js as it's non-trivial and heavily depended u
53.
by swannodette 9y ago
This feature is really, really a long time coming. Myself and other ClojureScript core contributors are happy to answer any questions people may have.
54.
ClojureScript Is Not An Island: Integrating Node Modules(clojurescript.org)
193 points by swannodette 9y ago|42 comments
55.
by swannodette 9y ago
That's exactly what I'm saying. You don't choose ClojureScript or Scala.js haphazardly, you're already using Clojure or Scala. Thus it doesn't make sense to lump them into choices that are primarily client-centric
56.
by swannodette 9y ago
I use Datomic everyday. While it's certainly a stunning piece of technology and you could pry it from my cold dead hands, I don't think it has that much bearing on the growth of the Clojure community.
57.
by swannodette 9y ago
I don't know but it seems to me Ruby is dying the same way anything else with 200,000+ questions on Stack Overflow is dying (i.e. it isn't).
58.
by swannodette 9y ago
I don't really have anything to say about your other points, but the only comparable compile-to-JS tech in your list to ClojureScript is Scala.js. The other options assume you don't see significant value in using the same programm
59.
by swannodette 10y ago
Glad it's working out!
60.
by swannodette 10y ago
Happy to answer any questions people might have about this release.

More ›