Of course, changing it now won't do any good with regard to previous leaks.
795 karma · joined January 23, 2009
Of course, changing it now won't do any good with regard to previous leaks.
Yes, when including the elderly, cancer and heart disease are greater causes of health-related deaths. Is COVID-19 not the #1 health-related cause of death for "young" people?
> accidents, suicide, drug overdoses and homicide
Not long ago this discussion was about health risks, such as infectious diseases or medical complications. But yes, young people can be pretty reckless.
We were doing arithmetic, such as multiplying the risk of myocarditis and hitherto uncorrelated medical complications by 1.0, and then a number that is likely several orders of magnitude larger (death by COVID, not even the much, much more likely disablement of "long covid") by a number you erroneously claimed was 0.25 and was perhaps around 0.6 almost a year ago (anti-body study, 9/2021-2/2022).
Where did you get this data?
> Remember, COVID hasn't been shown to be particularly dangerous to young people...
What are the top 3 leading causes of health-related deaths in your choice of demographic (15-24? 25-49?) in your choice of 2020 or 2021?
VScode wasn't as bad, as it usually seemed to work (but maybe flaky plugins were actually caused by snap?) but it was certainly annoying to lose the ability to switch between windows of the same app (alt+~, I think this was a custom setting to resemble mac) if the latest window/project was opened as a new version of the app (alt+tab)
But, unless I'm missing something about latest or future releases, isn't it still optional? Can't you use apt instead and uninstall snapd altogether?
I'd agree that needing to uninstall instead of opt-in is an annoyance, and that user-hostile actions tend to be a slippery slope..
The reassessments haven't been about learning how masks work but about how a particular virus spreads and the efficacy of various types of masks in various settings between parties of varying contagion levels. The advice also has to be grounded in practicality given current circumstances (supply constraints, rate of asymptomatic spread among vaccinated populations, etc)
SVG is a lot more finicky, but I've used React to generate SVG that imagemagick can then rasterize. If you limit yourself to primitives, you can have an interactive React UI and be able to render any state snapshot to .svg, .jpg, and/or .png.
I think things just get tricky if you want to use a browser-only library or something that mixes canvas, svg, and/or html+css.
* It looks like you're creating an emitter wrapper around an EventEmitter instance, freezing it, then exporting the instance rather than the frozen wrapper[0]. I see .on() and .off() are wrapped here, while the project appears to use .addListener() and .removeListener() instead.
* As a typescript project, I would recommend using typed-emitter[1]. Not only does it ensure you're only emitting recognized events, it ensures that the type of the payload is correct for the corresponding event. Currently, your typed handlers are coercing from `any` as far as your IDE is concerned, rendering it unable to help prevent you from mistakes.
* Instead of plumbing an emitter prop everywhere, even through components that don't interact with it directly, this looks like a better fit for the Context pattern to create the global emitter instance in a top-level context provider, then getting a reference to the emitter via useContext[2].
[0] https://github.com/bootrino/reactoxide/blob/master/reactoxid...
There was a fantastic HN comment[0] which actually spurred me to buy and read it. Do your queries go back far enough to pick this one up? It's an interesting example where one sentence mentioning the author alludes to an association with the title of the book in a sentence that is explicitly about the OS.
Aug 7, 2007: My buddy Steve Searer is keeping things rolling over at http://officesnapshots.com/ He is already up to 26 companies!
I think if you had stuck with only "Web 2.0 Startups" your initial audience's interest would have fizzled out eventually. It's brilliant you were able to pivot to an audience with a more professional interest, an endless stream of content, and better advertising opportunities.
Cheers, man. Amazing work!
There was a project similar to Wikipedia, but for semantic data. It lasted for a little while before being swallowed up by Google and shut down[1]. Granted there are some alternatives, but after investing some time working with freebase data, I should be allowed to hold a grudge.
Google played a key role in muzzling more widespread usage of RSS[2], along with Twitter and Facebook discontinuing support for it. Similarly, jabber[3], XMPP[4].
These days it's risky to even host your own mail server, since most people you correspond with are likely to use one particular email service that may arbitrarily block messages from lesser-known mail services[5].
[0] https://en.wikipedia.org/wiki/Censorship_of_Wikipedia
[1] https://groups.google.com/forum/#!topic/freebase-discuss/WEn...
[2] https://www.fastcompany.com/3013890/reader-may-have-died-to-...
[3] https://blog.twitter.com/en_us/a/2006/use-twitter-by-instant... (couldn't easily find press of the discontinuation of this service)
[4] https://news.ycombinator.com/item?id=9266769
[5] https://www.tablix.org/~avian/blog/archives/2019/04/google_i...