developit

7 ms·

1.
by developit 4y ago
This sounds fun
2.
by developit 5y ago
my unhelpful take is that I like both
3.
by developit 6y ago
<3
4.
by developit 6y ago
Nit: 212kb, the rest is a YouTube embed that I seem to recall is loaded lazily.
5.
by developit 6y ago
We are working on a new renderer that started out life as a way of addressing the specific corner cases that can lead to this. It will be released in early 2021.
6.
by developit 6y ago
It already does this. Only for .cjs files and things in node_modules.
7.
by developit 6y ago
The tooling space isn't broad enough to allow for differentiation across the board, so we have a number of tools that are working to validate/popularize a subset of functionality on top of the basics. WMR's unique take is bas
8.
by developit 6y ago
Oh I totally agree it's strange, haha. The cost tends to be magnified in Node land since everything is a million files.
9.
by developit 6y ago
You need to change the HTML to point to the tsx file too: <script type="module" src="./index.tsx"></script> There are ambient TS definitions for CSS Modules, it just had a bug in 1.0.0 - fix is merg
10.
by developit 6y ago
We've only shipped a helper library for Preact, but the Prerendering is actually generic. Some folks are working on helpers for other frameworks. The "API" is just a function exported from your first script tag: export async
11.
by developit 6y ago
It's built-in, just change the file extension to `.tsx` or create a new file with that extension.
12.
by developit 6y ago
It's designed for rapid prototyping. You can just use npm or yarn and ignore this feature though, it's entirely optional. FWIW the surface area for security issues here is far smaller than npx or similar tools, because WMR only wr
13.
by developit 6y ago
Hmm - it's not actually specific to Preact, it's just built by the Preact team and we use Preact in the docs. We are missing a bunch of documentation that would have made this clearer though, which I apologize for. While there are
14.
by developit 6y ago
tbh I think a good chunk of that size is babel-parser, which we're looking into removing from the preact ESLint preset. Still quite a difference though.
15.
by developit 7y ago
There are a few cases where syntax compilation is split up cleanly, but when you dig into the internals of preset-env, transforms are rarely that isolated. That being said, "watch this space"...
16.
by developit 8y ago
Most specs have a small number of authors (1-3) and a much wider group of people who have influenced the spec. This is as true for Import Maps and kv-storage as any other. FWIW I think "the web's first built-in module" is a r
17.
by developit 8y ago
Not a great example, since "independent" is the important bit there: browsers just shipped sqlite, and you can't have a spec that says "just ship sqlite".
18.
by developit 8y ago
It's more than memory use - it causes tree traversals to take longer, which means unbounded style recalculations (common) and side-effecting DOM changes take longer.
19.
by developit 8y ago
Preact and Hoodie/PouchDB. Frontend hosted on Netlify, backend on literally anywhere ($5 Dokku one-click installation on a DigitalOcean VM, Heroku, whatever). Hoodie/PouchDB gets you a pretty easy fix for the "whole DB on pag
20.
by developit 8y ago
It's possible now! https://developers.google.com/web/fundamentals/app-install-b...
21.
by developit 8y ago
It has a dark mode with different colors. Let's not villify blue in general though :P
22.
by developit 8y ago
For slow writers but quick typists, an app is always going to win out over a physical journal. Also interested in an event call export + parse.
23.
by developit 9y ago
It's true, the example could be better. However - adding any form of data pruning to the example would immediately show the benefit. JSON parsing happens in the worker, and only a small subset of data is actually serialized and sent ba
24.
by developit 9y ago
Agreed! There's an open issue to address this - the single letter names are silly, since they get uglified anyway.
25.
Microbundle: zero-configuration bundler for tiny modules(github.com)
4 points by developit 9y ago|0 comments
26.
by developit 9y ago
It's unlikely Preact infringes on a theoretical React patent. It's not a reverse-engineered reimplementation of React, but rather a library that happens to have a similar public API. APIs are not patentable, thus Preact's imp
27.
by developit 9y ago
Understandable, and agreed about my point being for copyright as opposed to patents. It's interesting to note that, since the majority of DOM rendering libraries now employ some variant of Virtual DOM (react, preact, mithril, glimmer&#
28.
by developit 9y ago
Also impossible because JSX is independent of React. The specification is only subject to a standard Copyright and is released under the Creative Commons Attribution 4.0 International license.
29.
by developit 9y ago
I'd be curious to hear about this too - I don't see any issues filed or commented on by him, perhaps the bugs are more perceptual mismatches with his React experience as opposed to actual bugs. We only recently released preact&#x
30.
by developit 9y ago
We've begun work on a NativeScript integration that would meet this need. It's early stage though.

More ›