121–130 of 322 posts
Now we’re talking. If Flutter is dying, how come I still see projects like this popping up instead of using native or KMP?
Makes me wonder if you might eventually see the OG Flutter team move to a shop like Toyota, the same way the original React team moved to Vercel. It's nice to see open source projects be portable beyond the companies that instigated them.
Earlier quoted context omitted.
Part of what has made modern EVs successful in the wider market is the connected navigation system that knows your battery level, current consumption, planned navigation route, and what charging stations are available along the way. To have a decent travel experience in an EV you'd likely at least need this data ported out to your phone via an OBD adapter or CarPlay / Android Auto integration with an in-car infotainm…
Connecting via ODB? Come on. The car does not need any of that built into it. You can connect an app on your phone to handle all of that and just use the screen as a display. There is no need for a car to have a cellular connection just to give this functionality. That would also prevent the car from being able to communicate with the mother ship. If there's an update, have the app do that as well.
Ol' Dirty Bastard? I jest, but I think the theory behind wanting an 'On-board Diagnostics' [1] connection would be to get data from the vehicle. You can get cheap bluetooth OBD-II adapters to transmit that info to your phone, it's not a given. I don't know much about electric cars, but if you want your phone to know the fuel level in an ICE vehicle then you'd need this kind of connection.
Earlier quoted context omitted.
No, it's common to all vehicles. You can't see small children behind a small passenger car, either. Blaming trucks and SUVs for everything is a favorite pasttime of internet comments, but all vehicles benefit from backup cameras and collision detection sensors.
The US averages 23 pedestrian deaths per million people per year. The EU averages 8. The US fatalities have increased by 50% since 2013, while in the EU have decreased by 25% in the same time frame. https://www.cdc.gov/mmwr/volumes/74/wr/mm7408a2.htm
Americans drive significantly more miles per year, and larger/more comfortable cars are in part needed because Americans spend far more time in their cars than Europeans.
Euro governments are also increasingly anti-car, which means citizens are loosing their freedom to travel as they wish and unreasonably taxed, policed, and treated like cash cows for the "privilege" of driving.
Earlier quoted context omitted.
How are you going to maintain all that when you find bugs if it generates a ton of code you did not get through to understand it?
You don't, and as long as you're comfortable with that you keep prompting to dig yourself out of holes. The problem is unless your ready to waste hours prompting to get something exactly how you want it, instead of spending those few minutes doing it yourself, you start to get complacent for whatever the LLM generated for you. IMO it feels like being a geriatric handicap, there's literally nothing you can do because…
To the degree that those same people are now writing 10-100x more code...that is scary, but the doom and gloom is pretty tiring.
Earlier quoted context omitted.
No, it's common to all vehicles. You can't see small children behind a small passenger car, either. Blaming trucks and SUVs for everything is a favorite pasttime of internet comments, but all vehicles benefit from backup cameras and collision detection sensors.
The US averages 23 pedestrian deaths per million people per year. The EU averages 8. The US fatalities have increased by 50% since 2013, while in the EU have decreased by 25% in the same time frame. https://www.cdc.gov/mmwr/volumes/74/wr/mm7408a2.htm
The US was ahead of the EU in requiring backup cameras on new vehicles.
The majority of pedestrian accidents aren't involved with backup cameras.
Are you just trying to turn this into a US vs EU argument?
Earlier quoted context omitted.
> buy one of those tablets that you stick on your dashboard and plug into the aux port Every single car I have been in in the last 5 years or so has Bluetooth. No need for aux ports in this day and age, especially when devices dont have headphone jacks anymore. Are you stuck in the 2000's?
I still use headphone jacks on my phone, I wouldn't buy one without it. It is just more garbage to manage and more stuff to fix when it doesn't work. It takes half a second to plug in a cable and I don't gotta run around broadcasting a bluetooth signal which drains battery when not in use and takes as long to disable as pulling out a plug. Plus it is often lower quality than the cord. Bluetoothing to your car is to m…
Earlier quoted context omitted.
This is 10 year old outdated, but 10 years ago 1 button was ~1.00. Probably closer to $1.20 or $1.30. But sometimes buttons had 2 buttons on them, Those would go for $2.10-$2.30. Then you had wiring each button wire I believe was $1. This wasnt 1 wire, but a few wires, power, ground, signal. Each button had them. This wasnt my job, so I didn't follow this price too much, but I asked the question at the time. I think…
> Anyway, you could assume 10 years ago, each button was $2. A car has 40-70 buttons? So its probably like $100 a car. Maybe $150 or $200 in today's money. I have a late 90s Range Rover. It has about 12 buttons on the dashboard, most of which I never have to bother with (they do things that turn on and off the fog lamps, which I don't need to use, or adjust the air suspension, which I rarely need to use). I turn the…
Backup camera. They are required by law.
Earlier quoted context omitted.
They needed a GUI toolkit for dash display, and didn't really like long engine init time of Unreal/Unity/Godot.
Was bevy considered?
Earlier quoted context omitted.
> Real buttons are more expensive than electronic. It might add up to a lot of money for the manufacturer who is cranking out thousands or millions of vehicles, but to the consumer buying one car it isn't a meaningful difference.
This is 10 year old outdated, but 10 years ago 1 button was ~1.00. Probably closer to $1.20 or $1.30. But sometimes buttons had 2 buttons on them, Those would go for $2.10-$2.30. Then you had wiring each button wire I believe was $1. This wasnt 1 wire, but a few wires, power, ground, signal. Each button had them. This wasnt my job, so I didn't follow this price too much, but I asked the question at the time. I think…
That doesn't make sense. $1 uninstalled might make sense for a fancy custom-molded button, even if it's too much for a generic button. (I'd rather have some generic buttons with labels than use a touchscreen, by the way.) But there's no way a few feet of signal wire and the proportional share of power wires get anywhere near $1 uninstalled.
Also I can find entire car stereo units with 15 buttons on them for $15? That kind of integrated button is cheap, has been common in cars for a long time, and can control things indirectly like a touch screen button if that's cheaper than direct wiring.
Please stop, all this does is introduce new ways for things to break.