I'm not entirely sure this is true. In 99% of cases yes, but it's the developers who cause the problems. I've worked on a very complex app written in vanilla JS, and all we had was a "helpers" file that was ~2000 lines of code, which made common js problems (like creating a node with classes easier). Everyone was taught to use containment modules that resolved promises, and you could chain these promises to do some really cool stuff without worrying about the timing of loading assets, database latency, user interaction ect... The app had a heavy use of WebGL and Wasm, and the initial developers found most frameworks got in the way of dealing with these technologies, so I'd still argue vanilla JS has it's place. As long as you can create proper subsystems that don't explode into your own bloated mess of a framework.

This just motivates me further towards making another shitty JS framework

on point

Well, if you build you own framework, but don't share it .. it's called "tooling" and is what i do :)

@@herrbasan xD there is no such things. If you create a concept or structure or system whatever you call it, its a framework. keep it to yourself or share with other has nothing to do with it

It might seem stupid, but it's pretty much the only sane thing to do

hahahahaha

I'm in the same boat, actually. The DOM has come a long way in the last 10 years. Example of a few things we have now: querySelector, insertAdjacentHTML, data-xxxx, css variables I think it's possible to have a small, lightweight "framework" where all the hoopla is just handled in the DOM and the documentation is MDN because it's just DOM. I could be wrong.

"I need javascript" It's already too late, man. At this rate, you're not gonna make it.

gonna file tons on issue for this

I am at point 2 right now and want to step into web 3 development eventually. Would any of those frameworks suffice or is one better than another. I see more developers using react online and they've begun using next.js as well.. There's always new libraries popping up and its overwhelming.

​@@mona-xf5mr React, Angular and Vue have been around the longest and aren't going away any time soon by the looks of it. Jumping on new ones as they pop up can be exciting, but it's not feasible for bigger companies. Changing a library means the entire staff has to have time off actually writing code, to learn new languages, unify their code and make it work across the entire app. Like Leon said, pick one of the three and go with it. Choose the one you feel is the easiest to work with. You can always change down the road when you master one, as it will be way easier hopping over to another at that point. I'd also focus on one solid project, like a bug tracker vs making 5-10 smaller demos.

I started learning vanilla JS, building smaller apps and such. Leveled up React later and used extensivly, including NextJS. Did this for a few years, then applied for a job that used Angular. Never touched Angular before in my life but with all my previous background, it wasn't too hard. Had a solid understanding of JS and components, some new things to learn how Angular does its thing, but passed the interview and got hired. So now I'm an Angular developer. So point is, if you have solid understanding of the basics, you can switch between these frameworks quite easily.

@@JamieRso after learning html css and js, go straight for react?

yea exactly. Because if you become really good in one framework, then you will know it's inner workings and will understand decisions why framework do things it does. And next time if you need other framework, it will be easier to pick up, because you already went in depth in one framework and understand why it's made it is. And after all, HR only sees what you can build, and not that much what tech you used (ofc they look at that, but if they see that you managed to do something impressive with some framework, then they have no doubt you will be able to do same in that other framework as well. Like, if you build spaceship, they will be impressed, even if they ask for React job, and you did it in Svelte. It's still hard work, and requires a lot of understanding and headache to work with framework, to understand everything to build it. They will hire you, because you are talented, and you will be able to make same spaceship in their framework they use.

Then fourth dimensional traveling WEB3 microinteractable clusterfuck becomes a trendy idea amongst designers and then you have to create your own framework.

That's why you pick the most popular one that will most likely be maintained the longest so it's easier to find documentation on it and get support. They all do the same thing.

C'est la vie.

Agreed

Have you run into any particular edge cases with React?

Interesting fact: this joke is old and overused.

I made a full fledged web app using phaser 😂

😂

I read this comment while I was waiting for the ads to end. I hadn’t yet watched the video, and you’re saying 3 JS frameworks were released? In literally no time flat!? Because that sounds accurate.

@@Angerfist1996 username checks out Edit: oh I thought it was "AngerFirst"...like you're an angry reactionary. oh well. Still fits.

@@Drpanda533 react is good but I hate Facebook, so i don't use it

@@Drpanda533 vue has shortcomings and its community is not able to support it as well as react ? does it feel like this using vue ?

@@NotTheLastOne you're wrong. And yes I do.

Agreeee

Absolutely agree! Thanks so much for taking the time Fireship! Actually seeing the same app in action all these frameworks is an absolutely superb way to demonstrate strengths and weaknesses

.NET?

@@afsstuff472 yeah

@@afsstuff472 Definitely, it's not. do your search and you will figure out that Microsoft is updating it yearly and it has become widely used at top notch companies as it became cross platform and doesn't run on windows only anymore.

I must study about it. I entered Software Engineering 6 months ago only. I don't have much knowledge.

@@afsstuff472 It's ok dude. Keep going, wish you the best of luck.

Hello world?

@@tranceyy A little more involved than that 😉

@@broomybroomybroomy it might be because you have already built that path in your head. Remaking seems like it's always faster, than building from scratch...

@@tranceyy That would mean Hello Worlds take days in React

@@oscarpetersson5324 But the penalties of not knowing the new framework should largely overcome that

Even shorter with playback x1.5 :)

