victorvosk

I don't care what the official line is, something changed with it. It might be the same model but the way it answers questions and the content of those answers is much more dubious now. I think how it manages its conversation context was gimped in the web chat version. I find it routinely completely forgetting things in longer conversations.

Bobby at it again

I know everyone is high fiving but this like most Euro tech laws, is so obscenely murky and essentially opens the flood gates on anyone running servers over there.

I always liked cars as a kid. Faster the better. But Tesla kind of broke everything. A super car for 150k and its only going to get cheaper and faster as time goes by. There is no longer any parity. EV's don't have roaring engines, outside of the cringe fake engine noises some are adding. There is nothing to be excited about when your future 30k 4 door sedan can do 200mph, 0-60 in 3 seconds.

I thought "should" was a product of silly TDD, like my widget "should do this thing" and it doesn't yet because TDD, and then the developer would implement it.

Hot take, I feel like people that complain Rust is hard typically write bade code in other languages. Rust is just preventing you from making common mistakes or using patterns that make your code hard to reason about and debug later.

Real people have disagreements and work through them. Lets not be mad for the sake of being mad. It was completely within the rights of WOTC to do whatever they wanted. People complained and they decided not to do and guarantee they will never do it in the future. Be happy.

I love how this software would have been legend in the 90s/00s but now you are just a weird audiophile nerd for messing around with physical CDs.

Basically the problem with every framework that think its fine to sprinkle in strings as code in html.

I am nearing that age, and personally I find its a factor of motivation more than anything. I got really excited about a side project last year and smashed out more code than I had in years. Refactoring an api for work doesn't sound super exciting. When I don't care, my brain doesn't care as much either.

If you do not believe that is a factor then examine your sleep and physical fitness. These things factor a lot more into brain function as we age.

Honestly this feels like an old man screaming at the wind type thing. Inevitable doesn't even begin to describe was going to happen over the next 20 years. You should be much more terrified of when their content isn't garbage.

I just got a Pixel 7 Pro. My photos look obscenely good. The new macro lens let me take a picture of a fly up close and you could see the individual hairs on its abdomen. It looks like it came out of a national geographic. I can't believe "normal" cameras even still exist for most photography.

Tailwind was the response to the "I need more control and customization than bootstrap or (insert framework here), but I also don't want to write a ton of vanilla, best-practice css."

You can easily add your own custom classes. You immediately jump to a complicated problem and say Tailwind is bad because it doesn't handle this edge case well. (btw, its not trying to handle it)

I find co-pilot useful when I am working with a language I am not familiar with but I imagine that isn't the case for most developers working their day to days. I see ML and AI in dev as more of a code generation tool. Describe something large in a prompt, get a bunch of code. Then a dev can run through it like a code-review, making changes and tweaking it to suite the need of the client/business.