as perfect text became an indicator for AI generated content, people intentionally make mistakes (capitalization) to make their text appear more human; and its also faster
Many community-oriented programs have failed after acquisition because they came out too firm, too decided, and too purposeful, only to realize the community is still skeptical and turning against them six months in.
Honestly, for a program like Anki, starting out by saying "we need to figure out what good governance looks like, as well as what might be agreeable and possible for everyone involved" is a much stronger positioning than coming up with something that may or may not fly to try make a strong first impression. Communities do not follow the conventional rules of American business.
From the posts, it sounds like the original maintainer was approaching the point where they'd just abandon it, so this overall seems like a better outcome than either abandonment or sale to a PE firm.
It seems more than a little bit careless to agree on a deal without having those very important things hammered out. What if there is disagreement about these?
Community focused organizations like this are hard to run without governance transitions. I think Anki brings value to the world and anyone willing to take on a leadership role in keeping it going should be given trust and grace to make the best decisions they can with the knowledge they have. I wish them luck.
Or: They don't want to force a specific governance model onto an existing community.
I have no deep insight here, but given the times I have seen a negative reaction from the community with ownership changes or similar, giving yourself time to figure out how to do things may actually be a good thing.
looks like the same framework they used to build chatgpt desktop (electron)
edit - from another comment:
> Hi! Romain here, I work on Codex at OpenAI. We totally hear you. The team actually built the app in Electron specifically so we can support Windows and Linux as well. We shipped macOS first, but Windows is coming very soon. Appreciate you calling this out. Stay tuned!
- looks like OpenAIs answer to Claude Code Desktop / Cowork
- workspace agent runner apps (like Conductor) get more and more obsolete
- "vibe working" is becoming a thing - people use folder based agents to do their work (not just coding)
- new workflows seem to be evolving into folder based workspaces, where agents can self-configure MCP servers and skills + memory files and instructions
kinda interested to see if openai has the ideas & shipping power to compete with anthropic going forward; anthropic does not only have an edge over openai because of how op their models are at coding, but also because they innovate on workflows and ai tooling standards; openai so far has only followed in adoption (mcp, skills, now codex desktop) but rarely pushed the SOTA themselves.
my guess is that openai/anthropic employees work on macOS and mostly vibe code these new applications (be it Atlas browser or now Codex Desktop); i wouldn't be surprised if Codex Desktop was built in a month or less;
linux / windows requires extra testing as well as some adjustments to the software stack (e.g. liquid glass only works on mac); to get the thing out the door ASAP, they release macos first.
I appreciate this (as a Windows user) but I'm also curious how necessary this was.
Like I notice in Codex in PhpStorm it uses Get-Whatever style PowerShell commands but firstly, I have a perfectly working Git-Bash installed that's like 98% compatible with Linux and Mac. Could it not use that instead of being retrained on Windows-centric commands?
But better yet, probably 95% of the commands it actually needs to run are like cat and ripgrep. Can't you just bundle the top 20 commands, make them OS-agnostic and train on that?
The last tiny bit of the puzzle I would think is the stuff that actually is OS-specific, but I don't know what that would be. Maybe some differences in file systems, sandboxing, networking.
A lot of companies that use Windows are likely to use Microsoft Office products, and they were all basically forced to sign a non-compete where they can't run other models- just copilot.
MacOS is unix under the hood so the models can just use bash and cli tools easily instead of dealing with WSL or Powershell.
MacOS has built-in sandboxing at a better level than Windows (afaik the Codex App is delayed for Windows due to sandboxing complexities)
Also the vast majority of devs use MacBooks unless they work for Microsoft or are in a company where the vast majority of employees are locked to Windows for some reason (usually software related).
Location: Japan (Osaka)
Remote: Yes
Willing to relocate: Yes
Technologies: Java, Spring Boot, Typescript, React, k8s, gitops, ai coding
Résumé/CV: https://github.com/AlexW00/CV/releases/latest
GitHub: https://github.com/AlexW00
Projects: https://alexanderweichart.de/4_Projects/Projects
Email: see CV
Doing a working holiday in Japan, Osaka starting April 2026. I love building stuff, especially when it has to do with AI (mostly LLMs). I have tons of ideas, so in my freetime I turned many of them into open-source projects (see GitHub). At work I'm working with Java / Spring Boot and k8s - 50/50 split between Dev and OPS. I would be particularly interested in positions that have something to do with AI native software development/applications. The field is rapidly changing and I think there's a lot to explore.
who would have guessed; we will see more of these vibe coding disasters in the future.
still waiting for the big OpenClaw security hole, exposing remote access to anyone having this vibe coded project installed tho
AI written text is often characterized by a very peculiar choice of words — many people report "delve into" is a particularly telling sign of text written by AI.
If you want me to add more examples, feel free to ask me for more!
reply