@@Pthphap I put it on 2x and slow it down to .5x when he's talking.

@@Pthphap cant watch in x1.5 :(

on the other hand - since no one knows how the framework you are using works and what job you are actually doing - it is easy to be a frontend developer as no one controls you and you can put any estimate you want :) that's not a joke. One PM friend of mine always complains about fronted devs - they take always a lot of time and he cannot control them :)

@@kostiatretyak A major problem of the tech industry in general....

why? you need to only know 1 and you are good to go for most companies. its often react or angular or vue and they will often look if you know any of these, not all or the one they need even at times.

What did u decide! Backend""-" ?

Shame on you! We are into that

is your framework ready?

@@hankersoree yes but the world is not ready for my framework yet 😉😌

*slow clap*

I was just going to submit the same comment

i think it suit backend engineer also right?

@@davidchandra8722 No it's for frontend only

@@sumitpurohit8849 what i mean is, its easier to be used by backend engineer since it focus more on basic html and the svelte itself. No need to learn new workflow/beviour like React for example

introduced in Vue 3.2 looks kinda similar to svelte

Depends really. Svelte is ultimately a compiler with associated syntax which is different from both Vue and React. I like that fact because we have enough virtual DOM frameworks out there and for less complex projects having a virtual DOM with an associated engine is so overkill in complexity it’s not even funny. Personally I go React where I actually need actually need complex front ends or a really broad ecosystem like electron or react native. Everything else I go to svelte. TLDR for that reason I think if you’re from the backend world you might be best off starting with svelte because there’s a lot less complexity to manage. But something like react is good to know eventually because as fragmented as the JS world is it’s about as close to a lingua Franca we’ve had since jQuery

Really hope it goes viral ! Not just for hobby projects but in serious stuff too

Just need more people to start using it so there's more material online / better docs / more bug fixes.

