0:01 well that was our tool chain from last
0:08 let me just put this
0:11 i have a three production already just
0:18 four my job is to keep our code running
0:21 while other packages are changing theirs
0:23 should you learn javascript nope is
0:25 there any other option no oh look
0:27 another library was added today to patch
0:30 the problems of the other 150 that were
0:31 also released did you know javascript
0:33 was actually written in seven days such
0:35 a messy language i love it did you know
0:37 javascript was actually not written in
0:39 seven days no one ever knows what value
0:42 variable is or what its type is now we
0:43 use typescript we still don't know i'd
0:46 rather use rust or webassembly they say
0:47 adoption is coming
0:49 they said that 10 years ago they say
0:50 that every year but this year is
0:52 different is it scalable no is it
0:55 maintainable no is it portable
0:57 not really yeah we use react we actually
0:59 use pre-act we actually use svelter we
1:02 actually went back to vanilla javascript
1:04 yeah we're using a library for this that
1:06 we rewrote to vanilla javascript because
1:07 it wasn't efficient we're stuck with
1:09 this messy language now
1:12 i love it javascript yeah it's the de
1:14 facto standard do you know there's a
1:16 library for that i wouldn't trust the
1:18 let's say finance application with
1:20 javascript what our finance application
1:23 does is totally fine to use javascript
1:25 but i'd recommend using typescript not
1:27 that we do we had callback hell
1:30 and then we went to promises await came
1:32 out went back to promises and now we
1:33 rewrote everything back to callbacks
1:36 because it's just more comfortable
1:37 at least you know it's bad oh it's
1:40 probably just a quick fix will take me
1:42 three to five days to find it we tried
1:44 coffeescript rewrote our codebase try
1:46 typescript rewrote our codebase and then
1:48 we went back to vanilla javascript
1:50 because it's just more comfortable so we
1:52 rewrote our codebase again yeah we used
1:55 react and then react 16.8 came out and
1:57 we had to rewrite everything to hooks
1:59 react 17 came out we had to rewrite
2:01 everything again and then react script
2:03 was updated to version 0.4 and we had to
2:05 fix everything
2:08 to work with local images and now react
2:10 version 18 is coming out we'll rewrite
2:12 everything again we rewrote our code
2:15 base around nine times this month yeah
2:17 you can use redux totally fine but but
2:18 if you're on it i'd recommend you use
2:20 redux toolkit but actually it's better
2:23 to use flux or flumax or flexible
2:25 actually better to use recall not that
2:27 we do but now react came out with the
2:29 hooks and context api which apparently
2:31 is better than redux apparently we'll
2:33 rewrite everything again sometimes it
2:35 just doesn't transpire we usually
2:37 rewrite our code base now we actually
2:40 wrote a custom transpirer to transpile
2:42 transpider it's such a messy language we
2:45 use it for our website desktop app
2:47 mobile app for the fridge the tesla is
2:49 not actually native i mean it is
2:52 actually native but it's sort of not
2:53 really native it's sort of hybrid native
2:56 but some of it is native i mean some
2:58 people use it in a native way
3:00 but we don't really use it in a native
3:01 way technically a lot of people are
3:03 switching back to native no one has
3:04 switched yet angular
3:06 talk to me when you use angular 2 or
3:10 react npm is such a bad package manager
3:12 no one uses that anymore npm is such a
3:13 good package manager how many languages
3:15 have one so that major version breaks
3:18 our code but our code breaks the minor
3:19 version i still don't know how to fix
3:22 pure dependencies until this day
3:26 yarn bpnpn turbo would make sense right
3:29 javascript doesn't think so jquery what
3:30 are you five
3:33 we use jj query global variables
3:36 no one uses them it must be somewhere in
3:38 the window how do you debug node apps
3:40 you don't you just write good code but
3:42 not in javascript no one ever masters
3:44 javascript i get a hundred thousand
3:46 points in stack overflow i'm still a
3:48 noob node is technically multi-threaded
3:51 javascript is technically performant our code
3:52 code
3:54 is never safe when they'll blow up
3:55 probably won't work anymore probably
3:58 will be using rust or webassembly or
4:00 whatever j s an array is technically
4:03 just an object object or object null is
4:05 technically not an object but objects
4:09 can be known so they technically can be
4:11 non-object unless they're an object
4:14 right so technically null is an object yes
4:15 yes
4:17 it's a bit hacky i admit
4:19 but javascript is by design is it easy
4:24 have you tried javascript probably will
4:26 be a bit hacky have you used javascript
4:28 before i don't recommend i don't like
4:30 our tool chain documentation
4:32 and another advantage is that it's free
4:34 so was java before it was bought by oracle
4:35 oracle
4:37 so we prepare ourselves by installing
4:39 modules from npm then we compile it to
4:42 typescript then we use a term spyler
4:45 called bubble to transpile it to es5
4:47 load it with system.js file for
4:49 bankruptcy bundle it all up with webpack
4:52 use it in a framework like react and let
4:54 the state be managed by redux or flux
4:57 flummox or flexible or recoil or
5:00 whatever js and voila
5:02 all of this just to avoid using jquery
5:04 or in our case jj query but that'll be
5:06 probably less performant
5:08 as most of the things this isn't our
5:10 production code it will be tomorrow
5:12 though probably gonna get fired again
5:14 i mean there's really no alternative to
5:16 javascript right now de facto no one
5:18 really knows what the value is until we
5:19 get an error
5:21 i love it well try writing anything
5:24 without javascript nowadays javascript i
5:25 love it
