0 Followers
0 Following
1 Posts
The BSODs I’ve had on Windows in recent years have all been due to faulty hardware. Once that was resolved I’ve had no crashes. Can’t really blame the OS for that.
Or better: abolish the concept entirely. Can’t gerrymander what doesn’t exist.
Do note that GitHub explicitly excludes those with an Enterprise (or other corporate) plan for precisely those reasons.
Mushroom
Good ol’ Goodhart’s law.
Going off the ycombinator discussion too, it certainly looks like it… I was hoping for some announcement for increased investment into an open source ecosystem, got an ad for a shady whitelabeled nextcloud host instead.
77F is 25C. That is quite the temperature swing: even bigger than the warmest day in a year vs the coldest day in a year in many places…
Most LLMs don’t push back when they should. When combined with situations like these, at a large scale, even 5 percent is abysmal, let alone 55 percent.

MIT still requires the license and copyright notice to be maintained though, it is why even proprietary software includes an ‘open-source licenses’ listing somewhere under help / alongside the distribution. Arguably, AI models reproducing a bit of MIT licensed code would be just as much in violation as with any other license.

GPL still gives much better guarantees w.r.t. providing the source code and modifications made thereto, though.

To be similarly pedantic: Ctrl+C is a hotkey that send the corresponding ASCII code to signal something, it is not an ASCII code itself.

You could have the same character be sent by using Ctrl+Q (if you were to remap it), and not break compatibility with other processes while doing so: the codepoint being sent would be the same. From a technological perspective there is nothing special about the key combination Ctrl+C specifically, but altering this behavior in a terminal absolutely wreak havoc on the muscle memory of terminal users, and altering it’s behavior in a text editor on everyone else’s.