oflor

4 ms·

1.
by oflor 4y ago
Rewriting a module from one tech stack to another is not much harder when that module was a part of a monolith and not a separate service, except that you haven't paid the upfront cost of bootstrapping a new service, putting in RPC cal
2.
by oflor 4y ago
Tech zoo sometimes considered to be an anti-pattern in microservices. By introducing a different language into your organization, you decrease the mobility of developers between code bases and dilute technical knowledge.
3.
by oflor 4y ago
> This references the "fuzzing" infrastructure hosted by the Reproducible Builds project, and doesn't show "true" reproduction of binaries. It's designed to help us figure out where impurites occur in builds
4.
by oflor 4y ago
You can always run Nix in Docker to build and run any software that uses it. Without Nix, however, I am forced to either install a bunch of bloat into my system such as Haskell compilers or libraries, or run Docker anyway.
5.
by oflor 4y ago
And how does it recover incomplete tasks in case of sudden power outage? Microservices use persistent message brokers for that, which are not there in threads. Or are these monoliths all treated as pets with redundant power supply and netwo
6.
by oflor 4y ago
I'm sorry, I don't have a good answer for you. While PGP-like web of trust is accessible on native desktop and mobile applications, it's certainly harder to use in browser. I don't think that it should be an argument aga
7.
by oflor 4y ago
It looks a lot like XMPP with some of its flaws – too much flexibility and no principled stance on privacy and security issues. For example, I couldn't find how ActivityPub supports signatures of sent content, while Mastodon (one of Ac
8.
by oflor 4y ago
It's not difficult, but it's disrupting to your coding flow, which is bad in itself and even worse when prototyping.