It will also pull more users in. I don't want to be looking at code. I want more of a codex style app where it's easy to shove all my projects in one place and context switch endlessly.
Not unlikely given the crash in Atlassian's share price over the last year or so. When I was in NetApp a long time back, such rumours would often do the rounds when the share price took a dip, with Oracle and IBM usually touted as the likely buyers. NetApp is still doing strong more than a decade later :-).
We're not doing Electron because some popular software also using it. We're doing Electron because the ability to create truly cross-platform interfaces with the web stack is more important to us than 300 MB of user memory.
> We're doing Electron because the ability to create truly cross-platform interfaces with the web stack is more important to us than 300 MB of user memory.
It's closer to 1GB but trust me, everyone is well aware of your priorities.
You should check the memory use of that browser tab. You’re not saving much either way running in a browser or in Electron, which is effectively a browser.
The idea of style being separate from content is great for something like a blog or a wiki article but when you're building an app each design needs completely different html and then it makes sense to couple. No naming. No hunting down styles. The html is your ccs. You get a formatter to sort the classes and it will compress away all the repetitive junk. Besides who looks at code much these days anyway.
As far as I can tell these tools have quite a low ceiling. Great to start off with but but at some point I just find it easier to express myself with bezier curve handles than prompting. Canva, and Stitch (and maybe Claude Design) don't go that far.
There is always one thing that bites you because Cloudflare is different. I just built an AI game (sleuththetruth.com) and the primary reason it's so slow to prompt a new board is actually not because of AI latency. It's because CF workers have a limit of 6 connections (including spawned workers). There is no way to gulp down all the wiki images I want all at once. If I had put the backend on Railway I don't think I'd have this issue.
You can farm out the requests to a bunch of Durable Objects. Each DO will have a separate six-concurrent limit. And you can send unlimited concurrent requests to Durable Objects. (This is not an exploit, this is working as intended. The concurrency limit exists to prevent creating excessive connections from a single machine; farming to DOs means the requests are spread out.)
Also note that as of recently, the concurrent limit applies only up to the point that response headers are received, not during body streaming.
reply