3 Gy is nowhere near what could be qualified as a "Low dose".
"A whole-body acute exposure to 5 grays or more of high-energy radiation usually leads to death within 14 days. LD1 is 2.5 Gy, LD50 is 5 Gy and LD99 is 8 Gy.[11] The LD50 dose represents 375 joules for a 75 kg adult. " https://en.wikipedia.org/wiki/Gray_(unit)#Radiation_poisonin...
There are treatments that are very effective for treating psoriasis, especially those based on monoclonal antibodies. I was treated for atopic dermatitis (which is a similar disease), and I have been in near remission for several years. However, the treatment is very expensive.
Certainly, but the use case mentioned here is not related to a performance issue. It's more about syntactic sugar when a user writes SQL in interactive mode to explore data.
Yes, that's true. After all, it's the functionality that is important, regardless of the means to achieve it. On the other hand, the fact that it is part of the syntax has other advantages:
- it makes the functionality independent of the querying tool used
- it is immediately understandable, and easy to use
- it can be offered by automatic completion and therefore have a higher discoverability power than a function that would be hidden in the editor
I am the author of the post. The reason is that English is not my native language, and summarizing is very resource-consuming for me, much more than if I had to do it in my native language. But I take note of the antagonistic aspect and I will make sure to rewrite the summary ;)
I think at this point we should quantify the proportion of "inflationary" updates (i.e. those that bring absolutely nothing in terms of functionality or security) versus real updates.
Let's take a fictional example: I import D3.js to use the parseDSV() function, after 2 years the method has not received any updates, but the package has gone from version 1.0.2 to 5.0.2. With a granular system, my function would still be on version 1.0.2 (because no changes were made), but with the current system I would have received an unnecessary update.
So, in this case, granular versioning would actually help to put an end to the chaos of dependencies.
I'm tired of people saying they're tired. I use ChatGPT every day and it provides results of a quality that has little to do with Google, even though I'm aware that it sometimes fibs to me, makes up names for functions that don't exist, or makes mistakes. There's hype, but I think it's much more deserved than the hype around cryptocurrencies
The criticisms regarding chatGPT remind me of what was said about Wikipedia at its very beginning, that it was supposedly unreliable. I think we will have a good laugh in a few years reading these first comments.
There is no doubt that chatGPT is the future. It is certainly perfectible, but the existing basis is a revolution in progress.
In my opinion, there are two essential things missing for chatGPT to become the perfect replacement for Wikipedia and Google:
- The ability to activate a "system 2" or slow thinking (theorized by Daniel Kahneman)
- The ability to cite sources
And the cherry on the cake would be the ability to interact with images
I tried to parse the result of standardized POSIX commands for the nth time and I realize that i would be much easier if it were already done by a standardized output.
I would dream of a flag that allow all POSIX commands to output standardized and structured content.
"A whole-body acute exposure to 5 grays or more of high-energy radiation usually leads to death within 14 days. LD1 is 2.5 Gy, LD50 is 5 Gy and LD99 is 8 Gy.[11] The LD50 dose represents 375 joules for a 75 kg adult. " https://en.wikipedia.org/wiki/Gray_(unit)#Radiation_poisonin...