juanbyrge

Yeah I can't take Marc Andreessen seriously any more after that incident, no matter how hard I try. He wrote that surreal letter objecting to building multifamily/affordable housing, claiming it would immensely reduce the property value of his walled mansion in Atherton. It just reeked of pettiness and hypocrisy.

This is just a sad attempt at marketing to OSS maintainers. Whoever came up with this idea has no idea how OSS maintainers operate.

Python is great for small scripts or explorations. You can't use it for anything serious that needs to scale due to the lack of concurrency and significant memory overhead. If you need something to scale you use something like C++, Java, Go, Rust, etc.

One data point: my wife and I were set in getting a Tesla as our next car. We are now in the market for a new EV, but we both decided against Tesla due to Elon's shenanigans. We will wait for the Kia EV9 or something coming out next year.

Lol, I could host all of substack as static html pages on a $20/mo linode instance. Embarrassing.

To be brutally honest it does not seem like Slack is the actual problem. I think you are having difficulties performing and are looking for an excuse, and Slack seems convenient. Just uninstall the Slack desktop client and use the web browser once or twice a day. Get real work done.

We used to pay CircleCI $200/month to run CI on a widely-used open-source project, which was set up before GHA was available. Around one year ago we switched to GHA, which was significantly better, and cost $0.

At around the same time we made the switch, we got an opaque email from CircleCI about their new `performance plan` which would have increased the cost to $300/mo. This was more metered pricing.

Anyway GHA has been a breath of fresh air and I have convinced several open-source maintainers do dump CircleCI in favor of GHA.

I think the primary use case is building the same code on multiple platforms. A developer can write a single CMakeFile and then CMake will generate Makefiles/Ninja files/VS soln files/etc depending on the underlying platform.

Now all of a sudden those physics problems involving shooting a gun while on a train seem a lot more depressing :(

To me that is a specious argument. It's like asking why Python was invented when Cobol could suffice.

The dozens of ASN.1 specs are absolutely hideous and entrenched in obsolete telecom jargon. If the sole goal Protobuf was to avoid having Google engineers be required to refer to the dozens of ASN.1 specs when disagreements or confusions arose, then it would have been 100% worth it for just that reason.

I feel like I have derived so much value from Google Maps, especially turn by turn navigation, than I don't even consider the advertisement aspects. I would happily pay a monthly fee to use it.

Before it you had to use paper maps or use those very expensive and crappy Garmin devices.

I am guessing FANG engineers (and most engineers in general) would unanimously suggest "delete this ridiculous , ill-conceived JNDI integration ASAP. If people want JNDI integration, use a custom opt-in log4j appender. Don't let this shit be enabled by default". Yet that may not sit well with the log4j folks.

This feels like the Google Plus fiasco all over again. Throwing an entire company at making a social product that nobody will use. Good luck!