tomatsu
These super basic fan+mat fume extractors do get the fumes out of your face, which is the most important part, but the particulate and VOC levels in the room will quickly exceed acceptable levels.
But even with a proper filter stack which filters over 99.9%, you can only filter what's actually captured. You still need some ventilation and it's also a good idea to run an air purifier in automatic mode to filter what wasn't captured at the source. What isn't filtered by filters is filtered by your lungs.
There's no need to stare at cold blue light all day long.
Fun fact, there is actually a CSS media query for selecting dark/light themes:
https://developer.mozilla.org/en-US/docs/Web/CSS/@media/pref...
Well, it's not a big deal. Just run `python3 -m http.server` or install "http-server" via npm.
They are usually triggered by a timer or humidity, but it would be also possible to trigger them based on VOC or CO2 levels.
Single-room heat recovery ventilation units are relatively affordable (about $400). There are also some which can be integrated into the window frame if drilling a 6" hole into a wall isn't an option.
R-600a (isobutane) only has 3.3 times the GWP (global warming potential) of CO2 and for a fridge you only need about 80g. For safety reasons, the limit is 150g.
For comparison, the GWP of R-132a is 1,430 and R-12's is 10,900.
R-600a has mostly replaced R-132a in Europe.
Isobutane is of course flammable, but the operational pressure is very low. Aerosol cans also use isobutane. It's comparable to those.
You only have to set the margins/width of your document and maybe some sort of header & footer and you're done with the CSS your very basic but also very readable website.
I recommend to use only top margins and to apply them to every element which isn't the first child (`whatever:not(:first-child)`).
This way there is no extraneous spacing at the very top or very bottom, which means the only spacing around the content is the padding of the container.
It's the same idea as the "lobotomized owl" selector (`* + *`). It's just more explicit.
Yes, it does look neater if you have a striped background and the lines of text align with that. However, you won't use a striped background. There is nothing else those lines of text align with unless you stick the text into multiple columns, which you probably won't do since it's annoying (zigzag scrolling) and pointless (there is no height limit on websites).
I think it's more important to pick distinct headline sizes which still look good when they wrap around. If they don't perfectly align with some imaginary stripe pattern which no one is imaging, then so be it.
At this point I just want those consent forms to be standardized via ARIA tags or whatever so that some extension can click the "yea, sure, whatever" button for me.
The air quality indoors is usually even worse than the air outside if you aren't using some filtration system. New-ish buildings release formaldehyde, laser printers release particulates and ozone, 3d printers release VOCs and particulates, and there is lots of dust generated by inhabitants and their pets.
Sadly, the Trump administration did a rollback of emission and fuel efficiency standards. It's a big step in the wrong direction.
Personally, I'd even ban combustion engines within city limits. It's completely insane that we poison the air we breathe 24/7.
It's still bad code. Using newer syntax to do the same thing didn't actually improve anything.
You could just use an infrared motion sensor. They are dirt cheap and widely used for controlling lights.
The AC unit at work has one, too.
So, all of this already exists. Without spying capabilities, that is.
V8 can be embedded in C/C++/Go/etc applications. That allows you to use JS for scripting. This is quite different from compiling to Wasm, though.
You can synthesize 1000 IU from 10 minutes in the sun if... you're young, have light skin (of which most is visible), don't wear sunscreen, it's the middle of the day & summer, and you're lying down to get roasted.
4,000 IU is equivalent to getting burnt to a crisp.
4,000 IU is the upper limit. 2K is high.
Also, making UIs with HTML/CSS/JS really isn't that nice. The workflow with Flutter is way more streamlined.
My phone's calculator app is about 14 MB and the gallery is 10 MB in size. Flutter versions would have been probably a tad smaller than these native Android apps.
Well, just check the file sizes of the apps which you have installed on your phone.
I like shopping at Aldi because they don't play music.
The worst are chains which don't just play pop music but also have pseudo radio jockeys which talk about gossip and try to be funny. It's insultingly stupid.
The gym I'm currently at doesn't have any TVs. Unfortunately, they play some music. The volume is very low, though.
csprng: 909 ns/Op
Xorhift128+: 2 ns/Op
Xorhift128+ is what all major JS engines use for Math.random().
I don't think it's a good idea if you use a CSPRNG if there isn't any reason for that. Especially if you need a lot of random numbers. E.g. a game might drop some additional frames here and there and your particle effects won't look any better and your AI won't behave any smarter either.
Not to use PRNGs ever is bad advice.
IE is discontinued. IE11, which was released back in 2013, only gets security-related updates. It's on life support.
IE11 part of Windows 10 which EOLs in 2020 (mainstream) or 2025 (extended).
Get your current nmol/L value and decide based on that data.
In Germany, you have to pay around €30 for that test. It's not covered by insurance for some reason. Anyhow, if they ask for significantly more than that, they are ripping you off.
https://en.wikipedia.org/wiki/Medical_debt
> 70 million Americans either have difficulty paying for medical treatment or have medical debt.
For me, the "clever" one is slightly faster in Chrome while the supposedly naive one is significantly faster in Firefox.
Looks like the naive approach not only wins in terms of readability, but performance, too. (Unless I seriously screwed this up which is always a possibility with micro benchmarks.)
Google experimented with something they called "strong mode". Classes were read-only, accessing nonexistent properties was an error, and things like that.
I liked it. Unfortunately, the experiment didn't go anywhere and strong mode was removed from Chrome.
Dart is somewhat similar, though. It got more straightforward semantics than JS and most of those WTF things are an error.