ok, could someone give me a short list of improvements in figwheel-main compared to the old one?

can't find such a list from figwheel or figwheel-main repos etc

with the exception of course that it is a complete rewrite

it emulates the interface of cljs.main and goes a bit further

it’s also clear it’s much easier to use as a library and the various parts are separated (REPL vs. building)

roger, so currently it's more about more sensible architecture than about features, correct?

need to look at it at some point, right now old figwheel works really well for me via user.clj inside normal Clojure REPL

was just curious when I heard there's this new version (had missed that). Naturally my next project should start with figwheel-main if I can integrate my flow with that

replicating cljs.main is actually a lot of work 🙂

so I would consider that a big feature

not saying it isn't

but no, once you’re up and running doesn’t seem that different

yeah, that's my main point. Currently all I need to do is type (user/start) to start my backend server, figwheel autobuild and watcher, garden watcher etc. If I want to jump from Clojure REPL to ClojureScript REPL I type (user/cljs-repl) and when I want back I type :cljs/quit

works really nice with Cursive, you can load namespaces between REPLs, Cursive recognizes automatically in which one you are currently and so forth

so I was wondering how figwheel-main could improve on that and right now it seems like it doesn't. But I can still totally see why it is necessary to do. So, my next project will be with figwheel-main but I'm not migrating old projects to it

not unless a compelling reason surfaces itself

@niklas.collin http://rigsomelight.com/figwheel-main/docs/#figwheel-main-vs-lein-figwheel

nice! Cheers

was that on figwheel-main repo readme?

missed that link if it was

no its in documentation that is currently under development

roger 👍

I should probably link to it nontheless

just wanted to say btw that figwheel transformed my frontend development, I laugh at the node and webpack people these days

@bhauman nice website! I missed that

There is a fighweel.main/start method it's mentioned briefly in the README

@dnolen thanks no link yet

oh ha

I'm still churning through documentation

k I was about to advertise but I’ll let you do that

btw, figwheel.main went great during the workshop

the attendees loved it

well that's good!

you never know whats going to happen in a situation like that.

seriously

great!

no problems at all

fantastic

> Figwheel Main also starts a Node process for you when you launch a build. Does that mean Figwheel main needs node?

nope

good

🙂

it's just better when you use node

I was also messing around with Figwheel + Datomic Ions the other day

performance improvements and the fact that you can choose the client where REPL evaluates are great

I’d call that a killer app combo

just copy assets to S3, and stop worrying about managing a server

although I think most of the performance issues I've had come from the cljs compile times (wink wink @dnolen )

@niklas.collin heh yeah, I renewed my OSS YourKit license the other day

(it's gotten way better over the years)

actually compile times have gotten worse

consistently

start up time has gotten better

right

well, overall performance is what matters

yes

but I'm happy to hear you are working on performance improvements

I haven't looked at this https://clojureverse.org/t/datomic-cloud-ions-aws-appsync-graphql-service-example-repo/2481

but the concept is pretty fantastic

yes it is

didn't know about app-sync

me neither

amazon produces services faster than the JS community produces build tools

ha

@dnolen did you have a CLJS repl running up on ions?

nope

ah k