I'm not sure the other commenters claiming all these features are attack vectors actually read the list?
How is the barcode detection API a security risk for example? Having it implemented would be amazing for web apps.
Also there's features like deep linking into PWAs that ought to be pretty basic PWA functionality that's not on this list that even Safari on Mac OSX has but Safari on iOS doesn't. Even the add to home screen menu option is deliberately made hard to find.
Apple doing this for the benefit of the user is one of the less likely hypotheses.
I think using the Quantified Scientist's YouTube reviews as reference for the quality of sensors is misleading.
He primarily tests the devices on just his own body type, and often doesn't test long enough for the device to adapt to him (some devices take a few weeks to "learn" your body).
He does make disclaimers about the above, but people seem to take the stats he presents as gospel.
I concur with the article. I recently got a ThinkPad X13 gen 2 (AMD) in one of Lenovo's heavily discounted sales. It was a pleasant surprise to discover how great a laptop it is, especially considering the price.
I do. I use toolboxes for pretty much all my development. I've scripted the setup each type of toolbox I use, so they can be reproduced. I use a terminal editor (neovim), but I think it's possible to run vscode from a toolbox too[1].
For graphical apps (browsers etc.) the flatpaks are very handy.
The above setup means I don't really need to layer much in the OS, mainly drivers and common terminal utilities.
I found Regolith nice to use except for the configuration. It seems to split the configuration into a bunch of files rather than just a standard i3 config file.
Ubuntu wasn't especially bad, it was more that Silverblue made so much sense. It fixed the issues I was having with other distros where messiness would creep into my setup over time.
I also tried NixOS, but it felt too rigid. Silverblue offered the same benefits of immutability without a loss of flexibility.
Thanks for checking it out, and the helpful feedback. I'll fix it.
There's a few motivations.
One was me noticing how I'd somehow just accumulated stuff over time, and I've seen the longer term result of that with my parents. So I wanted to be on top of what I'm getting and why, how long I'm using it for and also how I'm disposing of it.
A second motivation is to use others' lists to make more considered decisions.
And thirdly I'm curious to figure out what might be the minimal set of things one needs to live comfortably.
And cheers, I'm working on an update to Synced which I think will be quite cool! (coming in the next couple of months).
It's in a bit of a rough state (one folder is for a OLED + RGB Corne r2g, and another is a currently messy adaptation for a Ferris Sweep)
The keymap itself is pretty straightforward. As rgoulter guessed it's just a modification of Miryoku (https://github.com/manna-harbour/miryoku), with some tweaks I made to keep functionally similar layers "together". E.g. the mouse key and navigation key layers are mirror images of each other. And there's a numpad layer, with nested symbols and function key layers that stack from the initial numpad layer. I also designed it to share the load between both hands as much as possible.
The keyboard rabbit-hole gets pretty deep. I started off wanting a nicer typing experience, and ended up realising so much about the traditional keyboard designs didn't make sense to me (here's someone nicely summing up the reasons why https://www.youtube.com/watch?v=rrska7UU7BE).
Portal 2 is my all time favourite game and the most fun I've had playing multiplayer.
All the aspects of the games gel together so wonderfully to make a really immersive experience. I just loved how the backstory was unveiled as you went through the game (especially Portal 2). Plus Stephen Merchant as Wheatley is iconic.
I looked at the code check. The one 25% difference is in an intermediate variable (peak beds). The two differences of 10% are 39k deaths vs 43k deaths, and 100k deaths vs 110k deaths. The other differences are less than 5%. I can see why the author of the code check would reach the conclusion he did.
I have given a possible explanation for the variation, that doesn't require buggy code, in my previous comments.
An alternative hypothesis is that it's bug driven, but very competent people (including eminent programmers like John Cormack) seem to have vouched for it on that front. I'd say this puts a high burden of proof on detractors.
I took a look at point 3. and that extract from the code check is correct. Assuming they did one realisation I was curious why. It would be unlikely to be an oversight.
"Numbers of realisations & computational resources:
It is essential to undertake sufficient realisation to ensure ensemble behaviour of a stochastic is
well characterised for any one set of parameter values. For our past work which examined
extinction probabilities, this necessitates very large numbers of model realizations being
generated. In the current work, only the timing of the initial introduction of virus into a country is
potentially highly variable – once case incidence reaches a few hundred cases per day, dynamics
are much closer to deterministic."
So looks like they did consider the issue, and the number of realisations needed is dependent on the variable of interest in the model. The code check appears to back their justification up,
"Small variations (mostly under 5%) in the numbers were observed between Report 9 and our runs."
The other takedown reviews focused on the fact that there was non-determinism despite a seed, without understanding that's not necessarily a problem.
Agreed on the second point about not having a seed, but I added the "assuming you have used a seed" caveat because sometimes people do use the seed for some reproducible execution modes (even multi-thread/process ones), which are fine, and it's just easier to randomly vary the seed generation rather than remove it all together when running in a non-deterministic mode.
How is the barcode detection API a security risk for example? Having it implemented would be amazing for web apps.
Also there's features like deep linking into PWAs that ought to be pretty basic PWA functionality that's not on this list that even Safari on Mac OSX has but Safari on iOS doesn't. Even the add to home screen menu option is deliberately made hard to find.
Apple doing this for the benefit of the user is one of the less likely hypotheses.