You know what? For once I'm going to defend my fellow front-end developers (right? 🤣): I'm sitting in a meeting where async operation is moved from back-end to front-end because BE devs feel "dirty" about having their servers stateful. However, we just move this stuff to web app and then people complain about complexity and #javascript on front-end.
=> More informations about this toot | View the thread
Reminder to always add engines field specifying #nodejs version to your package file. I wish this metadata was automatically added there whenever you do >npm init<. Same goes for package manager version. It would make all of our lives easier. #javascript https://mas.to/@frontenddogma/113585478554019751
=> More informations about this toot | View the thread
:golang: anybody knows whether #golang program can compile other go programs? I know about os/exec but was hoping there is some API from stdlib exposed.
=> More informations about this toot | View the thread
For example - should I build my server in Go if I expect the traffic to be in lower thousands of requests per minute? Or is this something that NodeJS/Bun runtimes handle just fine, given it's running on decent hardware.
(This is just an example - I just gave those numbers as examples and have no idea what the real figures would be) (2/2)
=> More informations about this toot | View the thread
Does anyone have good performance comparison between #javascript and #golang? You read a lot how certain (usually compiled) languages are more performant and I wonder whether there was an article comparing these two and what are the hypothetical scenarios where one does better than the other. (1/2)
=> More informations about this toot | View the thread
The only thing missing from this setup is the validation part. The validation happens when you run docusaurs build and checks whether links are valid etc. I'd like to run this validation part without installing Docusarus, but not sure if it's possible. (2/2)
=> More informations about this toot | View the thread
We like to keep it this way, originally mkdocs was used to serve this documentation. This proved to be insufficient though so looking for replacement.
The tricky part is the build process in CI. I couldn't think of anything better other than putting these markdown files to S3 bucket, which in turn triggers the build process in the "docusaurus" repo (our internal doc site). (1/2)
=> More informations about this toot | View the thread
My goal is to gather various documentation sources from multiple repositories into single source of truth (Docusaurus documentation site). I know it's not the usual way to do this. Basically I will need to pull in markdown files from different repositories and build the site, without checking all of these gathered files into the documentation (Docusaurus) repository. The reason to do this is because the source of truth is in those other repositories (co-location with code). 🧵
=> More informations about this toot | View the thread
Does anyone have any experience with #docusaurus in multi-repository setup? More in 🧵
[#]javascript #devx
=> More informations about this toot | View the thread
=> This profile with reblog | Go to ondrej@social.synacek.org account This content has been proxied by September (ba2dc).Proxy Information
text/gemini