I’m not saying the robot is “right”, but the number of people crusing around with their high beams on as a matter of corse, is as they saying goes, too damn high. So I can absolutely believe that a vehicle’s high beams limited its “vision” because that regularly happens to me driving and as a pedestrian.

Now if the robot fled the scene that’s a completely different issue for which it’s operators are responsible.

For now…

While that’s a nice and logical thought, the fact is renting a car for a vacation adds price to the vacation and if youre already committed to a gigantic payment for a new car, renting a car for a trip is a non-starter for many people.

Not saying either is right or wrong. Everyone has to make their own value judgements for themselves.

You’re imagining a ui optimized for accessibility, which benefits LLMs but is not the same as an LLM optimized interface without having a visual component for regular human users.

You might, I think I would (at least personally, professionally I may not have a choice) but the vast majority of people will gladly go with this plan I suspect.

Look at car purchasing, most people don’t look at the sticker price or the total cost of ownership, they stop paying attention as long as their income can (and in a lot of cases it technically can but really shouldn’t) support the monthly payment.

Similar thing with new phones, most people buy a service plan that includes a lease or loan on a device. Very few people buy their sevice outright, because that’s a big purchase vs. a smaller monthly payment.

If there was a market for this for laptops, regular folks would eat it up.

That’s all opinion, so take it for what it’s worth. I hope I’m wrong. I’m fearful I’m not.

Off topic, I know, but I’m curious what you’re reading about the next ice age. Always found that history interesting, but never thought to look toward the next one.

That maybe true if youre single shotting. At some point, but that’s rarely the end. It takes iteration and experience to get LLMs to do useful work in most cases.

whips*

I don’t understand, do you not like Windows Terminal? I have found it to be one of the better parts of Windows 11. It isn’t perfect, but miles better than cmd.

It sucks that you had such a rough translation. I never felt hoodwinked, because it was always clear to me that any parts of .net that were for winforms or WPF would never fully supported off windows. And that certainly makes it hard to transition projects that started on the legacy framework before core.

With that expectation on my mind, I haven’t had these experience, most things I’ve wanted to do just work on Linux, CLI and web hosting. For GUI I’ve used Avalonia which has been great, but it’s definitely not a thing you just port to. Its viable for greenfield.

What do you mean not Linux friendly? Some of the legacy windows components of .net are not being supported, but that’s because there are alternatives that are better. ImageSharp is a huge improvement over system.drawing.

In the pre-AI days maybe, today 50TB is expensive due to increasing prices of all computer gear.

Do I need the ./s?

How else are the kids going to call a waymo to get away?

Maturity gap sounds more like a hiring miss on culture fit than an issue with mentoring. More of an org issue IMO. Their education level shouldn’t really matter if they have a good attitude and willingness to be coached.

Part of the job of senior devs is to mentor juniors regardless of their background. Not to gatekeep over your own degree.

Pushing SSL was probably the last big tech effort/push that actually benefited users. Sure it made self hosting a little harder, and probably consolidated some tracking behind bigger players, but overall end users did benefit.

Most of what I see now is purely for their benefit and users don’t benefit.

While true, the latest opus model has 1m token context. Which is a lot more than the previous 200k limit. Hard to fill that up with regular work, but easy if you try to oneshot a whole product.

While I agree with this, and I’m not defending skirting regulations, before rideshare apps, taking taxis was an awful experience. At least half the time, if you try to pay with a credit card, the machine was “broken”, if you wanted to get a ride at a specific time you had to call ahead and hope that a taxi would show up.

Rideshsre apps forced regular taxis to up their game and provide better service, some did and now have their own apps.

I mostly agree. It won’t replace people directly, but it might let companies do more with fewer developers.

Not to say they don’t need anyone, but maybe they get by with 75 instead of 100 developers? Hard to say where that falls because the outcomes if ai usage are so variable based on skill of operator and the target codebase.