Yarn

Recent twts in reply to #ym74jaa

@prologic you simply don’t… 😋

I made it by relying on parcel JS v1 (made some time ago).

I first tried create-react-app but aborted immediately once I saw it going for 3 minutes with npm install.

⤋ Read More

@justamoment Yeah this is total bullshit I have to say. This is the most stupidest way to to render shit on a page and do some reactive-style single page app 🤦‍♂️ To make things even worse, there’s Typescript in this goddamn thing 🤬 Why?! 🤦‍♂️

A: Hey guys, I have a great idea, Since nobody likes Javascript, let’s create a new language?
B: But how will the browser run it?
A: No problems ! We’ll transpile it to Javascript

🤦‍♂️

⤋ Read More

@prologic Haha, the current front-end JS ecosystem is too huge and slow to install. I still like just plain HTML + small JS for UI tweaks. At Deno company I work for, we have some people who don’t like node_modules and are working on a replacement for Node.js

⤋ Read More

The problem isn’t with NodeJS or NPM, it’s the developers that are so willing to use horrible frameworks/libraries/tooling that is just simply not needed. NodeJS gives you so much out of the box, and NPM is simply a place to store your packages. With Deno, you won’t even need a package manager as it takes a step closer to go modules approach.

If you’re going to use React, TypeScript, NextJs, Webpack, Styled Components, Material UI, Jest, and the 10k dependencies that comes with it, then yeah, your dev environment is going to be slow, bloated, and incredibly frustrating to work with. Not to mention have security issues. I’ve literally just done a fresh create-react-app installation (latest version 5.0.1 as I write this), and boom, 6 high severity vulnerabilities.

But it doesn’t have to be this way. Choose lightweight libraries that do one thing really well, and build your project from the ground up yourself.

⤋ Read More

The problem isn’t with NodeJS or NPM, it’s developers that are so willing to use horrible frameworks/libraries/tooling that is just simply not needed. NodeJS gives you so much out of the box, and NPM is simply a place to store your packages. With Deno, you won’t even need a package manager as it takes a step closer to go modules approach.

If you’re going to use React, TypeScript, NextJs, Webpack, Styled Components, Material UI, Jest, and the 10k dependencies that comes with it, then yeah, your dev environment is going to be slow, bloated, and incredibly frustrating to work with. Not to mention have security issues. I’ve literally just done a fresh create-react-app installation (latest version 5.0.1 as I write this), and boom, 6 high severity vulnerabilities.

But it doesn’t have to be this way. Choose lightweight libraries that do one thing really well, and build your project from the ground up yourself.

⤋ Read More

@markwylde No, it doesn’t have to be this way, but it is (almost) always this way. When a programming language makes it too easy to manage dependencies, you inevitably get microdependencies. It doesn’t help that many people learn JavaScript or Python as their first language.

⤋ Read More

@prologic I’m relying on vanilla JavaScript most of the time (even when using frameworks) to not have too much dependencies and lately I found that the type="module" works quite well for most of my needs so I’m dropping almost everything, instead of nom and other i rely on skypack for the libraries.

If you need something bigger but still lighter try snowpack, it uses CDN until you build by optimizing the disk space too.

If anything look bleak try pnpm for a more standard experience of the tooling.

⤋ Read More

Participate

Login or Register to join in on this yarn.