This seems like a nice state of the art improvement to native development... When I get around to trying out some native I'll definitely start here. Thanks once again David for your contributions to the ecosystem...amazing!
It’s just a hard sell, I’ve tried a lot and usually I can get approval in very small parts but people are very reluctant to change. And typescript was adopted because people can use “any” types so it gets out of their way, this is very different, and glueing a ts codebase and cljs together is doable but quite a pain in the ass
okay i am a little confused why you would use react native with clojurescript rather than just clojure. since that can run natively on andriod is it because this is a crossplatform app ?
I agree with David, coding is just not interactive enough. But also those percentages make me sad, given that every option below Typescript is superior to Typescript, Clojurescript, Elm, ReasonML, Purescript are all superior to Typescript and still Typescript is the dominant.
Thank you for pointing this out! We've applied an edit to this video to cut out the short period of time where David's audio dropped out. The changes should be processed shortly.
@@goodnight_noom Ha ha, I appreciate your humor, sir. Nevertheless, JS won't be a typed language, go Haskell to realize how far TS from that. JS is more of LISP, and so it is symbolic by design.
@@KotoOo Well, go Lisp to see how far JS is from it. Lisp is strongly typed (just not statically typed) and has great metaprogramming capabilities. =) But anyway, Purescript (or ReScript in a pinch) is the way to go if you want a proper type system for web dev.
@@KotoOo Typed features in JS are halfway finalized. The goal with TS from the very start was to a) give people a decent technology that's best supported by Microsoft's own tooling and b) steadily integrate TS features to the ES spec so that Microsoft doesn't have to keep supporting another set of projects but make a profit nonetheless. JS was indeed originally meant to be a LISP but Java-loving executives pulled some strings and now we have to deal with an abomination of a language with subpar oop and subpar functional features. The oop part is getting special treatment in the new standards and almost catching up with other oop languages. JS was, at absolutely not point in its history, popular or universal because of it's technological merits. Pre-2015 it was head-to-toe a toy language. All worthwhile innovations in that language are rooted in modern times and remain handicapped by the obnoxious backwards compatibility requirements of the web.
About time web app dev is enjoying what hardware engineering has enjoyed with lisp systems like skill for 30 years.
Every sufficiently advanced civilization discovers lisp
This seems like a nice state of the art improvement to native development... When I get around to trying out some native I'll definitely start here. Thanks once again David for your contributions to the ecosystem...amazing!
David Nolen is a boss!
It’s just a hard sell, I’ve tried a lot and usually I can get approval in very small parts but people are very reluctant to change.
And typescript was adopted because people can use “any” types so it gets out of their way, this is very different, and glueing a ts codebase and cljs together is doable but quite a pain in the ass
What's the name of the tool you use to develop React Native from cls? Krell? This looks like an awesome tool.
Had a little hope to see "hello world" with their stack.
okay i am a little confused why you would use react native with clojurescript rather than just clojure. since that can run natively on andriod is it because this is a crossplatform app ?
I don't believe Clojure runs natively on Android - if it does how do you go about it?
@@David-iq1kd Clojure can run natively since it uses the jvm
Good talk!
2. Intrepretation
…although when your slide consists of a single word, it’s a bit embarrassing for it to contain a typo 😄
David built a capability system? I mean, I think that Digital Key app would make Marc Steigler proud.
I agree with David, coding is just not interactive enough. But also those percentages make me sad, given that every option below Typescript is superior to Typescript, Clojurescript, Elm, ReasonML, Purescript are all superior to Typescript and still Typescript is the dominant.
Is the IDE IntelliJ with Cursive?
yep, looks like it
which app was it that is used in demo? Is it possible to take a look at source?
That’s a proprietary app for a car company so I seriously doubt it.
So, in conclusion, 50 years and tooling have hardly progressed. Programming is still a giant pita for the most part.
Going to try Krell soon
Laurence Krauss voice doppelganger
Audio comes back at 5:39
Thank you for pointing this out! We've applied an edit to this video to cut out the short period of time where David's audio dropped out. The changes should be processed shortly.
hhh, last 5min rant is worthy
sry, i should say 'confession'...
the people who made fun of react still make fun of react... that never changed
hmm, I knew an ember dev like this. Then ember copied the approach. Not sure what he's saying now.
that krell doesn't even work how they made it do they have another version other than the one on github?
When do you write automated tests David? Never? 😜
*You've seen your best days long time ago!*
So little information in this drag of a talk
Nolen sounds so much like Jordan Peterson!
Where have you seen the "age" of TypeScript? There was JS, there will be JS. It's just above all that hype and promotion.
How's the connection speed from your cave?
@@goodnight_noom Ha ha, I appreciate your humor, sir. Nevertheless, JS won't be a typed language, go Haskell to realize how far TS from that. JS is more of LISP, and so it is symbolic by design.
@@KotoOo Well, go Lisp to see how far JS is from it. Lisp is strongly typed (just not statically typed) and has great metaprogramming capabilities. =) But anyway, Purescript (or ReScript in a pinch) is the way to go if you want a proper type system for web dev.
@@KotoOo Typed features in JS are halfway finalized. The goal with TS from the very start was to a) give people a decent technology that's best supported by Microsoft's own tooling and b) steadily integrate TS features to the ES spec so that Microsoft doesn't have to keep supporting another set of projects but make a profit nonetheless. JS was indeed originally meant to be a LISP but Java-loving executives pulled some strings and now we have to deal with an abomination of a language with subpar oop and subpar functional features. The oop part is getting special treatment in the new standards and almost catching up with other oop languages. JS was, at absolutely not point in its history, popular or universal because of it's technological merits. Pre-2015 it was head-to-toe a toy language. All worthwhile innovations in that language are rooted in modern times and remain handicapped by the obnoxious backwards compatibility requirements of the web.
"simply can't be done", "state is not destroyed" ... bullSHIIIIT
Could you elaborate?