@warmbowski
One thing to realize about lodash is, if I remember correctly (don't really use anymore), it does a great job of picking the most performant algo for the size of the data. So I might use something like lodash if the collection sizes were big.
@JLarky
Astro and SvelteKit are crushing it
@grimm_gen
My fave state management library is Jotai and GOD IT IS UNDERRATED
@Rcls01
I don't even think too many people use AWS Amplify. We deploy frontend apps either to S3 as a SPA or run containers. Also, on the micro-frontends issue.. Microservices are a solution to organizational scalability and micro-frontends would mean you have so many teams working on a single system that the front-end has to be split between those teams into smaller services. I can see it work for companies such as Amazon who have a massive website, or AWS, who have hundreds of services in that platform, but most orgs never need it. We had about 4 teams working on a single front-end, but we simply modularized the app and that helped us not step on each other's toes. It has created a problem where nobody wants to take ownership or responsibility and many teams just shy away from it, so big decisions take a long time.
@DojoDyo
As a junior this video really helped me out in terms of direction
@kyrregjerstad
6:04 I remember taking my first sveltekit course from levelup on a 7 hour train ride, just as i was getting into web dev!
@SchalkNeethling
I reckon this is one of the more representative of the industry so, thank you for talking through all of this.
@yuriidrahomaretskyi561
Yes, please do an episode about CSS. I always use scss and can't imagine how to replace it with pure CSS
@binajmen
Why was Solid not represented? đ˘
@gregorykennedy-mindfuldude
Great content! Thank you!
@tom.watkins
Get Zack Jackson on if you want to talk about micro frontends. Guy invented module federation and is on the rspack core
@bopatzable
why is Solid not on the list?
@mickmister
24:00 AFAIK npm workspaces donât support the âworkspace:*â nor âworkspace:(version)â syntaxes. You must instead provide the version number, and it will try and resolve it locally before checking npm. This is just from my experience. I imagine there are other options to declare the package version for npm workspaces.
@rand0mtv660
13:50 barebones fetch API is horrible and you need a wrapper around it to have any kind of decent experience. Unless you are using it for like 5 requests in some small app so it doesn't really matter in that case. axios is great because it's battle tested, has request/response interceptors, has the ability to create instances where you can set defaults as Wes mentioned, has customizable error handling, has many other customizations etc. It also has support for file upload progress event (which fetch does not support) because it can use XHR under the hood, so you can display percentage number for the upload progress in browser. Also earlier this year it got an official "fetch adapter" which means you can use axios, but it will use fetch under the hood. So with fetch adapter you can get all benefits of the speed and support of fetch, but still use everything axios offers you on top of that with better DX compared to just using fetch.
@Richardritchie-w1f
Please at least once say Richard we glad you come home safe after work. I never miss your single video. Much much love
@timmyers9798
I just use lodash consistently on a big project and try not to mix in native js stuff..bonkers but it works!
@christophersuarez1356
Did you remove your video "why do people still use axios over fetch"? I can't find it. I see some benefits of using Axios and would like to know if fetch has an alternative.
@delektowski
Maybe I could have a small hint in order to make the survey results more informative. Wouldn't it be more useful if there were a separation of "used and liked" into: "used and liked at work" and "used and liked in my side projects"? The reason is that as a developer (eager to learn ;-) ), you need to constantly learn, try new things, and work on side projects. In the meantime, the typical developer has to work on projects within the company where they are often required to use specific technologies. I can easily imagine a developer who works in a company using Angular, but at the same time, they are trying React on their side project. Having that proposed split would provide information on which technologies the industry tends to use and which technologies developers would like to use. I can imagine that the conflict which could arise here may not be easily resolvable... BTW: I love the podcast, and it has fed me as a newborn developer a few years ago :-)
@MonoMario89
I run remix + Cloudflare pages. I push to prod by building the production files via remix build and then just deploy with wrangler. It's just a folder of assets
@TheAlexLichter