grepexdev

I think what he means is it is not just generally crawling and scraping, and uses a more targeted approach. Equivalent to a user going to each of those sites, just more efficiently.

Did you mean to include a link to the list?

If I buy a pencil and draw a copyrighted character, is that copyright infringement? No. If I sell that drawing? Yes.

Midjourney and other AI companies are not selling you the drawing, they're selling you the pencil. What you do with that pencil and the drawings you create with that pencil is on you and you alone.

Same! When he was last on the Lex Fridman podcast.

Are you familiar with the DICE framework in terms of VR? Essentially, VR enables one to do things that are [D]angerous, [I]mpossible, [C]ostly, or [E]xpensive.

Your racecar example is a perfect example. It would be dangerous and costly. Would it be better than VR racing? I think so. Would I be able to actually do it? Hell no. I suspect most people would answer the same.

Yes, I know expensive and costly are basically the same thing.

This! I recently ditched Spotify and rediscovered radio in the past few weeks. There are so many great songs I've come across from bands I enjoy that I had never heard of because, as someone else said, Spotify's algorithm is way overfit.

The reason I emphasize that he said it and didn't write it is because it indicated to me that you weren't aware it was actually a talk he gave and you were just regurgitating a cherry picked quote that's been passed around since he said it.

That further indicated to me that you are not aware of the broader context of what he was saying. He literally spends the first 19 minutes talking about writing something in C++, then says the quote.

It seems it is you who is catering to your own biases by using a few sentences from a 20 minute talk to oversimplify what Pike I'd saying.

The interpretation I am giving is based on the entire talk, not just the quote. I acknowledge that he said Go was created for less experienced devs, but I don't think it that means it is a step backward as you said. It enables so much to be done by the "dumber" demographic, as you so eloquently put it. Go, like any other language, has its limitations. It shouldn't be used for everything, but should be used for the things it is good at (obviously).

I understand what you are saying here but I think you've missed the point of what Pike was getting at.

I think Pike is acknowledging the practical realities of engineering at scale, and intentionally designed Go with simplicity in mind, which leads to more maintainable code and faster onboarding for new devs.

I'll also add that outside of the popularity metric, Go is not all bad. Fast compile times, readability, excellent standard library and toolchain, backward compatibility, to name a few things.

I don't think Go is particularly esoteric to where these "gotchas" are a big problem.

In fact, I would argue that the gotchas are an intentional part of Go's design philosophy. I think it is strange to work in Go when coming from another language because of this, which leads people to think Go sucks.

Could you let me know what language doesn't have at least 100 common mistakes across a broad range of developers with varying skill level?

Perhaps. But I'm sure Microsoft releasing Agent mode at the same time is not a coincidence.

I would recommend getting started with lazyvim (lazyvim.org). Once you're comfortable with the editor, you can change the config to kickstart.nvim and start customizing it to your liking. That's what I did and I have no regrets. LazyVim allowed me to switch without sacrificing productivity. I was on it for a year before I decided to make my own config