The difference is that Cloudflare has their own high quality network and PoPs everywhere, so the quality is generally even better than P2P.
This is my experience, we are a fully remote world-wide company and we recently migrated away from Tailscale to Cloudflare and it has been much better.
HTML was an application of SGML, and precedes XML.
HTML is a markup language, and not all of the elements and features are semantic in nature. The "span" tag literally exists to provide a way of affecting a bit of text where no tag with more semantic meaning applies.
People in England are getting arrested and serving time for their Facebook posts and for flying the British flag. The US doesn't have everything figured out but it's doing quite a bit better than the other western countries.
Ideally, it needs to be "from", then arbitrary number of something like `let` statements that can introduce new variables, maybe interspersed with where-s, and then finally "select".
"select" can also be replaced with annotations, something like: `from table_1 t1 let t1.column_1 as @output_1 where ...` and then just collect all the @-annotated variables.
I need to write a lot of SQL, and it's so clumsy. Every time I need a CTE, I have to look into the documentation for the exact syntax.
Of course it's sustainable. Gilead Sciences is a $155B company originally built on a single drug (Sovaldi) that literally cures Hepatitis C. Now they are more diversified and have a stacked pipeline. The business model just changes to one like oil or mining exploration where you find a deposit with a limited lifespan and you have to keep the treadmill going to find new ones before the mother lode is all tapped out and you go bust.
But in Biotech, this is already essentially forced, cure or not, because of patent life. Merck has probably the most profitable drug of all time (Keytruda) which has massively increased remission rates for a wide range of cancers, so it's somewhat of a cure as well. But that patent life is about to expire, and 46% of Mercks revenue will disappear with it. Of course, new people are diagnosed with cancer everyday, and Keytruda will continue to be prescribed in the millions, but Teva and others will sell the generic version and Merck will lose out on the revenue. A similar thing happened to Lipitor and Pfizer. Their stock has never recovered. So the race is on to get more things through their pipeline, acquire some promising assets, and keep the treadmill going. There are 100+ year old mining and oil companies. None are mining the same asset they had one day one. Doesn't make the industry unsustainable.
>The longer someone lives, the more potential value they can contribute to a society.
This is a function of how old the sick person is, as well as how severe their sickness and hence recovery will be. The data says, for the most part, healthcare is needed when one is close in age to exhausting their body’s capability anyway.
Yep ... its like people never read some of the main dev's motivations. The ability for people to be able to read each others code was a main point.
I don't know but for me a lot of attacks on Go, often come from non-go developers, VERY often Rust devs. When i started Go, it was always Rust devs in /r/programming pushing their agenda as Rust being the next best thing, the whole "rewrite everything in Rust"...
About 10 years ago, learned Rust and these days, i can barely read the code anymore with the tons of new syntax that got added. Its like they forgot the lessons from C++...
Containers for all the shiny loots that I cannot bear to just destroy, and the nice organised containers for all those currency types. Hits my weak spot right in the wallet.
Also, keep your api small as all the tool call, DTOs and user messages (e.g. workflow recipes) add up to big context windows and accuracy confusion, at least in the latest models. I hope that gets resolved.
When asked why they captured and locked up their daughter, twice, they replied "We suffered a lot too". They expressed only rage at their loss of status when confronting her initially.
Based on disclosed facts, actions taken (that are not in dispute), and statements by the perpetrators themselves before and after the fact, we can conclude that her parents do in fact care more about their own 'suffering' and 'status', more than their daughter's physical and emotional well-being.
You, on the other hand, just made shit up from whole cloth, but are too pathetic to stand on business and disagree directly.
If I could assign remedial reading comprehension lessons to anyone on Earth, today, I would choose you.
I had a discussion on some other submission a couple of weeks back, where several people were arguing "it's obviously AI generated" (the style btw was completely different to this, quite a few explicitives...). When I put the the text in 5 random AI detectors the argument who except for one (which said mixed, 10% AI or so) all said 100% human I was being down voted and the argument became "AI detection tools can detect AI" but somehow the people claim there are 100% clear telltale signs which says it's AI (why those detection tools can detect them is baffling to me).
I have the feeling that the whole "it's AI" stick has become a synonym for I don't like this writing style.
It really does not add to the discussion. If people would post immediately "there's spelling mistakes this is rubbish", they would rightfully get down voted, but somehow saying "it's AI" is acceptable. Would the book be any more or less useful if somebody used AI for writing it? So what is your point?
The unity of the block of cheese is circumstantial, but nonetheless we define a piece of cheese defined on the presence of actual matter. The article goes to some trouble to devise a definition of holes that's also based on matter rather than its absence. But only a strict materialist would feel the need to do that, assuming they didn't want to outright deny existence to holes.
I was gonna say the last few percent might increase the size disproportionally as the last percent tend to do[0] but looks like boa passes fewer tests (~91%).
This is something I notice in small few-person or one-person projects. They don't have the resources to build complex architectures so the code ends up smaller, cleaner and easier to maintain.
The other way to look at it is that cooperation has an overhead.
[0]: The famous 80:20 rule. Or another claiming that each additional 9 in reliability (and presumably other aspects) takes the same amount of work.
I keep a reading list at quinnkeast.com/reading. Would love to see others’ if any has one to share!