legopeice

Wood is a sponge for water. Exposing the grain of your wood to water even for a second will draw in far more water than a woodworker would be comfortable with. You may dry the outside of the wood in a few seconds, but the moisture has already been pulled into the wood like a straw, and this will expand, causing your wood to swell, bow, or even worse, crack or check.

Trying to clump the dust with moisture would also probably jam your machines and break them.

Just leaving a newly flattend piece of wood in your kitchen overnight will twist or bow the wood. experienced wood workers know that you actually use correct measurements to "pull" the wood into being square, more than you rely on the wood being 100% flat or true.

We actually have perfectly good methods to work wood with extremely little dust.

Cabinet makers will sharpen their chisels to 16000 grit very easily and quickly by hand. The chisel cut is so smooth that almost no dust is produced.

A hand saw that is sharpened correctly can crosscut wood very efficiently if you have proper technique, which also produces less dust.

Using a properly sharpened hand plane is roughly the same concept as a chisel and produces almost no dust.

The reason we have to have dust collectors now, is because there simply isnt a better way to mass produce furniture, or for a hobbyist to crank out a dining table in a weekend.

The machines give you ridiculous speed and precision for little effort. The trade-off is they kick up a tremendous amount of dust, and currently there is no better way to reduce dust while keeping powertools.

Tailwind has the sm: lg: and xl: prefixes that let you target screen size.

eg. you can give an element a class of "sm:p-2 lg:p-4 xl:p-8" to give different padding sizes.

the docs are here: https://tailwindcss.com/docs/responsive-design

In Norlisk, Russia, the children get doses of Ultra voilet light to combat the lack of sunlight.

https://allthatsinteresting.com/norilsk#8

Seems we are having a different discussion now about shared state instead of whether JS is necessary and capable. Over used. definitely. Obsolete and to be derided at every turn. absolutely not.

Seems like a pretty good place for the browser and JS to step in? unless you want a DB full of application_partial tables?

Precisely. Good observation.

Share state? I disagree heavily. There is no reason for the backend to know how many assets a user is trying to add to a loan, or delete, or accidentally load, or add but realize mid-way that it doesn't apply.

Do you belive the backend should know about human incorrect input and track state?

What if a cat steps on a keyboard? every addition to a form is a page reload and a query to the server. then the server sends a response. Which is exactly the bloat everyone seems to go on about.

Im sorry but living in a world of enterprise apps, the sentiment that JS is a poor language and a bad choice is both out of place and highly de-coupled from real-world usage.

I think sveltekit gets it right most of the time. yes its new tech. but I think its way better than the alternatives already.

You want a frontend server that handles auth and credentials. cleans up queries to and from the main backend server.

Then you want as low-level interaction as possible in the HTML space. HTML doesnt provide everything you need. but it gets close. JS should augment HTML, the closer you stay to HTML the better.

Sveltekit goes a long way in providing this, nextjs and all the others just threw way to much tech at the front end space.

You basically want a way to turn URL's and POST requests into GET and POST responses. SPA is mostly not great and was a sidestep in a useable web.

Please could you inform me how you would build a form that creates, lets say a secondary loan for a company with attached assets. The assets could be zero, or many.

How would you create this form without Javascript? Would you require a user to create the assets before the loan?

Saying that HTML provides everything a developer needs to provide an application to client is so ridiculous, I have no idea why this sentiment is so popular. the vitriol expressed for front end devs from the community seems out of place.

Forms work without JS for the most basic baby forms. the moment you go enterprise, more is needed. which is where JS steps in, What am I missing here?