It's an LLM-webapp-builder, sure, but different from the rest! I have the LLM write python code when it needs to modify an HTML file for example (it'll use beautifulsoup; then I run the code: it parses the source into a data structure, modifies the data structure, and then outputs the resulting html).

It's also a marketplace where you can publish your llm-powered webapp, and earn $ on the token margins (I charge 2x token rates) when people use your site.

Comments URL: https://news.ycombinator.com/item?id=47610336

Points: 198

# Comments: 223

BS.

Comments URL: https://news.ycombinator.com/item?id=47443158

Points: 4

# Comments: 0

I'm interested in the idea that LLMs writing raw code and doing line-or-diff replacements will not be the future, but that having the LLMs modify the structure of the code may end up being the best.

Also, I think that building LLM-powered webapps should earn the dev per token call; so I've built a margin into token costs where the end user is charged 2x the provider's token costs, and then I get 20% of the remaining and the dev gets 80%.

Plenty of work has been done on this front, and it can be demonstrated that you can assimilate the smartphone pressures into weather models and get some good results. It is hard, of course, and I’m not sure personally how much better the forecasts get. But it’s absolutely possible.

There are like, billions of internet-connected barometers in the world that are not used in weather models. I don’t know if Acme has any of that in mind, but there is plenty of good reason for a weather app to collect data from phones. I know @counters may disagree with me, but I believe there are opportunities to improve short term forecast accuracy using data collected from phones.

Also, pretty much every day, all the apps and all the sites will tell me the incorrect current conditions at my location, much less the forecast. It’s 2026 damnit. Why doesn’t my phone know what the weather is outside right now?

I haven’t got the app yet, but I plan on it (gotta upgrade iOS first I think). Acme seems to have a lot of ideas I agree with, so, definitely following this.

One more thing. Weather apps have not been “solved”. Not even close. They all suck, there’s billions in untapped opportunity, and a stale existing market of bad solutions. People die all the time from severe weather. There is so much more work to be done in forecast accuracy and communication.

Also, it seems a common misunderstanding about some weather apps: yes, most of them just package free data and steal your privacy, but some are really much more than a “weather app”. Some are attempts at building next-generation weather forecast models, which if successful are of course worth billions.

I’ve spent a lot of time building innovative weather apps, most of my career actually. And it’s always shocking to me when people say I’m wasting time or wasting my life or look at me like, “really? You’re dedicating your life to weather apps?!”

No dawg, I’m trying to improve short term forecasts to save life and property from severe events at scale!

I’m not sure what the Acme end goal is, but surely this isn’t just a “weather app”.

Comments URL: https://news.ycombinator.com/item?id=47098296

Points: 254

# Comments: 150

This is a silly little thing. It uses the skyfield python library to get the current light travel time to Mars so we can make this as accurate as possible. It's meant to simulate a conversation between you and someone on Mars with the correct communication delay. (Yeah, it's vibecoded, but still very fun). Since there is nobody on Mars (yet), an LLM is backing the conversation on the other side posing as a humanoid robot.

Sorry for the login requirement, but I want to protect from out-of-control token costs. The model behind it is full gpt-5.2.

I made this because I've always wanted to make it but never really wanted to put in the effort. Luckily, stuff like this is a lot easier to make now, so I get to have fun making all my project ideas that I wouldn't have otherwise made.

Have fun chatting with a 'Martian robot' with actual time delay to Mars!

Comments URL: https://news.ycombinator.com/item?id=47065237

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=46957403

Points: 6

# Comments: 17

Comments URL: https://news.ycombinator.com/item?id=46932651

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=46932263

Points: 2

# Comments: 0

1) I use Abstract Syntax Trees to have the LLM modify existing code. It will make more targeted changes than I've seen compared to codex/gemini cli/cursor etc. I wrote a blog post about how I do this if you want to know more: https://codeplusequalsai.com/static/blog/prompting_llms_to_m...

2) I double-charge for tokens. This creates a margin, so that when you publish your app, you get to earn from that extra token margin. An API call that costs $0.20 to the user would break down to $0.10 for the LLM provider, $0.08 for you, and $0.02 for me. I'm trying to reduce the friction of validating ideas by making the revenue happen automatically as people use your app.

3) I've built a "Marketplace" where you can browse the webapps people have created: https://codeplusequalsai.com/marketplace

I'm kind of trying to bring back and old-school web vibe into the AI world, where it's easier for people to create things and also discover neat little sites people have built. I wonder if I can also solve the 'micropayments' idea that never took off really, by baking in the revenue model to your webapp.

4) I envision the future of large-scale software development to be a lot more about writing clear tickets than ever before; we've all dealt with poorly-written tickets, ill-defined use cases, and ambiguous requirements. This site is an early take on what I think the UX might be in a future where ticket-writing may take a greater amount of time, especially to code-writing.

What do you think?

--

Some more quick nerdy details about behind-the-scenes tech: this is running on 3 linode servers: 1 app server (python/flask), 1 db server (postgres), 1 'docker server' that hosts your webapps. The hardest part about making this was getting the LLMs to write the AST code, and setting up the infrastructure to run it. I have a locked-down docker with python and node, and once the LLM responds to a code change request we run a script in that docker to get the new output. For example, to change an html file, it runs a python script that inputs the original file contents as a string to the LLM output, which uses beautifulsoup to make changes to the html file as requested by the user. It's quite custom to each language, so at the moment I support Python, Javascript, HTML, CSS and am currently testing React/Typescript (with moderate success!)

Comments URL: https://news.ycombinator.com/item?id=46919791

Points: 2

# Comments: 0

Also what is twin.so if it's not workos.com? The login with google says it will redirect me to workos.com, which I went to and seems like a totally different product.

Comments URL: https://news.ycombinator.com/item?id=46240952

Points: 15

# Comments: 6

When you write the code, you understand it. When you read the code produced by an agent, you may eventually feel like you understand it, but it's not at the same deep level as if your own brain created it.

I'll keep using new tools, I'll keep writing my own code too. Just venting my frustrations with agentic coding because it's only going to get worse.