This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-03-29
Channels
- # announcements (9)
- # aws (1)
- # beginners (133)
- # boot (2)
- # calva (94)
- # cider (48)
- # cljdoc (7)
- # cljsrn (22)
- # clojure (128)
- # clojure-europe (22)
- # clojure-finland (7)
- # clojure-greece (6)
- # clojure-losangeles (3)
- # clojure-nl (81)
- # clojure-spec (30)
- # clojure-uk (60)
- # clojure-ukraine (1)
- # clojurescript (45)
- # core-async (26)
- # cursive (18)
- # datomic (12)
- # defnpodcast (1)
- # duct (4)
- # editors (4)
- # emacs (6)
- # fulcro (37)
- # graphql (4)
- # jobs (2)
- # jobs-rus (1)
- # juxt (7)
- # kaocha (2)
- # leiningen (1)
- # nrepl (22)
- # off-topic (2)
- # re-frame (16)
- # reagent (8)
- # reitit (22)
- # ring-swagger (5)
- # shadow-cljs (81)
- # tools-deps (4)
@ag Maybe same as http://increasinglyfunctional.com/2019/03/28/why-clojurescript-react-native-text-input-slow.html
Does anyone have experience using web components in a complex clojure script application? Saw a presentation about Stencil yesterday with witch you can easily make 'pure' web components.
I guess react/re-frame is not really a viable option, https://reactjs.org/docs/web-components.html
react is basically a different solution to the same problem so it doesn't make too much sense to combine them
you are better of either doing everything in react (or any of the CLJS wrappers) or not at all
using 3rd party web components is easy since as far as react is concerned those are only html elements
I'm not really sure if just cljs and webcomponent are a good fit. You could do some routing and state management in cljs I guest, and use interop/closure to put the elements on the page.
web components are sort of OOP and about isolation so that each component has its own world
that absolutely doesn't fit into things like re-frame
as thats a completely separate world
it is not so much about CLJS and webcomponents being a good fit. React isn't a good fit. CLJS would work just fine.
Slow the first time, or just always. I can imagine them being a little slower since they are lazy loaded.
(defprotocol ILocalStorage
(set-item [this id value])
(get-item [this id]))
(extend-protocol ILocalStorage
"? js/localStorage ?"
(set-item [this id value]
(.setItem this id value))
(get-item [this id]
(.getItem this id)))
What shoud I out in "? js/localStorage ?"
?Wait, is React now GCC friendly? https://github.com/facebook/react/pull/15179#discussion_r268935674
> Can we avoid using methods on prototypes and instead call it with an argument - like we do in the newer code? function isPassive(context: DOMEventResponderContext){ ... } Methods are much harder to analyze for GCC and requires a virtual dispatch for every call. With stand alone functions we can feel good about getting automatic inlining and DCE with use of future feature flags and such.
This is on some new code that is being discussed, but I canโt imagine worrying about GCC for new code if old code isnโt also GCC friendly?
Hello guys. I just got started with re-natal. I tried going through the README, but react-native run-ios
fails with:
On ios simulator I see only the home screen, where is the error?
Apple Mach-O Linker Error Group is the root of errors, after I tried to compile in XCode
well, my xcode is up to date, now I am playing around with architectures. To be honest I thought it will be as easy as webdev. Like lein new reagent
๐
this is my last errors, I repaired everything what I could: Undefined symbols for architecture i386: "OBJCCLASS_$_RCTBundleURLProvider", referenced from: objc-class-ref in AppDelegate.o "OBJCCLASS_$_RCTRootView", referenced from: objc-class-ref in AppDelegate.o
okay, I tried the Expo approach, and it works beautifully, anyway, thanks ๐
in theory if everything on npm was standards compliant ES6+ we would have no issue doing :advanced
compilation for all of npm