It's larger than 4->4.5". It feels a tiny bit smaller than the 8, but with the notch and no Touch ID I wish they would've made SE sized with a 8 size screen. I don't need a phone this big, and with my usage (~3 hrs SOT) the battery is more than good on the Mini, there's room to shrink it.
And every year I'm disappointed at how small the "big" phones are. What I really want is the Nexus 7 without bezels, which is wider than the phones of today and had 142cm^2 screen. The 6 Pro only has a 110cm^2 screen despite being 6.7"
These things don't cost anywhere near $1000 combined. It's a "pro" tax with the standard Apple tax on top. That extra RAM costs, what $50? The extra SSD space is maybe another $100? The display is the only wildcard here and you'll have a hard time convincing me that's an $800+ component upgrade.
If you want the M1 chip and/or want to be in the Apple ecosystem the price is probably reasonable, but in comparison to the price points of previous-gen MacBook Pros stacked against competitors, this one seems overpriced.
>That extra RAM costs, what $50? The extra SSD space is maybe another $100?
I have had this told to me endlessly. And then I see the laptops these people buy and its the cheapest machine with the highest numbers on the sales page. The laptops are abysmal quality and fail in every single metric not directly listed on the spec sheet.
There is so much more to an SSD than capacity. Along with every other component. Also take in to consideration that these components are all on the same chip which makes them significantly faster and harder to produce than the average m.2 drive as the more components on the same chip, the more likely there will be errors so those top spec chips are the top of the production batch.
On top of the speaker and battery as mentioned, the extra RAM actually has better bandwith (the M1 probably has 16x1, M1P at 8x2). Still a hefty price tag, I agree. But not out of line from their previous "true" Pros (2 fan variety).
I agree that you get a lot, and that the new laptops are great. If I was going to be using this full time as my work computer I would get it, but as my personal/fun computer the upgrades don't make sense for me.
I can't wait for my work to upgrade me to one of these :)
Different kinds of cores. M1 has 4 performance (high power) cores and 4 efficiency (low power) cores. M1 pro base SKU has 6 high power and 2 efficiency, higher SKUs have many more performance cores
That calculator isn't telling you the risk of hospitalisation per case, but the risk of hospitalisation over a 90 day period during the first peak of the pandemic.
The two are very different. The calculated risk includes the fact that not everyone (or even most people) will get covid during that 90 day window. It's also based on the statistics for the original covid variant - by all accounts Delta is both more transmissible and more likely to cause hospitalisation.
For example, a 25 year old man with no co-morbidity who receives a positive covid test has a 1.6% chance of hospitalisation. Obviously not everyone with covid will receive a positive test (I've seen an estimate of 1 in 4 are tested) - so perhaps that rate is actually 0.4%. That's way, way higher than the 0.002% you said.
Ultimately if covid is endemic, you will get it. At that point, even as a 25 year old, you're risking hospitalisation.
That calculator includes an estimate of likelihood of catching covid - so the actual risk of hospitalisation for someone who does catch covid is way, way higher - for a 25 year old man in the US it's about 1.6%.
Ok, 0.008% if you want. Sure feels like an argument for argument sake. I can find a list of odds of things that will hurt/kill a 20-something where the percentage is greater than 0.008 if you'd like.
It could, but it doesn't. As many have remarked already, it appears there is a bug that's causing the site to reload Google's recaptcha multiple times.
This is a big low hanging fruit fix, another is simply minifying the Forum's JS, there is also bound to be a lot that can be done on the Nim side to reduce the code size generated.
As far as I can see you already have a minification task [1] in your nimble file. May I ask you why you are not using it to save bandwidth both for your sever and your visitors?
It had this weird system where all your projects were supposed to be located in one directory structure that mapped to their git namespaces, it made no sense at all and was a pain to work around.
