Fork me on GitHub

@chadhs: thanks. I tried it few months ago, but I'd like to setup the "real" emacs, and use it from terminal, the oldschool way. Besides, vim is not really a preference, it is just my default choice since the python times. The evil-mode is not a goal here too.


Ha, I should create the same but with om-next simple_smile


but cool indeed


It seems that two high-level approaches to React Native are (1) embrace the packager and associated web technologies, (2) embrace ClojureScript's compilation model, remoting it


I think we need to pursue both to learn the strengths and weaknesses of each


ClojureScript by itself fixes a lot of problems in UI development, but using it with libs like re-frame and om-next solves majority of the issues with UI. I’m really happy about using it all, especially because I’m replacing already existing functionality with CLJS - so I see the difference immediately


I suppose, (tell me if I’m wrong, because I don’t have a whole lot of experience), that Figwheel is like a analog of the React Native packager… in that it runs a server that can be used to fetch code to be loaded into the target environment.


hm.. kinda the same


but it’s more powerful - you can load whatever you want, skip, reload all the time, so on


Yeah, Figwheel is a packager that understands ClojureScript and its semantics


Just trying to get this straight in my head: So what Will Decker achieved is he figured out a way to make React Native’s packager work with Figwheel (a ClojureScript packager), by shimming some stuff in Chrome. I need to read the code to understand the details, but it appears that this is the architecture involved.


(Well, he made the app go to Figwheel instead of React Native’s packager, I suppose).


10-4 @misha, makes total sense. in that case a good resource is the chapter on emacs setup here:


@chadhs: yeah, that chapter is one of ~5 emacs setup "manuals" I have bookmarked until better times. but that's a topic for #C050AN6QW : ) thanks