Altho · HackerTrans

vor 3 Jahrendiscuss

I think it's an interesting hypothesis; it's definitely a complex piece. However there are some things like the different size holes and the little knobs that I don't see adding complexity to the dodecahedron and seem to be more functional to me. It seems like it could be rotated to put the right size hole whereve it needs to be and the knobs are placed so it can stand no matter what hole is chosen

Altho

vor 4 Jahrendiscuss

As far as I know Belgium, France, Germany, the UK, Greece and I think Spain and Italy have very popular unlimited sms phone plans.

Altho

vor 4 Jahrendiscuss

would shell commands not be a good way to do that ?

Altho

vor 4 Jahrendiscuss

Most European countries have had unlimited SMS way before messaging apps where a thing

Altho

vor 4 Jahrendiscuss

It's a tradeoff, basically the question is "Will most users need and read all the content or not". Displaying everything at once without making extra querries is best, but not always possible . The frontend is fetching the backend. So it's going to say "Hey, send me all the comments from all the posts from november 2021". If there are 3 it's fine, but if there are like 23,000 of them you can't really load everything at once , that's why we use pagination on the backend. We say "Hey send me results 1 to 25 of the comments from all the posts from November 2021" This way the frontend only displays 25 comments for a quick page load and we hope that it will be enough. To display the other comments either we ask the backend to let us know how many pages of 25 elements there are and we display that amount of pagination element links (pagination), or we simply tell the frontend to ask the next page once we reach the bottom (infinite scroll). Even if displaying all the content is possible, if there are content that only 1% of your users will read you might want to offer faster loading for 99% of users and add a few seconds of loading for the 1%.

Altho

vor 4 Jahrendiscuss

You're right if you're using the web in order to display content. That was the case in the 90s. In this case, yes, a simple index.html with a <h1> and <p> is fast, responsive etc. But with webapps being more and more common one could argue that displaying text is not necessarily the web's main purpose anymore. If you're trying to access figma with a text based browser it's gonna crap the bed, so it fails the test, but is it a relevant test though ? The web is bloated but it didn't bloated just because engineers were bored, it had genuine use cases where doing more than just displaying text was needed. And it wasn't ONLY for marketing purposes (but it played a big part i'm sure)