|
camoseven posted:Found the guy who's still using Backbone and jQuery Not sure how you made that leap. Right now I use React at work. NextJS for personal projects. My point was it’s better to keep an open mind and be able to see the value in any framework. They all have value. They will all also be replaced at some point.
|
#
?
Jun 9, 2022 00:27
|
|
|
|
| # ? Jun 3, 2024 10:05 |
|
|
Summit posted:Not sure how you made that leap. Right now I use React at work. NextJS for personal projects. My point was it’s better to keep an open mind and be able to see the value in any framework. They all have value. They will all also be replaced at some point. Found the guy who can't recognize jokes
|
|
#
?
Jun 9, 2022 00:32
|
|
|
Sistergodiva posted:Basically useState is you declaring a variable that should rerender the component if it chnages. If that variable came from a parent you wouldn't use. It's for something like a button setting the new value of the variable from inside the component. If it was something passed from the parent you would just have it as an arg in the component. Ah gotcha. The Vue 3 equivalent of that is ref (for a primitive) and reactive for objects. They both give you a wrapped version of the value that Vue will see changes on and update accordingly. The difference is overhead. Since ref is only for primitives, it doesn't do a bunch of deep object checking for changes. Summit posted:I’ve never understood the desire to get fanboi about frameworks. They all suck. They are all great. If you use one it makes perfect sense. If you use the other it would make sense too. In some number of years we’ll all have moved on to something else. It’s the way of things. Weirdly enough, no one is fanboying here. I mentioned I find JSX unreadable and why, someone else mentioned Vue is just as unreadable to them, and after that we've just been comparing poo poo in different frameworks. But no one is arguing that anyone else should change. The Merkinman posted:It's neat seeing the same thing in different frameworks. I'll throw in Angular. Yeah I started on AngularJS, and did some Angular 2 before moving to Vue. Vue to me, grabbed only the good parts from Angular and from React as well. You can even use JSX in Vue if you want to, and typescript is preferred over es6 at this point. They really make it feel like the "grabbed the good parts, trimmed the fat" framework.
|
|
#
?
Jun 9, 2022 01:11
|
|
|
I can summarize frameworks like this: Learn React, literally every company on the planet (except where I work???) uses it and if you don'[t know React then you're just wasting your time and will remain unhirable to any company ever.
|
|
#
?
Jun 9, 2022 20:14
|
|
|
The Merkinman posted:I can summarize frameworks like this: Okay well this guy is fanboying. But no one before that was.
|
|
#
?
Jun 9, 2022 20:28
|
|
|
React... good?
|
|
#
?
Jun 9, 2022 20:33
|
|
|
Protocol7 posted:React... good? The surprise twist NO ONE SAW COMING!
|
|
#
?
Jun 9, 2022 20:53
|
|
|
HaB posted:Okay well this guy is fanboying. But no one before that was. I'm not. Just my experience when I was looking for another job during "the great resignation".
|
|
#
?
Jun 9, 2022 20:56
|
|
|
What fucks my brain up with all the template style frameworks is that it’s javascript (or typescript really) PLUS some weird custom template language thing that’s full of it’s own magic bindings. With React have one thing, and if you hate JSX just don’t use it. That makes thing so much easier to reason about or debug.
|
|
#
?
Jun 9, 2022 22:53
|
|
|
zokie posted:What fucks my brain up with all the template style frameworks is that it’s javascript (or typescript really) PLUS some weird custom template language thing that’s full of it’s own magic bindings. yeah i had some gripes with Vue about this. You can either do 2-way data binding or 1-way, and if you've got more than a handful of devs on your team, you end up with different data binding methods in different components. which isn't wrong, but i just found it annoying. i wish v-model and poo poo wasn't a thing e: although i may be conflating my definitions because i suppose this is also 2-way data binding HTML code:teen phone cutie fucked around with this message at 23:30 on Jun 9, 2022 |
|
#
?
Jun 9, 2022 23:03
|
|
|
The Merkinman posted:I can summarize frameworks like this: Time to learn Vue and/or Svelte
|
|
#
?
Jun 10, 2022 01:39
|
|
|
teen phone cutie posted:e: although i may be conflating my definitions because i suppose this is also 2-way data binding I don't think I'd really call this 2 way binding
|
|
#
?
Jun 10, 2022 05:11
|
|
|
prom candy posted:I don't think I'd really call this 2 way binding ok good i thought i was going crazy because I was googling "2 way data binding in react" and then was reading this blog: https://reactgo.com/two-way-data-binding-react/ and I thought i didn't know what 2 way data binding was.
|
|
#
?
Jun 10, 2022 05:13
|
|
|
teen phone cutie posted:ok good i thought i was going crazy because I was googling "2 way data binding in react" and then was reading this blog: it's possible that I don't know what it is but I always saw it as like basically gluing an input to a variable. React doesn't have that (thank god) but you do still need inputs that show the value of something and also change its value so that's why you see the pattern above so much. But I don't think I would call it 2 way data binding since the getter and setter (for lack of a better term) are still separate and explicit
|
|
#
?
Jun 10, 2022 05:31
|
|
|
react has getters and setters
|
|
#
?
Jun 10, 2022 06:24
|
|
|
teen phone cutie posted:yeah i had some gripes with Vue about this. You can either do 2-way data binding or 1-way, and if you've got more than a handful of devs on your team, you end up with different data binding methods in different components. That doesn’t sound like a Vue problem, but a code review problem. Bad code is framework-agnostic. That’s what code reviews are for. I have heard ppl talk about data binding , and two-way vs one-way. But as I was writing this post I had to google two way binding just to make sure I understood what it was exactly. I found this definition which seems reasonable: quote:One-way data binding means that the variable is just bound to the DOM. On the other hand, two-way means that the variable is also bound from the DOM. When DOM gets changed, the variable also gets changed. Isn’t that just how the frameworks work? I guess I’ve either never understood what the problem is, assuming you are using :value to display something or v-model for something like a form field. At any rate: v-model is just a shortcut anyway. These two things are equivalent in Vue: code:
|
|
#
?
Jun 10, 2022 11:56
|
|
|
barkbell posted:react has getters and setters Yeah but referring to onChange= and value= as setter and getter feels a bit weird. I guess it applies though
|
|
#
?
Jun 10, 2022 14:55
|
|
|
teen phone cutie posted:ok good i thought i was going crazy because I was googling "2 way data binding in react" and then was reading this blog: Whoever wrote that article does not know what 2-way data binding is. Or what indentation is. React does not have 2-way data bindings. AngularJS 1.x had it - it had four different kinds of binding in fact - and it was one of several very bad things about AngularJS 1.x which were rightly discarded for the generation of web frameworks which followed it. 2-way data binding, in the context of AngularJS 1.x, meant that an outer component could pass a particular variable down into an inner component. Whenever the outer component modified that variable's value, the inner component would automatically be passed the new value and re-render or update or something. But also, the inner component could modify the variable too, which would cause the outer component to be notified and then re-render or update. Not through a setter, the inner component would just assign a new value to that member variable. This arrangement - especially with 2-way bindings being passed down through multiple layers of components - made it maddening to track ownership of that variable, or predict what could cause the UI to change or when, or to establish some kind of flow of control in the application. I don't know how this manifests in Vue. Most people who know Vue speak highly of it so I assume it's not so bad there. Doom Mathematic fucked around with this message at 19:13 on Jun 10, 2022 |
|
#
?
Jun 10, 2022 19:08
|
|
|
Doom Mathematic posted:I don't know how this manifests in Vue. Most people who know Vue speak highly of it so I assume it's not so bad there. The problem is that people generally spoke pretty highly of angularJS's two-way data binding as well. Blog articles would say "Hey you're doing this wrong! It's adding a ton of event listeners, it's obnoxious to follow, and honestly just bad!" and then if you looked at anyone's repos it was just wall to wall 2-way data binding. Literally every value passed was 2-way.
|
|
#
?
Jun 11, 2022 03:23
|
|
|
Doom Mathematic posted:Whoever wrote that article does not know what 2-way data binding is. Or what indentation Ah okay. That makes things clearer. I would say then that Vue (at least 3) doesn’t really have that. Or rather it strongly discourages it should you try it. A child updating the parent is generally done via emit. But only the parent can mutate the state. (Or the store, in some cases).
|
|
#
?
Jun 11, 2022 03:58
|
|
about data binding
|
Doom Mathematic posted:Whoever wrote that article does not know what 2-way data binding is. Or what indentation is. You're right, somewhere along the lines the term "two-way binding" was incorrectly re-used by some beginner tutorial writers to describe v-model in Vue (value in input tag changes, so does a local component). As you suspected, Vue does not have the "two-way binding" of AngularJS 1 and thankfully so. In no way can a component's child directly modify the state of its parent. To move data up to parents, it has an event system to "fire" event data to parent listeners, similar to Window.postMessage. When multi-component state gets involved, it's all best managed centrally by Vuex (basically Redux). HaB posted:Ah okay. That makes things clearer. I would say then that Vue (at least 3) doesn’t really have that. Or rather it strongly discourages it should you try it. All versions of Vue did not have this, they learned from the mistakes of their predecessors!
|
|
#
?
Jun 12, 2022 05:27
|
|
|
why do people love to reach for redux at the first sign of component interaction
|
|
#
?
Jun 12, 2022 16:29
|
|
|
I think a lot of webdev is Pavlov reactions, there isn’t a lot of deep thinking going on.
|
|
#
?
Jun 12, 2022 17:15
|
|
|
barkbell posted:why do people love to reach for redux at the first sign of component interaction MrMoo posted:I think a lot of webdev is Pavlov reactions, there isn’t a lot of deep thinking going on. Pretty much this, I'm guessing they haven't been graced with Context and multi-component state interactions yet. Time and a place for Redux but if you've got a few pieces of state that a handful of components all operate on Context is perfectly fine.
|
|
#
?
Jun 12, 2022 17:19
|
|
|
barkbell posted:why do people love to reach for redux at the first sign of component interaction I agree that you probably don’t need redux for state, but if you’re doing a lot of actions within a lot of components, the action-reducer pattern is soooo much more manageable than passing hordes of little callbacks through props. Nowadays you can replicate that with context and hooks, but the redux devtool is a pretty killer feature.
|
|
#
?
Jun 12, 2022 17:21
|
|
|
I don't work with super complex states all that frequently but Zustand has replaced the need for all redux and context-y things for me.
|
|
#
?
Jun 12, 2022 17:47
|
|
|
Any opinions on Recoil? I saw a demo a while back that looked promising.
|
|
#
?
Jun 12, 2022 18:16
|
|
|
Redux is insanely debuggable, more performant than hand-rolled context solutions, and with redux toolkit the boiler plate is mostly eliminated. I don't use it for everything but it's still a very relevant tool.
|
|
#
?
Jun 12, 2022 18:45
|
|
|
gbut posted:Any opinions on Recoil? I saw a demo a while back that looked promising. Yeah actually I've used this in a mid-sized app. I think I was using it in a Next.js app which HMR's a bit differently so I ended up having to suppress a warning because HMR would re-register an atom (though it said it's harmless in dev mode, just annoying to have it clog up the console). Fairly unintrusive API otherwise, almost a drop-in for state hooks. I only used it for the really commonly reused state like user info, one-off DB lookups, etc.
|
|
#
?
Jun 12, 2022 20:03
|
|
|
Zustand is great, I wouldn't go back to redux
|
|
#
?
Jun 12, 2022 20:26
|
|
|
Chas McGill posted:Zustand is great, I wouldn't go back to redux This looks really nice, I'm a big redux head but I'd give this a try. I think one of the other reasons redux has really died down is for years most react apps did their data layer in redux and now there's a billion tools for fetching/caching data that are pretty nice to use (including rtk-query which is built on redux) 5 years ago redux would be the brains of my app, now it plays a much smaller role (if any)
|
|
#
?
Jun 13, 2022 05:49
|
|
|
I wrote angular before react, and when i switched over hooks had already been released. I've just never been on a project where I've wanted to add it, and the projects that already had redux or any flux-like lib were a huge mess with anything and everything stuck in it. From talking to coworkers who like redux, they are usually front-end only devs that use it to wrangle data from poorly written APIs into a form they want to use.
|
|
#
?
Jun 13, 2022 13:30
|
|
|
So good options for app hosting these days? Needs: - my own domain name - ability to run node apps - if I can use sqlite, preferred, if not a suitable postgres/mysql/whatever will work - terminal access would be nice? - hopefully free, or very cheap Suggestions?
|
|
#
?
Jun 15, 2022 15:06
|
|
|
Digital Ocean droplets are a good option and can be very cheap.
|
|
#
?
Jun 15, 2022 15:13
|
|
|
HaB posted:So good options for app hosting these days? We're using Render after the Heroku GitHub authentication fiasco and it's been good so far.
|
|
#
?
Jun 15, 2022 15:19
|
|
|
kedo posted:Digital Ocean droplets are a good option and can be very cheap. 100% suggest DigitalOcean for this and they have very good guides on how to set up most of those services on a production server instance for most OSes they provide IIRC. You don't even need to be a DO customer for their guides but it's one reason why I love them.
|
|
#
?
Jun 15, 2022 15:22
|
|
|
kedo posted:Digital Ocean droplets are a good option and can be very cheap. I've been using DO for (too) many years now, and am looking into https://www.hetzner.com/ as an alternative for both personal and side projects. They are supposed to be similar in terms of the offering.
|
|
#
?
Jun 15, 2022 16:01
|
|
|
Realistically there are a ton of VPS providers out there but not all of them are equal. You could get away with Vultr, Linode, DigitalOcean, Hetzner, some cheap poo poo off LowEndBox probably.
|
|
#
?
Jun 15, 2022 16:07
|
|
|
What's the best SFTP / FTP client for Windows? Mac user for many years going to Windows now
|
|
#
?
Jun 15, 2022 17:07
|
|
|
|
| # ? Jun 3, 2024 10:05 |
|
|
I used filezilla last time I needed one
|
|
#
?
Jun 15, 2022 17:09
|
|
