I have stopped buying any new vehicles that collect “data” and has an internet connections for a long time. But it seems plenty of people does not care about it.
Every time I look at how easy for people to use this kind of thing but people tends not to, remind me if so-called "memory safety" is a real concern anyway.
I am not sure for people who wrote this, did they realize most of the time these conversations are just for politics reasons? In a non cooperative environment, projects moving fast does not mean individual is moving fast or vice versa. But if you are in a cooperative environment pretty much people just act what he suggested naturally.
The fundamental question is that if an address is “safe” is a runtime thing, which in some cases you can decide it in compile time but not always. To force that during coding is just handicapping oneself to be “safe”. Which you can do the same in C (or mostly any language if you want it)
The languages we're discussing here are high level - like C - and so they don't have addresses like the machine code, they have pointers. With pointers we're back to the compiler needing to know if they're valid - if you delay until runtime you lose not safety but performance before the compiler optimises based on knowing whether values can be modified via a pointer and if that's only decided at runtime we cannot perform these optimisations so now our program is slower or bigger or both.
reply