I'm so meh on ORMs, especially in scripted languages, I understand this is TypeScript, but all the same.
If I'm going to take the time to really lay out all of the boilerplate needed for an ORM, I think I'd just assume go the extra step for GraphQL. There's even a similar typescript library for this[1].
[1] https://typegraphql.ml/docs/introduction.html
Nice... usually when I see more than 3 upvotes on an article, it's either pretty good/useful or spam. Glad it's the former.
Not sure I'd use storeon over redux in anything resembling a complex app though... there's value in the module system. Though, you could probably just copy and tweak as needed for the size of the main store, and use the rest with it.
Similarly, although I find other react-alikes interesting, the feature parity isn't there and real world performance isn't that impacted vs. having the extra dev support in react.
TailwindCSS does look interesting, it seems to be a bit more specialized than say Bootstrap + SASS, that said, I've been leaning into more prescriptive components (material-ui), and while I do find the need to customize, I like what JSS provides in that space.
If this were 6+ years ago, before React, I'd probably favor tailwind... now I favor components.
Completely agreed... I have the following (roughly) at the top of my scripts in current applications (IE is the main browser that doesn't support the features in question).
async functions and fetch...
try {
eval('(function() { async _ => _; })();');
if (typeof fetch === 'undefined') {
throw new Error('no fetch');
}
} catch (e) {
window.location.replace('/legacy.html');
}
The XMLHttpRequest API was based on the Microsoft.XMLHTTP COM library that could be used in older IE browsers starting with IE5 in 1998. Netscape (later Mozilla) added XMLHttpRequest as a native option to Gecko in 2002 and it became the norm, standardized in 2006, until fetch API became available a decade later in 2015.
Most articles that I've seen referencing the past with fetch to XMLHttpRequest tend to get muddled a bit.
https://en.wikipedia.org/wiki/XMLHttpRequesthttps://developer.mozilla.org/en-US/docs/Web/API/Fetch_API
Very nice... reminds me a lot of the windows screensaver... would be cool to use something like this as a base for a data visualizer for music playback, one of the things I really miss from the old WinAmp days when playing music.
Interesting... not sure why you would actually need a C++ (native node module) for this though... seems like just an in-process http+websocket server listening on a high port would fit the bill. Could be simpler still if coordinating with a host to arrange webrtc.
Completely agreed... I have the following (roughly) at the top of my scripts in current applications (IE is the main browser that doesn't support the features in question). async functions and fetch... try { eval('(function() { async _ => _; })();'); if (typeof fetch === 'undefined') { throw new Error('no fetch'); } } catch (e) { window.location.replace('/legacy.html'); }