1,438 karma · joined January 16, 2012
Happy to talk - eddie [at] ringle [dot] io
[ my public key: https://keybase.io/eddieringle; my proof: https://keybase.io/eddieringle/sigs/QZtW0oYTMUR988YYBQpB7Mqfg775MsU3GCBvTTVaYX0 ]
Additionally, this would ideally be implemented while also eliminating income taxes (and general sales taxes). One of the biggest benefits of this is that we would no longer _need_ to track everyone's income, and could even eliminate vasts amounts of bureaucracy like the IRS and state-level departments.
I personally think income taxes have proven to be a beauracratic and political nightmare with high economic overhead. I don't see a VAT being much better. And as others will mention, just switching to a general sales tax is highly regressive.
> That’s why we’ve signed an agreement with HTC, a leader in consumer electronics, that will fuel even more product innovation in the years ahead. With this agreement, a team of HTC talent will join Google as part of the hardware organization. These future fellow Googlers are amazing folks we’ve already been working with closely on the Pixel smartphone line, and we're excited to see what we can do together as one team. The deal also includes a non-exclusive license for HTC intellectual property.
I'm still not a fan of Electron apps. I'd rather they at the very least be offline Chrome apps, so then I'd at least be using the latest Blink/V8 combo. Not to mention it seems that anything Chromium-based likes to make a ton of little writes to disk for just about everything (even when I'm just moving my mouse across the page), so to have multiple apps doing that with their own respective config/cache directories is annoying.
That said, VS Code is the least bad editor running on top of Electron that I've used, so I'm glad this one is based on it. :)
I rarely, if ever, have needed to do this, and I've been working with Android since 2009. Most of the time that is abstracted away by the support libraries, anyway.
The version fragmentation generally isn't a huge issue for Android app developers, in practice.
But I digress. Faster Java & JVM updates will help Kotlin out as well moving forward. :)
The next release of the NDK (r16; due out sometime this quarter) will stabilize libc++ for use by NDK applications and it'll be made the default STL in r17 (which will be out by the end of the year).
For example, something I was excited to see is in the updated documentation on source.android.com with regards to how they recommend developing kernel branches alongside devices: https://source.android.com/devices/architecture/kernel/modul...
Basically, one of the issues that's plagued OEMs in the past is the fact that each SoC vendor (e.g. Qualcomm, Samsung, ARM) would not only have a kernel for each SoC, but each OEM device using that SoC would be another branch on that SoC-specific repository. This would then be compounded by the OEMs having their own kernel repositories that pull from the device-specific branches of a SoC repository, and bug fixes from OEMs would have to trickle back upstream to the vendor repository before making them back to other device-specific kernels.
The new proposed model would see a single kernel soruce for a given SoC, and device-specific changes would come in the form of kernel modules, config overrides, and device tree overlays. They are also strongly recommending SoC changes to the kernel be upstreamed to mainline Linux, which would greatly ease porting to newer kernels in the future.
2 - Right, this is something Treble will attempt to solve.
3 - Which is why Google is making it as easy as possible for them to do so, right down to actually pushing out the updates for them.
Curious, what exactly were you expecting? There hasn't even been enough time for Treble to play out to see if it brings results.
The Android CDD maintains requirements for sensor accuracy and performance: https://source.android.com/compatibility/android-cdd#7_3_sen...
Which they'll be able to do with Project Treble: https://android-developers.googleblog.com/2017/05/here-comes...