The only thing I'll say is that it's great to see the feedback in this thread applied. It became very obvious to me what the tool is for and an abstract idea of what I can do with it.
However as others have said:
- A demo video would do a lot for your product.
- nit: Real-time markdown -> change to something that emphasizes collaboration/collaborative editing. For two reason - it's a much more familiar term in the space you are building and it's easier to understand (I think) for more people.
- A sample workspace (either public or a "starter workspace" that's available by default in a new account) that is non-trivial would be great to showcase your product. Look at obsidian using obsidian itself for it's own documentation site.
- Your about page is very well written - I wonder if you can pull up somethings from there onto the main page. https://hyperclast.com/about/
I didn't sign up yet however so can't provide more feedback.
Doesn't help much because even the standard library bitrots after enough Python releases. I have things I write today but can't run on a NAS that has older Python. No issues like that with Powershell for example.
Which of those are evolving at the rate of frameworks?
BTW I'm of the opinion that frontend tooling developers should actually try to contribute things to HTML and CSS instead of building "component libraries" on top of them.
If the native controls were good and if the browsers allowed using "uniformly styled" versions of them then there would be no good reason for such libraries to exist.
It's both reassuring and frustrating. Reassuring because they decided to secure IPC somehow. Disappointing because this is such an unexpected failure mode.
My scroll direction broke, custom operations that I had apparently "saved" to the mouse also stopped working.
I gave both Codex (GPT5-ExHi) and Claude (Opus 4.5 Thinking) the exact same prompts and the end results were very different.
The most interesting bit was asking both of them to try to justify why there were differences and then critiquing each other's code. Claude was so good at this - took the best parts of GPTs code, fixed a bug there and ended up with a pretty nice implementation.
The Claude generated code was much more well-organised too (less script-like, more program like).
The area I live in has homes that remain empty because the investor doesn't need the capital nor the space and just holds empty units for multiple years when they eventually sell (for even more than they would have sold in the past).
Housing demand will always be > 0 as long as population is growing and hence there can never be a oversupply.
They are pushing the time-series rendering code to it's limits I'm sure here and for sure would've uncovered lots of bugs and possibilities for performance improvements with this.
Why is this noteworthy? Who is this person? Am I missing something?
I agree that there needs to be talk about licensing and copyright but with so "less/no content" there can be no meaningful discussion other than aimless banter.
However as others have said:
- A demo video would do a lot for your product.
- nit: Real-time markdown -> change to something that emphasizes collaboration/collaborative editing. For two reason - it's a much more familiar term in the space you are building and it's easier to understand (I think) for more people.
- A sample workspace (either public or a "starter workspace" that's available by default in a new account) that is non-trivial would be great to showcase your product. Look at obsidian using obsidian itself for it's own documentation site.
- Your about page is very well written - I wonder if you can pull up somethings from there onto the main page. https://hyperclast.com/about/
I didn't sign up yet however so can't provide more feedback.