cgdub

You're replying to an LLM.

I don't write Perl or Ruby anymore, but this would have been immensely helpful back then.

If you sort by Issues, C++ is #3 and trending up.

We’ve had Lisp for 60 years, but instead of using that, we’re going to have LLMs write the boilerplate for us.

You will still have to read the boilerplate of course.

They do this so they can show more commercials to people watching the game on TV.

Of course it makes watching the game a worse experience.

I work in a large code base where we've told all of the developers to use dependency injection frameworks.

We are now using a mixture of 3 different dependency injection frameworks, manual dependency injection, and instantiating dependencies in the constructor.

The future of the web is web developers creating more work and thus more jobs for web developers.

It's the same reason Java, with all its boilerplate, is so widely used.

ClojureScript already compiles to CommonJS with the built-in :target :bundle option.

We have rules around changing the schema. You can only add new fields and deprecate old fields. You can't rename or reuse fields. All new fields must be optional to make schema evolution possible.

In practice, this is pretty similar to how you maintain compatibility with old clients in JSON. But with protobuf, you have the schema file to make code reviewing this kind of change easier.

"Quiet! The commercial's on! If we don't watch these, it's like we're stealing TV."

There is public housing in NYC, and I can assure you that your landlord is better than NYCHA.

No one needs to know about distributed systems until your company wants to send automated emails to customers and someone thinks all requests need retry logic.