React / Angela vs Jquery

Every year the js community is like "yo check out this hot new framework/library that's gonna solve all our problems!". Next thing you know, everyone's jumping on the hype train, rewriting their whole codebase. Six months later, half the projects are abandoned and we're left with a ton of legacy code nobody wants to touch. It's wild how we keep doing this to ourselves. one minute we're all about angular, then react, then vue, now svelte... don't even try to talk about the state management circus.

That's just how we roll in js land. gotta keep it spicy, right? At least we're never bored and get that novelty effect and excitement that especially immature people LOVE. Who needs stable, maintainable code when you can have shiny new toys every few months?

You see all these fresh-faced devs straight outta bootcamp diving headfirst into the js ecosystem. they're all about that instant gratification, spitting chewing a hamburger: "look ma, I made a todo app with 50 dependencies!". Meanwhile, the old guard is chillin' with their python and C. They've seen some shit, been through the trenches, had a company, had a real world job and developed a real product. They're not about to rewrite their whole stack cause some dude on twitter said redux is out and mobx is in.

When seasoned devs do touch js, they're like "nah fam, we don't need all that noise." they bust out some vanilla node.js, no fancy frameworks, just pure js goodness. and somehow their stuff still works better and faster than some overengineered, intertwined monstrosities. Kinda makes you think, right? maybe we should cool it with the framework frenzy and actually learn how the language works. but nah, that's too boring. Gotta chase that next shiny thing.

The js land is stuck in this never-ending cycle of problem creation. Every other day there's some new build tool or paradigm dropping on github. webpack, rollup, parcel, vite. It's like we're collecting them or something. There also are all the "-first" approaches. we went from mobile-first to api-first to jamstack and now it's all about "ai-first" development.

Meanwhile, the C crew is over there actually solving real problems. they're optimizing compilers, improving system performance, and writing code that runs entire operating systems. you know, actual computer science stuff.

In the meantime JS kids are busy arguing about whether to use spaces or tabs, or if semicolons are still cool. They create problems just so they can solve them with a new npm package. They say "hey, check out my new library, it adds padding to your strings but only on Tuesdays!". It's like they're allergic to stability or something. The second a codebase starts to settle, someone's gotta come along and suggest a complete rewrite with the flavor of the month tech stack. It's just a kid thing. One they those people will grow up and focus on actually building stuff that lasts, but until then, React is still yet to introduce a compiler or a new js framework that's totally gonna revolutionize web dev this time. Oh...

New version of language inspired by C to read about something that's actually interesting... https://en.wikipedia.org/wiki/Zig_(programming_language)
Not Wikipedia is interesting, just that Zig. Maybe there's a way to write something cool in it. I mean useful.

Then start focus on something real like debugging instead of reading some dumb patterns that everyone can notice after 3 days of coding.

Here's first lesson.
https://nodejs.org/en/learn/getting-started/debugging

If, as a solopreneur, you plan to focus only on product packaging (i.e. frontend), you're severely limiting your potential. Think of it this way:

Packaging products is like painting a fence - it looks cool, but it doesn't build you an empire. By focusing only on that, you're putting a ceiling over your head. And the ceiling here is really low. The max you can get out of this approach is about six figures a month. And that's at best if you're also very pushy at sales and are able to lie to your clients about advantages of having a frontend with more controls which in fact is just more distractive.

Too see "the beauty of frontend" (irony) just go to Google Analytics and try to use it. Maybe someone likes it if they don't know anything about simplicity, but that's not for me. It's like spam of data I don't need and just stuffed 100s of things that make it impossible to focus for me. To use that I need to write down first what I want from it, otherwise it's counterproductive and it wastes my time.

A strong reliance on front-end or a framework or a CMS means that:
- You'll be stuck while others build powerful systems.
- You'll be constantly chasing new customers instead of creating something that works for you.
- Your business will depend only on you - if you get sick or want a holiday, the highs will stop flowing.

With a solid backend you have a system that generates value, creates content and collects real data from certain data-points that aren't chosen by a 3rd party where the data is further analyzed by a dumb, proprietary algorithm. This may be harder of course and I wouldn't recommend if you're 15.

Who wants to package products for life? It's a job for a few months. Send it to India or Pakistan. I can automate front-end though. So either outsource it or put some automation in place if it's possible. But once you understand that you can simplify it, you probably can just automate it, and probably even improve UX of your stuff because that's what happens when you reduce UI complexity you improve UX.

Now if you're a corrupt corporation stuffing 1000s of features into one view, I'm sorry, but it doesn't match solopreneur stuff.

Writing just 3 back-end functions with Node.js took a whole fucking week, despite constantly reading docs and taking notes, watching videos, and all that shit. Even after coming back to the code and re-reading the docs, the same goddamn problems persist.

The documentation is a joke - no visualizations, no learning aids, nothing. It's like they took C, stripped it down, removed all the substance, and called it a day. It's a complete fucking farce.

Trying to write code in this mess ended up with only one thing working smoothly - a front-end build tool that generates 1000 landing pages a minute, probably an idea worth 100 thousand dollars, right.

But the backend? It's melting my brain. I took child_process and coupled with other things in there, it's very, very, very complicated.

I remember I was writing backend in Laravel and C#, and it was what... it was simpler. Oh no. Why? Because...

Writing backend in Node.js is like taking C, slapping on 2-3 layers of abstraction, and making the whole process of writing algorithms 6 times more complicated with all this "async/await" bullshit. I never asked for this crap, but suddenly it's in my project because it's "trendy".
It's like they took a perfectly good language, fucked it up beyond recognition, and then told everyone it's the next big thing. What a load of bollocks.

So in conclusion, node.js fits as a front-end tool to automate it.

Now, database operations and things that could be done procedurally at lower level with some amount of assertions? None of that I will ever do in node.js, ever again. It's too high level of abstraction for my style of work to comprehend.

Data structures in node.js?

• Tables? They're supposedly there, but when you want to do something more complicated, you suddenly find it's not so simple.
• Objects? Yes, there are. But try to do something more advanced, you suddenly find you've fallen down some fucked up rabbit hole of references and prototypes.
• Maps and Sets? Seemingly cool, but, why doesn't it work as intuitively as it does in other languages?
• Queues and stacks? Unless you like writing your own implementations or downloading some left-over libraries.
• Binary trees? You can do it in C straight away and import it as a module.
• Graphs? Well, now you've gone completely off the rails.

Ho... ho... ho... holy C...

I won't pay with my fucking mental health to write 50 functions in some fcked up environment where I can't find whether it's already using C or it's maybe PHP inside of some NPM package. It's like a mystery each time. It's like that mental illness - bipolar disorder - or some personality disorder -in form of programming environment / language. I'm trying to prioritize my health and wealth and freedom instead of this tightly coupled clusterfucking piece of genius architecture.

Please, don't confuse it with Puppeteer and automation. I said backend operations that are using external processes from C. It's not worth it to do C inside of JavaScript. Just no. I know you can learn it, but NO. I can instead learn how to do it on the ORIGINAL level and that's it, stop fishing with a rod that is too long and that's over-engineered or something like that. That's quite wise to start from a programming language, then a framework and I feel like Node.js is a C framework for javascript (wtf).

It's sick, if you change your goal, you suddenly have to admire that what you use isn't the right tool for the job.
I don't get how I ended up in this async / await stuff. What had I had on my mind when I started doing that. Maybe just some stupid assumption that it's gonna take me to the next level. I went backwards instead and that happened like 15 times lol.

I still don't get how people make 15 million dollars in their 1st month of coding (joke). I started 8 years ago and still see these crazy flaws. But each time it's like less code and more power? I heard that's about reaching that level when you write 3 lines and it breaks the whole database of Zuckerburg? Yeah, that's it!

I mean, if you started coding 8 years ago, what can you know? It's like being 14 and then 22. Maybe you can get a job but not code anything superb. Maybe in 7 years I'll build some real enterprise software. I don't give a fck.

Node.js is a 15 year old technology which means... it was created just around the time when Docker came out! Yeah, tell now people who do it they need to learn C first to use node.js. What a surprise. Then why use node.js when you can write C++? For one library. If you know C++ you can just fork some library and build your own stuff. There's no easy way. Forget about $666.666 without learning everything. There's no way to hop over this understanding of programming.

Previous generation created C++, and before that there was C, and then there was assembly and now they created Go which is... I don't know what to say, but I'm certainly from that C / C++ / Java / C# generation. Nothing after C# I can stand. Async / await code it's just too much code surrounding my code that I have never asked for and someone stuffed it into my workflow just because... that's cool in an enterprise environment that is stressful... not my fcking home.

@reaaski I am on the same boat with you it seems. I am using framework7 with jquery. Give it a try.

All the puppeteer and selenium is a CIA scam anyway. It doesn't work if you don't tweak it to some really granular level and most of the stuff boils down to sending fake signals which that framework doesn't provide.

That's fun to discover how to not be a kid that picks up random stuff and makes decisions based on assessment and analysis. Someone taught me this and they told me I can analyze stuff harder and harder until I find the solution without doing anything. Lol

Now I was trying to figure out some stuff about puppeteer and disassemble it but it wasn't that simple at one point I felt like some stuff was hidden. I didn't have time to research that further but it seemed quite confusing, like they tried to make people NOT see something...

Of course they did that for our own good. Because if we get too much money, it will harm us.

The truth is that if someone wants to get interested and is curious, they will write from scratch solutions like they give and learn more quickly than simply using these off-the-shelf solutions, which you have to take apart to control anyway.

Yeah, you can write synchronous code in node.js, but so what. Nothing. But, but but...almost everything is written in this async / await pattern included. Plus that you have to configure typescript. It's quite a lot of stuff. That typescript thing is little bit handicapped.

Not that switching backend stuff to C++ would be a problem cause that'd be just more fun than anything else. Just that realization is like waking up from a bad dream.

Anyone can publish a package to NPM and so... you can publish some ransomware and target devs. Wooah.... man... stop these truths for now. They're gonna destroy this world.

Don't make business applications if you want to see the world in a "colorized" way.

reaaski said:

Not that switching backend stuff to C++ would be a problem cause that'd be just more fun than anything else. Just that realization is like waking up from a bad dream.

Click to expand...

It's a problem to change anything in your life and that includes learning a new tool. So if you want to do that, do it slowly.

For now I'll remove async / await from my program in node.js and it'll pay off big time. Procedural programming and some weird multithreading is a classic workaround for those who don't give a fck like me about some flexing about async / await syntax. If you don't give fcks, you get mental comfort. If you give fcks, you get mental discomfort and extra pain / effort. Doing too many challenging things at the same time is a b1tch and it landed me in a mental hospital almost a few times, so I'm not gonna make that mistake again. Think of your core values instead of just "need to prove it". No, there's time to learn, apply and reinforce stuff. There's no need to hop onto new train just because you noticed a flaw in a previous one. Just change something small.

Since my program is one that is just a large procedure that runs on repeat, there's no real benefit to doing things in that style. And uhm... I believe it's completely possible to not use async / await everywhere and that's probably a mistake to use that everywhere. Huh, critical thinking benefits. How much stuff can you remove when you question and bring simplicity where it's possible is great.

I don't know about you, but for me what I've noticed my programs were smoother and less error prone without that await / async stuff. So... I'll just go to the old PHP style where that stuff isn't that pronounced from what I saw. I think PHP community is more mature than node.js one. They had to sanitize their input or they'd get hacked. There was more to that stuff than just putting "async / await" everywhere. It was more insightful stuff.

I feel like this is too complicated to introduce asynchronous programming into your program in the early stages and even further. It's probably just a convention of developers at this point more than a valid reason. Bad practices can be popular too and that's scary!

Instead of writing procedures, I had to think about 3 extra things that async / await syntax implies. Was that like writing a 6 levels deep nested loops. Because that async / await is something like using new Promise() and that has some serious implications. It's no fun like people think. Can cause serious headaches. "Distraction" - deep stuff, isn't it. How we can get distracted if we're not conscious.

Every line of my code had some implication that I'm in some "async / await" paradigm. What the hell. And there was absolutely no reason for that. It just became a habit. "Why am I so inefficient" - plenty of reasons behind that stuff.

Woah man, I was trying to do multi-threading and asynchronous in C# 2 years ago. That was a real clusterfuck. Experience is worth more than a 100 books.

What is more important is handling errors and not write async / await everywhere. Then there are also assertions to be written which are also important. And there's also a need to make a long term queue system without reliance on 3rd party tools and virtualization. The key is deep thought and not their tools created 10 years ago. You need a king - 0 dependency software - only low level libraries if any and you need a king. Neither intertwined with other software, nor any ecosystem, nor platform. Without 16 extra layers. Reduction of complexity to minimum. Removing corporate stress and lies from workflow.

Debugging + assertions vs async / await. This is time investment. If you invest in everything, you're gonna have huge costs and small returns on each thing. If you invest in what you value more, you're gonna have lower costs and better return from that one thing like debugging.

Huh, ever tried to debug 40k lines of code program written in node.js and had no real stack traces?

Now, I'm sure some people lost their jobs because of that. ;P
Yes, that was me. I lost my first (and last) software job once I had to debug 40k lines of code without real errors written and I saw that code for the first time. Everyone left that company eventually. Nothing there made sense. Well, just like nothing makes sense in this world, people just do "generators and yield" because it sounds cool. Or they'll do yield* X(). Or some "proxy".

They need a king which is 64 assembly and C. Understanding lower levels is like a soulful relief. I had a real mental health issue cause of that stuff. I even developed some problems with that horrible competitive community from Twitter / Reddit that doesn't get paid more than an average person and flexes left and right about how much leetcode / code katas they've accomplished. Man, that's building stuff, not doing math operations using code. Wtf is that!

I was more efficient with code when I was 14. Then I was introduced to "code novelty" and it was just this... getting lost in things that are irrelevant to real work and are only fancy tools for developers who love to learn new abstractions but those abstractions can't even return stack traces.

Now 12 years later I would be glad to still be able to write Lua and bash files cause that's where all this mindfuck disappears. People love to bullshit themselves and create that illusion that they've learned something new. No. You've just learned how to make something more complex, harder to understand and not future proof. That's the opposite of progress. That's called regress. And I don't know if regressing in your life by making it complex is some nice fun psychological game. Maybe it is.

Python had this advantage that you could just do it and it wasn't clusterfcked to that point. But it wasn't that good for working with DOM and stuff. Not that I liked that fact when I was automating web. 12 years just go back to square 1. Fcking crazy sh1t.

In a world where progress is falsified and you have strict deadlines, something like this may make sense assuming you're NOT the one who will debug. You don't care about pain of the person who will refactor? And you have a plan to get a new job and you're constantly sending 1000 CVs to the same companies? Wow, wouldn't figure that out. As a solopreneur, fooling yourself like that takes you to the graveyard. There's no way to hop to another project. Once you're in, you got to figure that out.

"One-upmanship is a prevalent phenomenon wherein people partake in subtle or overt competition to assert superiority over others."

Now, why would I need to one-upmanship myself? That'd be stupid.

Automating stuff is usually very synchronous and scheduling happens via a database, so I don't know what's happened... I had to refine everything. Maybe I'll just make some microservices and delegates. Events, observations... CIA? Software architecture? No? Maybe just steal someone's style and lose all your health, all your money, all your wisdom and spend 10 years in mental hospital.

https://www.blackhatworld.com/seo/you-reap-what-you-sow.1615889/#post-17896969
Now that I got them out of the way, I can continue.

So there's another problem.

All this async await is based on the belief that someone somewhere knows better than us. How could a general, theoretical guide translate into solving real problems?

