Notably that's not due to subsidization but rather due to investment in capex for future growth. The reason to not subsidize is largely because of already being hardware constrained. There is no extra unsold capacity to use.
Companies at the size of Google naturally have different business units with different goals. Flutter solves something from some teams with other parts of the company that do not solve for them. That doesn't mean there are some sort of systemic problems. It just means that it operates more like a series of smaller companies in many ways, which is overall healthier for everyone. It's confusing that everyone always expects some sort of unified strategy from the top. That's like suggesting countries should act more like dictatorships rather than democracies.
For devices that are entirely controlled via an MCU and lack wireless connectivity, that is probably true. However that's not true for the pixel watch. The cpus and dram take significant power.
Murder has a negative meaning. Let's name it "neutralization" or "sending to a higher place".
Giving it a new name doesn't mean the original name is less correct. Vulnerability is a relative definition. It's a vulnerability in the context of the chipmakers security model but not necessarily yours. It could be a hidden feature in your world.
If they can get productivity increases equivalent to .1% it pays for itself. That's roughly equivalent to firing 1 in 1000 employees to finance the software.
Preventing you from faking data is exactly what attestation is designed to do. You want something different from what the folks requiring attestation want. That's fine, but just don't expect to be allowed to use those apps.
If someone holds a gun to your head and tells you to run a red light, who is liable? Humans can get persuaded to do illegal things by criminals just as well.
I'm not suggesting a new system or a timeout. I'm suggesting passing a two sided handle (like a socket) where you can listen for the other end closing. Upon closing, which should only happen due to a bug or the process exiting, the notification bar can remove the icon. This is IPC 101.
Look at the git stats for the project. Lines of code submitted haven't changed dramatically. Not everyone is just merging slop into the codebase. There are many ways to use AI, and most established players are not merging vibe coded nonsense.
There is hype, but there are also real tangible wins as well. Analyzing code for bugs is something that works very well. We use it for helping us revert changes that lead to a flaking test and it's dramatically faster than previous techniques. It's great at suggesting duplicate bug reports. It's amazing at scaling an API migration throughout a codebase. It's great at prototyping an idea before you decide to do it properly.
There are many things it's not good at (eg design and architecture), but that doesn't invalidate the things it is good at. Everyone is learning how to best use it and there are growing pains. Ignore the hype and try to find the common patterns in what people say.
I don't think there is anything wrong with increasing liability for writing preventable bugs. The floor should be raised as our tools improve and the negative outcomes of these bugs increase. Making c illegal is not a goal of anyone I know of.
More specifically apps and users have equal agency in the android security model. Which comes down to the fact that if you don't own the app you can't control its experience. This feels grounded to me. Push for more open source apps where you retain control and ownership.
Have you read the android security model? It's a multi party security model which considers apps and users as equals. It's a legitimate security model and just because it's not what you want doesn't mean it's wrong.is it user hostile? Maybe. But that is different than saying it offers no security. It's also not worth bickering about every small decision that is made in line with that security model. If you want a different one, push for it via alternative OS.
adb is not being stopped, the bug is talking about a niche way folks use it without a secondary device. There is also no conclusion from the bug on what action will actually be taken.
It provides a way to improve the safety of existing code without rewriting it. It would be nice if it could solve the memory safety issues around data races too.
It sounds like you don't genuinely care about other people and their experiences. Being able to relate with one another and take interest in their lives is the primary reason I talk with my friends, not because they are interesting.
This was not my experience. I had to climb a few levels to really start interacting with other teams on a consistent basis and see how politics plays out and how it could affect my own career. In particular, learning that while at a high level teams may be aligned but on a lower level there are a lot of natural reasons why individual team goals may end up in conflict with each other and how to have empathy for the goals of folks outside myself was something that took a long time to come into focus. A large number of folks seem to live in eternal ignorance of politics for most of their careers. Sometimes you just need to be exposed to the right situations to grow.
The open source community is built up by many project leaders with unprofessional attitudes. Honestly I think a younger version of myself would have resonated with the post. I'm almost certain there are many folks who will see the post as a net positive for addressing the bun rewrite. Zig is full of people who think they are strong enough engineers to avoid needing tools to solve issues for them and the post largely says that bun was written by weak engineers and they were to blame for its problems which will resonate with the community.
Unit tests aren't useful for rewrites, only integration tests are. So there may be missing coverage. Also many things are simply difficult to test (eg performance under very specific conditions)