Hacker Newsnew | past | comments | ask | show | jobs | submit | ghop02's commentslogin

15 SEER relates to cooling efficiency, what is its HSPF rating?


just need a "follow who you followed on twitter" feature


API fees will be high on that order?


While I agree the partition syntax may not be super straightforward, adding a new operator for another way to sort, sum, and abs etc. seems like chaos


I think "may not be super straightforward" undersells the learning curve here. I took to SQL pretty naturally but gnarly partitioning is still the easiest way for me to get tripped up. Having taught a lot of data sciencey folks advanced SQL, even simple uses of partitioning tend to be a big barrier compared to what comes before.


(NB: Post author here)

Totally understand the concern, for now, it’s just for a particular datatype, all of the other operations are happening normally inside your query and you can still use window functions...

And btw, I love window functions and will probably be doing a post on them, but they can be a little bit weird and have some really odd ordering properties with aggregates etc.

The point of this is really much more about providing choices for folks. But yeah, if we find that people are just getting really confused we could re-consider, that’s part of why we released it experimentally.


Also, the team picked `->` as the operator, which I thought was a very natural and intuitive choice :-)

e.g.,

  SELECT device_id, timevector(ts, val) -> sort() -> delta() -> abs() -> sum() as volatility


What if those functions (were something that) returned json{,b}?

Oh or I see timevector returns a custom datatype, so I suppose the answer is it has to be one of a fixed number of provided types?


> Oh or I see timevector returns a custom datatype, so I suppose the answer is it has to be one of a fixed number of provided types?

Exactly! These aren't general arithmetic operators, they're specifically for mapping arithmetic operations over timevectors.


(NB: post author here)

We're planning on providing various outputs, json is definitely one format we'd want to support, want to file a github issue with the layout that you'd want and we can start getting some feedback to implement?


There have been numerous studies showing that 2 doses elicits higher antibody responses than natural immunity alone, here's an example of one:

https://www.nature.com/articles/s41591-021-01325-6


From the paper you cited:

> circulating antibody levels alone are not definitive measures of immune status

This is well established in the literature.

The paper you have cited absolutely does not support the claim that the "vaccine is more effective than antibodies from a previous infection".


Useless paper. Measuring arbitrary antibody levels. The antibody levels produced by natural exposure could be sufficient to protect against hospitalization, and the additional vaccine dose could be unnecessary. Also, 21-day follow up (laughable).

Show me some real-world data of previously infected individuals getting severe reinfections at significantly higher rates than the fully vaccinated. That's the metric needed to make your claim and those data have not been produced. Also, the staying power of the vaccine is already in question BY ITS OWN MANUFACTURER just via the prospect of boosters. They admit implicitly that the immunity their drug produces does not last.


I don't quite understand the "censorship" argument. Of course governments and public health officials are going to push the most effective tools we have to save as many lives as possible.

What is censorship in this case? Not spreading debunked or poorly-supported claims?

True censorship would've been something like keeping hush the rare blood-clotting incidents with J&J. But there are so many studies across so many countries that are freely available to read and be informed by.

Even the claims of twitter/other social media censoring don't hold water for me. Extraordinary claims should require extraordinary proof imo


Core ML 3 adds a ton of new operations, including control flow support.

https://heartbeat.fritz.ai/whats-new-in-core-ml-3-d108d352e5...


What about Android?


Android has its own incompatible world with NN and NDK fun.

https://developer.android.com/ndk/reference/group/neural-net...

Or you get to use Tensorflow Lite and target both platforms, also with a smaller feature set than its big brother.

https://www.tensorflow.org/lite/guide/get_started


But, crucially, larger feature set than the likes of CoreML etc. You don't get access to the NPU that way though, at least not on iOS. The only acceleration option there seems to be Metal. Which isn't bad, but also not the most power efficient thing the hardware supports.

Still though, it's the only game in town if you don't want to have insane un-debuggable headaches everywhere you deploy to device. Plus it also supports embedded Linux boards, and pretty much all current TPU-like things available there.


They're (slowly) making this better. Starting with 1.15, there is only one tensorflow pip package, no tensorflow/tensorflow-gpu hell any longer.


Really? https://www.tensorflow.org/install/gpu says to `pip install tensorflow-gpu`.


https://groups.google.com/a/tensorflow.org/forum/#!topic/dev...

Ah I guess it's on the way but not fully there yet


> This is also the last major release of multi-backend Keras. Going forward, we recommend that users consider switching their Keras code to tf.keras in TensorFlow 2.0

https://github.com/keras-team/keras/releases/tag/2.3.0


I would love to see Medium profiles untethered from the actual medium site itself.

I love that you can post on your "personal" page, another publisher and not need to make a new account.

Are there any solutions out there that let you keep a consistent profile across multiple blogs?


What many of the comments seem to be missing is that you don't need to enable javascript on all google sites, only the sign-in page. With that in mind, I don't think there needs to be as much concern as we're seeing here.


This kind of apology for a problematic change misses how allowing small changes eventually normalizes the change[1], allowing another similarly "small" step to be taken in the future. Today it's "just the sign-in page"; tomorrow it will expand to cover something else because "it's already something you're used to using on the sign-in page".

It's rare for major changes to arrive all at once. Small steps are taken, with each eventually becoming the new normal that allows another small step to be taken[2]. This isn't always intentional - each small step can seem rational at the time, in isolation.

[any replies complaining about "slippery slopes" will be ignored; the normalization of deviance does not mean change necessarily will follow, just that normalizing incremental changes allows people to support changes without noticing the larger picture]

[1] https://en.wikibooks.org/wiki/Professionalism/Diane_Vaughan_...

[2] https://en.wikipedia.org/wiki/Overton_window


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: