Cool project, unsure of durability or redundancy constraints, let alone something akin to gossip to re-seed and/or re-balance records to partitions after coming online again.
Seems like a natural pairing to leveldb for local storage or even just an in-memory store for distributed caching.
Would still probably be better off with something with a higher memory threshold than node.js supports out of the box.
Two biggest reasons, I like the syntax, and using object de/structuring...
export default ({ foo, children }) => (
<div className={classNames(
'some-component',
{ foo }
)}>
{children}
</div>
);
The first few paragraphs are a bit muddled...
WebAssembly is a low-level target that applications not in JavaScript can target to run in the browser and other wasm runtimes outside the browser, including Node.js. Rust has first class support for targeting wasm.
What these technologies together offer is the opportunity write and run heavy compute tasks in worker threads inside Node.js via Rust + wasm. Beyond the samples in the article, you can also write node-native modules with Rust using the neon[1] crate.
[1] https://github.com/neon-bindings/neon
BoostNote is a pretty nice application, I remember trying the prior version at some point in the past couple years and don't recall why I didn't stick with it. I'm a huge fan of Markdown for documentation and note taking, may give this another shot. IIRC it's free for personal use and looks like there's a "team" version coming. Best of luck given the competition between other apps, some that also integrate communications. MS Teams, Slack, Confluence and others are all pretty entrenched at this point.
For work, I really do like teams, it's best at nothing, but good enough at pretty much everything. Biggest complaint is that the Teams wiki section is *NOT* stored in markdown (it's in ms html doc format) and doesn't sync with the OneDrive sharing via Sharepoint. Also, Shairpoint sync with OneDrive has been problematic for me.
For persona use, I mostly use keep for this type of thing. For all it's faults, being able to share a shopping list with my fiance is useful. Also, being able to use my phone or any desktop with a browser.
#1 portions are dated and overly simplified, the browser DOM has seen a lot of significant improvements, and so has React...
#5-4 JSX is *not* complex at all imho... some developers don't like it, and there's a heavy overlap with developers who don't like JavaScript in general, or like tech in different files or prefer general templating DSL.
#9 part is demonstrating CommonJS vs ESM ... the other is React's legacy interface VS class based inheritance, which is supported natively in all modern browsers (though JSX isn't without transformation).
#10-2 React supports both SSR and client
#12 ignores functional components
#13 doesn't explain functional components
#16.1 is wrong, state isn't received from the parent (not to be confused with state initialized from prop, or context)
#16.5 likewise with 16.1
#16.6 both no, you can send a function/event handler for child to bubble out, or use context.
#18 fat-arrow is a JavaScript thing as of ES6, not specific to react. It is a context bound lambda expression.
#21 neglects functional component hooks.
#23 unbound function
#25 example is just plain *WRONG*
#27 demo is wrong
#28 demo is wrong
... not reading beyond #28 ...
Two biggest reasons, I like the syntax, and using object de/structuring... export default ({ foo, children }) => ( <div className={classNames( 'some-component', { foo } )}> {children} </div> );missing object support { 'className':truthyFalsyValue }