This sounds like an intellectual debate but there's nothing of substance being said here lol. casey2 thinks British people today are wrongly (naively) complaining about the rich/powerful/elite (structuralism). top1bobby is making fun of casey2 because the latter is using a lot of big words (overwrought) while _reducing_ complicated politics to a single issue; basically "you think you're smart with fancy words but you are just as bad as the people you complain about (P.S. I can use fancy words too)"
I saw that one in the comments section, and I pretty much only agree with the last sentence. We should probably make more human-friendly architecture. However, the rest of the article reeks of eugenics. "Giving input to people who deviate from the norm harms our society". Ironically, that's actually what was bad about Le Corbusier, he was an architectural fascist. It wasn't that his mind processed visual stimuli differently, it's that he hated the way other people saw things. Here's some quotes from "The City of Tomorrow":
"There is only one right angle; but there is an infinityde of other angles. The right angle, therefore, has superior rights over other angles; it is unique and it is constant"
s/right/white/ and s/angle/race/ and you probably have a direct quote from Hitler.
"things which come into close contact with the body, are of a less pure geometry"
You don't have to go around trying to give fake diagnoses to Le Corbusier to find where things went wrong. You just have to listen!
My devil's advocate take on this article is that they're using Rust as scapegoat to their scaling (team not performance) problems. I use Go at $DAYJOB and we're having similar problems for lead times. OTOH, the novelty of Rust in webdev, means there isn't someone to make a decision like, "we don't need performance, so use threads instead of async and pass everything around in a box". I've sunk plenty of personal time trying to wrangle async on a CRUD app for learning, and I recommend it as an exercise, but I'd avoid async if I was trying to ship something.
> Based on the cheapest instance that matches my own PC's specs
I wonder how much comoute and ram you need for the routing part.
When I worked on a maps stack (no routing and cloud) we would only provision a big compute instance for importing data and seeding (pre-caching) the new tiles. The server itself could be less powerful, though you might have to pay extra for more hard drive space.
Looks like it was deleted. From the wayback machine:
Hi All,
We all knew that this day was coming. The day where Ethereum FINALLY merges into Proof of Stake after years of development and delay. As a result, Ethereum can no longer be mined. This is a devastating blow to the mining community as a whole and signals that /r/GPUMining and the corresponding discord server are ready to be shut down.
Yes, there are still coins out there that are minable. Go ahead and go for it, but most of them pose an extremely high risk and the moderators aren't comfortable keeping this subreddit going knowing that it will be used as a platform used to shill and push scamcoins. People already do push shill and scamcoins in this subreddit and discord, but the moderators have done an excellent job of filtering out the obvious shills.
We will keep this subreddit viewable, but we will no longer allow new posts. The discord server will be soon deleted and only /r/gpumining will remain in read-only mode.
While /r/GPUMining will be over, we still encourage you to get involved in crypto communities, join teams, and help push this technology forward to benefit the greater good.
We hope you got in early and made your bag before it was too late.
Thank you for all of the fun through the ups and the downs. We'll see you all around soon!
Not the parent comment, but my personal use case is for rendering a selectable list. The server side would render a static list with fragment links (ex. `#item-10`) and include elements with corresponding IDs, and a `:target` css rule to unhide the element. This would hopefully be paired with lazy loading the include elements.
edit:
My goal is to avoid reloading the page for each selection and rendering all items eagerly. JS frameworks are the only ones that really allow this behavior.
> I feel like that's the one scenario you'd care about, making the Busan players have 35 ping was the whole point
I think the key word is "significantly". The post states that the tool was originally developed for matches where both teams would be remotely connected, so neither team would have a significantly different latency (you can usually enginneer this by the first approach they suggested, of picking a server in between two locations).
reply