Filter
Exclude
Time range
-
Near
Replying to @gmail
I do, and I still mostly use the #Gmail #BasicHTML UI. Back then, we just enjoyed the "Beta" tag that continued on when Gmail went from invite only to sign-up mode.
2
13 May 2022
i truly am, i am actually the # 1 damnokracy/BasicHTML stan
1
Obviously need to test for real. But a general DOM capable approach. 3x gains over basicHTML would be enough to silence any contention over emulated DOM not being fast enough on the server.
2
Replying to @WebReflection
This is game-changing. I've been doing a ton of benchmarking on SSR render times. I actually started with using basicHTML. I did a little back of the napkin math. I imagine this should outperform any VDOM SSR approach other than Inferno. And be faster than both Vue and Svelte.
1
4
LinkeDOM is general purpose DOM, basicHTML was born to make viperHTML possible. I won’t use basicHTML anymore, as the β€œhyper” family is mostly maintained but not actively developed
1
except for the cached results (memory greedy), JSDOM is incredibly slow at parsing documents, but it survives crawling 12MB of HTML living standard page. basicHTML was designed to be fast after parsing, but it fails crawling 12MB. linkedom is experimental but it has linear perf
4
1
16
I don't know how I've managed to debug anything in NodeJS before NiM existed. node --inspect-brk folder/file.js NiM in Chrome/ium chrome.google.com/webstore/d… and happy debug ever after πŸ‘ today I've fixed a Custom Elements rabbit hole coming from basicHTML in heresy-ssr 😎

1
12
Replying to @lemmon @RPorsager
SSR? basicHTML works great but it does a lot of convoluted things I *think* could be simplified, and boosted up, via a better underlying engine. moving a whole node costs 2 double links update, as opposite of splices and stuff, and fragments simply links their nodes, if any.
1
1
I love when it’s not just me using my libraries ❀️ basicHTML is been used for years now, providing code coverage to most of my FE libs, but also working in workers, heresy-SSR, and much more πŸŽ‰
#riotjs can from now be used as server side #javascript template engine github.com/riot/ssr/releases… Many thanks to @WebReflection for providing the DOM rendering engine that made it possible github.com/WebReflection/bas…
1
1
7
HTML Element Reference: Basic HTML . Follow @idrumahcoding for daily updates, cek website kami di rumahcoding.co.id . . #html #basicHTML #HTMLElement #web #webdeveloper #coding #programmer #kursuscoding #belajarcoding #rumahcoding
2
5
not only basicHTML supports even Custom Elements basically since day 1, but it's been developed and tested in devices like the Raspberry Pi 2. heresy-ssr is entirely based on it, and all my code coverage uses it too, so it works speedy in CIs too πŸ‘ github.com/WebReflection/bas…

4
most developers don't know basicHTML even exists ... here a trace that shows 8 times less memory usage for your server-side related projects. JSDOM goal is to reflect standards 100%, making it heavy and slow, which is great for headless tests, but pointless in most other cases πŸ˜‰
18 Mar 2020
AFAIK, you don't have direct control over freeing the memory in Node.js, you may only allow for it be freed by the garbage collector. The issue isn't really tied to your code anyway, see the impact of just switching to a lighter HTML/DOM implementation than JSDOM
1
1
7
Replying to @dmitryiv_
<style><!-- this is CSS text --></style> <textarea><!-- this is textarea content --></textarea> these two elements can't have comments, these will have those comments as text nodes, hence visible in the layout (in textarea case) both cases fixed in latest basicHTML πŸ‘‹
1
1
The textarea has a special "feature" that appended comments, or already there, become text nodes and show up as content. I've accidentally discovered yesterday evening, while covering uhtml, that basicHTML had this bug. *had* πŸ˜‰
1
4
as @_coreyfarrell_ mentioned, heresy-ssr πŸ”₯ was shipping with a canvas module, from basicHTML, that was bringing in ~100MB, so I've dropped that from basicHTML, now in v2, and bumped heresy-ssr to v1. You won't notice any difference but faster install πŸŽ‰ github.com/WebReflection/her…
6
hyperHTML, viperHTML, basicHTML, heresy and heresy-ssr, neverland, wickedElements, or hookedElements, if you're curious about differences, strengths, and goals, beside being offers for all Web tastes, I've tried to summarize as much as I could in here: github.com/WebReflection/vip…

1
2
15
basicHTML v1 is out πŸŽ‰ the major change is due 2 new kind of nodes that acts like native: `canvas`, and `img` see the example in the updated README and happy coding! github.com/WebReflection/bas…
2
4