I think there is an element of audience capture that sets up a self reinforcing feedback loop that drives out the normies and ends up rather cult like.
ICE reminds me of what I read about the 1930s era - but it is really stupid on top of that. So basically this then screams of a money machinery for a few. Taxpayers money goes into private pockets here, all under the disguise of "EVIL MIGRANTS".
That's fine for database-like meta-data (e.g. game entity properties), but not for images, videos or audio files. Just writing those as hex dumps into text files doesn't make them any easier to merge.
Yes you can install and use it (I hold my passes, tickets and loyalty cards in there), BUT payments won't work for now because Google says malware-ridden Oreo handset is safe and secure, but phone without ad delivery network running in the privileged mode isn't.
There are alternatives for payments (scroll the thread, maybe look up on GOS discussion site).
Yes, that's why I said 'signal' and not 'sole metric used to determine worth'. Devs get so touchy about this subject. I didn't say being good with the terminal is all that matters, it's just an extra piece of information.
Wanted to share this project I have been working on for a while. In the past few years and my previous startup, I really struggled to get any form of AI adoption in regulated industries. So I built MakerChecker: A way to add structural guarantees into how Agents and AI systems would operate in high risk environments.
It wraps around agents you already have and provides structured controls:
- Each agent acts only through a role and can only run skills its approved for.
- It cannot approve its own work.
- Support for human approval gates.
- Every action is committed to a hash-chained signed log.
I also build alot of runnable examples based on real life case studies (e.g. Knight Capital, Air Canada refund chatbot) and how it can be used to prevent them.
The goal is to help get agents that do impactful work (move money, healthcare triaging, prod releases, etc) out of pilot and into production.
Happy to answer any questions and always looking for constructive feedback :)
to be fair, that's just the desktop client. You can use or build on top of the CLI
they do say they will open source it, but who knows:
"It isn’t open source yet—it currently depends on some proprietary components, including Epic’s internal design system—but we’re committed to open-sourcing it in the future"
By your reasoning, 99.9% of people use awfully insecure OSes on desktop and servers. And yet, the world hasn't collapsed. My bank account is not hacked regularly, too.
At least browsers wouldn't have to warn users that they'd be resubmitting data if they reload the page after submitting a query form, since query requests are intended to be idempotent
This is correct, but I'd say there's something beyond that that's more specific about Codex + GPT models though. They've done some sort of training that makes it far more diligent about seeking out data races, unhandled errors / negative cases, and missing test coverage than the other models I've played with. It also seems more prone to testing its hypothesis.
This makes it slower to work with for prototyping, and it will, if not properly disciplined, litter your code with "legacy adapters" and "bridge code" and temporary incremental refactoring steps [arguably not terrible for work in real commercial software projects]. And it will create too many unit & integration tests, if you're not careful.
But it does, in my opinion, tend to produce more reliable software and I trust it far more than I did when I was working in Claude.
When I could afford it, I had both plans running, Claude to produce new features, and then Codex to brutally critique it battle test it, sharpen the edges, and produce better tests, and this flow went extremely well.
Now I just work with Codex and various open models.
One example - I'm building an MCP server at the moment for a database I'm working on. In ChatGPT I want to do dry-run posts first that roll back before committing - both are POST requests with a property - and it loves to trigger the safety layer in the tools (for various reasons, it's hard to debug exact causes)
But I think this would make it better - QUERY before POST means different request types, not just the same with a safety flag.
I'm glad those tests apparently work out for you but a benchmark where three of the top 5 models are different flavors of Gemini Flash and zero are anything by Anthropic, is just so wildly divergent from my personal experience with the models that it's not useful to me.
Whatever it is you're measuring, it's not anything related to what I use models for.
The point of a UI library is to interface with users. If it totally fails to interface with a subset of users then it is obviously deficient to some degree. It is callous and foolish to dismiss offhand users who rely on assistive technologies. You probably have a poor idea of who they are and how many people we’re talking about. You never know when you or someone you care about will become one of them, even temporarily. You never know how far your software will reach when you write it.
when you make a contract with facebook or any other large site you're making a contract with a legal team tasked with protecting their money
at a certain point scale only works through oppression