Upgrading has been relatively straightforward. Every common web app architecture problem has a solution with this framework, and the less common problems are solved by packages - which tend to be high quality, and the community tends to agree on which packages to use. Design concerns are addressed neatly and comprehensively, following a lot of time-tested software design principles everything has its place - models and data access, views and UI stuff, rendering performance, controllers/view-models, routing, development tooling, test support, CI/CD integration. READ MOREĮmber.js is a complete framework for developing frontend applications. I chose Microsoft To Do over them both because it has the simplicity of Google Tasks, with the integrations of Todoist, and when you take a bit of time to configure it, it looks damn pretty. Google Tasks is also a fine choice (it's hard to screw up a todo list, really) especially when paired with TaskBoard (Kanban!). Todoist is by far the most powerful of the two, and it offers many easy to implement 3rd party integration (notably with Obsidian!) Has a paid option, which of course I need to have if I'm going to use it, so I try not to! ok, i can (relatable?) end up following the dopamine to 19 other things and by the time i get to my to do list i've forgotten the idea or reminder that sent me there. While much of this stack involves complicated platforms that have numerous forms of list making options -which I utilise- sometime you just want to quickly jot down an idea or reminder for yourself and if you're not inside your platform of choice you can. So, I think with that you can have a better big picture of those frameworks. For instance, I've seen frontend developers that prefer Bootstrap's Grid System, but like Semantic UI's components more. In my opinion, the most difficult thing on all of those frameworks is customization and layouting (the Grid of those systems), so when a designer gives you a Figma (or other wireframing tool) mock so you can reproduce - and that's why you'll need Sass (or pure CSS if you want) to apply some stylesheet rules over the frameworks components (please do this with caution and try as hard as you can not to) - that's where you'll struggle the most, hence the importance of have a good understanding of those frameworks catalogs.Īnother thing to keep in mind, this frameworks are not mutually exclusive. Sass is a, in my opinion, better way to write CSS once you'll do it like your HTML structure, which at the end of the day is more readable.īootstrap by all means it's the most used frontend framework worldwide, so if your purpose on learning is to apply for a job, it's more likely to find open positions to work with Bootstrap than any other.īootstrap, afaik, was the pioneer frontend framework and pretty much all of the others has "borrowed" one or another thing from Bootstrap. Just one FYI, Sass doesn't compare to Bootstrap, Tailwind or Semantic UI. Plus, when you grasp one, I assure you the next will be way smoother to learn, once you'll have grasped the underlying concepts of frontend element positioning and wireframing, as well as basic component behaviour (like an accordeon, tab selection, complex menu items, etc). Keep in mind that the most you know the better will be. I'm also adding Semantic UI and Milligram to your list. So, all of them, Bootstrap, Tailwind, Semantic UI and Milligram are solid, well stablished and coherent frontend frameworks, so I'd advise you to choose the one you like the most regarding the look and feel. So, if you want a straightforward response I'd suggest you to start your learnings with Bootstrap and Sass, but I leave bellow some more reasoning you should be aware of.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |