DEV Community

Serhii
Serhii

Posted on • Updated on

Stop using frameworks and libraries

Inspired by Stop using React article.

Let's say you want to use some framework/library in your application. What are the reasons this is a bad idea?

1. It's slow

Really, have you seen the benchmarks for that X framework/library? It's very slow in comparison with the alternative in Assembler. You want to use libraries that relatively fast to boost your app, not to slow it.

2. It's poorly maintained

Even if a Github repository has 156k stars like React it doesn't mean there are no issues. There are always problems. There is only a small chance you don't face a bug.

3. It's made by dangerous people and companies

This library is maintained only because there is an interest from special companies and people who want to conquer the Internet and all the software.

4. There could be sensitive data leaks

Almost all libraries/frameworks make additional network requests and pass your personal data. Recently we became aware of a huge leak of credit card data on applications using Javascript, source.

What is the solution?

Just don't use external software. You can write your own. I don't think it's hard to write your own platform to run server-side Javascript or a module to convert CSV to XLSX. It may be hard at first, but it becomes easier later. It is a question of time.

Some of you could say it's hard to write a Node.JS clone but think about how much you'll learn in the process and the only great reason to do this is that you have your own platform that only you control and maintain.

Have you been ever thinking about why do you need to use, for example, Javascript to write web apps? It's a very bad language to do that. If you want to prevent memory, data leaks, poor support, slowness then you need to pick another language/platform to do that(for example, Assembler with WASM). Or better - write your own.

Please write your own stuff. Let's make the Internet safer, faster!

The article is a joke, please don't consider it seriously

Latest comments (46)

Collapse
 
alidrus profile image
Abu Bakar Al-Idrus

Haha. You really had me going there for a while, until I got to the end of the article.

Collapse
 
kretaceous profile image
Abhijit Hota • Edited

This article better be sarcasm.

Edit: oh ok, it is

Collapse
 
qm3ster profile image
Mihail Malo

This article is a lie! React has 157k stars!

Collapse
 
andrewbaisden profile image
Andrew Baisden

The sarcasm is lost to some πŸ˜‚

Collapse
 
easrng profile image
easrng

WASM is nothing like assembly tho. It's more like a cross between lisp and RPN.

Collapse
 
gsarig profile image
Giorgos Sarigiannidis

When I hovered the link and saw that it was a YouTube URL I made a bet with my self that it would be RickRoll.

The good news is that I won the bet.
The bad news is that I lost the bet.

Collapse
 
puruvj profile image
PuruVJ

I was so gonna bash your head until I read the last line πŸ€£πŸ˜‚

Collapse
 
joelbonetr profile image
JoelBonetR πŸ₯‡

I read the post even the line that says it's a joke but there's some reasons for not using frameworks or libs on the real world. Using them makes your project sensible to the maintenance of another company or community that maintains that framework, apart from that I see many people using them indiscriminately instead on using them for the reason they are made to.

Data leaks could happen on any system but of course they could be more frequent when using some backend framework that has a day zero security hole that hackers can use, it can happen to your own system too but the hackers will need to inspect your own system for months instead on inspecting a framework used by hundreds of thousands of people. That's why you need to audit your security when on production, specially if you're on a big company that can be a target for hackers.

Don't take this matter of conversation as a joke because it's not, important facts are over the table when analyzing and architecting a project that can be or will be used by a high number of customers in order to protect as much as possible your customers data and privacy.

Collapse
 
efleurine profile image
Emmanuel

Plus if you use this library your are missing a chance to use a more powerful library tomorrow. Don't limit yourself and lock away the possibility to use the perfect one. Once it comes out. You better stand ready by using your own stuff

Collapse
 
ashishk1331 profile image
Ashish Khare😎 • Edited

Writing Your Own framworks:
Pros -

  1. You know the need
  2. Try own compressions
  3. Precise
  4. Hassle-free from parallel world syntaxs

Cons :

  1. Can be tedious without help
  2. Strangle yourself with your own code.

While a attempt is worth it.
Once a time every js coder should try to make a framework.

Collapse
 
anzhari profile image
Anzhari Purnomo

Whelp, got my first rickroll in 2020.

Collapse
 
shahrozahmd profile image
Shahroz Ahmed

Seems like you are encouraging to reinvent the wheel🀣

Collapse
 
louislow profile image
Louis Low • Edited

Oh no... Not again another controversial Not to use frameworks.

Collapse
 
dsaw profile image
Devesh Sawant

Stop using programming languages, write in binary!
Lol, like your sense of humour.

Collapse
 
sergchr profile image
Serhii

The article isn't serious :)