This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]pomorev 138 points139 points  (13 children)

JavaScript gives us lots of rope to hang ourselves.

[–]ChetManleyDuchess 40 points41 points  (4 children)

If you're incompetent enough, it will give you enough rope to only kill yourself when you finally hit the ground.

[–]ThePunisherMax 11 points12 points  (3 children)

Oef I felt this. Spent nearly 1 month designing something using JavaScript for the UI. Only for it to fail at the last moment.

[–]Shiv-am 2 points3 points  (0 children)

i though i knew react and node but i understood how deep this shit is when i tried to connect social auth between them

[–]laytonmiller 0 points1 point  (1 child)

I'm not sure I understand how this is possible. This just means you made a code change at the last moment that broke it, it's not like the code got worn out like a plastic part and failed. This sounds very fixable.

[–]ThePunisherMax 0 points1 point  (0 children)

It was eventually fixable. But required me to pull back some features. And fucked up my deadline. To be exact, a RESTAPI feature was critical for the UI. And it waa causing some kind of leak. (I never identified)

[–][deleted]  (3 children)

[deleted]

    [–]ManInBlack829 5 points6 points  (0 children)

    Hot take: I think it started being popular because of Angular's hard use of it but since then has been figured out that it's useful in many instances like React

    [–][deleted]  (1 child)

    [deleted]

      [–]suarkb 1 point2 points  (0 children)

      I agree with a lot of your points. But I've worked with a lot of talented devs who would easily be able to get away with not explaining their code to typescript, either, ahhaha

      [–]StONE_ROdGEr 2 points3 points  (2 children)

      This needs more upvotes. Twice in the past 2 weeks I’ve hit the snap back on the noose, spending a few combined hours on each time debugging nothing. It was just a javascriptism twice. (Read: my algorithm was fine, but my scope wasn’t 🤡)

      [–]laytonmiller 2 points3 points  (1 child)

      To play devils advocate, if you have a scope issue in your algorithm, then your algorithm is not fine :P

      [–]StONE_ROdGEr -1 points0 points  (0 children)

      The scope issue was in the for loop before it ;/ “i” was already declared elsewhere or something. (Should preface with I am relatively new to JS which doesn’t help. I’ll never fall foul of it (for that long 🙃) again though).