It’s generally seen as bad because it means that wealth is flowing out of the country.
What most governments prefer is that that wealth stays within the country and is used to employ people and pay taxes.
I’m starting to switch some of my following activity back to #Mastodon. I have nothing against Bluesky, and I think its usability is better than Masto, but I can’t escape the feeling we’re just helping build another US controlled social media platform.
I see folk post here, on a the site of a US organisation, about boycotting US products. The thing, for me, is if you're going to do that, you need to do it for free products as well as paid-for ones.
Giving things away for free is a solid strategy for stopping non-US competitors gaining traction.
If you're hitting a problem with large file transfers using adb when doing #androiddev, and you're on Linux, it could be down to libusb. The way to check, and switch to the old native backend, is in issuetracker.google.com/issues/37241...
TIL; In Windows, if you have long filename support enabled, you still need to tell git by running;
git config --system core.longpaths true
otherwise it'll assume LFNS isn't enabled and complain when long filenames are encountered 🤦
It’s this kind of garbage that makes me feel that setting up @snappautomotive.snapp.social was the right thing to do. Now all we need is for manufacturers to have the courage to engage with smaller companies and not sit in the loop of existing processes that ships this junk to customers.
These are the kind of systems that gives software development a bad name, and, when I try to use the it, it makes me think that @volkswagen.bsky.social blaming Chinese competition, and the economy, is deflecting from their own quality issues, or they’re fishing for folk to pay for upgrades.
I was manually changing the density via adb before we settled on 160dpi. Seemed to work well.
If you're interested in the journey we took to end up with the #AAOS devkit, here's a blog post about it; www.snappautomotive.io/blog/how-we-...
One thing the dev kit lets us do, which tablets can’t, is try different aspect ratios and resolutions easily.
This, for example, is a 1920x720 10.3” display, which is something that could be embedded into a dashboard.
Exciting news! We're publishing free Android Automotive builds for the Khadas VIM3, allowing anyone to create their own affordable developer kit!
Grab a VIM3, add a touch display, and you’ll be ready to go!
www.snappautomotive.io/developer-kit
We can't wait to see what you'll build!
It’s been a long road, but finally we, at @snappautomotive.snapp.social, are in a place to offer folks some concrete steps to create an #AAOS setup that they can use to develop #Android #Automotive OS experiences 🥳
Hi there BlueSky! We're Snapp Automotive and we're here to fix in-car software. We built SnappOS, a white-label infotainment system, and we work with many major carmakers to help them get the most out of Android Automotive from a design and development perspective. 👋
