The only good thing is that I was finally able to switch away from Chrome on mobile, but for a high bad usability price.

I use Svelte when I want static site generation. It's good for that.

I hate that it's all different from v4 to v5.

Comments URL: https://news.ycombinator.com/item?id=42746606

Points: 2

# Comments: 0

I don't like drama. Why is it in trouble just now and it has not been an ongoing process?

- Cannabis has been known to help, both with Cancer as well as feeling unwell during chemo and increasing appetite.

Best of luck

http://www.orangepi.org/html/hardWare/computerAndMicrocontro...

I would respond but HN is limiting how much I can post per day, only 4 posts.

Orange Pi 5 is the go to solution for IRL streaming right now as well as router. The openwrt project has created a special variant of the orange Pi, but the regular one is cheaper and has more features. Both are very well supported. Claiming it's an eventual paperweight is FUD and not true.

Yes, it's not perfect but right now it's pretty good. I like composables, there are a few gotchas to get used to, but that's everywhere, when in Rome.

Vue is better IMHO, but doesn't have the graphql client I require and there is more momentum in the React ecosystem right now. More innovation is happening in the React ecosystem than elsewhere.

Angular is still stuck in the past. Ngrx as the only state management library, full of boilerplate and the annoying rxjs. One doesn't simply with Angular.

Svelte is too barebones for my taste. Manually doing form validation and rendering for instance. If it had a larger ecosystem it would be great, but it doesn't. It for the purists who like reinventing the wheel. Of course it has other good uses as well, it's fast, much faster than React.

When I used React, I use high level libs where I don't have to manually do stuff. But when I do it comes naturally, it's a simple learning process.

I prefer logic in templates from Vue over the brackets and conditions of React. I like Angular's templating and 2way binding. I don't like Reacts aliases, like having to write className instead of class.

But in the end productivity is what matters for me, and React is pretty productive and has a large ecosystem. But finding the right packages is a journey.

React SSR is a horror story. Vue's especially with Quasar is a love story with butterflies and perfume. Great tooling.

It's good enough and I'm actually enjoying to work with it, maybe because it's so new to me and learning new things makes me happy (like when you're young you're happy because there is so much new stuff constantly, which studies found that it makes people happy).

That they removed the ability to embed it without compilation from v19 on is a very bad move though.

"But that's not SOLID and not OOP". But it's simple and does the job.

I moved to Go and AngularJS. That was 2013. I did full backend aka full ssr with Go, and it's a PITA.

I did try htmx with a jinja like template language in Go, with templ and in Rust and ... I forgot the library, it's the go to library in Rust for htmx. All the annoyances are still there.

Session management, service oriented design, if else blocks between and inside html tags. Path parsing and comparison. Template macros. And now also fragments.

Now I use a graphql backend for data, and react consumes it while the ide supports intellisense for queries. It's more simple than writing your queries by hand on the backend. You have interactivity for free. And you let the client worry about how the data is displayed. Also you let the oidc server worry about users.

Concerns are separated. I have authz middleware on the graphql backend, easily written. Everything has layers and there's order and a clean structure. As a plus I don't have to annoy my users with captcha. And I have reduced infrastructure costs as well as traffic.

I'm 50. My internet journey began 1995. I did enough of the old way to hate it and to know when something is better. I have met my share of fanatics, of language and framework Nazis.

You have to stay curious. I have tried htmx multiple times and found it inadequate, not good enough, too limited.

Like I wrote there are no frameworks in any language for it. It's just JS hidden behind html attributes, claiming it isn't JS.

I hate deception, the zealots are deceptive as all zealots in any language, package or framework are. Angular Nazis holy crap. Or React retards where you mention how Vue has simple SSR adaption and Rract doesn't, and are labeled as a React hater.

I'm pragmatic. I like clean structure and efficiency as well as simplicity. Sometimes you have to learn a bit of complexity to have it simple and efficient in the long run. I have tried many things. Ruby on Rails, Elixir. You know what, I have started programming at the age of 11 on the cpc 464 in basic, at 12 I cracked c64 games and wrote cracktros in asm. I'm one of the first cheat creators for MMORPGs ever. I don't consider myself super smart, but I have seen a lot and tried a lot. I also struggle with learning new things. But you have to. Htmx is not the way. It's a step back. It's only for simple things.

I do believe the hype when it's reasonable. Like with MVC. It was the natural way to write SSR websites. This is the way. But then something better came along and it took a while to solve the inadequacies it had. But now it's at a point where SPA + graphql + oidc = awesomeness. And it's going to become better. And I'm not talking about the Nextjs crap, those fake backend libraries that are hugely overcomplicated.

I'm currently using Go with Ent and Gqlgen and Relay extension on the backend and React vite with Relay graphql client as well as React-oidc-context for oidc with zitadel as the oidc idp.

It doesn't take 2 days to make a simple form.

You need to get put your comfort zone and learn.

I built a classifieds site in 3 weeks. Including admin ui. I'd call that as productive as it gets. There's currently as library in the works where you will be able to tell generative AI to make a frontend just from showing it the graphql schema.