So I decided to enter Web Dev

After 3 long months of "Analysis Paralysis", I decided to enter the world of web dev. Now, I know there are tons of resources, tons of roadmap but I will still take the community and devs advice. Looking forward to helping and ask for help in the community. Feel free to drop advice, roadmap, tips, resources which will help me in advancing my journey in this web dev world.

P.S.: I am not a newbie, I have been learning Java and I am familiar with the concept of OOPS.

Comments

[Ivan Jeremic]

Go with ReactJS as frontend library, you won't regret it!

[Yash_Jaiswal]

Thank you so much. I'll make sure I'll learn it.
Also for backend what should I choose?
Django/flask/deno or Spring or Nodejs or laravel?

[Ivan Jeremic]

Start with Node then maybe adopt Typescript after this take a look at C# also learn about serverless and the Nextjs framework

[Daniel Hintz]

I know I'm late, but thought I'd chime in in case you're still on the fence re: JS framework. I've read that Vue has a much smaller learning curve than React, and is best for smaller, simpler sites (like a personal portfolio site). React is a heavier framework, but has a ton of advanced features. If you're short on time and are just doing a "mini-project" you might want to read into it (I started to, but haven't gotten far due to other priorities).

However, React is more popular once you're looking for a job.

[Yash_Jaiswal]

Yeah, my team decided to go for moon.js, if we can't complete till deadline will go for vanilla js, as for backend we are using flask!

[Mihail Malo]

Would it be completely insane to suggest learning

1. Javascript
2. Typescript
3. HTML5 + CSS
4. A framework (React? Vue? Svelte?)

in this order?
For example by making JSON apis or cli tools in nodejs first.

I feel like this would give better knowledge than going head first into a framework OR vanilla js in the browser.

[Yash_Jaiswal]

As per the internet norms step 3 comes first then 4 then 1 then 2 but if someone had to try something they gonna have to make their hand dirty by diving straight into something. I'm at the css part now will eventually learn bootstrap and vanilla js. After all this I'm thinking of getting my hands dirty with moonjs or react. As for the backend part I'm still deciding whether to use Flask or Vaadin or JHipster for smaller projects and Spring boot/ Django for bigger projects.

[Mihail Malo]

1. Why bootstrap at all?
2. Why specifically moonjs? Why not solid?
3. Why non-isomorphic, non-js backend? Why backend at all?

[Yash_Jaiswal]

1. Well, bootstrap makes your front end responsive and add something more to it.
2. Moonjs um... I don't know I just felt the name was cool and it's not mainstream.
3. I'm not sure what non-isomorphic means but I choose non-js backend because I don't plan to deep dive in js that much I just want to learn it enough that it'll be sufficient for me to design frontend. I'll choose backend where java is used. And as for my mini Project (The main reason why I dived in the world of web dev) I'll use flask as it requires less time to learn. Also I am aiming for full stack developer but that'll eventually change to either front end or backend depending on my experience with them.

Also thanks for recommending solid I'll look into it. I wasn't aware of any other framework beside VUE, Angular, React and ajax

[Mihail Malo]

1. I get that it has many "components" that all change at the same viewport width media queries, but with flexbox and css grid there's a much lower barrier to entry than there used to be to make your own css responsive. On the other hand, if you don't want to design anything and just want to present your data/controls as soon as possible, you should grab a component-pack for your specific framework, like a Google Material Design or Ant Design one, that directly exports components in your frameworks format.

2. Oh, that was precisely my reaction, that it is very obscure, I barely heard about it. Certainly less than Angular, Elm, Svelte and Cycle.js. Also, if you are just looking around for variety, see lit-element and stencil.js, which produce Web Components.

3. I meant that you would have the same component code running on the server for server rendering and on the client for clientside rendering. Personally, I feel like server side rendering is overhyped, the cases when it's advantageous are fairly limited. Having a completely static homepage + clientside-rendered-only inner pages makes more sense.
   Only if you are making something like a shop or Medium.com, with a lot of dynamic public content, would you want to render on the server to give new visitors that are following a deep link a fast experience.
   However, if you do plan on pumping out dynamic HTML serverside, perhaps you should skip fully featured frameworks altogether, and use something like STIMULUS to just give your pages interactivity.

[Yash_Jaiswal]

Thanks for providing information I'll do look into that

[Deepak Poojary]

Hi, I am from India and I am into webdev as well (finished html, css , bootstrap now in DOM and js) would be nice to connect with you(Im in my first year)

[Yash_Jaiswal]

Sure, follow me on dev! That's actually great I'm in third year and web dev will be the last domain I'll explore (currently exploring) probably if I won't get attracted towards blockchain. As for now nothing is decided. I am comfortable with Html,CSS. As for backend I'm learning flask and in databases I am familiar with MySql