3,760 karma · joined May 10, 2020
People don't bother a google search, after, what, 20 years in town?
They'll have unlimited energy based on some quantum shit.
Please don't get me started on suspend-mode low energy consumption. It hasn't been true for any device I've owned. Perhaps yours, fine, but my anecdotal experiences and acquaintances' show you're in a minority.
If you count the number of devices. By app store sales, the figure is maybe 50%, probably higher.
One can license without legal warranty and still do it responsibly. If they don't, others will judge as irresponsible. This is more of a social contract than a licensing one.
This should be the first paragraph in the README.
It's not responsible to release something like this in the first place, let alone without a big red warning sign in front of it.
There should be an exponential back-off algorithm for proposals. The public should be able to ask a judge to decide whether a new proposal triggers the back-off or whether it's a new one that can be proposed immediately.
The public, in general, gets tired of repeated messages.
I suspect their motivation to pass orwellian laws are higher than the public's resiliency.
If it's possible in justice, why not in law making?
Developers are taught to overkill everything. They implement things naively, admired of how "smart" their "solution" look, compared to a "dumb" browser.
They shoot themselves in the foot all the time. Users suffer with bad UX. Projects move slowly and expensively. Everyone loses.
You could use hx-push-url [1] every time the scroll triggers loading more rows, updating the total number of rows loaded. When the browser refreshes the page, the backend will know how many rows to return. No need for complicated JS plugins and service workers. Just basic browser feature, HTTP and HTML. You have fewer ways of shooting your own foot.
I think the modern frontend environment have a tendency to look for over complicated solutions.
Most times I see people proposing JS to manipulate the browser, a simpler browser-based solution would be perfectly good.
In most cases when I browse the web, the JS manipulation leads to very poor UX.
Even when the developer is exceptionally good and can deliver better solution than the browser, the advantage gain is so small that it's not worth the effort. Unless you're Facebook and can dillute the high-quality development cost to billions of users.
About the state: there are plenty of ways to have a polymorphic backend responding with fragments or entire HTML pages, depending on state and what's required by the request. Can't see the limitation you guys are talking about.
About the scrolling position, it's actually dynamically loaded content that messes everything. Browsers do a pretty good job keeping scrolling position, as long as the page loads with the same content as before. Which is easy with htmx and very hard to impossible with dynamic content.
I see two scenarios:
1. User interacts triggering "/blog/foo", which should return a fragment
You can add a "?fragment=true", or a custom header, or hidden input indicating the backend the desired behavior.
2. User's mobile browser reloads "/blog/foo"
Respond with the entire page, including the fragments as if the user had interacted each step of the way.
Depending on RAM limitations, the mobile browser will kill the tab session. When the user comes back, it'll reload the page. But I don't see how this is different for htmx or JS websites.
If you mean crying is a recourse, otherwise this is an understatement.
There's no recourse.
this is not going to end well...
When you find good content depends on when the algo judges you're already primed to a colorful dopamine intake.