Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
ryansolid
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
7 ms
·
31.
▲
by
ryansolid
5y ago
There are a lot of React state libraries that do similar things with Proxies. I think the part that is not as emphasized is how that reactivity extends to the view. Instead of re-rendering components it uses that knowledge to directly updat
32.
▲
by
ryansolid
5y ago
What does a reusable (ie import from another file) `useAutoCounter` look like in Svelte?
33.
▲
by
ryansolid
5y ago
I'd also look at other repos. Admittedly for the core code it has been mostly me. I think there is an intimidation factor. When you create a library this performance oriented it is hard to get people comfortable working on the core. Bu
34.
▲
by
ryansolid
5y ago
Yeah this is correct. The trick to this is that the subscriptions happen in our JSX and hooks. And really is just a nested tree of `createEffects` if one ever re-evaluates or is disposed it releases its child computations. So while the life
35.
▲
by
ryansolid
5y ago
Reactivity like this predates React Hooks. It doesn't have the hook rules/stale closures etc... No dependency arrays, useRef, or useCallback. It's a very powerful model and very different. The similarities are surface level b
36.
▲
by
ryansolid
5y ago
This is the article series for you (I wrote it so I'm biased): https://dev.to/ryansolid/a-hands-on-introduction-to-fine-gra...
37.
▲
by
ryansolid
5y ago
More than likely it's the lazy loading of the REPL. Those code editors are heavy and when they scroll into view they need to load. If we load up front it would drastically tank the load performance for people just visiting the site. It
38.
▲
by
ryansolid
5y ago
Hey Solid's reactive system uses Signals which are different than streams but work in similar use cases. Streams are slightly more oriented to transformation than synchronization. Most stream libraries could be used with Solid with a b
39.
▲
by
ryansolid
5y ago
Something you don't need to think about until well, you realize reactivity leaves templates and you need to write a store. Or that you have large data and need things to only update piecewise. Or you need to hoist things out into funct
40.
▲
by
ryansolid
5y ago
Solid's diff algorithm generally is faster(or atleast very comparable) than Mithril's. We test very well in list benchmarks like: https://krausest.github.io/js-framework-benchmark/current.ht... . We are also f
41.
▲
by
ryansolid
5y ago
It's a bit like MobX but instead of re-running full components or subtrees it contains the updates granularly. Picture if your renderer was just MobX Autoruns wrapping specific DOM updates as depended upon. In so because the reduced of
42.
▲
by
ryansolid
5y ago
Hmm.. Remix is based around their router. And a nested router is what we need to for Solid (see Solid App Router https://github.com/solidjs/solid-app-router ). I think the challenge is that we don't render like Rea
43.
▲
by
ryansolid
5y ago
It's a fair question. Pre React Hooks I expected the proxy plain object approach to be more common. We definitely want consistency regardless if component consumer passes signal or literal, so I went that way. There are cases like with
44.
▲
by
ryansolid
5y ago
Yeah I see the bug. Thanks for reporting. Looks like the code added for re-adjusting has mins set that weren't intended for smaller viewports. This has been a community effort(PR that added the feature: https://github.com&#x
45.
▲
by
ryansolid
5y ago
You can put createSignal anywhere. It isn't hooks based. It's reactive like MobX or Vue. Some of the primitives don't have much meaning outside of a render setting. What sets Solid apart is the rendering is just that. It'
46.
▲
by
ryansolid
5y ago
Props are getters. They are shallow. It are stores that are actual ES proxies. I think the term is used loosely here to suggest that they are wrappers on top of objects. It isn't so much about the specifics but to explain why destructu
47.
▲
by
ryansolid
5y ago
Virtual DOM came about since it offered a simplistic top down view = fn(state) model without terrible performance. Other top down renderers were terribly inefficient and this built on that. It was never innately faster than targeted direct
48.
▲
by
ryansolid
5y ago
It's unlikely. Solid has had this performance profile since 2017. React hasn't really budged. Fundamentally different approach. There are different types of performance to explore but raw performance for small things is not someth
49.
▲
by
ryansolid
5y ago
To be fair the first few years I wasn't really promoting it. Honestly just was content entering benchmarks and using it for my own purposes. Then React announced Hooks and it was like looking in a mirror. At that point I realized that
50.
▲
by
ryansolid
5y ago
It could potentially if we do analysis to identify components. It's kind of like React's rules though in that sometimes you want to access things in an untracked context on purpose. A simple linting rule that is ignorable would pr
51.
▲
by
ryansolid
5y ago
Solid author here. Hmm don't see this on Firefox on Windows or on my Macbook air. From what you are describing it's probably the REPL acting up. I wouldn't use that as a measure of performance. SolidJS is a UI library, that i
52.
▲
by
ryansolid
5y ago
Yeah it is sort of buried and probably not very clear: https://www.solidjs.com/guide#react . And good point thank you about updating my profile.
53.
▲
by
ryansolid
5y ago
It's awesome to see performance-oriented projects to find their way to SolidJS( https://www.solidjs.com ). So satisfying to see success stories like this one. Great work.
54.
▲
by
ryansolid
5y ago
Awesome to see replay get even better. More accessible the more we can do. Really excited by this release.
55.
▲
by
ryansolid
5y ago
I am a JavaScript framework author, and was one of those fortunate to get early access and honestly it is the most useful tool I've ever used in the debugging space. Sometimes things are complicated. Often there is a need to do digging
56.
▲
Introduction to the Solid JavaScript Library
(css-tricks.com)
4 points
by
ryansolid
5y ago
|
0 comments
57.
▲
by
ryansolid
5y ago
It's surprising how little syntax is here. It's even less code than Svelte.
58.
▲
by
ryansolid
5y ago
It's unfortunate because of all the platforms it is one that gets the most human interaction in terms of real thoughtful humans willing to discuss things. I've tried a lot of platforms and dev.to is the best as writer from this pe
59.
▲
by
ryansolid
5y ago
The problem is by then most of the damage is done. HN algorithms clearly work off some amount of time based decay. It basically suggests getting a stable of people to vouch when whenever you post something.
60.
▲
by
ryansolid
5y ago
Would you say the same about medium.com too? Or any site that allow people to sign up and create blogs/articles?
More ›