I suspect that if a subterranea home were built so poorly that radon gas is infiltrating the walls then so would water. Both would have to be factored into the design. Modern bunkers are designed to keep radon gas out and are equipped with high flow ventilation systems. High pressure shotcrete or some similar material should more than suffice to keep gasses and water out.
Radon is a problem in traditional brick and mortar basements as those walls are typically just one layer of brick and mortar. Water and radon can easily penetrate through micro-cracks that develop over the years in traditional basements.
"I suspect that if a subterranea home were built so poorly that radon gas is infiltrating the walls then so would water."
I'm no expert, but your statement makes me ask... Why then do we have homes with basements that have radon problems, but not water problems? I don't think the two problems are always related.
Water infiltration depends on the amount of water and type of soil and the drainage designed into the basement. e.g. layers of concrete and rows of shale/rocks for drainage. Not all basements are equal. The amount of radon depends on the quantity of uranium and thorium in the soil/dirt. So you are right they are not always related but the mitigating controls can be potentially related. Some construction companies just focus on maximizing profits in my opinion and some individual home builders will use construction dirt that contains low or no uranium or thorium.
One of the most recommended hosters [0] offers a 90 EUR/month plan just for up to 50 concurrent users! What I joke! This is like an instance fir my extended family and friends!
Also, in the 'about the plans' section of that page, under 'Concurrent Requests' and 'Users and Active Users' you have more details. But one can think of concurrent requests limit as actions occurring simultaneously (eg: 50 people clicking a button at the exact same time). Even on the rare occasions when that happens, the actions are queued and take a couple more seconds to process.
Netflix runs Java heavily on the backend to scale their platform. Twitter ditched Ruby on Rails and moved to JVM (Sala) for the same reasons. Any benchmark comparison for programming language performs will show Java beating Ruby on Rails, Python etc by huge margin.
I bought an '88 900 Turbo when I was 19 years old. That car and I had a LOT of fun together. The closest thing I've found to that (feeling) is my '19 Golf R.
Paw is _beautiful_ but it has no GraphQL tooling at all, I think? (Just native POST requests etc.)
(Unless there's a beta you're using?)
I use Insomnia but I am quite keen to start building myself a local-cloud-based toolset so I can reduce my reliance on a single machine, so Hoppscotch looks interesting.
Hoppscotch and other gQL clients allow introspection on the GraphQL schema so you get a API reference out-of-the-box. Makes it super easy to write queries and mutations.
I believe generalizing all Android phones without differentiating between a flagship experience and budget price experience to be a dishonest representation.
Is it though? You have a reasonably consistent and good experience from iPhone SE to 13 Pro Max. Why would it be unreasonable to expect the same from Androids?
(Personally I have found the real differentiator is not the price, but the amount of crap the vendor adds. There are crap 1k+ phones running Android and often you can find some cheaper ones that have a better software experience)
You have a fairly reasonably consistent experience going from one Samsung to the next, or from an LG v20 to LG v60. But, going from a Samsung to an LG? Yeah, there's differences. They're skinned differently, some have their own custom apps by default that aren't stock Android. Each does certain things slightly better or worse.
As an example, in my experience and preference, I've preferred the audio on my LG phones to my prior Samsung phones (I don't use my current Samsung with headphones at all, as it doesn't have a 3.5mm plug and I don't have an adapter and I don't want wireless headphones, pure personal preference there on no wireless and I've had no need for an adapter for the duration I've had the Samsung this last 9 months). I'd say for my personal taste and use, the audio experience has been a fair comparison as I've used the exact same headphones and largely listen to the exact same music files across the different phones (literally by moving the SD card from one phone to the next, no copying involved). I'm sure someone out there will disagree, though, and that's fine.
But, there you go and counter an anecdote with another just like OP pointed out. I can counter the counter too: I have all my old Android phones - all the way back to my Sony Mini (with sliding keyboard!) and they all work just fine. All of my girlfriends old iPhones are broken or bricked. I'm sure that wasn't what you meant with a reasonably consistent experience from Apple devices. There are a ton a Apple repair shops in any town so its not unreasonably to say that it isn't a rarity that they break. These are anecdotes and you simply cannot use it to compare.
IMO that Apple devices break less are a myth. They just get repaired instead of thrown out hence last longer on average.
Also the SE cost twice what most Android phones cost. It is not a budget phone.
iPhone SE (which you seem to describe as "budget price experience" considering the message you're replying too) base price is 489€. I can buy 2 very decent budget price Android devices for that amount of money. 6 if I don't go with decent.
Yep just came back to comment after checking it out. Not sure why comment has been flagged... I'd say a reccomendation of that type is likely to interest people checking out a looping DAW.
