I think it’s a game of diminishing returns.
Let’s say 6 minutes gives you perfect 100% cleaning.
Well 30 seconds probably already gets you 50% or more of the total benefit just by getting fluoride on your teeth and rinsing your mouth a bit so getting people to 3 minutes is probably approaching perfection anyway and if you start asking people to do 6 minutes then they’ll say fuck it I won’t bother at all so settle for the 80% win.
I assume.
I have a SpaceX joke. It’s a blast.
Also Brave allows for background playback of YouTube videos on mobile, iOS at least
The way I feel about slow walkers or families who spread out to block the entire path is what I need to keep me humble and remember that there’s no such thing as a “good person”.
Writing prompts or some kind of creative writing exercise
Yeah I would never use vanilla JS unless forced to these days. Always Typescript if I’m doing anything JS related that isn’t completely trivial.
As for HTMX, it looks fun but I would consider that kind of fancy and fresh framework more appropriate for hobby projects or a rapid iteration proof of concept and not for production. For a start it’s just fresh and that alone means you can’t really use it yet except for more trivial cases since you need to be assured that the tool will be able to scale with your needs and it just hasn’t been proven for that yet.
Secondly if you need to be able to scale a team then you need to either be willing to pay to train people in a new framework (and there are a constant stream of cool new frameworks so training should be conservative), or you need to be able to hire for it easily and to hire for it easily it should be a widely used framework with a deep of talent available.
Finally it lacks type safety, at least so far as I can see, and so I wouldn’t want to use it for anything more complex than a storefront.
I can totally see that being a fun tool to use for a hobby project and maybe in two to five years we will all be using it just like we are all using react and vue today but there’s value in being conservative in these choices when you’re looking for scalability, long term maintainability, and the ability to assemble a team.
And finally it’s not the first js in html framework. It’s been done before and hasn’t really caught on. Maybe HTMX will be different, im not saying it won’t be the one to crack that nut because it very well might be the future who knows, but I would want to see it’s approach to be proven before selecting it since in the past js in html has tended to hit a wall. Like you can often do some really cool shit with minimal code and you fall in love but then you hit some use case that requires more complex logic and bam you find yourself either resorting to traditional JS anyway or even worse you are left stuck.
These are general remarks on why fancy fresh isn’t necessarily the best. I haven’t used HTMX so it’s possible it will be the next big thing. Eventually something will replace React / Vue / Svelte for sure and maybe it’s HTMX.
But that’s the rationale for considering for a hobbyist tool or a rapid prototyping tool rather than a production ready framework.
Today for anything that really needs to scale and where SSR is desired i would almost certainly be choosing Vue or React or maybe Svelte. And if I was feeling adventurous I might use Qwik since it’s not a radical departure from those others, being a lot of the best of Svelte with some cool new ideas.
These things move in cycles of course and clearly we need to start moving on from Vue and React soon since SSR is an afterthought in their design. But that needs to be balanced against a healthy conservativism if the product needs longer term scale and maintenance.
I think the more immediate path forward is to get much better server side runtimes such as bun and smarter caching and bundling techniques. Bun or some other very snappy and optimized server side js engine, using html templating more than jsx components, with very smart webpack bundling and extensive caching using an islands or micro frontends architecture for progressive enhancement is a more conservative choice that can achieve a lot.
Maybe something like HTMX will be a paradigm shift. It will happen soon enough of course. But I wouldn’t throw away a decade of tooling and development in those less sexy frameworks too easily. Not when there are less radical changes we can make to achieve dramatically better results that are still on the table that don’t require the adoption of unproven and not widely used frameworks.
Sorry I’ve written a lot here xD but to add one more comment, for server side code dotnet is making huge strides and modern dotnet core is blazing fast now. Sure it’s not necessarily the fastest but it’s nonetheless really fast now and it comes with DECADES of proven use, a massive community, and tooling that is second to none. If I didn’t want to use server side JS it would take a very fancy framework indeed to convince me to forgo the decades of proven reliability and development that is available to me there. Plus I can say with a very high degree of certainty that dotnet will still be around in 5-10 and probably even 20 years from now while HTMX has a high chance of disappearing to another fresh faced sexy framework in the near future.
My apologies if this was too long or repetitive :)
I didn’t say anything about Reagan. If you are saying “Fuck Reagan” then we don’t disagree about anything important so far as Reagan is concerned.
As for it not being a legal right in the USA that’s a straightforward fact. It was DC vs. Heller, a 2008 case where a Washington DC law was found to be unconstitutional which is the first case where such a law restricting access to handguns was found to be unconstitutional. There were plenty such laws prior to 2008 that survived legal challenges which is what proves the legal right to own a gun didn’t exist prior. But in 2008 the Supreme Court stated the law was unconstitutional at the federal level (DC being a federal district) establishing an individualized right to guns for the first time.
And it was in 2010 that this was extended to additionally restrict the law making power of states, in addition to the federal government, since by default the constitution is understood to restrict the federal government and not the states, but the poorly defined legal doctrine of “incorporation” basically says some bits are applied to restrict states as well.
In the sense of having an individualized legal right to own a gun, prior to 2008 it didn’t exist.
As for ruby ridge types saying shall not be infringed sure, I’m sure many of them advocated the maximalist interpretation way back when that the courts later adopted in 2008, but up until at least the late 90s the idea that weapons could be regulated wasn’t even controversial and the maximalist position could then be called mostly fringe and was only just beginning to emerge as a position a suit wearing serious legal professional would advocate. Bill Clinton banned a bunch of them in 1994 and no one really blinked an eye at the constitutionality of it and the federal assault weapon ban of 1994 survived legal challenges that it definitely would not have survived after 2008 and DC vs. Heller.
The NRA became a lot more activist in the 80s and 90s and really it was their activism that pushed the once-fringe idea that the constitution required largely unrestricted access to weapons into the mainstream.
Which requires editing out an entire sentence by calling it a prefatory clause, a preamble, which flies in the face of the fundamentals of constitutional interpretation which requires the assumption that each word was written for a reason.
If rapid iteration is more important than performance or cost then you can more easily have a monolithic-ish build system that creates the client and the server from a single code base, or with shared code between them.
If you are trying to upgrade frontenders to be fullstack it’s an easier entry point.
Sometimes the performance characteristics of node actually is useful for serverless since a cold start and a hot start are not very different, closer to a fixed cost just to run a script when compared to something like dotnet which has slow cold starts but fast hot starts. Which is also why it sucks for most server code but on occasion this can be a useful characteristic.
If you want to do serverside rendering with client side hydration then it can be handy to implement the display logic once and run on both the client and the server (eg server side rendering react or vue etc)
Those are a handful of decent reasons but broadly speaking agree, it’s not the best choice if you care about cost and the benefits in the specific cases above are either rare or short lived.
Except really for SSRing with client hydrarion, that’s really the slam dunk case where it’s the more often than not correct choice due to the advantages of not duplicating logic.
The real reason why I often use server side JS is that it’s just faster to write in the first instance if I need to spin something up real quick or for infrequently invoked code where performance and cost don’t really matter. Of course for anything serious it’s a bad choice.
20 years of software engineering and you too will have a 10-20% chance of knowing how to exit vim.
The 2a doesn’t, or didn’t until 2010, make reasonable gun control outside government legislation.
It was a sharp shift to the constitution first in 2008 at the federal level and then applied to the states under the doctrine of incorporation in 2010.
Gun nuts like to pretend it is some eternal constant, or more likely most of them simply don’t know the law here and are just parroting the gun lobby take on things, but it’s a straightforward fact that the individualized right to own guns didn’t even really exist until 2008 and the near complete inability to pass any gun laws didn’t exist until 2010.
The 2a was reinterpreted very recently. Before 2008 it wasn’t well defined and most assumed the bit about militias had something to do with it. Scalia basically is the one who decided to edit out that part of the constitution by calling it a preamble, which is extremely against the fundamental principles of constitutional interpretation which is to assume every word was written for a reason.
And for the record I like guns and am for gun policies that allow sane and healthy adults to have guns.
Unlike your Java program amirite.
The benefit of java is that you didn’t write the security holes in your software.
You have a drink in your hand, you go “oh hey it’s Alex how have you been man?”
Alex tells you about his new hobby.
You gesture to your friend “hey Alex have you met Jamie?”
Alex and Jamie get to know each other.
Rinse and repeat.
Jamie meets a friend and starts chatting. You awkwardly stand beside Jamie taking sips of your beer until Jamie says “hey Andrea have you met my friend 420?”
You introduce yourself.
After a while everyone has met and had a few drinks and some good music starts playing and you start dancing in the dance floor. At first it’s very self conscious but after several songs and another drink you start vibing.
Asking for evidence is unreasonable, you fucking tankies
Not really. At all. Like they’re barely even a bandaid.
The issue is a car weighs a couple of tons and it’s being used to move a person who weighs around 100kg.
It’s massively inefficient use of energy.
Even in some fantasy world where the energy used to charge the batteries is all renewable - not even close to reality but let’s pretend - all that lithium and other precious earths are still an environmental disaster.
The answer is mass transit and lower mass vehicles. A lifestyle change is actually required and the thing is it wouldn’t even make people less happy, just that change is so fucking scary for some reason.
Walkable cities are a dream lifestyle and an electric scooter in a walkable city is outstanding. Fuck urban sprawl.