Don't worry! We're releasing this beta to show off the tech and wanted to start somewhere people were familiar with. We are releasing a handful of differentiators over the coming weeks :)
Well, this is not even an MVP. I couldn't get my GitHub org name, so I'm not interested in your vibe-coded clone. You don't get the value of identity! When you release stuff like this, you can't leave it to be driven by chaos. Facebook had a strict timeline for releasing Facebook users' names, and everybody got an equal chance; it did very well recently with WhatsApp usernames as well. And what you did was let some people grab the usernames of paying customers, who were on vacation or busy at the moment! What a big fiasco, but, of course, you don't care as you've got yours already, right?
Totally agree. I wonder if git itself needs to be looked at, its objects and history are likely not as important as the context/instructions used to make code changes these days imho
The original GUIs were all flat because that was the default. A button was a rectangle with text in it. A checkbox was a rectangle with or without an X across it. Pure black on pure white, no colors or shades. Windows used this style until Windows 95.
Nobody seemed to have a problem with it. It was largely clear what was a button and what was a checkbox. In hindsight it was certainly uglier than the 95 style (maybe just because I grew up with that) but it wasn't unusable at all. As you say, it was clear what was a button, what was a checkbox. I think it was because GUIs were mostly made out of standardized elements whereas today we have everyone trying to put their unique spin on every element.
I might be misunderstanding what you're saying, but: In the PC space, Windows 3.x definitely had some skeuomorphic elements. This presents most-commonly with the minimize and maximize buttons[1].
We have to go all the way back to Windows 2 in before we find flatness.
And Windows 1 and 2 were barely even used. Windows 2 sold less than 2 million copies. Windows 3 and co sold 7-ish million. Windows 95 sold more than 40 million.[1] There's a lot less people to complain about Windows 1 and 2, and those people were probably a lot more experienced in the first place.
I don't think making a good product is enough. X is still prevalent despite Musk's actions both as a public person and as X's owner. The alternatives, be it Bluesky or Threads, are fine to use, yet people aren't moving.
There's no way we'll be able to compete against Google or Meta in any meaningful way if we can't even get people out of X. Even more so because I'd argue that a good product is a little more boring than the ones that are currently at the top.
No, it's not enough. In your case it's not even anything: Being a second mover and copying the incumbent without the benefit of the existing user base does not make a good product to begin with.
A lot of these principles are totally transparent for the user. For example, emails are a complex system but users can sign up to any email service and send emails regardless of which service their recipient uses. This could totally be possible for any social network, and many apps, would they be willing to implement it. The end user experience wouldn't be any more complex.
The article explains what's needed to run something like Bluesky (ctrl-f "To be fully sovereign you need").
My understanding is that Eurosky aims to be a non-profit ran alternative, hosted in EU. It integrates with Bluesky seamlessly (Bsky users and EUSky users can interact) but would keep working if Bluesky was taken down. I believe it also gives Eurosky agency when it comes to moderation.
Do you have any good resources on how to work like that? I made the move from "auto complete on steroids" to "agents write most of my code". But I can't imagine running agents unchecked (and in parallel!) for any significant amount of time.
Right now, I'm finding a decent rhythm in running 10-20 prompts and then kind of checking the results a few different ways. I'll ask the agent to review the code, I'll go through myself, I'll do some usability and gut checks.
This seems to be a good window where I can implement a pretty large feature, and then go through and address structural issues. Goofy thinks like the agent adding an extra database, weird fallback logic where it ends up building multiple systems in parallel, etc.
Currently, I find multiple agents in parallel on the same project to be not super functional. Theres just a lot of weird things, agents get confused about work trees, git conflicts abound, and I found the administrative overhead to be too heavy. I think plenty of people are working on streamlining the orchestration issue.
In the mean time, I combat the ADD by working on a few projects in parallel. This seems to work pretty well for now.
It's still cat herding, but the thing is that refactors are now pretty quick. You just have to have awareness of them
I was thinking it'd be cool to have an IDE that did coloring of, say, the last 10 git commits to a project so you could see what has changed. I think robust static analysis and code as data tools built into an IDE would be powerful as well.
The agents basically see your codebase fresh every time you prompt. And with code changes happening much more regularly, I think devs have to build tools with the same perspective.
It will come naturally! I have started with autocomplete as well. I was stumbling upon different problems and was fixing them by implementing best practices. Current stack is:
1/ Claude Code with yolo mode
2/ superpowers plugin
3/ red/green tdd
4/ a lot of planning and requirements before writing any code
It feels like you always touch this edge of capability of models and your current workflow. Delegate more complex task, and system fails. Delegate more simple and system works great. Improve your workflow and move this complexity to a higher level.
But... I am llm power user for more than a year and a half now. I cant delegate exactly because ive reviewed a lot of llm's code, and it is never good enough for me to step down from reviewing everything manually. I can understand how you can vibe code dashboard or tests, but vibe code your entire backend without checking it thru carefully? Madness.
For me you open a markdown editor and draft up a code plan and details of what you'd do as a coder at a high level then bust into whatever tool in planning mode (I usually fire this into the opus 4.5 model) and have it break it down into concise steps and then hand it off to a simple model (gpt spark, sonnet, composer or whatever) to execute. when I feel frisky I'll just have opus one shot it and it can be done in a few minutes.
I'm also team USB-C wired earbuds (the Apple ones are cheap and solid, mic is also nice for calls) for podcasts and commute.
I never stopped using wired headphones at home but also had BT ones on the go. When they started showing signs of age I got a cheap BT receiver instead of replacing them. It's not quite as practical but for many people it's something to consider, they work surprisingly well!
I'm firmly on team "dual USB port" for this problem. We do this on computers, which can then perfectly well charge and play audio at the same time. Why not phones? It seems like there's plenty of space for a second port.
the usb port is much more complicated than a 3.5mm port. It is more expensive, it takes more space. Do you add another real port or a built in hub? (they would go with the latter, probably)
This depends heavily on your use case. I'd get rid of Windows entirely if I could. For most people I'd say MacOS is the most sane and plug and play experience. The email/browser/note taking experience is better than on Windows, and easier than on Linux.
This gets less and less true when you start pluging peripherals and wanting to change the default behavior or use certain apps. But then they're not the target of the Neo.
that example is just worthless... most people are used to notepad and windows (by a huge margin) than ANY mac thing you can say. So, no, sorry, you are wrong, the sanest plug and play experience, still, is windows, who is pirated all across the globe and put on anything.
Some domains in that list are truly ancient. That was a trip down memory lane.