Used to when I was in hardware service and sales, but that was back in 2008-9. We mostly dealt with their flash media at the time such as SD cards. The running joke was, customer asks why are the ADATA cards so cheap, someone answers - there's 50/50 chance it'll lose your data. That arose from really high return rates. They'd just die on people randomly. It wasn't a single batch issue either. They're probably different today. RAM is hard to screw up too. Just don't scrape the bottom of the barrel for chips. Yes I know OCZ managed to screw RAM spectacularly, but in this case it sounds like Framework will choose the chips. They've mentioned they'll be using SK Hynix.
Well written but there's sus contents in there. Finding common ground with reasonable people is one thing. Affirming their negative opinions about objectively good concepts like feminism, diversity, and inclusion for example is very different. 🙃
Sir, this is a door knob.
You may find that we really like safe spaces on Lemmy.
The same reason it works for the US. A bigger population, all else being equal, means higher economic output and therefore larger political influence internationally relative to other players. If Canada had 1B population, groups in the US would have found it much harder to exert any significant influence over our politics given how much louder than them our voices would be. By voices think all types political voces, individual, collective, etc.
Related - something I learned during a research course at uni - the shifting of some functionality from software to hardware or the other way around has happened on many occasions. It all depends on how the tradeoffs between performance, optimization, cost and so on shake out.
The hybrid compilation approach is spectacular. Really smart design. It's as close as having the cake and eating it as possible.
Java performance has rarely been an issue in any environment, Android or otherwise. Recall that one of the most successful mobile OSes running on much slower chips than even the first Android was written entirely in Java - BlackBerry OS. C++ is great too but it requires a lot more competent engineers to do well. Modern C++ is spectacular. Yet often people we interview for C++ positions write C with cout in place of printf.
This name rings a bell. Was that used along with J2ME?
There are many benefits. For example great exception handling. We're paying very little performance cost for having the conveniences of a managed runtime. Let me flip it, we don't want unmanaged runtimes, we are forced to run in native, because we need the absolute highest performance in some cases. If the hardware could understand Java bytecode and provide all other JVM facilities, that would have been spectacular. Unfortunately that would be very expensive and pointless as we've demonstrated over the decades. If anything we're moving towards reduced instruction set chips - ARM, RISC-V. And so in many ways the complexity you see is well understood by the folks that have to understand it, it's well managed, it's worth it and it's not at all a performance problem worth tackling.
Long term, by growing our population.
Ouch. 🫢🤣