@why_not_export_default

Consider you have a file foo.ts with the following contents: class Foo { } export default Foo; You would import it (in bar.ts) using ES6 syntax as follows: import Foo from "./foo"; There are a few maintainability concerns here: If you refactor Foo in foo.ts it will not rename it in bar.ts. If you end up needing to export more stuff from foo.ts (which is what many of your files will have) then you have to juggle the import syntax. For this reason I recommend simple exports + destructured import. E.g. foo.ts:…

Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

I switched a naive, unoptimized #Nextjs project from @reactjs to @preactjs and you won't believe what happened next

@qoouep @swyx (and 2 others) I'm not sure but preact implementation of vdom is simpler and a little faster. So for huge and not optimized (manually) apps you need concurrent react rendering which use more cpu (and battery), for others preact will good enough.