131–140 of 189 posts
Every time Javascript is discussed, the discussion turns negative. Fact of life is that the browser is THE cross platform app, and people have differing opinions on how things should be done.
Some takeaways of mine; - Typescript keeps strengthening its position as industry standard. - Svelte is hyped, but is it battle tested enough? - Testing Library is quite new in the town but already the runner up testing tool. - In terms of data management, GraphQL holds its position on the top while good-ol Redux kept losing interest. What are yours?
We've been using Enzyme for a few years at my company. Very recently a new guy introduced testing-library, and oh my god it is so much better.
For one thing, it actually allows to render component on react-native (Enzyme's `mount` doesn't work for some reason) and that's reason enough for me to switch.
Vue is the 3rd in framework ranks... and like the 16th ranked? "Testing Library" is the top testing library apparently? Had to check that this was an actual library, I'm sure many people just left it as a 'whatever' choice. Someones data is dirty dirty dirty
Par for the JavaScript community course.
As someone who is relatively outside of the JavaScript ecosystem, I had the following realization yesterday when I was reviewing this: JavaScript has what I would consider two distinct flavors of "back-end" frameworks. It has frameworks like Express and Koa, which I would consider traditional back-end frameworks. These are designed around handling HTTP requests and providing dynamic responses in myriad forms: rendere…
SSR means that it runs on a server (of course), so it's not too hard to expose basic server functionalities for when you just need a basic endpoint, but you wouldn't want to build a backend on that. It's more akin to dropping a PHP file on a server because you just need a bit of code to run server-side (ie to do some auth with a 3rd party without exposing an API key to the frontend).
Earlier quoted context omitted.
>All the front end devs are like, "You have to wait how many minutes for compile times?" for instance. This is funny because waiting for typescript to build is probably double or even triple waiting for my .NET project to compile at this point. I swear it gets slower every update.
Thankfully on my projects FE and BE are separate builds, so I only do FE builds when needed, I save so much minutes.
Earlier quoted context omitted.
Svelte and React would meet the criteria you described. So would Mithril. Give Svelte a try online, their tutorial page is pretty slick: https://svelte.dev/tutorial/basics
I've gone through those. It looks clean. My biggest worry is the npm package manager and all the crud it brings into the repo.
It seems like the overall trend is that people are getting more and more unsatisfied with the current landscape now that a little bit of the sugar high from first wave of shiny new tech is starting to fade away. The jump from "whatever js was in 2014" -> angularjs junk -> react/vue/angular was pretty big. But now the glamour is gone and we're moving into the phase of actually having to maintain some of the things we…
I can see how that'll turn around to bite me once the code base gets more complicated though
Every year I see these reports come out and every year I'm more jealous of JavaScript/front end developers. I know the landscape is complicated and hard to keep up with, but damn it's just so cool the possibilities you guys have. I am comfortable with c/c++/python/sql/java in an enterprise context. Might some folks help me get back into the JS world? Do I need to sit down with a JavaScript 1.0 book and go from there?
Honestly just play around and try not to let the size of the landscape get to you. Unlike some JS devs seem to believe, you don't need to know everything about everything to get going.
Vue is the 3rd in framework ranks... and like the 16th ranked? "Testing Library" is the top testing library apparently? Had to check that this was an actual library, I'm sure many people just left it as a 'whatever' choice. Someones data is dirty dirty dirty
Personally I'm not surprised that testing-library came out so high in satisfaction; its an incredibly useful layer over Jest and and incredibly popular in React-land.
Earlier quoted context omitted.
>All the front end devs are like, "You have to wait how many minutes for compile times?" for instance. This is funny because waiting for typescript to build is probably double or even triple waiting for my .NET project to compile at this point. I swear it gets slower every update.
Yeh Babel and webpack blow out compile times to epic proportions. Any app that grows to a certain size will slow down to a crawl on incremental builds.
https://raw.githubusercontent.com/evanw/esbuild/master/image...
