Bootstrap

Why do you need Bootstrap / Tailwind in the first place? Angular Material already has responsivity built in out of the box and you can just plug into that?

Be good at javascript initially. Forget mongo or anything for now.

Nowadays, everybody is using components to build their frontend and I hardly see someone touching html deeply.

For css framework, choose a utility framework such as Tailwind CSS. It wont look magic to you and wont hide technical specs like magic.

Choose one front-end framework (I recommend react.js or vue.js) for employability and node/express combo for the backend.

I think you scan skip MongoDB for now and focussing on creating web component with Reactjs or Vue, I would also recommend to use TypeScript for type hinting support.

For styling, learn CSS first then upgrade to SASS/SCSS or LESS (pick one as mostly same concept) to make CSS more maintainable.

Also to improve your skill on both sectors, install linters if available. For TypeScipt, there are TSLint and for styling, i think there are Stylint. Linter will help you adapt to make a clean code and understand how other peoples usually styled their code.

Hey friend, first of all, nice to listen your journey. Hold on it. It is not easy, but it pays. My advice to you is to try NodeJs and Express as webframework for the beckend part. I am pythonist, so Django lives in my heart. But, in the beginning, I think you wanna speed up. So, trying Node coudl be good cause you will learn JavaScript, that you will use a lot at frontend too.

Of the two options you mentioned, only Django is a backend technology. AngularJS is another toolkit to build web applications, though more of a framework with a complete set of technology than Bootstrap which is just a UI library.

I think that the best way to push yourself forward is indeed to learn multiple technologies and multiple programming languages, and Python is often a good choice - it is simple, clean and has a lot of mindshare (i.e. you can easily find help).

So when looking at the next technology to learn and the next programming language, Django is a good choice. If you want to stick with Javascript, then I can echo the recommendation to look at Node.JS as a backend service - though if you want to push yourself and become a better software engineer, then putting all your eggs in the Javascript corner is probably not the best choice. Good engineers have a large set of tools to draw from and knowing more than 1 language can both increase your marketability and tech you to think in more than 1 way.

Hey Vaibhav, luckily you don't have to pick between these two. @react-bootstrap (https://react-bootstrap.github.io/) let's you easily use Bootstrap (a CSS UI framework) with React (a JS library). That being said Bootstrap tends to be pretty heavyweight, so it might include a lot more than what's needed for your app. Good luck and happy coding.

For a new project with angular use angular.io, not angularjs. Angular has pwa ready to go functions, ngrx data to optimise data loads and store management. PrimeNg is a powerful library but angular material gives you enough power. Take good care adding such libraries because of compatibility issues on uograde. Look at what you can do with angular material, and then add primeNg if you have no choice.

I have used bulma in several projects. We could not customize with the websites very well. Also when we need "quick solutions" Bulma is not suitable (I mean basic animations, to-top buttons, transparent navbar solutions etc. For these solutions, you need extra js codes).

Everybody knows about Bootstrap (heavy but popular).

Now we start a new project with UI kit, I like it. Pros: It is fast and lightweight and imho it has very good UI. Cons: Small community. Documentation.

Check this link for kick-off. https://github.com/zzseba78/Kick-Off

Maybe it is helpful.

Been checking out Bulma, myself, and really dig it. I like that it's a great base level jumping off point. You can get a layout going with it, pretty quickly, and then customize as you want. It definitely sounds like it's the one you're leaning towards but a big factor would be who will be using it most? Your boss, yourself, others? Whichever you like best, you'll prob be most productive with but if in the end your boss says it has to be UIkit, then best to be open-minded and give it another shot. Sometimes you may not jive with new tools in your stack, at first, but then they can become tools you learn to love. Best to you in your decision! Take care & keep safe.

I would recommend to upgrade your stack and consider Angular.

Also, if you are working with docker, instead of manually managing your EC2 and docker inside it, switch to ECS as its free of cost and hassle free way to deploy and keep running your containers efficiently.

