people give me grief all the time because i don't use proper capitalization in my texts. they even ridicule me if i say "you understand what i mean so who cares"
but i don't get to do the same thing when they say stupid shit like "smol". that's just normal, while i am retarded
Using capitalisation is actually reasonably useful for people with certian classes of disabilities, maybe concider it purely from the perspective.
So is breaking up things with whitespace which you did reasonably well.
So it's not a matter of "You know what I mean, so who cares?". They may realistically have had to put in significantly more effort into understanding what was written.
That isn't entirely true for something silly like the word smol.
i often avoid capitals myself in informal writing, but to be fair, there's a valid argument that period is pretty small and can be hard to spot by itself for something as important as the statement separator . capital letters help with that somewhat, although it doesn't help that we've overloaded them for other things . putting a space before the period helps keep it more distinct, but i really wish our punctuation was better designed (right after we reform english spelling i guess ...) .
but i digress . whataboutism aside, what's the actual problem ?
Glad to see you here swyx. I think the issue you outlined is acknowledged by the htmx's authors and addressed in the Morph Swaps documentation: https://htmx.org/docs/#morphing
What is ironic though, is that the morphing algorithms are similar to what modern SPA frameworks do, except that it can be addressed without introducing new concepts such as vdom, zones, signal etc.
I agree that the island architecture is limiting when it comes to large scale application with state shared across multiple areas in the UI. I'd be curious to hear others finding success in building apps.
Funny timing. StackBlitz announced Bolt.new (https://bolt.new/) today with multi-file edit, emulated filesystem, arbitrary npm installs, and is open source. I feel ChatGPT is still chasing after Claude 3.5 artifact.
Has anyone had much experience with it, that can share their findings? I'm happy with Claude Sonnet and can't try every new AI code tool at the rate they are coming out. I'd love to hear informed opinions.
I tried Bolt this morning for about 5 minutes, and it did output valid React code, but things like inputs and buttons it created didn't work without additional prompting, and then it started throwing "There was an error processing your request"
Just tried it, it wrote promising code but in the end only the last file was created and the other files had no content (even though I saw them being written). Seems a bit bugged at the moment.
This feels like Cursor + v0. From the GitHub project README:
Claude, v0, etc are incredible- but you can't install packages, run backends or edit code. That’s where Bolt.new stands out:
1. Full-Stack in the Browser: Bolt.new integrates cutting-edge AI models with an in-browser development environment powered by StackBlitz’s WebContainers
2. AI with Environment Control: Unlike traditional dev environments where the AI can only assist in code generation, Bolt.new gives AI models complete control over the entire environment including the filesystem, node server, package manager, terminal, and browser console. This empowers AI agents to handle the entire app lifecycle—from creation to deployment.
Really saddened by the FOSS landscape. Docker, Terraform, Redis, and now Wordpress. Aside from who’s right and who’s wrong, the sheer drama and rug pulls make it feel like the beginning of an end to open source as a viable business model.
All parties are making millions off open-source WordPress.
Matt's team are upset because they only make tens of millions, whereas purportedly, WP-engine makes hundreds of millions. Matt gives back much more than WP-engine.
All their clients are businesses also making money through their WordPress-hosted websites.
I don't think there is a problem with open source and viability. It is raining money.
It's simply an in-house fight over inequities in giving back to the open source pot of gold.
We can bring another OOP idea: loose coupling, strong cohesion.
Inheritance can be useful when it captures a single shared aspect across multiple designs. It becomes unwieldy when it captures multiple shared aspects where each aspect may need to change independently.
reply