I run codex in a dedicated vm, I have a cronjob which resets it to clean installed state every week. Nothing too fancy just bhyve and debian, 8gb mem. It has root access there, can install stuff, no permissions to push to protected branches etc. It didn't take very long to setup, and I can sleep a bit better...
May be decorative only —- Isn’t it due due to their wimpy electricity that it takes forever to boil a kettle and that’s why everyone gets coffee externally? Or, absolute horror, they microwave teacups….
Poor trade off, the model is then designing a massive chunk of your solution instead of you. With a good spec, bits of typo’d pseudocode, and slightly more effort than a couple of sentences they can actually produce passable software.
I think the reason claude has so much mindshare is exactly because it’s more useful to non-developers who wouldn’t know how to describe what an api call executes to his grandmother.
For those who can, I can’t find much of a difference between them. Codex has the slight edge, but that’s all just “feels” to me.
> "we will inquire into something, but we
will not grasp it, if in some way we depart
from ourselves and from our own nature,
and besides, in the same way as the
remaining arts may be said to be perfected
in one respect, but to be deficient in
practical wisdom in another respect"
Did you happen to get covid or had a really heavy reaction to a inoculation around that time? That's what triggered mine; but it's actually been getting a lot better and (pure anecdotal) but I think 6 months or so of a b complex vitamin pill in the mornings have helped. Apparently, it can promote nerve repair, there's absolutely no money in studying this effect however so research is scant. I think you have very little to lose by trying it, though.
It's still there, but I routinely go weeks without noticing it now.
Backups in such a system are quite pointless; if losing 10 seconds of data means you lost 4000 transactions then periodic backups are invalid if not instantly than close to instantly.
The system I work on has such a property and the only real infra style approach is sync replication before responding to a caller and a delayed replica for delete/drop protections (say with a 2hr or more window).
Should also defend for this in your code (be able to reply from your initiation systems also etc)
Any sufficiently complicated concurrent program in another language contains an ad hoc informally-specified bug-ridden slow implementation of half of Erlang.
I am a fan of the idea, but the websocket is also quite a big attack surface; you can do a lot more by sending messages over this socket to your phoenix app than you would likely expect to have exposed via some api on another framework.
It’s difficult to secure, in my opinion. Perhaps not impossible but the cost of doing so pretty much eclipses the benefits of using liveview imo.