That looks to me like Forth with extra steps and less clarity? Not sure why I'd choose it over something with the same semantic advantages ("terse english" but in a programming language), but just agressively worse for a human operator to debug.
I'm brazillian, moved to Finland 2 years ago to work here, and can confirm the sentiment.
If you ask a Finn, most people are actually quite harsh to the Finnish government, economy, etc - specially as of recent, since Finland now has one of the worst unemployment rate in EU. But lifestyle here is quite sober, everyone has hobbies and are quite dedicated to them. I guess the Sauna and Avanto culture are the main happiness drivers here, and tbh after experiencing it, I wouldn't change for anything else.
Probably not intentional, but the title is incomplete ("- this is how I get rid of it in minutes"). It does make the HN title incredibly funny for my twitter-rotten brain though.
One comment that I haven't seen yet and that puts PWA for Games in jeopardy: the maximum caching allowed for Safari PWA's (thus the whole iOS ecossystem) is only 50mb. Most mid-core / hardcore mobile games are bigger than that after downloading remote assets when the app loads for the first time, and this means a player of a mid-core PWA game would have to redownload a good chunk of the assets everytime the game loads.
I could be mistaken though, but I tried looking for how PWA's work with caching and it is a whole layer of uncertainties that depends on which browser/OS/ecosystem you are in, and if the user clears it's browser cache. In the end, it seems like PWA will only work reliably when the PWA is super light, and doesn't need a lot of caching, so for gaming that would mean only lightweight, casual and hypercasual games.
It is in the list though! The programming languages query was broken (should be fixed now), did that somewhat made you not find it? (Asking so I can improve the site UI)
Hey! Website creator here :)
I honestly wasn't expecting someone to post the link to the site here so soon (I posted earlier as ShowHN but it flopped a bit haha). I'm reading all feedback now!
EDIT: As some people posted here, language programming tags are getting wrong queries. I'm looking into it rn, but other tags should be working!
EDIT 2: Just fixed it, I made a Django query oopsie from last time I was fixing the queries. Thanks for the feedback!
I know this feeling, so hopefully this is going to be as helpful to you as it was for me.
There is a budhist parable called the Parable of the Poisoned Arrow, from a Theravada sutta. You should read a good translation on the "accesstoinsight" website, but it goes somewhat like this: Malunkyaputta, one of Gautama Buddha disciples, asks him to answer the metaphysical questions that were afflicting him (questions about the Universe, life after death and such) - and if Gautama failed to answer him, he would renounce His teachings. To which Gautama Buddha basically responded that he never promised to answer those questions, and the reason is:
"Imagine as if a man were wounded with an arrow thickly smeared with poison. His friends & companions, kinsmen & relatives would provide him with a surgeon, and the man would say, 'I won't have this arrow removed until I know whether the man who wounded me was a noble warrior, a priest, a merchant, or a worker.' He would say, 'I won't have this arrow removed until I know the given name & clan name of the man who wounded me... until I know whether he was tall, medium, or short... [lots of "until I know" later].. He would say, 'I won't have this arrow removed until I know whether the shaft with which I was wounded was that of a common arrow, a curved arrow, a barbed, a calf-toothed, or an oleander arrow.' The man would die and those things would still remain unknown to him."
So those questions were, in fact, useless. No matter the answer, the arrow was still there inflicting pain. And Gautama follows that by saying that his Teachings were the way of removing the arrow and treating the arrow wound, and not a way of answering those questions.
I'm not budhist, but I read this passage in a moment of my life I actually spent nights awaken because thinking about death was simply too dreadful (it's a very personal background, but I was VERY christian until the very night I noticed after my prayers, at 20 yo, that it was not that I believed in christianism, but I was just afraid of not believing in anything at all), so I was looking into anything I could support myself with. This story made me understand a couple of things:
1. Someone around two millenia ago also had trouble sleeping because of those questions. That's weirdly comforting, knowing that this is something part of our human condition, and something we've been trying to figure out how to deal with for as long as we became self aware.
2. The story aknowledges that what we are feeling, this existential dread, is pain. Is real pain, even if a mental and emotional one. That means that we can and should find a treatment to it, philosophically or not.
3. Most important of all, looking for answers of the kind "Is there life after death?" Is independent of not fearing death anymore. Someone two millenia ago noticed that we can live a happy life and not suffer from the existencial dread NO MATTER your own personal answer for those questions.
Again, I'm not buddhist, and by no means I no longer fear death. I still have my existential crysis now and then, still have some trouble sleeping sometimes. But it's a process of facing this feeling and understanding that it is possible to face our little time alive with human dignity and without feeling overwhelmed by death. We still can treat this pain and live happy with ourselves and our loved ones. Everyone deserves this.
Anyway, hope this helped, even if a little bit. No matter what you believe, knowing someone faced this same problem before and actually discovered a way to live happily is something that soothed me in my worst nights, hopefully it can start something good to you too.