There are a lot of strange spots in Russia. I was looking at a spot south of the Pechora Sea on the light pollution map, then comparing it with Google Maps/Earth. I can't see anything that would correlate with that much light.
At least in the PS5, the ultra-fast SSD and some technology around it are supposed to drastically reduce the need to keep things in RAM in case they are needed quickly later. There's a talk about that and other PS5 innovations by Mark Czerny. It's a very high quality talk.
> This last one also surprises me, was expecting at least 32GB
Well the GPU is comparable to 8GB models, so I can see why 16GB would work fine. You don't need that much space for game state.
Though looking into the Series X more, they sure set up the ram weirdly. There are 4 1GB memory chips and 6 2GB chips. This gives it 10GB of very fast memory, and 6GB of somewhat fast memory. The operating system reserves 2.5GB of the somewhat fast memory, and games get 13.5GB
The 'natural' setup would be 20GB, and they didn't even go that high, so they must be plenty confident that 32GB is well beyond what they need.
While I have no insider knowledge here, weird memory architectures like that are often a cost measure. The XBox 360 had a small block of super-fast memory alongside its huge block of slower memory (the super-fast memory was used for framebuffers, among other things) and there have been occasional PC video card releases that had weird tiered memory architectures as well - I believe NVIDIA released at least one card where part of its VRAM had certain limitations.
> While I have no insider knowledge here, weird memory architectures like that are often a cost measure.
It depends on what you're comparing to. It costs more than having 8x2GB, but costs less than 10x2GB.
> I believe NVIDIA released at least one card where part of its VRAM had certain limitations.
Well there was the fiasco that was the GTX 970, because one chunk of memory was one seventh as fast as the rest. Plus a couple other quirky models. This move should be much easier to deal with, and making developers deal with it is the kind of thing a console can do much more easily than PC hardware.
On the other hand, some people want Bitcoin to succeed so much - or rather want the price of Bitcoin to succeed because they speculate on it - that they'll engineer some fraudulent schemes in a relatively unregulated market to support their bank accounts.
I think it's likely a bit of both, but you can't deny there is something unsavory going on with Tether and these offshore exchanges
I'm curious - is there a tool handles solely the "frontend codebase generation" part of this? This looks great, but we already have a well-defined backend and REST API built using Python+FastAPI, with SQLAlchemy as an ORM and Postgres backing it. I am not a good UI/UX designer, but I understand and have built React applications, so really find myself looking for something that can take an OpenAPI.json spec and produce a hackable frontend codebase that follows best practices.
I had seen this a while ago but should take a fresh look at it - it seems like there should be a community tool that generates data providers from an openapi spec. Thanks!
I believe so - basically following the vanilla SQLAlchemy integration guide they have [0], and not trying to await query results as they do in the the async guide [1]
If you had a chuckle at Immortal's Battles in the North album cover, please watch the video for The Call of the Wintermoon [0], which was on their first album, Diabolical Fullmoon Mysticism. I'm convinced they knew it was hilarious
Immortal very much was doing the whole black metal imagery thing with tongue firmly planted in cheek. Not parody, but absolutely having fun with it and not taking anything seriously.
Seems like Forza would be easier to interface with too, example: this guy built a virtual cockpit[0] using VW parts -- the shifter, tach/speedometer all work
The most impressive thing about Stripe's website is IMO their documentation. I've tried to replicate it using tools like widdershins and slate, but can't get it as beautiful or functional.
> 10/ When we say "inflation-adjusted wages look good," we are actually saying "if you could take your wage back to 1970 and spend it, you'd be better off than you were at the time with a 1970 wage." I mean, maybe that's interesting. But it doesn't describe lived experience.
Isn't more like saying, you can buy more units of 2020 "consumer goods" with a 2020 wage than you could buy 1970 consumer goods with a 1970 wage? His point is just the definition of inflation: $1,000 in nominal dollars more valuable in 1970 than in 2020.
The important part is the segmentation of inflation between the whole economy (consumer goods, industry, and also the basics) and the price of just the basics: housing, health care, transportation, education. If those basics were the basket of goods used to define inflation, then the numbers would be very different.
$1000 in 1985 dollars buys $2300 worth of consumer goods in 2020. But you'd need $3,110 2020 dollars to buy the basics you could get for $1000 in 1985.
Also, another aspect to consider is what is the basic minimum to be integrated in society and exist socially.
In the 20ies cars were not a social necessity, but beyond the 70ies, not having a car generally means partial social exclusion (more difficulties to get a job, etc).
Today, not having a computer/smartphone/tablet and an internet subscription would impact social integration.
This basic minimum need is not set in stone, it's a shifting target. Rephrasing the problem with "What is the current median revenue Vs What is the basic minimum to be an integrated member of society" would be a better way to put it.
Or, in other words, inflation indexes are an average, and like all averages, it's a bad idea to blindly trust it, because sub-groups of the overall data may show much different results.
https://www.lightpollutionmap.info/#zoom=5.85&lat=68.2729&lo...