icons VS Vue.js

Not sure if you already are using, but bootstrap has a lot of readymade icons for a project like this.

Bootstrap Icons

You can take the svg element from here. In the filter section type emoji and choose your desired emoji and copy the HTML. It will look like this

💡 This step is optional, but I wanted to use an icon for the close dialog button, which you'll see in a minute, but if you want to follow along, head to https://icons.getbootstrap.com/ ,scroll all the way down, copy the CDN Link, and paste it in the head of index.html

I wouldn't say it is more or less difficult, it is just a lot of work that somebody or something has to do.

Just to take an example, that Excel clone is going to need a whole lot of icons which have to come from somewhere. If you're not picky about what they look like you can find some icon set like

https://icons.getbootstrap.com/

which I picked for my RSS reader because I am using Bootstrap CSS already which itself is a low-effort choice because I use Reactstrap at work. Somebody pickier could look at free and paid icon sets or hire a graphic designer which would involve a significant amount of talking about how you want it made.

I am mainly a coder but my exact responsibilities have varied a lot from place to place. YOShInOn, my RSS reader and intelligent agent, is a one-man show which eliminates the overhead of communicating about things but means I don't get the benefit of other people's insight. I worked at an academic library where my first assignment was to take a very detailed Photoshop comp and make HTML that looked exactly like it. In other places nobody told me how it was supposed to look, or it was obvious from the get-go that I was supposed to add a new field to this form and it is going to have look like the rest of the form. I worked at a web development company where I worked on about 70 web sites in 8 months and we did projects very fast and cheap and forms that we made from scratch always followed a style guide we called "spider forms" which meant we could get better-than-average results without spending much time thinking. Where I work now I don't make decisions about the database schema except when I do, other places I was basically a DBA.

So the point is a "coder" can have varying levels of responsibility for UX, business rules: they can get very vague descriptions of what it supposed to happen and they figure it out, or I can get very detailed storyboards for everything. One way or another a lot of design and planning work has to get done.

A "low code" or "no code" system, whatever technology it is based on, is going to have to have a lot of decisions already made for you within some particular domain. Most of the worlds' business applications involve filling out forms and updating a database. But you might want a toolkit for making games that look like The Legend of Zelda with very little coding, or maybe something for making applications that put objects into your space with a Hololens or Apple Vision.

You could bust out apps really quickly if you take the defaults in a domain but if you want to make something really special the sky is the limit for the talent involved. Take a look at the credits for a major video game for instance.

Bootstrap Icons are packaged up and published to npm. We only include the processed SVGs in this package—it's up to you and your team to implement. Read our docs for usage instructions.

Vuejs

Vue.js is a big favorite for making websites because it's easy to use and fits in well with other stuff. Many people worldwide are using it, and the community keeps growing.

Vue has a thriving ecosystem with a wide range of third-party libraries and plugins available for extending its functionality. These libraries cover everything from state management to routing, making it easy for developers to find solutions to common problems and enhance their development workflow. As of this writing, Vue has 200k GitHub stars.

6. Vue.js

I have got the privilege of working on Vue 2 couple of months ago and its really amazing framework to work with .

Angular is as little innovative for web frameworks as Firefox-ESR is for browsers. It merely keeps copying features from other frameworks - just many years later. It is a chronically outdated framework that always struggles to keep up with its competitors. It would be ok if those were deliberate design decisions, but if the features get copied some day anyway, what is the point? Why not do it the right way from the start?

For example, this update brings us computed properties, an essential feature for any complex performant web application that was made popular by Vue.js 10 years ago [1]. And now in 2023 we get it in Angular, essentially a confirmation by its devs that its lack has always been a design error.

I also cannot understand the "mature" argument. For example, it took five years for documentation on `` to arrive [2]. This is something I'd expect from the side project of a lone programmer, not an enterprise-level framework.

The only upsides of Angular are its "batteries included" approach and the (debatable) default of RXJS, while the downsides are plenty.

[1] https://github.com/vuejs/vue/tree/218557cdec830a629252f4a9e2...

It's down since months. https://github.com/vuejs/vue/issues/11867

{ "user": "vuejs", "repo": "vue", "url": "https://github.com/vuejs/vue", "stars": 201555, "description": "🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.", "topics": [ "javascript", "framework", "vue", "frontend" ], "label": "repository", "commitCount": 3544 }

Vue.js is a progressive open-source MVVM frontend JavaScript framework that is designed to be implemented incrementally since the core library focuses only on the presentation layer. Nevertheless, this framework is used for building UI (user interfaces) and complex single-page applications with modern tools and libraries to support them. It enables you to take advantage of libraries for client-side routing and state management when you need it.