One of the good things in the UK is seeing how quickly my neighbours swapped out their Tesla's for BYD's.
I'm not in the market at the moment so don't know what the UK protectionism position is on Chinese EV's, but has been interesting to watch how quick it's happening.
I work in design and we're talking to two Chinese EV companies launching in the UK this year, so the wall can't be that high for them.
The UK has a local car manufacturing industry (Nissan, Jaguar/Landrover), but not large enough to be able to lobby for protectionism. And in any case the UK has basically given up on having a coherent trade policy since Brexit.
I've seen quite a few BYDs and MG4s, and there are Jaecoo and Leapmotor dealers near me. I've been told that some NHS boards were using MGs as "pool" cars, but the only example I can find a reference for is Shetland. https://www.nhsshetland.scot/news/article/43/nhs-shetland-ro...
I don't think I've ever seen a Rivian. The R2 is supposed to be coming to the UK in 2027.
Imo its not anti-China protectionism. Western models are cheaper in China, and Chinese models are more expensive in the EU & UK.
I think it's a combination of manufacturers wanting a higher profit, some adaptations & certification processes, dealer and service infrastructure necessary for selling in the West that just costs more.
I don't think Chinese manufacturers will be able to significantly undercut the competition while maintaining a desirable quality
Same here! American-made EVs ask for an incredibly heavy price tag and don’t deliver on the reliability of ICE or Hybrid cars a third of their price. It’s the primary thing stopping me from getting one as my next vehicle.
I’m trying to shop around to replace my wife’s aging crossover and I really can’t find anything more attractive than a Prius or another Kia Soul. If we could get electric cars from the CN market it’d be a no-brainer!
I’ve had software issues on an ID4 and iX, but I’ve never had reliability problems. The cars always have just worked with no maintenance. Same with my model Y, minus any issues!
Maybe it’s a “but when it happens you’re screwed” situation. I’m thinking of the story of BMW’s battery safety fuse (the one that trips in an accident to protect first responders and the people in the car) actually tripping when you hot the curb or a pothole harder. It requires a very expensive trip to the dealer. Some of my Tesla owning friends keep spending time in the shop getting something about the suspension fixed 2-3 times already.
I have no idea if Chinese EVs are consistently better, Volvo can be seen as one and I don’t think they excel at reliability lately.
P.S. Software issues are reliability issues. The software is a core part of the car and its value proposition, you can’t discount them as “just software issues, not reliability”.
Well, there’s also the fact that some organizations actually tie career progression to patents authored by the company. My brother works for a company that offers multiple technical career pathways to promotion, and one of them is essentially “obtain a software patent”
Great if you’re you, but try getting AverageSWE a local kube setup and see how quickly they ramp up on it
In my ideal world everyone would use kubernetes, it is the hammer and everything is a nail, but we must recognize that it is difficult for a lot of people to pick up.
That being said, if you’re deploying on kube in production, use kube locally. But if you’re not, dont
Using kube in production but really, even if I wasn't, I would still use the podman play kube approach. It isn't hard (at all) and isn't kubernetes, just kubernetes yaml. I actually find docker / compose a bit harder sometimes with the daemon running in the background.
I mean if you are going to bother to introduce the concept of kubernetes yaml to a developer shouldn’t you just go all the way and teach them proper k8s instead of some weird intermediary? I fail to see the value of offering k8s yaml that isn’t k8s or one of its siblings that’s basically k8s
I'm not arguing for the relative superiority of jsonnet vs yaml vs anything else. I just recognise that Docker Compose is loved by most open source developers. And invariably any project you touch will have a docker compose setup by default.
I'm just making it possible to run those on kubernetes seamlessly.
Tilt is great but it doesn’t solve the problem you’re asking about. This project more directly addresses that. Fundamentally the problem is that you want to maintain the lifecycle of several services during an ephemeral ci run and tear them down when you are done. As you mentioned it gets unwieldy and annoying to try to run all of these on a single machine and doubly so when you have a lot of services/containers. Kubedock is more like what you are looking for, it translates compose calls to Kube equivalents and each service in the compose file is it’s one kube pod with its own lifecycle. It should be possible under that to do what you are saying, spawn multiple docker composes from a single run.
It is worth noting that Kubedock has some really annoying limitations, part of it is that it’s one person the other part is that some concepts don’t translate to kube very well. So make sure that whatever you will be doing fits into those constraints before you try it
Why is obesity not considered a necessitating condition? It often carries the comorbidities you just mentioned. Should not exclude people just because they haven’t had these specific health problems (yet) but will eventually have them.
The problem is that if it's just about obesity, you have to prove that cheaper treatments such as diet and exercise didn't work. That's not impossible to do, but it's hard and annoying even for people who really were trying. My doctor told me that you basically have to keep a detailed journal of your weight loss efforts for months on end.
Are GLP-1s so much more effective that we should make an exception to the general principle, maximizing healthcare resources by providing the cheapest effective treatment? I kinda think so, but I have a conflict of interest, and I can understand why others might think that money is better spent elsewhere.
While I tend to agree, insurance companies don't see it that way. They need a doctor to indicate a necessity to treat a condition, as opposed to it being the easiest way to treat it.
For example, I have to take digestive enzymes to digest my food (pancreatic insufficiency). For someone with an unusually high metabolism, they would also give them a leg up on gaining weight, even though there are other approaches to gaining that weight. However in many cases, the insurance company wouldn't cover their prescription when they will mine.
As always it’s insurance nonsense. If incentives were aligned insurance companies would be lining up out the door to give this to obese people because they (the insurance companies) would eventually be on the hook for paying for the care of the conditions you just mentioned. It is very well demonstrated in literature that obese people have a much higher occurrence of these conditions than non obese people.
But the system is not set up with aligned incentives
Actions is many things. It’s an event dispatcher, an orchestrator, an execution engine and runtime, an artifact registry and caching system, a workflow modeler, a marketplace, and a secrets manager. And I didn’t even list all of the things Actions is. It’s better at some of those things and not others.
The systems I like to design that use GHA usually only use the good parts. GitHub is a fine events dispatcher, for instance, but a very bad workflow orchestrator. So delegate that to a system that is good at that instead
“Light work” is a pretty bold statement my dude. I run max for 8+ hour coding sessions with 3-4 windows where I’m babysitting and watching the thing and I never even get session warnings. The only time I bump up against limits is on token hungry tasks like reverse engineering 3M+ LOC codebases or 5-6 agents generating unit tests in parallel. Something tells me that what you call “light work” is not remotely the same as what I consider “light work”
Postgres is widely used enough with enough engineering company blog posts that the vast majority of NotPostgres requests already have a blog post that either demonstrates that pg falls over at the scale that’s being planned for or it doesn’t.
If they don’t, the trade off for NotPostgres is such that it’s justifiable to force the engineer to run their own benchmarks before they are allowed to use NotPostgres
reply