Need advice about which tool to choose?Ask the StackShare community!
AngularJS vs HTML5: What are the differences?
What is AngularJS? Superheroic JavaScript MVW Framework. AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding.
What is HTML5? 5th major revision of the core language of the World Wide Web. HTML5 is a core technology markup language of the Internet used for structuring and presenting content for the World Wide Web. As of October 2014 this is the final and complete fifth revision of the HTML standard of the World Wide Web Consortium (W3C). The previous version, HTML 4, was standardised in 1997.
AngularJS belongs to "Javascript MVC Frameworks" category of the tech stack, while HTML5 can be primarily classified under "Languages".
"Quick to develop", "Great mvc" and "Powerful" are the key factors why developers consider AngularJS; whereas "New doctype", "Local storage" and "Canvas" are the primary reasons why HTML5 is favored.
AngularJS is an open source tool with 59.6K GitHub stars and 28.9K GitHub forks. Here's a link to AngularJS's open source repository on GitHub.
According to the StackShare community, HTML5 has a broader approval, being mentioned in 3135 company stacks & 3373 developers stacks; compared to AngularJS, which is listed in 2793 company stacks and 1806 developer stacks.
Hello,
I want to generate dynamic CSS for each user with an expiry link.
I've created a cloud-based tool (Example - https://www.tablesgenerator.com/) where people can create tables and use them on their website by pasting the HTML generated by the tool.
Now, there are a few styling options needed, which can be done using CSS. As of now, I'm asking the users to copy the CSS and paste it in the "Custom CSS" section, which is a bit hectic work as they need to change the CSS every time if I make any changes to the styling.
So, I'm just wondering if there's a way to generate dynamic CSS for each user with an expiry link.
Currently, I have around 200 users, and what's the best way to do it?
The best way, as usual, is a "it depends".
Still I would go to something as simple as storing the expire date+the generated css and other metadata in a table. If a user tries to access something that is expired than he's redirected to a specific page. Periodically (like once a day), a janitor process deletes the old data.

Instead of having the user copy and paste the CSS directly, have them copy and paste the HTML that will include an external CSS file generated and hosted by your application. This will allow you to control when the stylesheet is updated as well as control privileges on who can request the file. Additionally, using a CDN service (e.g. Cloudflare) will allow you to cache the static assets being requested reducing overall server load.
When your server (and optionally CDN) no longer are serving the file, consider the link expired. Unique URLs can be generated using a multitude of methods but maybe consider if there is any benefit to the users if it follows the scheme: yourdomain.com/USERNAME/CUSTOM_NAME.css rather than something like: yourdomain.com/style/SOME-UNIQUE-HASH-1234.css
What is the best MVC stack to build mobile-friendly, light-weight, and fast single-page application with Spring Boot as back-end (Java)? Is Bootstrap still required to front-end layer these days?
The idea is to host on-premise initially with the potential to move to the cloud. Which combo would have minimal developer ramp-up time and low long-term maintenance costs (BAU support)?

React might be a good option if you're considering a mobile app for the future, because of react native. Although, Vue.js has the easiest learning curve and offers a better developer ramp-up time. Vue.js is great to build SPAs, very clean and organized and you won't have a lot of long-term maintenance problems (like AngularJS, for example). Bootstrap can still be used, but with flexbox there's no need anymore.

I recommend React because of less memory occupant compare to Angular, but this will depend on your organisation flexibility. When you use React you need to import different libraries as per your need. On the other side angular is a complete framework.
Performance-wise I vote for react js as it loads up quickly and lighter on the mobile. You can make good PWA with SSR as well.

