They differ in a similar way to how React differs from SolidJS.
In react when state changes the component functions that depended on that state are rerun to compute what the component should now look like. Then react diffs the new output with the previous to touch only the parts that changed in the DOM.
In solidjs the component function runs only once (when the component is instantiated), when state changes signals will trigger and cause the specific parts of the DOM that depended on them to change. This is generally more efficient.
Too bad it will only be available as a Pro feature. I’m not against supporting hard work by any means but framing it as an alternative to free options set me up for a bit of disappointment. But I agree with everything else you said that this seems very impressive.
I think I agree that it's akin to organized crime, it's a case of "the goal justifies the means".
You see the goal of forcing union usage as a noble thing so you agree with these means. If the goal was one that you don't see as noble you'd definitely agree that it's very organized crime like.
No, performance and power consumption should go hand in hand in this case. If you are strongly IO bound, paying for the synchronization is not really going to matter much I believe.
There are cases where you can be CPU bound and using the share nothing model would work out to your advantage. There's also the case where you only have one cpu core anyway (for example if you want to get all the juice out of a cheap single core VPS)
I've found that practically I'm more likely to simply use Box, Vec, and just regular data on the stack rather than Rc and RefCell when I esque Arc and Mutex by using a single context. The data modeling is different enough that you generally don't have to share multiple references to the same data in the first place. That's where the real efficiencies come to play.
Realise that this means more recruiters and it being a hugely valuable service all of a sudden, whereas today it is maybe neutral on the average (helpful for some, annoying for most). Since random strangers on the internet couldn't be trusted in this possible scenario, recruiting firms could be the ones to build up reputations of having suitable/legitimate candidates. You might not realistically be able to get around them.
More middle (wo)men does not sound like an improvement. But to be fair, I don't really know what the deal is with cover letters. When applying to a job, I always write some text in the email that explains why I can do that job and why I'm interested at all, it's not like I just drop my CV on an email address and trust the recipient to take it from there. The application process may be different in NL/DE versus whereever OP lives, or for my line of work compared to theirs.
In react when state changes the component functions that depended on that state are rerun to compute what the component should now look like. Then react diffs the new output with the previous to touch only the parts that changed in the DOM.
In solidjs the component function runs only once (when the component is instantiated), when state changes signals will trigger and cause the specific parts of the DOM that depended on them to change. This is generally more efficient.
reply