no, its the problem that will be created by solving the touch screen problem, with a physical user interface, that is still just an input to a digital device.
There's more to the article than just the article. A technical blog elicits discussion and conversation in the comments. I never get why people totally miss such value add.
Have those outages actually been blocking your work? Somehow I haven't even noticed, just seen complaints on HN. I'm not saying it's not real, just wondering where the gap is.
A big part of my job is doing code reviews, and its very common that pages or diffs just don't load. Or PRs literally don't appear in the PR list, even though they exist. It's a daily occurrence to play the 'is my internet down or is GitHub just being shit again?' game.
Oh, and don't forget the cases where the diff view sometimes misses some files for unknown reasons. Both in the 'new experience' and the 'legacy view'. You just can't trust it as much anymore.
Yes, many times. Roughly once a week this year my team or an associated team can't ship changes because PRs, GitHub Actions, or some other associated mechanism is down.
What's the alternative if you want full ad-blocking in a Chromium browser? I use Firefox normally and wouldn't trust Brave, but there are some sites FF doesn't work with, so it's understandable why some people wouldn't use it.
Look I'm not an expert in web browsers, but I defer to those extension authors who definitely are. There's some reason uBO doesn't work well in MV3 even though they tried. Whatever technical explanation there is for why MV3 is fine, there's some caveat not mentioned.
Why do you need agents patching your kernel to enable efficient agentic workflows? Are those agents working on building a kernel? If they're just building some web backend or whatever, I don't see why any of this is needed.
reply