My only commend is it seems like socket.io is a bit overburdened and a faster/lighter socket server implementation might help... pretty cool all the same.
Interresting, though the article doesn't actually link to Cypress[1]. The first reference, or two, should absolutely link out to the project's home page.
I've been using Puppeteer with Jest myself, which isn't so much fun to setup, but has really been productive for me.
[1] https://www.cypress.io/
I don't think that Web Components will grow much as-is, it's cool for relatively discrete UI components, but the lack of non-string property support and a good story for state management, I think React is generally better for most use, but you can combine the two.
I also do think that Web Assembly projects will mature, and should a better DOM story come to bear fruit that will be really nice. I have a feeling that access to Canvas and sound primitives will come ahead of general DOM access, which will have some really cool options for webifying more applications more easily.
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.
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 }