DEV Community

RetardeMangojuice
RetardeMangojuice

Posted on

Js and burning out

Im just burning out more and more as i understand that i understand nothing. Using with complex spa? 30% of code is type and value checks because js doesnt really care, type coercion and legacy parts of it, weird interactions.

I've tried typescript and its better, not by a lot but better, but many devs that i know or work with say that it is useless/they know what they are doing? Most of the time i dont develop i develop around javascripts kinks.

Js alternatives for web are not really big and have no really meaningful marketshare.

What should i do? Try another language/programming field ? Stick to typescript/flow/reason/elm/purescript for my pet projects and look for new opportunities? Im lost on what to do. Any help would be appreciated.

Experience 1.5 years.

Top comments (7)

Collapse
 
itskitto profile image
Kitto Khrangtong

I think the best thing you can do atm is take a step back and get a solid foundation going with your JavaScript fundamentals. It's really easy to get caught up in the hype of new technology and to get jealous seeing what others are accomplishing.

Ways you can level up your fundamental JavaScript is by making some simple interactions: outputting form information into an email, creating your own modal, creating info/error message popups that show and hide divs with that info based on user input.

In my opinion, javascript30.com/ by Wes Bos is a nice segue into learning what JavaScript can do beyond its syntax

Good luck!

Collapse
 
rmangojuice profile image
RetardeMangojuice

What if i've done things you listed and even more complex stuff?

Im not jealous about what others acomplishing too, im just feeling forced into bad language just because browser supported language wont be changed because of backwards compatibility and politics.

Collapse
 
itskitto profile image
Kitto Khrangtong

Well, you very well may just be burnt out on JavaScript, or don't have a passion for it. Web dev is possible without heavy usage of JavaScript but you'll definitely be scraping around to find work-arounds.

What makes you feel that JavaScript is a bad language compared to others? Obviously it has it's quirks but so does every other language.

Thread Thread
 
rmangojuice profile image
RetardeMangojuice • Edited

Complex react enterprise grade app with lots of data queries followed by constant data and variable checks in the components. For example once i've seen calls for 3 functions that didnt exist and were deleted long time ago on auth form and js didnt throw any errors whatsoever. I kinda have some type of ocd that when i do something i must do something perfectly and i had fun with elm, but elm wont get me employed. Maybe i should try moving to angular? Im just feeling lost and dont know how to solve or tackle this issue.

Collapse
 
juancarlospaco profile image
Juan Carlos

Try Nim lang, inferred static typing, compiles to JavaScript:

  • Natural type is from 0 to biggest integer possible
  • Want an integer from 42 to 54?, range[42..54]
  • Sized integers? int8 to int64, sized floats too
  • Byte type from 0 to 255 with just 1 byte
  • JSON is a literal JSON, not inside a string
  • Distinct type, Tainted string type
  • Syntax similar to Python or CoffeeScript
  • Compile to WASM

Sometimes the most Trendy stuff can suck yeah :)

Collapse
 
jdforsythe profile image
Jeremy Forsythe

If you're worried about backwards compatibility being a persistent problem, you're going to need to find a new field.

In my opinion it is just as important to learn the history of JS as it is to learn the grammar and patterns. Why are the bad parts there in the first place? You can thank a big business deal for that.

Once you know the why, you can find ways to utilize the language to your benefit. I have been writing JS for fun and profit for 20 years. I have also written code in at least 10 other languages. News flash, they all have their problems! That's why so many exist!

If you're trying to use Angular or React and can't do basic DOM manipulation or XHR/fetch, etc. manually, it's going to be a headache. If you're trying to jump into Typescript and aren't intimately familiar with JS and why you want types in the first place, it's going to be a headache. Don't choose the new and shiny because it's new and shiny. Use the right tool for the right job.

If you can't use a screwdriver, don't buy a drill. Go back to basics and fall in love with JS again. Or choose something else. But fall in love with the basics or you will end up in the same place.

Collapse
 
niorad profile image
Antonio Radovcic

no, it sounds like you need to work on your JS fundamentals. forget all the frameworks for now.

Some comments may only be visible to logged-in visitors. Sign in to view all comments.