151–160 of 198 posts
Haven't been using react because of the JSX, but is this really where we are heading? https://hyperapp.dev/tutorial#rendering-to-the-dom Looks like som obfuscated JS-code..
I have tried Hyperapp some time ago. It's usable for small apps, but the lack of ecosystem makes it unfit for anything larger -- as is usual for all niché JS frameworks. Funnily, the "ecosystem" page contains just Lorem Ipsum ( https://hyperapp.dev/ecosystem ) and the Awesome Hyperapp section for V2 is almost empty ( https://github.com/jorgebucaran/awesome-hyperapp )
Is niché a portmanteau of niche and cliché?
Earlier quoted context omitted.
Their guide ( https://hyperapp.dev/guides ) page is also filled with Lorem Ipsum.
Ouch, yes, that's also a WIP, thank you for checking in, though.
But it looks like a great start
Earlier quoted context omitted.
Ouch, yes, that's also a WIP, thank you for checking in, though.
The quickstart is quite clear, but I'd love to see some slightly larger examples like, how is state passed between components? How do event handlers work? The API page seems sparse as well. But it looks like a great start
Earlier quoted context omitted.
There has never been any separation of concern in web development. Just because you put your scripts, HTML and CSS in different files doesn't mean they are separated.
Isn't that the definition of separated? If you want to edit content or markup, you open the HTML file. If you want to edit business logic, open PHP or JS. And so on.
"Surely, you couldn't use an actual arrow here... right?"
I find myself having to copy and paste the text to find out for sure.
Earlier quoted context omitted.
Going back to PHP and ASP you mean.
Text templates are the technology for web development. They are so much better than anything else that there's no comparison. There are some bad templates implementation, and some good ones. The original PHP and ASP are bad. But that doesn't mean templates are bad.