Previous common advice was 8 hours sleep. The graphs show that 5-6 is about as risky as 7 hours and 4 hours is as risky as 9 hours. Given this info it seems that 4-6 hours is not the a huge risk factor.
4,679 karma · joined February 25, 2007
What do you mean by "never been specified"? They are in the spec: https://www.w3.org/html/wg/spec/syntax.html#start-tags
> Then, if the element is one of the void elements, or if the element is a foreign element, then there may be a single U+002F SOLIDUS character (/). This character has no effect on void elements, but on foreign elements it marks the start tag as self-closing.
Regardless, do you think over 50% of households use the voice commands to the extent we call it "pervasive"?
You think Google home has over 50% penetration?
Because you need to have an idea of how many machines you need. And you need an idea of whether 'it will take as long as it takes' or if there's an issue in your code.
Sometimes Java decides to JIT using aes instructions. Sometimes it doesn't. Even if you run the same benchmark suite twice in a row it just does its own thing and gives wildly different results.
My learning was that one shouldn't depend on JIT performance and prefer using JNI libraries if you want consistency. Hence my comment being negative on JIT.
But pjmlp, I use Python because it's a wrapper for C/C++/Fortran libs. - Chocolate Giddyup
Context: I use python for data processing and webdev. When doing data processing, Python is merely glue for libraries in compiled languages. When doing webdev, I mostly use python itself.
First, any numbers regarding benchmarks need to be treated with contempt. JITs are unbenchmarkable. No matter what you do, someone says you do it wrong. Warmed up the JIT? You did it wrong. Didn't warm up the JIT? You did it wrong. Warmed up and didn't warm up the JIT? Wrong.
You lose predictable performance characteristics due to the above. It's difficult to describe the importance of this to the people who look at Python as glue for their compiled code.
Next, on the face of it, it doesn't look like it will compose well with subinterpreters. If each subinterpreter does it's own tracing, it's going to be harder to hit the 10k watermark of jitting hot code.
This uses LLVM's JIT which is particularly slow and heavy (16MB added to the binary size) last time I tried to use it. So this limits Python attractiveness in being an embedded language.
While this remains experimental - and hence strictly optional, packaging this in distributions that use gcc would now apparently need llvm tools installed to build python. Expect feedback from distribution packagers.
Idea for improvement: when I do data processing, I'm using python to glue bits of C, Rust, and other compiled languages so this is not very useful. When I'm doing webdev, it could be useful - and I am deploying using Docker. So why not make this AOT so I can add it to a docker build step and get all the benefit without the complications of tracing jits.
Cui bono.
There are also many law suits against AI works:
https://www.nytimes.com/2023/09/20/books/authors-openai-laws...
You really require that they resort to physical violence when they know fully that data in one DC will be backed up elsewhere so it will have no effect. From my pov, they are using the violence of the legal system to stop/slow AI.
Sibling post said it best: if you think you're immune to the trillion dollar brainwashing industry then you're fooling yourself.
Without this, the next best thing is anonymity which is simpler to enforce and covers future eventualities.
>The solution is what it is in real offline life. A regulated legal framework that allows most and limits little, a open dynamic culture that accepts diversity and constant change.
The real offline life where people can be punished in the US for aiding abortions? Or where homosexuality is illegal in many countries? Or where people conflate a mental disorder (paedophilia) with a criminal act (child sex abuse) (intentionally edgy example to highlight the edge of what's acceptable).
>and the solutions are still the same - democracy, voting, making a noise, agitating our neighbours.
This is good advice for the Belarusians with bloodied faces and no change. Or the million people who marched against the Invasion of Iraq.
Otherwise the same once it's done.
But I'm curious what the nature of a black upgrade being forced on you. Like a manager or stakeholder had an edict stating everyone must upgrade to 23.x?
Unlikely. If you are using pre-commit to run black then the version being used lives outside your venv and hence not subject to dependencies you are using. Poetry should also be outside your venv.
They have enough information when yiu clock back and select a different result. And this hasnt killed SEO spam.