HN user

wired_devil

23 karma
Posts0
Comments28
View on HN
No posts found.

Nice! I was searching for something like this! Jus got a install error: corepack install Adding pnpm@9.9.0+sha512.60c18acd144bff695d339be6ad13f7e936eea6745660d4cc4a776d5247c540d0edee1a563695c183a66eb917ef88f2b4feb1fc25f32a7adcadc7aaf3438e99c1 to the cache... Internal Error: Mismatch hashes. Expected 60c18acd144bff695d339be6ad13f7e936eea6745660d4cc4a776d5247c540d0edee1a563695c183a66eb917ef88f2b4feb1fc25f32a7adcadc7aaf3438e99c1, got 60c18acd138bff695d339be6ad13f7e936eea6745660d4cc4a776d5247c540d0edee1a563695c183a66eb917ef88f2b4feb1fc25f32a7adcadc7aaf3438e99c1

This things exist to solve "modern" problems, like the "inconvenience" of waiting 0.5s for your page to load. So you have to add a placeholder thing. But for that to be smooth, you need to have an SPA, and SSR. So you end up with a whole new approach, just to not see a blank page/appearing text for 0.3s.

I think over time there were more use cases for everything. People still make sites with pure html and css (myself included) but that is not always the best way to do it. For example, take a complex admin control panel thing like AWS, it would be a nightmare to replicate that without a front-end framework. A really complex business logic made with a bunch of .php files? You would end up with a code base that is a mess and hard to maintain.

It is easier for the frontend developer to look only to the status code of the response and pop up a paywall or something, rather than some message in the boby. The same goes for 401 Unauthorized or 403 Forbidden, etc.

I don't like this syntax: "if: {". Using ":" for a one line statement is ok, but in most cases you have to use multiple lines and end up with two identifiers that represent the same thing. Maybe you can make the "{" for multiple lines and ":" for one line. I like to have an indentifier for one line statements, unlike the C approach.