Stylistically, you’re changing the array when you add something to it. Javascript is a janky language in the best of times, but FE devs like to artificially introduce additional unnecessary complexities on top of the jank.
const is simpler. why would I declare an array as let if I’m not reassigning?
Why would you declare a const that’s going to have different data every time to function is called?
Now I’m thinking it’s a form of gatekeeping. Just an excuse for FE devs to throw out terms like “immutable” to make it sound like they know what they’re taking about. Y’all need to constantly sound like you know what you’re talking about when dealing with users, pretending weird stylistic choices have real technical reasons for them. But the BE devs know what you’re saying is complete bullshit LOL.
You are literally just describing the conceptual differences between functional programming and object oriented programming. It has nothing to do with front end vs backend, except for the fact that React has vastly popularized functional paradigms on the frontend.
If you come from a Java / Spring background, that will seem foreign, if you come from an express background it will feel natural.
Functional programming is extremely pleasant though. Its been described as what object oriented would look like if you actually followed all the SOLID principles. You should keep an open mind.
I’m questioning why things are being done in the way they’re being done and you’re saying I’m being close minded? Also spewing out some more jargon like that’s going to impress me?
And LOL at “it will feel natural after you get used to it.” I don’t think you understand the concept about something feeling natural. Like I say I just make stuff const because someone put some bullshit in the linter. Enforcing dumb rules in a linter is the opposite of keeping an open mind, it forcing preferences on people.
I think I’ve confirmed it’s just FE religious dogma. Just keep on repeating whatever Theo says and people will think you know what you’re talking about.
Stylistically, you’re changing the array when you add something to it. Javascript is a janky language in the best of times, but FE devs like to artificially introduce additional unnecessary complexities on top of the jank.
Why would you declare a const that’s going to have different data every time to function is called?
Now I’m thinking it’s a form of gatekeeping. Just an excuse for FE devs to throw out terms like “immutable” to make it sound like they know what they’re taking about. Y’all need to constantly sound like you know what you’re talking about when dealing with users, pretending weird stylistic choices have real technical reasons for them. But the BE devs know what you’re saying is complete bullshit LOL.
You are literally just describing the conceptual differences between functional programming and object oriented programming. It has nothing to do with front end vs backend, except for the fact that React has vastly popularized functional paradigms on the frontend.
If you come from a Java / Spring background, that will seem foreign, if you come from an express background it will feel natural.
Functional programming is extremely pleasant though. Its been described as what object oriented would look like if you actually followed all the SOLID principles. You should keep an open mind.
I’m questioning why things are being done in the way they’re being done and you’re saying I’m being close minded? Also spewing out some more jargon like that’s going to impress me?
And LOL at “it will feel natural after you get used to it.” I don’t think you understand the concept about something feeling natural. Like I say I just make stuff const because someone put some bullshit in the linter. Enforcing dumb rules in a linter is the opposite of keeping an open mind, it forcing preferences on people.
I think I’ve confirmed it’s just FE religious dogma. Just keep on repeating whatever Theo says and people will think you know what you’re talking about.