"Whatever you've just done wrecked the system mate."

@nitwhiz Fking hate to elaborate

@yehaaw True, could actually be worth to look into.

> npm lint

I'm still contemplating if I actually should. I like my team, but the stack sucks.

This guy is husband material.

Every open source project has some ideas and values, you can't just come in guns blazin' and change their api if it doesn't fit you.

I still have no Twitter account for this reason, creating one now seems like such a daunting task :P

Rather this, than "TODO"

@yehaaw it actually pisses me off that a lot of things you google instantly result in a StackOverflow question, you actually have to search for the docs

Notion is great.
Obsidian is an open source alternative, that is also great.

@Crost i need a devRantRant, I want to rant more about the things I read on here then my day to day coding experience, maybe I should just leave this platform

@i-like-foxes
I don't understand your points tbh., but this isn't going anywhere. If you hate it, then hate it.
I wish you the best of luck in your development career.

Congrats. Your library looks really good, might come in handy some day.
The code is also very clean, I like it.

Omg I want this for our services

@i-like-foxes Well obviously your codebase will be different, and you can always add on top, but the fundamentals are always the same. React is much more "low-level" than Angular.
Components, Services, Modules, Interceptors, Pipes, Tests, HTTP Requests etc. will always look (except for its contents) the same and anybody will know what to look for, and what to expect when opening a file.

@martin-juul React is a library. NextJs is a framework. React does not appose any structure on your code, neither does it tell you how to solve problems that might arise during development of an application, like routing.
With React you build your own framework.

@i-like-foxes I don't know what type of observable you mean, the HttpClient does not need, Forms do not need it, the Router does not need it. If you have your own RxJs Observables that cause leaks that's not Angulars fault.
My point is, that Angular has a definitive way of doing things. Everyone that joins a project knows what to expect and can quickly start developing as long as he knows the business use case. With React, there is so many libraries, and architectural patterns you may choose, that you never know what the application might look like at the end. Especially for beginners designing applications, this kind of flexibility is not actually a good thing. But you might disagree with me.

Me programming:

Every single thing in Angular automatically handles its garbage, if you have memory leaks that's your fault.
Angular and React cannot compare because they are not supposed to. React is just a library for reactive components. Angular is a web framework.
If you want flexibility, and ease of use, use React, if you want robustness and team scalability, use Angular.

@12bitfloat It's probably personal preference but I have to agree. When I write code I do not think about the exact data type I need to use, so laying down the things that I need, without having to break the flow to consult the strange api I'm using, as to which representation it wants me to use, is such a nice way to code. Data and logic are two pieces of a puzzle, and I like being able to separate them mentally.

@ojt-rant HA that's the exact reason why I really want to try it, I love its syntax.

if you ever feel useless: remember that this rant exists, which you read, scrolled into the comments of, and got pissed. Value your time.

Mine's called senpai.

now

Why Java?

It's all fun and games until you get a match.

Or that libraries now actually care about the developers using them and provide useful documentation and tutorials.

Quality meme... on devRant... pretty sus

For me it's the other way around