I don't specifically seek them out. I follow quite a few different programming blogs, and I am just sharing what people are posting about, and it just so happens a lot of people are posting about this topic.
What's to stop people outside the Elixir community voting posts down?
Headless does not mean “no screen anywhere.” It means you are not required to use the company’s app or site to finish the job.
You might say: “Book a flight and a hotel in Tokyo.” A helper (with hooks into services, e.g. MCP or other agent APIs) talks to airlines and hotels for you. You might never see their homepage or their “join our club” popup.
Whilst I can see where the author is going with this, I can't see some tasks, particularly booking concert tickets, being done by AI agents. Whilst it may be convenient for end users, it's also open to exploitation by scalpers.
I can't tell if the downvotes are people hating Elixir, AI coding agents, or both. 😕
If you're going to make that claim, could you please provide some evidence.
Not sure if you were even looking for paper reviews.
I didn't write the article, I just shared it because I thought it was interesting.
I think you're misconstruing the author's argument, at no point does the author imply that Claude knows best, or that Electron apps are better. Their closing argument is certainly not an endorsement for Electron or AI slop.
Don’t get me wrong: writing this brings me no joy. I don’t think web is a solution either. I just remember good times when native did a better-than-average job, and we were all better for using it, and it saddens me that these times have passed.
I just don’t think that kidding ourselves that the only problem with software is Electron and it all will be butterflies and unicorns once we rewrite Slack in SwiftUI is not productive. The real problem is a lack of care. And the slop; you can build it with any stack.
Imagine being such a slop-brainwashed fanboi
Do you have any evidence for this? Looking through the post, and the author's other blog post titles, there is very little mention of AI or Claude.
Instead of throwing labels at the author, it's much more worthwhile to discuss their key argument about the challenges of developing native apps.
If your code is already in a Git repository, the simplest solution would be to use statichost, which has a free plan. It works on the same principle as Netlify, where your site is updated when you push the code.
This is a very technical way to self-host, and I feel there are easier ways to go about it. Is your end goal to be able to upload a website but avoid big tech platforms?
I wonder if we’ll end up in a situation of open source projects with closed source tests. Though I don’t know how that would work, because how would you contribute a new feature if the tests are closed? 🤔
view more: next ›
I agree but it depends on how teams create and refine their tickets. For example, you could have high level tickets, and someone picks one up and creates an implementation that's not an appropriate fit for your architecture.