Good luck.

Instead of Docker , no doubt its great but it has vulnerabilitis and restricitions with dameon and root thread. I would pickup Podman. Also Ambasador is a culmination of Gateway LB and ServiceMesh on istio and Envoy. Great for both East-west and North south microservices communication, policy managment and security with Istio. Spring Boot is not a WebFW. For platform web fw one can use Reactive like SPring WebFlow rather than Spring MVC. For java experience, Spring provides great assets.

I will switch to using Kubernetes whether managed or custom depends on several factors rather than AWS ecs. For LB Amabassador is a great alternative on AWS. One can simply use this on top of ECS clusters. Instead of running in to different frameworks one can simply use one FW at both client and server side for consuming and SSE. I believe one can look at Lot of it depends what you need a full FW or a light librarry like React to be part of V in your MVC. Whether you need a SPA , on Mobile etc... in that case KOTLIN is also another option on Java. Dont go with Android. Best luck. Swapnil S

Factually talking about systems, we gotta make two bold headlines about each one: Bootstrap has been around for a while, has a vast community and much probably will not be gone in a while. Tailwind in the other hand, is the trendy framework starting from the past year. Referring to UI, I really prefer Tailwind, however I can't ignore the fact that a lot of libraries that emerged felt short in the end after a few years (a point where Bootstrap kept his status).

You are able to use both them together but I advise you — it will be a mess. And you gotta hope that you won't have any kind of conflicts between class naming and other general styling.

My recommendation would be to use one and only one. Perhaps rebuild the UI with a specific framework in mind, otherwise you will start to workaround things of both frameworks to contradict each other - and your team (if you work with one) will hate you.

You might have heard about bootstrap 5. Bootstrap is now totally jQuery free. i have tried foundation and bulma too. but eventually fall again for bootstrap, as it is most convenient and stable. i use bootstrap with less or sass.

You can use almost anything you want with React, in the end it just renders out html/css. There are currently two major projects wrapping bootstrap in React components. I have personally used reactstrap and created my own components using bootstrap css and both worked fine.

You can use also something like MDBootstrap, which includes Bootstrap and Material Design. This is the link to the React version: https://mdbootstrap.com/docs/react/

I used it for a JQuery project and it works fine.

The only significant potential drawback I see to Vuetify is that it is targeting only the Vue framework. If that is not a problem for the project, or as in this case it is actually one of the specifications, then I would certainly recommend Vuetify.

The Vuetify components are more rich and complete, the documentation is great (especially compared to the Bootstrap documentation, plus a new version of Vuetify docs is imminent now), the support and community are considerably better and more responsive, and there are very active updates (pretty much weekly).

I'm an owner of a paid Bootstrap theme and there was effectively zero support, it was weak, and I'm sad to say that I think Bootstrap is something that looks better in a demo than in practice.

Vuetify components are more modern-looking, and directly designed for use in Vue applications. I am biased in the sense that I have looked at both (bootstrap-vue as well) and my work with Bootstrap over a year old now, but at that time I chose to go with Vue and Vuetify and every day that decision feels more rewarding. I do not regret it at all, and I highly recommend Vuetify on Vue. It's also a really great fit with Laravel.

If you're already working with bootstrap, then it would be straightforward to move onto vue bootstrap. I'm using it in one of my projects and it's been a pleasant surprise. Easy to use, smartly designed, intuitive. I started using bootstrap back in 2012 and I grew tired of it so I moved forward to material design. After years of fighting against MaterializeCss, Bootstrap Vue feels slick. Vuetify is nice, it has awesome components and everything, but I wouldn't go back to it. Bootstrap Vue is my new favorite and they create new components every week.

Honorable shoutout to ElementUI, which is amazing too, albeit a little tied to the presets of 2019 which are getting stale.

I've tried VueStrap Vueify and CoreUI too but they weren't a full blown solution. The latter is lacking in documentation too.