I switched to it from chrome and never looked back. Tons of good features, really customizable, and (what seems like) a pretty sound business model (no crypto!)
One of my colleagues uses Vivaldi, and he is constantly finding the weirdest bugs that I can only ever reproduce in Vivaldi, and that seem to break with every spec I can find.
* In all other browsers, clicking a "select file" element and then cancelling out of the dialog does not fire a `change` event on that element - except in Vivaldi, where you get a `change` event with no files in it.
* In all other browsers, setting the `Content-Length` header is enough for the browser to be able to give the user a file size estimate. Not in Vivaldi, which seems to use some other heuristic that I never managed to figure out - currently on our systems, the download dialog shows the file size as "unknown" and I've left it at that.
* Vivaldi has a feature where, if you close the window and then reopen it, it opens the page you were previously on. It's a nice feature, and I like it. Unfortunately, for the instant that the page is being reopened, any `matchMedia()` listeners will produce weird results. (Note that `window.screen.width` will still report a reasonable value, just one that contradicts the result of the `matchMedia()` query.) This is by far the weirdest and most niche bug I've found.
Obviously every browser has its own quirks - although modern browsers tend to have far fewer of them, so I'm much less tolerant of an evergreen browser that doesn't match spec these days - but what makes it far worse in Vivaldi's case is that, if you do find one of these bugs, the only way to report it is an online form with almost no feedback at all - there's no public list of bugs and not even a way to view the status on your own bug. Apparently they email you if something changes, but I've not experienced that yet.
In all fairness, from having tried out Vivaldi to reproduce these weird bugs, I'm quite impressed with how the browser feels, but the non-compliance with standards and the inscrutability of the bug report system have turned me off completely.
That starship one is nothing special. Sure, it got me to instantly download and install Starship and its recommended NerdFont without having heard of either one or knowing what they do, but I'm sure the page design had nothing to do with it. /s
Starship uses Vuepress, which is amazing. I used it for a side project and not only is the result great, but the setup is also extremely quick and painless. I find it a lot better than Docusaurus (the React equivalent).
This is the approach that works very well for me. Especially since I keep my repos cloned into a directory structure inspired by "go get" using https://github.com/grdl/git-get
Thanks, I'm familiar with the link you posted. You're also right that there's plenty of online resources about writing technical design docs.
However, what I'm looking for are not the articles about writing technical design but the actual design documents. Preferably ones that are considered well written by the community.
I've prepared some technical design documents for my day job. I think this somewhat comes close to the template that we follow. Take a look if this works for you:
You're not missing anything. It does use GitLab's mirroring API. However, GitLab doesn't have any global mirroring settings, you need to set up each repo individually. The tool just saves you a huge bunch of clicking around and copy pasting auth tokens. Useful if you have a big collection of repos you'd like to mirror. And if you'd like every new public repo to be mirrored automatically.
Can you share advice or recommend any resources on how to improve one's writing? Especially with regards to technical writing and communication in remote organizations.
You mostly get better at writing by doing it. There are a fair number of online publications that have editors and are always looking for writers. (Not paid but this is a case where it really is good exposure and a way to build skills.) Opensource.com is one I write for fairly frequently.
Try HFT companies. I live in Amsterdam, we have a bunch of them here and I used to work for couple of them. Their business is extremely low latency so they live and breathe C++ (and also stuff like FPGAs).
I switched to it from chrome and never looked back. Tons of good features, really customizable, and (what seems like) a pretty sound business model (no crypto!)