Ranter
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Comments
-
inaba46257y> Frontend
Moment.js is probably the only JS thing for frontend that I would really reccomend. It makes working with dates a lot nicer.
Get yourself a CSS transpiler. Something like LESS or SASS will really save you a lot of headaches in the long run.
Those are probably the only things that I think you really need for the frontend. There's a myriad of other tools and frameworks and stuff that can also help you with development, but I'd suggest you check them out yourself to see if you really need them tbh
And as a CSS framework I'd suggest Bulma. It has the added benifit of not requireing jquery or anything JS at all
Also use semantic tags. They're goooooood -
The only thing I can recommend is to never trust user input or client side validation.
-
> Frontend
Take a look at Babel so that you can use new JavaScript features without worrying about browser compatibility.
I suggest also picking up a bundler, so that you can use modules from npm. They also help you manage assets, by generating hashes for different files (so that caching doesn't bite you in the ass). The most used bundler is webpack. There is also parcel, which is a new bundler that doesn't require configuration.
You should also take a look at eslint. It checks your code statically and warns you about some neat things, like unused variables, redeclared constants, confusing syntax, etc. Configuring it can be a bit of a pain, since there are a lot of rules, but some companies open source their eslint configuration, so you can use one of those at first. A good one to start is airbnb's: https://npmjs.com/package/... -
devTea240886y> Frontend
If you just started to learn front-end, then I suggest you to fully understand the basic of css and js first before jumping into any framewok. Css probably do not need any framework IMO as laying out your web has never been easier since the grid system got introduced. For js, now the only library I really need so far is still jQuery. Quite old, but I’ll try some modern one, once I finished and confidence of all proper basic
Related Rants
-
ahmedam23What only relying on JavaScript for HTML form input validation looks like
-
isaacWeisberg21Me and my wife are software engineers Started dating while doing a project together I guess you could say that...
-
JMoodyFWD48My "Coding Standards" for my dev team 1.) Every developer thinks or have thought their shit don't stink. If y...
So as all of you web developers know. If you are stepping into the world of web development you stepping into a world of unlimited possibilities, opportunities and adventure.
The flip side is that you step into a world of unlimited choices, tools, best practices, tutorials etc.
Since even for a veteran programmer, this is a little overwhelming, I'd like to take the opportunity to ask you guys for advice.
I know that 'there is no best' and that everything 'depends on what you want to achieve'. So how about just say the pro's and cons or when to use and when not to use. Or why you prefer one over another. Everything is allowed! :D
Maybe it will help others too. Start a nice, professional discussion:)
These are the parts I'd like advice about:
- frontend: what frameworks, libraries
- backend: language, framework, good practice
- server: OS, proxy (nginx, Apache, passenger), extra tips (like don't use root user)
- extras: git, GitHub, docker, anything
Thanks in advance everyone willing to help!:)
Also, if you only know frontend or backend. No worries, just tell me about your specialism!
question
full stack
web development
advice
tools