endunless

2 ms·

1.
by endunless 6mo ago
Very interesting, thanks for sharing. > I doubt they're being misleading or even overly grandiose here I think I agree. We could definitely do much worse than Anthropic in terms of companies who can influence how these things develo
2.
by endunless 6mo ago
> If a bunch of CVEs do in fact get published a couple months (or whatever) from now, are you going to retract this take? I would like to think that I would, yes. What it comes down to, for me, is that lately I have been finding that whe
3.
by endunless 6mo ago
Another Anthropic PR release based on Anthropic’s own research, uncorroborated by any outside source, where the underlying, unquestioned fact is that their model can do something incredible. > AI models have reached a level of coding cap
4.
by endunless 6mo ago
Given GitHub is owned by Microsoft, I think VS Code supporting mixing fonts in a buffer would be a good start!
5.
by endunless 6mo ago
Fair points on the technical implementation. I more meant the idea of using different fonts in the same buffer to represent different kinds of text.
6.
by endunless 6mo ago
I do like these fonts, but DJR had this idea with the (excellent) Input family of fonts years ago: https://input.djr.com/ A bit weird to not mention that. Unfortunately until editors start supporting this (and I’m not sure
7.
by endunless 1y ago
What is the auto-update mechanism on macOS? One of the primary reasons I use ungoogled chromium is because I can update it via homebrew myself. I don’t trust browsers with running invisible background auto-updaters.
8.
by endunless 2y ago
Keystone had a pretty mixed history on macOS, with things like the WindowServer bug and that one time it deleted the /var symlink. Do you know if the new updater is safer to use? I can't find out much about it.
9.
Keystone no longer used to update Chrome?(issues.chromium.org)
2 points by endunless 2y ago|3 comments