We had an optics lab at the Faculty of Engineering, Lund University about the idea behind the FlatFrog display system back in 2014 (I think) and I remember thinking it was genius.
It bothers me immensely that they redirect docs for services that work perfectly fine by themselves to amplify docs with a note that says something like "use amplify".
Other than that, using AWS services directly is always a much better experience. In my opinion amplify is like a dumbed down version of that.
One of the best tips I have gotten from the internet is to never copy and paste code you have not written yourself. Even rewriting it verbatim makes you think about what it is you are actually copying.
You could use GitHub issues for posts and comments, fetched using the GitHub API. I did a proof of concept of this a long time ago [0]. Not sure if it still works.
Pretty much the same with SVT in Sweden. They also have a site called ”öppet arkiv” (open archive) claiming to be one of the world’s largest TV archives.
Just because they are both open source does not mean they share a common goal or methodology. My guess is that KaTeX was written to overcome the deficiencies of mathjax.
Yes, I decided to add the instantiations for readability. It would be more efficient in a production setting to do the operations directly on the raw data.
I've been to two AWS Summits (Stockholm) and most if not all AWS employees explicitly point out that you should never use the console for anything serious. It might be good for presentations, but it's horrible when you need to manage infrastructure.
For anyone working with linear algebra in Node.js, I wrote C++ bindings to BLAS a couple of years ago [0]. I also started working on bindings to LAPACK, but never had the time to finish them [1].
> (There's also of course the personal satisfaction you may get from knowing a bunch of strangers use, and maybe even love, something you made or contributed heavily to).
From my experience this is actually way more rewarding than getting paid.
I’m quite the opposite, I feel like MDN is the only sane resource in an ocean of opinionated crap. Not saying it covers everything but for syntax it’s practically the only place I visit.
You can't count productivity in hours. Someone who goes "all-in" 6 hours a day can certainly accomplish more than someone who says they go "all-in" 12 hours a day.