my heart says svelte but my wallet says react :(

@@andrewcathcart I think the docs are great and the tutorial is even better though it never used it haha

@@lored6811 I feel that. I never really got into react but I'm tempted to build stuff with it just for the resume and potential job. I feel it's most likely id go for Vue though since the syntax is a little nicer in my opinion

I’m not trying to argue here & I don’t use ng, but I find it baffling that it is always pitched as being for large projects/teams. Is that because even a hello world has 100 files & you can therefore have 100 developers working on them? .. ..maybe a slight exaggeration there, but the structure just makes it too overwhelming for many, even though there are seemingly some good features (especially the cli, that was good even when I tried it years ago).

@@everyhandletaken The people pitching it for large projects/teams are speaking from experience. I built my team a couple of Angular libraries that make refactoring our complicated legacy system into single page apps a breeze. You don't have to worry about the file structure when your building blocks are encapsulated behind an npm package. The libraries themselves are modular enough that they are pretty flat and easy to step through and have about 80% test coverage. React is better as a pure UI framework, but it does not scale as well the way it manages state, lacks dependency injection and test-driven design, etc.

@@everyhandletaken automating linting, formatting, and testing with CI/CD pipelines only takes you so far. No need for 100 devs on a single project for it to become a PITA. Even 5 devs could cause merging issues in SC given that SC isn't being used by many companies as intended, especially ones where there are over ten long-term branches. Add in a backend like Django and/or Flask, things get even more interesting. Opinionated structure is a GOOD thing. Think of it like a standard operating procedure. The military has SOPs for a reason. This allows a plug and play with anyone replacing anyone. Ever try to work behind another free-form developer? Or try to fix something someone already had their hands in? Mechanics generally don't work on the same car behind another mechanic. One starts the repair, the same one finishes it. For good reason.

@@wilkes-barrescrantonsentin7401 ok

Angular is of course the best frontend framework currently available. These "Hello-World" comparisons have no significance whatsoever. I have never experienced a customer ordering a "Hello World" app :D. Basically, for simple apps, the physics of simplicity prevails, thus technology or processes plays a minor role. The main problem that I have experienced over the last 14 years especially with frontend developers, is that they have little understanding of principles of software engineering, and rather prefer chaos code that does not apply to any intelligent design rules. What you'll find in Angular are fundamental concepts of software engineering, nothing more! Hence, I recommend to learn software engineering first, and then Angular!

why it can't be 2 screen mirroring and , he might be copying everything from the other one.

@given I use vitejs for building svelte and never have problems with building

@given sveltekit

💯💯💯

I'd recommend avoiding Svelte at all costs personally. It's very enticing because it easily has the best syntax and format for defining components, but after using it for a while in a real app I was so frustrated I nearly gave up on frontend frameworks altogether. It has two major problems. First, while the syntax is the simplest to grasp, all the stuff it's doing under the hood with the compiler makes it very finicky, easy to break, difficult to debug, extremely complex, etc. Everything I did created an often nondescript error - not in my code but in engine code - and I could never get my IDE to reliably stop at a breakpoint and step through the code. I ended up spending half my time just fighting with the platform to get it to compile. Second, and even more serious, they have a fundamental design decision that makes it take longer to develop in than normal js code. The components themselves are just invisible wrappers removed at compile time (so you can't target them in CSS) and they purposely make it very difficult to style anything inside the component from outside it. They want you to write a property and expose it for anything you want to change inside the component - which just isn't realistic to work with. Want to position your component in the UI? Wrap it in a div and target the div and hope the children don't require any special positioning styles. Want to target the children inside your component's slot with a few styles? Wrap it in a div and target the children of the div. Worst of all, want to create a component that's a button with a little extra functionality but still want to be able to style it? Have fun rewriting every single style property a button has one by one in a long list - and even then you can't apply a class to style them. They're just properties on the component.

@@dillydadally wow, i now understand why most people search something they can crush with their hands instead to break apart the machine to know why the automatic proccess did not do it good.

I've used Svelte for 2.5 years now with the Routify library for routing. I found both Svelte and Routify very easy to get into and use. In that time, I've only encountered one bug with Svelte and it turned out that they had already found and fixed the issue and I just needed to update to the latest version. I haven't experienced the issues with styles that the guy above mentioned, because I tend not to have inline styles in the component. Instead, 1) I used css from a template I found or bought online - so basically I already had all styles I needed in a global css file and just needed to use the right elements and classes in the html, exactly the same way you would if you were building a webpage with regular HTML/javascript. I did this on my first 3-4 projects. 2) Since then I've started using Tailwindcss which gives you loads of helper classes to style anything the way you want (and is also customizable if you need more), and follows the same compiler mindset that Svelte does, where your css file is compiled using only css classes from Tailwind that you're actually using in your project, rather than having a giant css file of everything from a template like I was using before. Been using that for 9 months now and I haven't looked back. There is also the new SvelteKit, which is an official library that has routing etc. I haven't used it yet so can't comment, and haven't really had a reason to switch since I'm happy with what's offered by Routify. The downside is as per the video, Svelte has a smaller community, so sometimes when looking for a library to do something you want, there isn't one available for Svelte. However, since your code is compiled to vanilla JS anyway, you can simply find a library for vanilla JS that doesn't have dependencies on say JQuery, then without much effort just make your own component that uses that library to have the html elements/inputs and javascript to do the init/destroy/etc using that library, as well as the props that you want for configuration and binding, then you use that component wherever you want it in your application. Also, I guess this applies to all the frameworks, but once you've made a component, you can just copy and paste the file into another project and use it. So the more I use the framework the quicker it is to get new projects going.

