To me being able to do some templating/inheritance to generate slightly different config (or deviating from the standard/default config) seems to be vital as a config DSL. In that regard, even YAML is superior with its half-ass anchor thingy.
3,080 karma · joined September 17, 2012
To me being able to do some templating/inheritance to generate slightly different config (or deviating from the standard/default config) seems to be vital as a config DSL. In that regard, even YAML is superior with its half-ass anchor thingy.
3.8 Flash + /boost is very capable.
It would be great if it can use fingerprint to unlock different profiles.
Disclaimer: I work for Google Cloud.
The adb connection is intentionally over Tailscale so in the morning after I connect to some random WiFi (Android remote debugging is only enabled w/ WiFi connection) I can start reading the report, then quote and ask Gemini to fix some issues.
"Install this app on your Apple TV or Android TV, login with your Gmail, and let me know your email address."
It doesn't show in the desktop UI.
My tweet on Sep 26, 2026
In fact I've start doing that myself. Sending PR and convincing the maintainer why the fix is necessary is just too much effort.
And I saw it do this twice, once for Android 14 and once for Android 16.
I think this is just within 3.8 flash's capabilities.
If you accidentally did that, I believe there's a way for the admin to scrub that for you.
Now to the second part: I think speed still plays a role back when Bitbucket and Google Code provides Mercurial hosting and people were comparing Mercurial with Git. Eventually GitHub won the competition, so then we kinda stuck with Git.
Why is git's "forced conflict resolution" better, assuming the same workflow (local change+sync upstream) would produce the same # of conflicted commits?
You worked on multiple things, you sync with the upstream, then boom now you have conflicts in one or more of your local branches.
Instead of immediately presenting you a conflict resolution view (usually 3 pane vimdiff) and you'll have to resolve at the sync time, the commits are simply marked as "have conflict", and you can continue working on other things until you have time to deal with it.
And for a chain of commits that all have conflicts, chances are fixing the first conflict automatically resolves all other conflicts in the chain, thanks to the auto-rebasing feature.
Gemini says you can power a piezo buzzer (causing a small bump on a PCB) w/ NFC (just enough power to drive it) to play the modem dialup handshake audio.
(Reading the wiki I'm really glad this is still alive).
https://community.home-assistant.io/t/serial-projector-contr... from a quick search.