Not to mention his argumentation can be used to make a case to stop using JavaScript all together... Or stop being a web developer. If you dont web develop, you can't do it badly...
Web Dev full-stack [LAMP] since 2005, but much heavier on the JS stuff these days.
Jack of all Stacks, Master of some.
Always looking to learn new things. Always glad to help out, just ask.
Location
Atlanta, GA
Education
B.S. in Biochemistry 2004, M.S. in Computer Information Systems 2007
Web Dev full-stack [LAMP] since 2005, but much heavier on the JS stuff these days.
Jack of all Stacks, Master of some.
Always looking to learn new things. Always glad to help out, just ask.
Location
Atlanta, GA
Education
B.S. in Biochemistry 2004, M.S. in Computer Information Systems 2007
Contrast to my previous comment, I understand the point a little more (I think). This is a "decent" elaboration.
And sure, what you're saying is true. Just because I can use match instead of if let doesn't mean it would look good in the context. I think you could have made the point more general and left the message at that, instead of targeting one specific ES6 feature, considering there a quite a few features that can be abused.
As my previous message states, I believe I understand your intentions, but your delivery of it was botched horribly (IMO).
As I suggested, maybe rework it, or put more emphasis on the developer than the feature, but explaining in the way you did before I understood was not doing your view any justice.
Since this is not a terribly huge issue I don't think it would take much effort to fix.
(On an unrelated note, let me turn on my MoistCritical impression, because damn. - When you said "That is not my point and you know it." that comes off as kind of an asshat thing to say, especially when you add "but you do you". It just strikes me as "Hey. I'm overly confident people can understand me right away!". Because no, I did not understand you. @brense didn't seem to understand you either since they were on board with what I originally said. - I dunno, maybe sounding blunt wasn't your intention but I just thought I should point it out because others might get the wrong idea.)
Web Dev full-stack [LAMP] since 2005, but much heavier on the JS stuff these days.
Jack of all Stacks, Master of some.
Always looking to learn new things. Always glad to help out, just ask.
Location
Atlanta, GA
Education
B.S. in Biochemistry 2004, M.S. in Computer Information Systems 2007
Your other replies are clear, i see that you see what i meant and i get where you are coming from. In addition i merely picked on that specific feature because it was the feature the OP wrote about. There are other things in ES6 I do and do not like. I don't really control what gets added but my sentiment is that the JS community is adding too many bells and whistles to a language that works well without them and that there are other areas that could be addressed that are far more important. My biggest beef with the language is the number of things that do exactly the same thing. One example running code in the order you want it to: javascript.plainenglish.io/callbac...
I don't intend to offend people, but sometimes i'm too tired to think of the best way to say things and i just drop in the info as best i can at that moment. [probably why so much of the internet is full of horrible comments]
My biggest beef with the language is the number of things that do exactly the same thing. One example running code in the order you want it to
This is something I also find distasteful, but I feel like this, relatively, is one of the better things.
I think the JavaScript community forgets it has learners that are working in .html files, so it would be cool if they focused on that side of the community, such as allowing modules in the the browser.
[probably why so much of the internet is full of horrible comments]
💀
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Not to mention his argumentation can be used to make a case to stop using JavaScript all together... Or stop being a web developer. If you dont web develop, you can't do it badly...
That is not my point and you know it.
That's not my point. It's more a case of "Just because you CAN doesn't mean you MUST" but you do you, it's not like i'm gonna convince you otherwise.
It is. It shares the exact same logic.
If you don't use pointers you can't use them badly and run into segfaults.
How is my rhetorical question not like your point?
Contrast to my previous comment, I understand the point a little more (I think). This is a "decent" elaboration.
And sure, what you're saying is true. Just because I can use
matchinstead ofif letdoesn't mean it would look good in the context. I think you could have made the point more general and left the message at that, instead of targeting one specific ES6 feature, considering there a quite a few features that can be abused.As my previous message states, I believe I understand your intentions, but your delivery of it was botched horribly (IMO).
As I suggested, maybe rework it, or put more emphasis on the developer than the feature, but explaining in the way you did before I understood was not doing your view any justice.
Since this is not a terribly huge issue I don't think it would take much effort to fix.
(On an unrelated note, let me turn on my MoistCritical impression, because damn. - When you said "That is not my point and you know it." that comes off as kind of an asshat thing to say, especially when you add "but you do you". It just strikes me as "Hey. I'm overly confident people can understand me right away!". Because no, I did not understand you. @brense didn't seem to understand you either since they were on board with what I originally said. - I dunno, maybe sounding blunt wasn't your intention but I just thought I should point it out because others might get the wrong idea.)
blunt comes out when i'm having a stressful day and just want to quickly get something out of the way, so for that, my bad.
Your first reply to that prompted me to do this, lol, which i still felt like sharing now: gyazo.com/694be84381c62bd88a14540a...
Your other replies are clear, i see that you see what i meant and i get where you are coming from. In addition i merely picked on that specific feature because it was the feature the OP wrote about. There are other things in ES6 I do and do not like. I don't really control what gets added but my sentiment is that the JS community is adding too many bells and whistles to a language that works well without them and that there are other areas that could be addressed that are far more important. My biggest beef with the language is the number of things that do exactly the same thing. One example running code in the order you want it to: javascript.plainenglish.io/callbac...
I don't intend to offend people, but sometimes i'm too tired to think of the best way to say things and i just drop in the info as best i can at that moment. [probably why so much of the internet is full of horrible comments]
This is something I also find distasteful, but I feel like this, relatively, is one of the better things.
I think the JavaScript community forgets it has learners that are working in
.htmlfiles, so it would be cool if they focused on that side of the community, such as allowing modules in the the browser.💀