@@reikooters Honestly I need to follow up on my original comment a little. I've used Svelte daily at work since I made that comment. I realized a couple things. First, I learned Svelte and Sveltekit together and didn't really separate the two in my mind. Now that I have, I realized most of the issues I've had related to debugging, engine complexity, and finicky behavior is mostly Svelte-kit and not Svelte. A lot of it has to do with the poorly written load function and strange behavior around the soup of static, SSR, and SPA rendering. Svelte-kit at this point is still not even version 1.0, so some rough edges are expected, and they just announced a big rewrite before 1.0 that is going to address some of the issues I had, (such as the aforementioned load function). Still, the official browser tools are abandoned and don't work and I can't get debugging to work properly in my IntelliJ IDE. There's a debugger keyword that lets you pause execution, but it's not ideal. Again, these issues might change as Svelte-Kit matures. Second, I stand by my original claim that the component structure of Svelte is monumentally stupid when it comes to targeting and styling components in the same way you would a normal element, as well as having to expose properties of underlying elements one by one rather than just extending one of the elements. Judging by the complaints and thumbs down on comments by the devs about it and the massive amounts of issues opened about it, I'm not the only one. There's a proposal that is being considered that might make this better. Having said that, if you just use Svelte and not Svelte-Kit (or wait for it to further develop), and you find ways to work around the component styling issues (i.e. use Tailwind and never target the components or add classes to them), then Svelte is very good and probably the best thing out there.

​@@dillydadally I spent over a year working with Svelte and agree with the first issue but not the remaining issues. The first problem with learning Svelte is that you have to learn the good and bad ways of doing things. For example, don't create components having state that varies by page, instead embed a new component per page with page-specific state. I found state management pretty easy for the post part, but every once in a while the magic under the hood gave me a huge headache trying to figure out why things were misbehaving. Sometimes I wasn't sure of the right way to arrange state and ended up duct-taping a solution that passed the tests despite my not understanding why. On the issue of styles, it took me a while to learn that the sharing named CSS classes across pages was not suitable for Svelte or any component framework. Rather, in component frameworks, style should be local to the component. In fact, the way you establish consistent style is by defining components and using those components consistently. What style would you like buttons? Figure it out and make a button component, rather than define it in CSS for reuse across different button renderings. This is a best practice across all component frameworks, not just Svelte. The popular tailwind CSS library takes advantage of this way of developing components and can only be used this way. I used Bootstrap for that project but swore I'd use tailwind for subsequent component frameworks to make my life easier.

Flutter all the way..

KMM soon

Actually i like react native because java is big scary idiotic slowpoke shit

@@Gameplayer55055 3 billion devices says otherwise

This comment needs more likes

Me too now :(

How do you use libs for the ui like material ui?

Now I think Vue us better than Svelte

No offence but, your statement is the epitome of why frameworks suck! Stagnation because something "new and shiny" comes along that DOES the same bloody thing lol!

@@encoder6717 I don’t believe in the scarcity mindset. If svelte is good it should grow, but just because it grows doesn’t mean other frameworks die. All the good stuff should catch on IMO. Established frameworks aren’t going anywhere unless they stop being useful for solving problems.

Yup

I’m with you

Why would having lightweight JS in HTML be interesting / relevant for a backend dev? Multiple front end components in one place?

@@senmingwu It's because we're often already very used to dealing with raw HTML, so just "adding on" a few things isn't so foreign as switching how we think about how the page is shown/delivered---i.e. messing with components/client side routes/virtual DOM/etc.

@@ruhnet Ohh, thank you!

When I was watching the video and heard "There is no way to see if this form has an event listener attached to it...", your comment was my immediate reaction. Edit: Just so you guys know, I left a comment explaining what a lot of people seem to agree about his JavaScript presentation, not being fair while I explained my choice using my helper libraries with RxJS in the most maintainable way possible, without creating my own framework. Guess what, he deleted the comment! So I guess this channel is misrepresenting JavaScript or being a sellout for some frameworks. Was going to subscribe, but if he deletes people's opinion, then I'm just gonna select to not recommend this channel for me.

Doing it this way means you're adding your functions to the global scope which is not a good idea

Lol I told him to use a web component but this blows my answer out of the water nice dude

How about using onclick to call a function?

@@mosesnandi inawezekana but iko considered a bad practice

Maybe you find frontend a chore because you're using Angular 😂

Coming from React, I find Angular to be such a chore, especially when you wrap Ionic on top of it 😂

I completely agree. I used to work with Java, but decided to learn angular simply out of interest. Coming from the Backend, it's really amazing. TypeScript is the best thing to happen to JS in my opinion, and I really like the strict and logical way Angular apps are structured. Also, the fact that it comes with so many things like routing is nice, because I can just use what was intended and therefore works instead of having to make decisions at every point about what third party library to use. Yes, it's less freedom than with other frameworks, but more freedom of choice always comes with more freedom to fuck up as well, so that's something I can live with.

Different design philosophy, these simplifications may be a mental burden for novices

Noticed that as well, vue 3 is better but its a bit fragmented and confusing with the multiple APIs

you havent even watched it..

@@ccost yeah thats why i say "excited to hear your opinion" and not "i agree with you" :)

