jQuery

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.

If you are used to use JQuery, Vue.js more similar to Jquery because you only can import a CDN and start to work. Vue is really flexible and you can use it wherever you want.

In other hand, if you have time to learn and install a new framework as React, use it. React works with a standard and several conventions in his code, then is really easy integrate new libraries and plugins .

both are absolutely great choices. while you'll find more resources and a larger community with react, vuejs typically does some quality of life "magic" for you. its pure taste.

if your html markup comes from razor, I'd recommend globally registered Vue components though. I've successfully used this stack for 4 years. (content from sitecore cms rendered through razor, enriched with vuejs components)

in any case, you will want to try to remove jQuery, if you pick a frontend library, as you should not mix two ways to modify the DOM. it wont break but its unnecessary bloat.

I would say go for Node.js since you probably would only build a REST API that would talk to the frontend and some communication with the database.

On the other hand, Laravel is a much heavier framework that follows MVC pattern. Since you don't need the V in the MVC of Laravel. You can go for a straight Express that just handles the API request and return a response.

Hello Varun S,

Project-1 : If the Laravel part is an API, you should check Flutter or Quasar Framework for your frontend in order to reduce the development time and process.

Hi Eva, As you have solid experience with Spring already, you should jump into freelancing with that. It would be quite stressful to start freelancing with a tech stack you don't know well. Then in the background you can keep learning/practicing an alternative and switch over when you are confident enough (eg. 0.5-1 year later). I think you should learn Laravel as you already like it and find it easier. Express has better performance but that is not required for most of the small freelancer projects.

I think Patrik and Alex are right: if you're comfortable with Spring Boot already, you'll be more productive right from the start.

If you wish to learn something else besides, both Laravel and Express are good choices. They aren't in the same category of frameworks: Laravel is an all-in-one solution, while Express is more like "build your own stack from different parts". Which implies that you can use whatever you want as a database engine: MySQL or PostgreSQL are perfectly valid choices (in my school, we teach Express with MySQL, because SQL is still a big thing here in France, and a sought-after skill). You can use Sequelize or TypeORM which support all major SQL DBMS.

Express is widely used, but if you're seeking the JavaScript equivalent of Spring Boot or Laravel, you probably want to look at NestJS. The only potential downside is that it's still young, maintained by a small commmunity, compared to those behind Spring Boot and Laravel.

Bottom line: using a stack tech, that you enjoy and are comfortable with, matters. Spring Boot + Vue.js seem perfectly fine to me. But do forget jQuery if you're using Vue.js, React or Angular, because it will definitely bring more harm than good!

Unless you're either using a local database or a backend server, you shouldn't choose either.

My recommendation would be having a NodeJS API on the backend that connects to the database and Electron connects to the API. Never give the database connection data to the end user, unless it's a planned move and it's to use on a local database.

I can recommend Sequelize because what I'm use the most on every project I need to create database connections. It supports TypeScript, and if you already have the database create you can use sequelize-auto to create the models, as easy as that.

I've only used Electron once and I liked it, but it's not a good comparison, since it doesn't offer any database access by default. I used React for the frontend part of the app, you can use whatever you want.

Hi Adan,

Javascript has changed quite a bit in the recent years and lot of it was inspired from jquery. Now almost all modern browsers support javascript syntax everything that jquery does with few elaborate / sometimes better alternatives. So, if you like to switch, find the equivalents of what portions of jquery you use and replace those parts. Btw, jquery is still nicer sometimes with its method chaining and a lot simpler syntax - the equivalent in js may not be that sugary syntactically.

I was like you two years ago, used to jquery and didn't want to switch, but if you're willing to use js frameworks in your projects(React, Vuejs...), I advise you to switch asap, and get used to normal javascript, because in the end, it's the core language, but there are some new ways in it (especially in ES6) that will make your life easier, like you can replace the document.querySelector() with $() and document.querySelectorAll() with $$(), using this line of code: const $ = e => document.querySelector(e), $$ = e => document.querySelectorAll(e); then you can select a p element just by writing: $('p'), and multiple p elements like that: $$('p'). I hope my advice helped you in any way.

What your penetration testers mean by this is that you need to upgrade these libraries to the latest versions. The newest available.

The versions you are running are 6 years old (Bootstrap 3.3.7) and 9 years old (jQuery 1.10.1). Neither of these versions are supported by their developers. What this means is that if are any vulnerabilities present in those versions or discovered in those versions, the developers will not make a patch fix for them.

You should update to the latest versions so that any known vulnerabilities are not exploitable and that any newly found ones are fixed by the developer and are easy for you to apply and upgrade to.

Sounds like you are working really hard at improving your skills. Keep at it. I think something you could look at which you haven't mentioned is learning how to use source control in a team setting. There are many things which using a source control system unlocks. When you work in a team you'll be working on a feature that is part of a bigger project, before your code is inserted into the shared code base someone will usually review it and approve the request to merge your feature into the main code base. It also unlocks concepts such as CI/CD and maybe better ways of work (using a task/bug/test tracking tool) - all none-code skills which are just as important as being a good coder.

I would recommend to watch something about architecture and design patterns on youtube to get a feeling for it. Apart from that you mentioned "how to work in a big real project", I would recommend searching up "scrum"(project management). Also looking into CI/CD continuous integration and deployment will help you as well. But most important is that you stay up to date, since everthing changes all the time. Which also means to not worry to much if you will miss something, because you can't know everything in that field with the current speed going :).

PhP might be old fashionned but Laravel is really great. I've tried nodeJs backend with express, python with flask and a little bit of serverless, and quite frankly, laravel was by far the best in my opinion. It has a lot of official packages that speeds up development (from authentification to serverless deployement), it also uses Eloquent ORM that support Mysql databases. Finally it works great with VueJs for the front end development.

I recommend ExpressJS or NestJS as BackEnd and React as Front-End and PostgreSQL as the database. The reason is as follows. First of all, since it is a financial system, various services will exist, and each service must be well connected and combined with each other. The organic combination of small services that work very well is the foundation of a great system. For this, it is best to use Node.js based, and I think ExpressJS or NestJS is the best choice. We recommend choosing React or Vue as the FrontEnd. PostgreSQL is currently the best performing database. These three combinations have many examples, and their superiority has been confirmed by my implementation in many projects already. If you are interested in my advice and have any questions, please feel free to contact me.