If you are new to all three react will be a good choice considering, react-native will be useful if you want to build cross platform mobile application today or tomorrow. If you are talking about bootstrap styling framework than it's a choice you can style ur components by ur self or use bootstrap 4.0 framework. The complete stack mentioned above is platform agnostic u can run it anywhere you want be it cloud or on-premise.
A major part of our project includes visualizing the data through graphs and charts. We chose to use d3.js since it provides a wide selection of well-designed graphics and animations. As a library, it is also easy to use and be included in our UI. JavaScript which our team has experience with was also selected to integrate graphics from d3.js into the UI, as well as to integrate the UI with the backend system. Along with JavaScript, HTML5 and CSS 3 are also selected mostly for styling and formatting the webpage. These three languages are widely used which means that more support will be available, making the implementation process easier.
The key to our product relies on explainability and user experience when using our product. With this is mind, it is important to build a clean, readable web interface that a user will be able to navigate easily and quickly debug their security issues. The stack chosen for the interface of our product includes: JavaScript + React, CSS, HTML, Material UI and D3.js.
React provides us with simplicity to allow us to deliver the MVP as soon as possible. React also has multiple open source libraries to ease our development. Being able to reuse React components will help in developing the product fast as well as making the user interface modular. Since we're using React, we will also be using JavaScript, HTML, and CSS to create the frontend.
To design the UI, using a minimal approach would be the best solution. The Material UI library provides us with minimal and aesthetically pleasing React Components which would make our frontend look pleasing to the user.
Finally, our UI will consist of displaying information from our Machine Learning model in a dashboard type view. To display data in tasteful manner, we have chosen to use the D3.js library. This library is the most popular data visualization library for React with over 80k stars on Github. D3 also provides seamless compatibility with React and has a variety of features which would make the data we produce visually pleasing.
As our team will be building a web application, HTML5
and CSS3
are one of the standardized combinations to implement the structure and the styling of a webpage. Material-UI
comes with all sorts of predesigned web components such as buttons and dropdowns that will save us tons of development time. Since it is a component library designed for React, it suits our needs. However, we do acknowledge that predesigned components may sometimes cause pains especially when it comes to custom styling. To make our life even easier, we also adopted Tailwind CSS
. It is a CSS framework providing low-level utility classes that will act as building blocks when we create custom designs.
Have you ever stuck with the question that which one is the best front-end framework for you?
With continuous web development progress, the trends of the latest front-end technologies are also continuously changing with more and more sophisticated web features. These top front-end frameworks and libraries have made your complex web tasks more flexible and efficient.
Check out top front end frameworks and their features at https://www.nmtechedge.com/2020/09/24/top-4-trending-front-end-frameworks-2020/
Am I the only one to think that libraries like Bootstrap, Vuetify, Materialize, Foundation are too much sometimes ?
Most of the time you are loading all the library and using 10% of it. And on that 10% you are modifying 90% of it.
I feel like using grid and pure CSS / JS are enough and cleaner.
I honestly think the best choice for which framework you use should come down to your team's skills. If you have one Senior Dev that is great at React, but like 3-4 mid-level devs, and a handful of junior devs that know Vue.js ... maybe look at using Vue.js a little more seriously.
Yes, there are pros and cons to framework decisions, but I honestly see a LOT of teams not even consider whether a specific framework is a good fit.
I honestly think the best choice for which framework you use should come down to your team's skills. If you have one Senior Dev that is great at React, but like 3-4 mid-level devs, and a handful of junior devs that know Angular ... maybe look at using Angular a little more seriously.
Yes, there are pros and cons to framework decisions, but I honestly see a LOT of teams not even consider whether a specific framework is a good fit.
It was easier to find people who've worked on React than Vue. Angular did not have this problem, but seemed way too bloated compared to React. Angular also brings in restrictions working within their MVC framework. React on the other hand only handles the view/rendering part and rest of the control is left to the developers. React has a very active community, support and has lots of ready-to-use plugins/libraries available.
It is a very versatile library that provides great development speed. Although, with a bad organization, maintaining projects can be a disaster. With a good architecture, this does not happen.
Angular is obviously powerful and robust. I do not rule it out for any future application, in fact with the arrival of micro frontends and cross-functional teams I think it could be useful. However, if I have to build a stack from scratch again, I'm left with react.
I used React not just because it is more popular than Angular. But the declarative and composition it gives out of the box is fascinating and React.js is just a very small UI library and you can build anything on top of it.
Composing components is the strongest asset of React for me as it can breakdown your application into smaller pieces which makes it easy to reuse and scale.
Pros of AngularJS
- Quick to develop887
- Great mvc588
- Powerful572
- Restful521
- Backed by google503
- Two-way data binding349
- Javascript343
- Open source328
- Dependency injection306
- Readable197
- Fast75
- Directives64
- Great community63
- Free56
- Extend html vocabulary38
- Components29
- Easy to test26
- Easy to learn24
- Easy to templates23
- Great documentation23
- Easy to start21
- Awesome18
- Light weight17
- Angular 2.014
- Javascript mvw framework14
- Efficient13
- Great extensions13
- Easy to prototype with10
- Coffeescript8
- High performance8
- Lots of community modules7
- Two-way binding7
- Mvc7
- Clean and keeps code readable6
- Easy to e2e6
- One of the best frameworks5
- Easy for small applications5
- Fast development4
- Works great with jquery4
- I do not touch DOM3
- Dart2
- Declarative programming2
- Be a developer, not a plumber.2
- Hierarchical Data Structure2
- Typescript2
- Community2
- The two-way Data Binding is awesome2
- Common Place1
- Great1
- Very very useful and fast framework for development1
- Amazing community support1
- Readable code1
- Linear learning curve1
- Scopes1
- Programming fun again1
- Supports api , easy development1
- Opinionated in the right areas1
- Fkin awesome1
- The powerful of binding, routing and controlling routes1
- Consistency with backend architecture if using Nest1
Pros of HTML5
- New doctype447
- Local storage389
- Canvas334
- Semantic header and footer285
- Video element239
- Geolocation121
- Form autofocus105
- Email inputs99
- Editable content85
- Application caches79
- Easy to use10
- Cleaner Code9
- Easy4
- Semantical4
- Modern3
- Better3
- Audio element3
- Websockets3
- Content focused2
- Compatible2
- Portability2
- Semantic Header and Footer, Geolocation, New Doctype2
Sign up to add or upvote prosMake informed product decisions
Cons of AngularJS
- Complex10
- Dependency injection3
- Learning Curve2
- Event Listener Overload2
- Hard to learn1
Cons of HTML5
- Easy to forget the tags when you're a begginner1
- Long and winding code1