This is based on some concept of "producer" and "consumer". Unfortunately, everything happens in sequence in most software that I saw. Maybe someone has some software where everything needs to happen asynchronously, but I have never seen need to do that at all times.

Alright, in my program... nothing happens in the background. Production of one thing does not take place in the background and my program does not wait for a product of some function. This could happen, but that's probably the only use for this async pattern. I would use it maybe TWO times in the whole program.

If my entire program is built around that async pattern, for my work environment and style it becomes a disaster. It's so buttery. In my opinion it should be the other way around, that only some things are built this way, and not all things are built this way.

It is even more complicated than "producer" and "consumer". You need to communicate to the constructor what happens when something fails and what happens when something succeeds (2 callbacks passed to a callback function). Unfortunately, putting this in everywhere makes the entire code incredibly complicated if you have plans to use that code in the future and not just create 12th thrown away project.

You can immediately send such a code back to India and let them decipher what's going on and where the error is. You know how much a person decoding those hieroglyphs gets paid in India? $5000. You know how much money it is in India? A lot. Why so much? Cause nobody can solve it cause it's like archaeology - you can't learn it quickly and even if you do, you're gonna need Sherlock Holmes attitude to go through it.


And again, is this some kind of irony? “Promise” is intended to remove complications related to callbacks. Meanwhile, to fit into this pattern, you need one function, which requires two more functions. If we want to automate this somehow, we will create functions that take functions that are used in the function, which is passed to the “Promise” constructor.

Node.js - a tool that improves the work of programmers - the top solution of 2024. Forget about all C#, C++ and Java. Now there is a new king - the promise of the promise and the functions performed after the promise is fulfilled. This is probably trolling by JavaScript creators. People can be sarcastic, and maybe some cynical pig did this and left it as it is, and the next one imposed the "async await" syntax on it.

Additionally, we have no insight into what is happening inside. What if some new person starts using it? This would be a tragedy. This is not suitable for use by someone who does not write out everything in a small piece of code on 30 boards. But do we need this or something else? Maybe it would be better to instead think about multithreading, sensible runtime error recognition, debugging, and failure scenarios?

Now I have some distractions for us. https://www.purescript.org/

Of course I wouldn't use it. Just some open-mindedness provocation.

Yes, yes, yes. I know C#, C++ and Java all have that stuff inside, but... they're not abusing it for some reason. Maybe their community is just... more... more... different?

reaaski said:

If my entire program is built around that async pattern, for my work environment and style it becomes a disaster. It's so buttery. In my opinion it should be the other way around, that only some things are built this way, and not all things are built this way.

Click to expand...

Yeah i don't understand why should that be the norm and not the exception. Luckily for me, as a solo freelance dev, i can pick the tools in my toolbox and Node.js (well, basically everything JS ) is out of the equation.

Backend:
- You want some quick solution for some in-house/internal tool or a PoC for a wannabe production-ready app? -> Flask
- You want a production-ready, high-performance and , most of all, RELIABLE AND STABLE app? -> Axum

Frontend:
- Server-side template rendering (Jinja2 or Askama) + HTMX
- Server-side template rendering (Jinja2 or Askama) + HTMX
- The client wants React/Angular ? -> hire a frontend dev for this.

Mald0r0r said:

Yeah i don't understand why should that be the norm and not the exception. Luckily for me, as a solo freelance dev, i can pick the tools in my toolbox and Node.js (well, basically everything JS ) is out of the equation.

Backend:
- You want some quick solution for some in-house/internal tool or a PoC for a wannabe production-ready app? -> Flask
- You want a production-ready, high-performance and , most of all, RELIABLE AND STABLE app? -> Axum

Frontend:
- Server-side template rendering (Jinja2 or Askama) + HTMX
- Server-side template rendering (Jinja2 or Askama) + HTMX
- The client wants React/Angular ? -> hire a frontend dev for this.

Click to expand...

