webpack-common-shake
wtfjs
Our great sponsors
| webpack-common-shake | wtfjs | |
|---|---|---|
| 2 | 94 | |
| 914 | 33,999 | |
| - | - | |
| 0.0 | 0.0 | |
| about 1 year ago | 5 months ago | |
| JavaScript | JavaScript | |
| - | Do What The F*ck You Want To Public License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
webpack-common-shake
-
CommonJS Is Hurting JavaScript
While I agree the dynamic nature of CommonJS would be problematic, there were successful projects around treeshaking commonjs[0] that worked really well.
I think dynamic imports have some of the same footguns here, to be honest. Can't deny ESM is easier to statically analyze though, that much appears to be true across the board based on available evidence.
[0]: https://github.com/indutny/webpack-common-shake
-
[AskJS] What are still present issues in contemporary (2022) JavaScript?
Tree shaking in CommonJS is possible: here's a Webpack CommonJS Tree Shaking package.
wtfjs
- Milyen hasznos Github repokat ismertek?
- doNotDespairEverythingIsAhead
-
Companies: We can't find any good candidates!!! Also companies:
Me in the interview: "Generally, no, a variable can only be assigned one numeric value at a time. However, Javascript is famous for unpredictable behaviors in variable comparison statements, for instance [] == ![]. There's actually a whole library built around documenting this type of behavior this for comedic value, and other more serious libraries geared towards solving the problem. So it's possible that some obscure variable assignment scenario would result in that line evaluating as true, but it's not something you'd expect to encounter in the real world. This has gotten a lot better with typescript and es2022, but still something you need to watch for a bit."
-
“Go is hard to justify unless at massive scale”
I do see that point of view, didn't think of that, there are some aspects of go which are a bit weird if you never touched lower abstraction languages, yet once you learn what they are, you are all set and you can code in anything. go has the least amount of gotchas I have seen in any programming language. compare it with loads of the weird stuff javascript does https://github.com/denysdovhan/wtfjs and go is like heavenly lol
- Typescript is polishing a turd
- 3 < 2 < 1 === true
- Show HN: Whatdoesthiscodedo.com – AI explanations for other people’s code
-
Learning Frontend/React is the new rat race.
Its a very poorly designed language. Its syntax and semantics are often confusing and unpredictable. There is no well defined mental model of how constructs work in this language.
-
🚀 8 GitHub Repositories to learn JavaScript
WTF JS
-
Awesome Github Repos to Master JAVASCRIPT
😎 A great guide to Javascript that is both simple and wonderful, but also difficult and fun that seems like bullshit. -> wtfjs
What are some alternatives?
proposal-upsert - ECMAScript Proposal, specs, and reference implementation for Map.prototype.upsert
Power-Fx - Power Fx low-code programming language
meta - Meta discussions and unicorns. Not necessarily in that order.
jsfuck - Write any JavaScript with 6 Characters: []()!+
esm - Tomorrow's ECMAScript modules today!
html-over-the-wire - HTML over the wire: List of frameworks which receive HTML snippets from the server.
loader - A universal async JS loader.
wtfpython - What the f*ck Python? 😱
proposal-do-expressions - Proposal for `do` expressions
proposal-shadowrealm - ECMAScript Proposal, specs, and reference implementation for Realms
node-fetch - A light-weight module that brings the Fetch API to Node.js
typegoose - Typegoose - Define Mongoose models using TypeScript classes.