@@ccost 😂😂 true

I am only 5 words into your comment and really impressed with the way you use the language.

As a complete noob: yes.

Agree

Agreed. A lot of concepts in other frameworks would become clear if you start from vanilla JS.

No, the state driven & declerative approach of e.g. react is a completely different way of thinking & probably superior

@@johannes.schaffer True that! React is really different than vanilla JS but if you had some experience with functional programming then it comes easier,

link please?

problem with web languages is how vague their data are. when you need to loop through something, an array is always faster than map. If you need to search for something, a map is always faster. If you need to loop through but add and remove elements on the whim, you want a list. but to web languages whenever you define an array, its a map.

@@System0Error0Message this comment is not referring to maps/hashtables as a data type, this is about the map function that applies an operation to every element of an array

Adam, you use React right ? 😏

I think so too, it feels like an evolution Vue -> Svelte React -> Solid

Pardon me, but I love your photo profile 😍

@@mrsurver1890 beluga?

@@butterfly7562 My thoughts exactly. When I was taking a quick course on Svelte my first impression was "wow, a Vue that works". Also, Solid looks amazing. These 2 guys should get more attention from the dev community, they are really amazing takes on their predecessors.

well this is very basic stuff

I don't want to sound uuh... But this was like the readme page of each of those githubs. Maybe second page of google level

@@goeland4585 It is not that hard on paper, but honestly doing it 10 times while explaining everything is nerve cracking.

Most of us don't have the time to learn 10 frameworks, basic or not..

Yeah, Vue 3 is awesome. :D

oh didn't know that, thank you

Wow, I just ditched Angular and jumped to Vue for this reason. NOT!

@@muhammadhassankiyani8953 no one asked

yes svelte is a lot of fun to work with

I like Angular structure but I hate the insane amount of files it generates for one component, so that's why I prefer Vue instead.

Working with Angular daily, and Vue for my alt projects. I have to say I prefer Vue, the footprint for Angular is massive, and although fine for an app, it’s just not a catch all for web projects. Vue is flexible and has a good sized community, it’s also independent so no corporate overlord behind it. It’s also way easier to get going with it, as the learning curve is way lower.

@@OzzyTheGiant I agree, that's also a reason why Svelte catches my eye. You put everything in one file while separating html, css and js like angular

Angular is for real work, others are for fun. A big and long project using react or others will be impossible to manage on medium/long term. Angular was built for that, ive been working on enterprise projects with Angular for about 4 years and will keep doing so until the framework dies.

Composition API is also nicer imo

Same

Same

Same

Same

Same

100% agreement with this. Since their rebranding earlier this year, Lit has shown even more how capable it is of handling more complex applications on its own. I’d encourage every UI/UX developer to try it out.

How is Stencil and Lit different from React when it comes to creating custom elements? Why not just do it with react?

