They also compare to RLHFed GPT-4, which reduces capabilities, while their model seems to be pre-RLHF. So I'd expect those numbers to be a bit inflated compared to public release.
Keep scrolling past the main list. There is an additional list of six "Warning Schools":
> The following schools have policies that clearly and consistently state that it prioritizes other values over a commitment to freedom of speech. These colleges were excluded from the rankings and were scored relative to one another.
They all have much less free speech than any school on the main list.
> When f-strings were originally introduced in PEP 498, the specification was provided without providing a formal grammar for f-strings. Additionally, the specification contains several restrictions that are imposed so the parsing of f-strings could be implemented into CPython without modifying the existing lexer. [...]
> The other issue that f-strings have is that the current implementation in CPython relies on tokenising f-strings as STRING tokens and a post processing of these tokens. This has the following problems: [...]
> By building on top of the new Python PEG Parser (PEP 617), this PEP proposes to redefine “f-strings”, especially emphasizing the clear separation of the string component and the expression (or replacement, {...}) component.
You “just” have to make your parser understand how to have all expressions or whatever inside braces. No idea how the python parser works but think about how you can nest json arbitrarily.
It's a combination of two things, open source packages have matured to a very stable level. Fedora uses very recent packages and it just works somehow because they've all become very good. So to keep a stable desktop system there is no more reason to use "sta(b)le" packages.
The other reason is snapshots, because no system is perfect. An operating system should in fact be designed around the fact that something will go wrong. Windows has had this for years, and some linux users have done it with btrfs.
But Fedora Silverblue does it seamlessly with ostree and grub, so if something does go wrong in a newly applied update, you simply choose the last working one in the grub menu and go on with your day until you have time to resolve it.
This for me to use Fedora as my daily driver is crucial.
Make your code open-source, but don't merge in PRs, don't actually use it for development, and don't promise anything buildable. (NetApp, Tesla, Samsung do this)
OR have the core of your tool be open-source but add proprietary value on top of it so that the proprietary version is more attractive (like Tailscale with their Coordination Server). With Terraform, this could have been the cores that manage plans and state.
The issue here (purely unsubstantiated outsider opinion) is that Mitchell is a hacker that created things that were immensely valuable and punted the profit part of it for later. Hard to undo that, but it was good enough to raise millions on millions and create a super sweet company to work for (before they went public and were forced to wear a suit like the rest of The Street)
Yeah, so Tesla AFAIU isn't even GPL compliant as what they publish is not the complete corresponding source code for their Linux/buildroot based firmware.
Salami slicing tactics are pretty common, that way you can gaslight detractors by saying they’re crazy for making a fuss over such insignificant changes.
This is a fantastic library. I plan to use some of the search functionality with a system that tries to figure out how to manipulate/work with/add features to existing code.
