Or alternatively just provide the statistics on what the chance is that the signal was errant/natural in cause
733 karma · joined May 27, 2020
Or alternatively just provide the statistics on what the chance is that the signal was errant/natural in cause
I am completely disgusted by the HN tone of "it's pointless to look at this because there are potential flaws"
"The mansion is just 5 miles from the busiest center in the world yet appears completely abandoned from the outside"
How rich can someone be that they can buy mansions, do nothing with them, and also dodge the fines that should seemingly come with not maintaining a property? Unless they're not being fined of course, in which case, sign me up for that.
Back in my day we were using AIM in the 5th grade and joining friends of friends of friends of friends chatrooms, playing Gmod, or Habbo Hotek :)
However, if the experiment in question is, "using python glue code, can a developer string together a service that replicates the functionality of redis", then that illustrates what would actually happen in the real world.
For example, for a very junior Python developer, writing something in C is basically like asking a C developer to write assembly- possible, but they'd have to learn a lot of different things to do it.
Similarly, when I write Java, I want to be calling Arrays.sort(myarray) instead of writing my own sort (if the focus is on developer convenience and development velocity).
So, it's just a difference in what you're desiring to measure.
1) Write Redis in C. Hard for some devs who only know Python, but good performance.
2) Write Redis in Python with C libraries. Doable for a Python dev, performance hit.
3) Write Redis in pure Python. A fun experiment to see the performance limitations of Python when compared to C running on the same machine.
is probably their deceptive response.
A researcher desires to download a 50 minute archived video. A request is sent from their laptop to a lookup table server. The lookup table contains the metadata for where that file is stored.
Then the request is passed to a media server which has an SSD and RAM large enough for receiving the actual media file. It opens a connection with the tape library. The tape library handles loading the media from tape to a staging server, which also has an SSD.
So totally the media file goes from tape, to staging SSD via hardwire, to main server's SSD over the network, to client's device over the network.
But if you think that your FB or Youtube or Fidelity or Geico or SSN or IRS or Apple or Google data isn't sitting on a tape somewhere, you are extremely mistaken, because I was the one who wrote the tape control software they purchased from us.