@@emonymph6911 It comes down to native support for me. Web Components, Shadow DOM APIs and are meant to be a native way for your browser to handle your own fit-for purpose functionality, and native is generally harder to break long-term (even if it's not initially easier to build). I only have Lit experience, and the way the tagged template literals work is very intuitive.

Composition API

This is exactly what I was thinking, I just finished converting all my components over to script setup syntax and it's so easy to prototype new components and work on old ones. I have to wonder though...did Evan You take inspiration from Svelte or was it a happy coincidence? lol

@@Aedaeum He did. He always makes his inspirations clear. When Vue 3 Composition API was announced, the RFC included a comparison to Svelte. *After* that he came up with and it was clearly an answer to Svelte

true 0 code = no bugs

The idea is to simulate what js frameworks do, and state management is one of them, so that’s why he made it like that

You also just add an id to the form which is descriptive. Personally, the vanilla javascript is the best in this video.

@@marc_joan Maybe, but IMO the main idea is to build the app that does the assigned task in the best way available in given environment. And ignoring convenient features of the environment and doing things roundabout way just to simulate other environments does a disservice to presenting that environment. If you have a wide collection of hammers and nails, smacking a screw with the handle of a screwdriver will sure prove the screw is a lousy nail and the screwdriver is a lousy hammer...

​@@marc_joan Why simulate how frameworks do when showing how to do with JS directly? Doesn't make sense. He's comparing how to achieve with different means. He's not explaining how frameworks execute the work. You can even notice that he doesn't really solve most of his complaints. Sometimes even, he says a framework is OK, even though they have the exact same problem that he complaints about vanilla JS: 1:56: If it's so, then just use the on* attributes 2:54: Why is he doing it like that?!?! There's so easy ways for the li tag. If he doesn't like createElement, he can use tags 3:05: He never shown a way to keep it coupled. As in: the HTML is the source of truth etc... Even though it's usually called "Vanilla js" it doesn't mean "no libraries allowed". It just means the syntax and such is by using javascript and then DOM. With or without a library to assist with the process.

@@flipsnap I think his vanilla one is done in a way that shows he's either being deceptive or he just doesn't know (potentially out of practice) how to leverage the HTML and the DOM framework.

But at least in this video... another limitation might be that he doesn't know the basics. You can add onsubmit on the form with plain JS too (one of his biggest gripes with plane JS).

Hehe - just say you still love Ruby on Rails (still awesome for back-end) and developer happiness.

@@aviral1841 I learnt react as well, both the class based and the latest function based component and its just so complicated to use all the different hooks. Angular has a lot of stuff built in so it takes less time deciding basic stuff.

@@aviral1841 I don't feel comfortable with writing Jsx for my views(html). It feels like I don't have control over the app. In angular or any other framework, they give us a way to integrate Js in HTML, which feels comfortable. Maybe it's because I have worked with vanilla HTML CSS JavaScript too much and hence am habitual of seeing an HTML file as a control hub.

For serious things, use Angular. For playing a bit with JS, use Vue or React xD

It was a steep learning curve but now everything makes sense.

@@ProjectExMachina Exactly. Whenever you finish learn Angular, the other frameworks seem to be incomplete.

Another thing to consider is what companies in your area are using, which may help you if you are developing to get a job.

Considering he is one of the few people who speaks as quickly as he does on rather complicated subjects and you understand everything he says, I would say that you are an English speaker (even if English is not your mother language)

Aay three.js is awesome

How do you incorporate nicely threeJS to Angular ?

@@thommetsacha4462 just import it and use it in your components and services?

No need for Angular to use firebase and threeJS

I am one of them. Ember is the best! Ignoring Ember in a JS framework comparison is like ignoring Rails in a Ruby framework comparison. Ember is the most productive front-end framework IMHO. 👆ALL THE GOOD IDEAS HERE WILL END UP IN EMBER. ITS JUST A MATTER OF TIME. ukposts.info/have/v-deo/e6arYW-ampydrIU.html

@@DhakshinDooliv no !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

Die hard users? You mean hipsters.

@@carldrogo9492 lmao good jest.

Totally agree. Lot of articles say that it has a "steep learning curve". But honestly...If you studied programming or you come from a backend language, there is nothing complicated about it. You create a component, a service, using dependency injection through the constructor and you are good to go. You dont even have to know RxJS or more complex pattern at first.

I think it gets more complicated as soon as you need some native js lib, because you have to step out of the ng-zone to prevent change detection from. running wild. The same. is true for fast firing events like scroll, touch, mousmove. I really love Angular, especially the dependency injection and the fact that I don't have to install a lot of packages, but some stuff is just to complicated. Like programmatically creating an Component with the component factory and. inserting it on the top level of the dom. This should not take so. much code and be so. complex in my opinion

I would definitely lean towards Angular, but only if it figures out a way to do Single File Components like Vue and if the template syntax isn't too complicated

@@OzzyTheGiant Hi There! Well... Angular actually has a way to do this. You really only need the typescript component file, an instead of pointing to a html file for the view & scss file for the style, you can just write them inline within the component's decorator properties. Of course, I guess the dev experience is not that nice since I believe you don't have intellissense features on VSCode for doing this inline on the ts file... Despite being quite strict on doing things the Angular way, I love it!

@@OzzyTheGiant You can use inline template and css in Angular