@ifeanyi_we@ibuildthecloud the misguided revulsion toward oop [as if it's inherently flawed] is pretty pervasive
the runtimes of these langs are all turing machines at the end of the day and can execute programs written in oop, functional, procedural, or whatever pattern you want
@Yuchenj_UW Anthropic's problem was not quantity of GPUs/TPUs, it turned out to be 2 things:
- poor developer relations
- hardcore leftist-ctrl worldview of their ceo
@thsottiaux You shouldn't have to select an agent env bcos there's the risk to mess up config.toml. Based on the `pwd` of the repo, the env should be inferred and provisioned
i have seen enough proof now that using a coding agent is a deep skill
it's confusing because the people you see heavily using them produce horrible results
but that's because it's a skill! you can get better and the ceiling seems pretty high - this is very exciting to me
@mitchellh@doctorscm Hopefully the elite ones find a way to spend the time in rabbit holes figuring things out for themselves like their ancestors did regardless of the new technology on the block
@James_M_South Quite good for code reviews when you specify the review session to use sonnet 4.6 but I think the code review functionality leverages my account-wide custom instructions heavily so ymmv
Switching to WSL is really messy. At installation time, prompt the user to choose the agent env and then provision that so we don't end up with Win11 filesystem paths inside /home/user/.codex/config.toml when switching post-installation on the WSL side [or come up with a better implementation]
We merged an early C# 15 preview feature into .NET 11 preview 5: closed class hierarchies.
Allows a `closed` modifier on a `class` declaration.
A `closed` class prevents direct inheritance from other assemblies, so pattern matching can treat its derived types as a complete set.
@_Felipe C# is more forgiving bcos familiar patterns like async/await is widespread in training data, so agents generate functional code faster for typical runtime scenarios