Urban Dictionary might be a better place for recent internet slang: https://www.urbandictionary.com/define.php?term=Cracked

Fair enough, I should know to check Urban Dictionary first. Thanks.

I'm not the person you're replying to, but here's my take: even though the two look conceptually similar, Unix programs are just a lot simpler. All programs run on the same machine, they read their input, execute, produce output which is piped to the next program, and terminate. Want to change something? Change one of the programs (or your command line), run the command again, that's it.

Microservices are a lot more complicated. You'll need to manage images for each of the services, a fleet of servers on which the services will be deployed, an API for services to communicate together, etc. In many (most?) cases, a monolith architecture will be a lot simpler and work just fine. Once you reach the scale at which you'd actually benefit from a microservice architecture (most companies won't ever reach this scale), you can start hiring devops and other specialists to deal with the additional complexity.

What actually gets hate, I think, is not microservices themselves, but the fact that microservices are often used in contexts where they are completely unnecessary, purely because of big tech cargo culting.

We only think of Unix programs as simple because we have many more abstractions nowadays. But you should compare a Unix program with DOS programs (probably CP/M also but I never wrote those myself) at the time. Poking directly at the hardware, using segmented memory, dealing with interrupts. The idea that a program should be well behaved, should accept things an inputs, should push outputs, and should have a virtual address space are actually huge abstractions over what could just be a block of code run on a spare OS. I'm not saying that microservices are better than monoliths, just that Unix programs aren't as simple as we think they are in a world where we're managing servers like cattle and not like pets.

    > should have a virtual address space

I'm pretty sure that most of the GNU POSIX command line tools were written before virtual address space (VAS) was common. And, as I understand, VAS is hidden from the programmer behind magical malloc().

This was a very enjoyable read. Thanks for sharing.

Very cool and fun project! Thanks for sharing.

The Q5 Pro is a 96% layout, but Keychron also has quite a few 100% layouts: https://www.keychron.com/collections/all-keyboards?sort_by=m...

Okay, now we’re talkin’.

I have a full-size Keychron with Cherry Browns and it is glorious. The Mac/Win switch means I don’t have to reflash the firmware to swap between Mac and PC usage.

Stripe does use Ruby, but not Rails.

Apple's ad business is fairly limited in scope (I think they only sell ads in the App Store and the News app) so user data is not as valuable for them as it is for Google and Facebook.

They definitely do make some money off Apple Pay transactions via interchange, but it's probably something like 0.1 to 0.3%.

Presumably this: https://en.wikipedia.org/wiki/Yahoo_Sherpa

There are definitely some parkings where you can only pay with a smartphone. The worst is when they force you to download a shitty app. Super fun when the parking does not have good reception and you have to download an unnecessarily large app over 3G.

I've also been to random parking lots in the middle of nowhere with a cardboard sign saying "Venmo $5/hour at X".

I'm not sure I understand how your analogy is relevant to the discussion, but you should know that the current consensus is that the pyramids were build by paid laborers, not slaves. Cf. https://en.wikipedia.org/wiki/Slavery_in_ancient_Egypt#Great...

The point I was trying to make is that being part of building something great isn't always a reward in and of itself.

The laborers of many great works reaped no rewards for their efforts, and the people remembered for the work were often those standing on their backs.