fabiospampinato

11 ms·

91.
by fabiospampinato 4y ago
Actually that's just a common misconception, which I believed too. The complex compile-time transforms enable almost no performance improvements. As a proof just take a look at the js-framework-benchmark table [0], my framework (Voby [
92.
by fabiospampinato 5y ago
The logo is amazing!
93.
by fabiospampinato 5y ago
WebWorker may be one of the most important ones missing in Node.
94.
by fabiospampinato 5y ago
I've been writing this thing over the past couple of months, I'm quite liking the performance I'm getting out of it (see the benchmark [0]) and the APIs it provides. Hopefully there aren't too many bugs left to fix . I d
95.
Show HN: Voby – a new (toy?) high-performance web framework similar to Solid(github.com)
1 points by fabiospampinato 5y ago|1 comments
96.
by fabiospampinato 5y ago
Here I am still waiting for ES2018 regex look-behinds to be implemented. The folks working on the regex engine must have jumped ship or something.
97.
by fabiospampinato 5y ago
I've spent the past month kind of rewriting parts of Solid in an attempt to better understand it, and coming from React the way Solid works is just so much more beautiful, it feels liberating. There's no rules of hooks, no depende
98.
by fabiospampinato 5y ago
I read on wikipedia [0] the other day a fairly disturbing statistic related to this, apparently human men have on average a ~10% bigger brain than women. It'd be interesting to know if that translates to a higher neuron count or the di
99.
by fabiospampinato 5y ago
For the record the code you linked to doesn't implement event delegation either, which is something pretty useful that even more modern libraries like React use under the hood. Here's [0] an article about the usefulness of namespa
100.
by fabiospampinato 5y ago
Hello, I explicitly asked for it: > How should one do the same with vanilla JS? And you said: > With the code here
101.
by fabiospampinato 5y ago
It doesn't support event namespacing.
102.
by fabiospampinato 5y ago
Except that's broken beyond belief. Neither event delegation nor event namespacing are implemented in that snippet.
103.
by fabiospampinato 5y ago
For some basic use cases that's probably good enough, but saying that that can replace jQuery is like saying that farts can replace rocket engines. For example I can do the following with jQuery: $(document).on ( 'click.ns&#
104.
by fabiospampinato 5y ago
I didn't mean to hijack the thread, I was just replying to somebody saying something about Cash :) I'm ambivalent regarding your documentation point, on one end jQuery is way more popular and one can largely just read jQuery'
105.
by fabiospampinato 5y ago
Cash's maintainer here. I don't think this is true actually. Zepto supports some methods that Cash doesn't, but you probably shouldn't use them to begin with, like $.ajax, $.isArray, $.fn.animate etc. In 2022 either bett
106.
by fabiospampinato 5y ago
It's sad how buggy IndexedDB is in Safari, and in general how much pain Safari causes to web developers and consequently their users. I hope regulators will eventually force support for other browsers (that can install apps) in iOS, I
107.
by fabiospampinato 5y ago
Pikchr is awesome! I'll just mention that the Markdown-based note-taking app I'm working on as far as I know is the only app on the planet that can syntax-highlight Pikchr code: https://github.com/notable/nota
108.
by fabiospampinato 5y ago
I've been looking into memory leaks for an Electron app recently, and a major source of problems are strings, strings have sort of this hidden feature/bug: if you slice a string a new string is not allocated in memory, instead the
109.
by fabiospampinato 5y ago
That's a big "just", but yes in theory that's doable, however: - The performance you are going to get will be terrible compared to the native implementation. - Oniguruma, which I think is Ruby's engine, weighs half
110.
by fabiospampinato 5y ago
Electron does not weigh 300+ MB for starter, and one means basically statically linking your app so that it ships with its own dependencies and works more consistently, while the other means shipping a language because the one you have to u
111.
by fabiospampinato 5y ago
A lot got released in the past 4/5 years. I don't have a list of favorites off the top of my mind. Many useful things got shipped though.
112.
by fabiospampinato 5y ago
Proxy polyfill: assuming you are referring to this [0], since I haven't seen anything else like this, then I'll paste here what the readme says: > The polyfill supports just a limited number of proxy 'traps'. It also
113.
by fabiospampinato 5y ago
Right? And that's not the kind of feature that you can just polyfill back in. I don't understand how it's possible that that's not implemented yet.
114.
by fabiospampinato 5y ago
That's actually not true in general, tell me how to compile Proxy and regex lookarounds to ES5 or whatever version that doesn't support these features. In fact tell me how to polyfill these features in any way at all.
115.
by fabiospampinato 5y ago
>>Testing on Chrome would save you from accidentally using Chrome-only features, but that's only part of the problem, >How? Sorry I meant "Firefox" and "Chrome-only" there. In general though it's not l
116.
by fabiospampinato 5y ago
I think this is a great point. The delta in performance must be visible for people to even care about, and that's not obvious even for technical people (if something takes 15ms or 0.15ms to render the difference is massive, but probabl
117.
by fabiospampinato 5y ago
Testing on ~~Chrome~~ Firefox would save you from accidentally using Chrome-only features, but that's only part of the problem, caniuse.com kinda works better for that as you get data about other browsers too.
118.
by fabiospampinato 5y ago
Unless I'm missing something that doesn't fixes the issue, the problem is symmetrical, browser A is different than browser B, so browser B is different than browser A, testing in either of them doesn't guarantee a correct out
119.
by fabiospampinato 5y ago
By this logic requiring web devs to write ES3 code should be acceptable too. The platform changed significantly, improved significantly, in the past few years, some of these major advancements can't be ignored just because a browser do
120.
by fabiospampinato 5y ago
Sorry but requiring web devs to ignore the last 4~5 years of progress is just unacceptable. Not that that would fix the situation, there are still rendering inconsistencies between browsers when using stuff like margins floats and tables.

More ›