I got 20... that was rough AF. This just reaffirms my disdain for most DateTime parsing and libraries. Not just in JS, where it's *VERY* flexible, almost too much so. I really wish normies would get used to ISO-style YYYY-MM-DD format for dates, at the very least. Though I did once work on a project where early on a Jr dev had made the mistake of using YYYY-DD-MM, which is used nowhere on earth as a standard and was "too far along to fix"... Pissed me off to no end.
Yeah, Rust has a really good path to WASM for use in the JS ecosystem. I did similar with an html sanitization library a couple years ago and it ran about 5x the speed of a similar JS library at the time.
Source is obfuscated without sourcemaps, only the interface is mentioned, no link to docs in MozDev for the specs or API methods used by the example.
It's cool to show that something *can* be done, it'd be nice if it went the half a step further to guide to how it is done.
As pointed out in the article, the scope, arguments and 'name' properties are different for arrow functions.
One point not made, is it makes it easier to use tiered functions to make functional constructs and pipelines...
For example...
const takeWhile = (predicate) => (arr) => {...}
Can be used as a function that returns a function which takes the final argument... this can be used to build new functions that can be reused and passed around. It's often used as part of middleware patterns in various frameworks to handle various stages of middleware processing or not.
I really wish the site would point out and link to the Github repository for this project.
https://github.com/hodgef/PRSS
The link is spammy even if the utility seems nice. There used to be several static blog management tools for offline edit and publish, I wish there were more. I also wish there were publish targets for Cloudflare pages, and other JS SASS providers that would make a great target for this kind of utility.
I don't like Wordpress much at all, it's too big, bloated and the attacks from the script kids are just overwhelming to say the least. Mostly static content should be published to a mostly static, or at least vastly simplified platform.
I'd like to see the underlying data format be mostly markdown with a few HTML custom elements for better image and embedded snip options.
As pointed out in the article, the scope, arguments and 'name' properties are different for arrow functions. One point not made, is it makes it easier to use tiered functions to make functional constructs and pipelines... For example... const takeWhile = (predicate) => (arr) => {...} Can be used as a function that returns a function which takes the final argument... this can be used to build new functions that can be reused and passed around. It's often used as part of middleware patterns in various frameworks to handle various stages of middleware processing or not.