Yes and no, and the answer will depend a little bit on your background. It's Rust, and the learning curve around that still exists. The HAL does a very good job at papering over some annoying details, e.g. if you're working on STM32s you'll be able to get things working without having to dig into the monstrous clock trees and timer peripherals. I found one of the biggest learning curves to be dealing with shared mutable state; embassy offers lots of primitives and tools for dealing with this that are more approachable than you'd encounter with a vanilla embedded Rust project, but there's a little bit of a time investment to learn them and you'll find yourself reading a lot of example code.
Once you get the basics, though, it's very productive and I've found it surprisingly easy to write building blocks I can reuse across a wide range of hardware projects and MCUs!
I feel there was a disconnect in communication here. I'm saying that the Ultra Rich Guy and his pet project should be held to the same standards that are affecting regular people and organizations.
Especially if we want those standards to change, giving the politically-powerful special privileges to ignore the rules is bad! It makes reform less likely to occur, rather than more, and encourages other problems like regulatory capture and selective prosecution.
And most users will have no idea. They just know that it's a super clean, easy to read page that conveys the message you have about Raku.
Yet the biggest benefit is for you; in 3 months or 3 years you'll return to this web site and make some changes, and you'll instantly know what's up. No super complex React / TypeScript / Node app that won't even build.
I've found that just using vanilla JavaScript for this handlers and simple state management also works fine. If you are using a template, each HTML page can have a little JS section at the bottom with glue logic, and it's super easy to read and maintain.
I've used htmx on several projects in the last 3-4 years and it's a success story. The only issue I've had is when onboarding other developers who don't understand the htmx mindset or wanting to strive for simplicity.
Basically the core API will remain nearly identical, but we're moving the internals to fetch() which will allow us to support streaming responses, take advantage of the async infrastructure in JS to simplify things, etc.
Hopefully most htmx users won't notice much different when they upgrade.
Thanks for being a part of this community. It means a lot that you guys try to connect with users. It gives even my skeptical grey beard a tingle and a reason to try it out.
Can someone at Apple who's also on HN please forward this to Craig Federighi? Seems this is a bit of regression or someone asleep at the wheel. I'm overall happy with the stability of Tahoe but some of the design is getting a bit sloppy.
>On December 2021, The New York Times published the Civilian Casualty Files. These files reveal that the US military, under the Obama and Trump administrations, deliberately killed civilians
Ah yes that well known conspiracy site known as “The New York Times” /s
reply