Can't say anything about a language that came out in 2010 and for me everything post 2005 is just experimental / beta / alpha stuff. It'd be hard believe few people who create those tools could really make it good in less than 15 - 20 years. JavaScript is a language that's been rewritten and rewritten times and times again. That tells me there is some chaos and I don't want to use tools for engineering that are brittle and can blow up the entire city. I don't like these time ticking bombs and what I can find about Rust when I Google is that they ignore good practices by using "unsafe block". Well, with each new tool, there's a new generation of people (young, inexperienced people) who went on a hype train and created another immature parts for an ecosystem. JavaScript is probably the most immature of all - those people use ChatGPT content as source of truth - terrible for themselves.

Frustration compounds over time and then it ends up in rehab cause someone becomes an alcoholic. It starts from listening to other people on the internet who said "this is better for you", "smart ways are bad for you", "take impulsive decisions". Really? And maybe watch TikTok on top of that rationalizing that other people do that, so you should too. Not a lifestyle for me. I can't live like that and independence is too good to not use it as far as I recognize freedom.

reaaski said:

what I can find about Rust when I Google is that they ignore good practices by using "unsafe block"

Click to expand...

Hmm why is that ignoring good practices? Quoting the Rust Programming Language book:

You can take five actions in unsafe Rust that youcan’t in safe Rust, which we call unsafe superpowers. Those superpowersinclude the ability to:

• Dereference a raw pointer
• Call an unsafe function or method
• Access or modify a mutable static variable
• Implement an unsafe trait
• Access fields of a union

It’s important to understand that unsafe doesn’t turn off the borrow checker or disable any other of Rust’s safety checks: if you use a reference in unsafe code, it will still be checked. The unsafe keyword only gives you access to these five features that are then not checked by the compiler for memory safety. You’ll still get some degree of safety inside of an unsafe block.

In addition, unsafe does not mean the code inside the block is necessarily dangerous or that it will definitely have memory safety problems: the intent is that as the programmer, you’ll ensure the code inside an unsafe block will access memory in a valid way.

Click to expand...

So basically, an unsafe block is only needed if the developer wants to do one of those 5 things.

Putting that "unsafe block" thing aside, i actually believe that Rust ENFORCES good practices.

Another thing that i really like about it is that the standard toolset covers essentially everything. No need for unofficial tooling. Dependency management? Cargo. Unit testing? Cargo. Generate documentation? Cargo. Format the code according to the official style guide? Cargo.

This is actually something that really bothers me with Python (and maybe the same applies to JS). The community is too broad, too much hype for so many years (although rust is very hyped too, but the people actually developing code in Rust are a very specific set of individuals and they mostly came from a solid C/C++ background (my case). Just compare the amount of job openings for Rust developers vs. Python or JS).

And what does this "the community is too broad, too much hype" has to do with what i was saying above about Rust having a very solid toolset? Well, just look at how many dependency management tools exist for Python. pyenv, venv, virtualenv, pyenv-venv, Conda, Poetry, WTF! -> this is the result of a "programming community" that is so hyped and so easy to access that sooner or later every amateur programmer will think about contributing back to said community and so they come up with a new HOT tool that does the same as the other 12359318741 tools but it is better because it was written by them and posted on reddit for likes and github stars haha

15 pure functions written in 2 hours after eating a nice set of foods. I've done more in those 2 hours using "Sync" methods from node.js than in a week using async methods. Now, that's your decision, whether you want to be slow and impress colleagues or powerful and be a little bit free financially if things go right. A classic for loop instead of for-in's, a classic Sync method and only sending things to background when it's necessary. Avoiding useless syntaxes. Power is power. Now synchronous code is a lot shorter and simple. It's angel compared to devil that my code was back then. Removal of all dependencies from functions and only accepting primitives in them, now that's another trick to get reusability and indempotence. Feels like last 10 years all I was doing was getting myself confused only to find myself in that place when I was 15 and then I wanted to make things "more complex", but I made them complex in the wrong sense. Complex means you build a system of modules instead of using complex syntax. That's a little bit of a difference. Now it feels more like writing C without handling memory stuff.

