Getting burned once in a two year time span triples your risk of developing melanoma compared to not getting burned at all. That base level obviously depends on your genetics.
You have a base level of resistance determined by your genes. When you get burned you tan and that burn is a function of time spent out in sun multipliednby that base protection. Tanning is our bodies response to the damage done by this as a form of preventing more damage. The damage however is accumulative.
It breaks your body down till your about 50 and you start to develop chronic issues which can impinge your enjoyment as you age. Dont romanticise get a workout on.
There's no need to be so angry about a hypothetical situation in which you by a laptop that you never wanted. I just prefer simplicity right now. I'm a PhD student and I don't need the code to be super fastz just need it to work right now. As it stands j just got it all to run under native so I guess my slight modicum of patience you don't have lags dividends :)
Yeah I am not running code which is hardware constrained and numpy was a real doozy tto get working because of pep517. I found Rosetta pretty fast anyway. Certainly faster than my Ryzen 2600 on arch Linux at running the same code.
I run everything python under Rosetta. Easiest way is to install home brew for Intel processors then make an alias to that version for managing rosetta stuff
Yes because software exists in a vacuum? The software is being discussed, and it's a monumental failure that it is hosted and distributed and used the way it is.
What they fail to mention is that those two aspects were broken up initially by the government after privatisation in the first place because the accountability and running of both aspects simultaneously was so bad.
I feel like video calling is not great because you lose that depth which is natural to human communication. That said, I work in field focused on digital audio and sound and so all my colleagues have professional microphones and headphones which makes up 90% of that difference immediately.
It's not necessarily just that we can't hear above 20khz - recording above 44.1khz has its merits. For example, if you want to apply digital distortion or do amplitude modulation then up-sampling or having a high SR stops wrap around in the spectrum and getting all those nasty artefacts. The end user should never need to worry about this and it should be downsampled at the master.
Can't you do partial hydration by setting certain components to not hydrate inside the <script context="module'>? Thats what it says in the docs but it might not be the same thing in my understanding (which is limited). Also aren't app-wide stores basically the least trivial way of keeping data in sync across an app? Certainly not difficult in SvelteKit as it is - in fact I can't imagine it being any easier.
I get kind of annoyed when people can't do at least 10 or less minutes of their own research. I believe it states on the front page that its akin to Next for svelte and the successor svelte/sapper. If you don't know what those are then perhaps just follow the links backwards and read?