expr

It makes a lot of sense for very rural living: you need a defense against the wild, and possibly hunting for food. I fully support that.

The general desire among Democrats is stricter regulation, which is a very reasonable thing. People should be required to prove that they can be a responsible gun owner and are mentally fit to own one. I shouldn't be able to pick one up from the sporting goods store like it's a bag of potato chips. It is an incredibly powerful tool and can easily kill others. It should be treated as such.

You're the one who has been spamming, it would seem, based on how much you've been posting this exact same message everywhere.

I actually tend to drop off my mail ballots at the local library drop box.

No, he's not. Dumb as fuck take.

I wasn't suggesting making JSON "REST" APIs (not actually REST, more accurately you might call them JSON data APIs or something). I meant protocols that are specifically meant for RPC, like gRPC, JSON-RPC, etc. Or message queues like RabbitMQ.

Exactly, heavy taxation on the ultra wealthy and wealth caps are incredibly popular topics in liberal circles. I swear some people have never actually talked to a liberal and just attack some strawman they've lumped in together with conservatives.

I'm leftist and anti-capitalist, but I also recognize that most liberals are people who want the same things leftists do, but simply haven't thought deeply enough about what the true root causes of society's issues are. It's an issue of tactics rather than a fundamental disconnect in core principles and values. Ultimately they want a more equitable, less stratified society where society helps and supports the disenfranchised. The same thing leftists want. They just don't understand that capitalism has to go in order to achieve it.

Liberals, unlike conservatives, are actually generally quite reasonable people since they aren't motivated by hatred. As leftists, we should be doing everything we can to educate them and bring them into the fold, rather than tearing them down.

Ah I see, my bad. You mentioned Ruby on rails and GraphQL so I assumed you were talking about some kind of MPA situation.

Yeah htmx doesn't replace data APIs for sure. Still not a fan of GraphQL for that purpose for the reasons above. There's a lot of good options for RPC stuff, or even better, you can use message queues. GraphQL is just a bad idea for production systems, IMO.

I was replying to someone talking about GraphQL and Ruby on rails, not the OP of this post.

I don't know what you mean by an API standard, but yes, it is technically a JavaScript library. But that's only an implementation detail and the spirit of htmx is that you write very little JavaScript. Javascript is simply used to extend the HTML standard to support the full concept of hypermedia for interactive applications. An htmx-driven application embraces hypertext as the engine of application state, rather than the common thick client SPAs hitting data APIs. In such a model, clients are truly thin clients and very little logic of their own. Instead, view logic is driven by the server. It has been around for quite a long time and is very mature.

It's fundamentally different than most JavaScript libraries out there, which are focused on thick clients by and large.

This is something often repeated by OOP people but that doesn't actually hold up in practice. Maintainability comes from true separation of concerns, which OOP is really bad at because it encourages implicit, invisible, stateful manipulation across disparate parts of a codebase.

I work on a Haskell codebase in production of half a million lines of Haskell supported by 11 developers including myself, and the codebase is rapidly expanding with new features. This would be incredibly difficult in an OOP language. It's very challenging to read unfamiliar code in an OOP language and quickly understand what it's doing; there's so much implicit behavior that you have to track down before any of it makes sense. It is far, far easier to reason about a program when the bulk of it is comprised of pure functions taking in some input and producing some output. There's a reason that pure functions are the textbook example of testable code, and that reason is because they are much easier to understand. Code that's easier to understand is code that's easier to maintain.

In Nebraska, I get my ballot by mail way in advance. I fill it out at my leisure, doing research on candidates as needed. I can then either mail the ballot back or drop it off at one of several locations around town (including any of the public libraries). I haven't voted in person in years. This method is so much better.

Yeah our corporate machines won't run any external media. I assumed that was standard practice.