I think Meta should be sued for dirty business practices. But... people who create it already pay fat bucks for it. They work at $25 / hour doing the harshest stuff you can do in the whole space. It's like painting packaging for products manually. Bullshit. It doesn't even feel like using computer but some scam machine. lol

"Declarative programming" - you mean using your own vocabulary created by your in-house team of Meta developers who have been doing that for the last 15 years and general public has to adapt to it cause what? You're some conceptual God? Those fcking retards after 11 years realized they need a compiler. I'm not even doing for 11 years and I knew that long time ago.

Now, Facebook is full of bugs, more so than any other huge site. I saw some of those bugs posted on this forum.

Edit: to build business soft you need control, which means you want to control "how" and "why" (mix of imperative / procedural / oop) instead of only "what" - declarative programming.

I identified another thing that seems to be here for no apparent reason and it's strictly related to front-end. I was in a forest for a little trip and something was deeply wrong inside of me since last 48 hours. It wasn't related to programming, just existence and environment.

I had a high amount of negativity inside of myself that I absorbed from all around. I don't have energy, almost at all. I'm feeling as if demons sucked out everything out of me. It's hard to cleanse from it.

In that state thinking about software I realized the complexity of my frontend stuff is too high and I created another vision for it. There is a common misconception that browser automation should be done from the outside (via connection to browser) and not from the inside.

What's important is that these aren't based on C or anything like that. They don't bring some unique feature you wouldn't be able to create yourself using just in-browser features. They're simply JavaScript executed via Node.js connected to browser. It brings nothing to it.

So I'm getting rid of frameworks called Puppeteer and Playwright. None of that is useful for me.

If anyone wants to have custom Puppeteer or Playwright, these are open source. I don't see super high value in open source software. It's usually not doing much and brings a lot of complexity. Maybe I need 3 - 4 functions off the whole set and I can just create them on my own.

https://github.com/microsoft/playwright

Notice the trap. It says
Which means you need to use another solution called an anti-detect browser.

This can be gotten rid of too if you do from another angle which is just in-browser and basically chrome + chrome profiles on real, physical machines with common CPU + GPU combinations.

Also you can do front-end in Python which is faster and you can use Python style which makes this work take hours instead of days.

Advantages of removing test frameworks to control browser from the outside:
- less resources needed;
- no memory leaks / no bugs from open source;
- no problems introduced by node.js like insane memory sucking;
- decreased complexity;
- a browser from a command-line opens in a second:

These are nothing but front-end test frameworks. None of that front-end is needed.
Consider getting rid of falsehood other people introduce into your projects.
Think more consciously and understand they're wrong and are paid to do wrong things.

I realized that this "computer science" is created like a TV-show.
Developers are influenced via large corporations and their mainstream messages.
It has nothing to do with programming.

The only value comes from ourselves and you can't find it inside of frameworks, libraries, business models, ephemeral stuff etc.

Hence I went to C, Python and I'm exploring from those positions.
Then I found a way to create a compiler, a programming language, a computer, a machine, and a whole civilization. I write myself out of over 100 cultures I subconsciously subscribed to listening to narrow-minded people.

It looks like I had been creating subconsciously hell on earth cause I assumed someone is wiser than me. In fact it was just a manipulation for me to get lost and serve unconsciously for those at the top.

So this was like massive shenanigans. It took over 5000 posts to find my way outside of this cluster and see what it was doing with my whole-being.
I found more wiser circles and it was revealed to me that this dynamic of "ruling or being ruled" is very common in every industry.

It comes from being inauthentic and not being able to trust reality itself enough and finding some outside solutions in ideas of other people etc. Trusting people doesn't make sense if you can trust the whole reality which essentially created us and so we help it create itself.

We don't create reality. It expresses itself through us and that's where you can make mistakes by thinking you're creating it with other people. That's insanely flimsy world and if something fails in those in-person relationships, navigating reality will be like being a toddler.

So then I created my own civilization and then a social media network within it. Thank god the frontend is generated by the reality itself. Yes!!

Lol why was this legend banned, this is highly entertaining, me too, I strongly dislike reactjs and angular, well, that one committed suicide long time ago