burtekd

While I agree with the majority of the arguments, there are some cases where toolchains make it easier to manage monorepos. With JS/TS we had a monorepo with react web app, react-native mobile app and a shared REST API client library. Once a change was made to the library, tooling bumped library's version based on commit message (conventional commits) then updated the library version in both apps, bumped their versions too and released them to staging. It worked for us and was something that would require more config to achieve with separate repos.

I believe it's up to developers to decide what suits them best based on their requirements, process and tooling.

True however that putting everything in monorepo just for the gist of it is not the best approach.

Love how everyone plays with redundancy - multiple hosts, balance loader, etc, and yet half of the web relies on single point of failure being CF

I'm just gonna leave this here too: https://www.youtube.com/watch?v=MijmeoH9LT4

How did noone post https://xkcd.com/927/ yet?

I love how the only two omegle.com links on hackernews are one from opening in 2009 and one from closing in 2023

It's not a hack. It's just sending a well-known three tones sequence on given frequency.

Thanks. The "unrevokable" part sounded fishy, but I get it now.

Can someone explain the unrevokable legacy IP addresses?

> high-level statement about a relevant side point

Here's how it really works. I'll write a couple paragraphs on all the exceptions I can think of, explaining how you should have said "often" instead of "almost always".

The author acutally posted above your comment ;)

One word to sum this up: wow

Pixelart images?? You sir have too much free time on your hands

Love the outcome though

I love Tom Scott's explanation of Unicode: https://www.youtube.com/watch?v=MijmeoH9LT4