skysight-inc/HackerNews huggingface dataset:
I worked for an early cable high speed internet provider in the mid-late 1990s. Amongst other things, we used SGIs to power the proxy-cache servers at the edge of our customer networks. In some places, we even had SGIs on racks down in manholes where some of the headends were located. I also remember some SGIs up at our northernmost outpost in, I believe, Fort McMurray, Alberta. One of them had a hardware failure but they were under service contract and some poor SGI tech (or whatever company they had subcontracted to) had to make a day-long drive up to fix it.
Probably the most important result:

>There is one S-PRNG construction where we have not been able to find any fault, namely the hash based generator of Claessen and Pałka (2013a). In particular, the generator was subject to the test methodology described in Sections 5.5–5.6, passing all tests.

Does anyone know if splittable PRNGs are equivalent to the class of PRNG you could implement with a parallel prefix scan?
Effective Java
http://www.amazon.com/Effective-Java-2nd-Joshua-Bloch/dp/032...
May I suggest adding also USB plugs to be able to load your devices without extra bulky part?
The author of this tool should use history.replaceState instead of history.pushState. Otherwise the way the page saves state using the HTML5 History API makes it impossible to use the back button.
It's gonna be like "Beauty and the Beast" up in here. You have far too many opinions Cogsworth!
Agreed for individuals. For (commercial) organizations I think it is valid. One good citizen in this respect is btw the ASF: http://attic.apache.org/ … clearly flags the dead ;)
I definitely recommend Gandi.net.

They have a very easy interface to manage your domains and their zones.
As a result, if you develop your business and need more domains, you'll save a lot of time.

Plus, they have a good customer service, they offer SSL certificate for 1st year, and free emails addresses.
I have never used it before, but brackets, parens, curly braces in this language don't act like they do in a C-like language.

__beats_______________

))) - whole

)) - half

) - quarter

] - eighth

]] - sixteenth

]]] - thirty secondth

__rests_______________

}}} - whole

}} - quarter

} - quarter

o/ - eighth

oo/ - sixteenth

ooo/ - thirthy secondth
Is there any mid-range 4G Android phone that you would recommend? My priorities are battery life, camera, tethering, and GPS signal acquisition time (only had a problem with this on one phone long ago but super annoying).
Almost all mine are registered with either enom or sitelutions.com. sitelutions lets you choose a charity where they donate to and your portion goes to the charity you choose (that they recognize). I have never had a big issue with either, although Sitelutions support has been a little faster in getting back to me when I have a question or issue but I have been moving more to enom because we integrated an app we have with their reseller api.
Google's response: http://www.politico.com/magazine/story/2015/08/google-2016-e...
Try again https://en.wikipedia.org/wiki/LG_Prada
They tried that in react-datagrid, but they forgot to expose a bunch. It's easy to use inline styles and hard to go back and add the layers of exposed properties you need to make sure they are accessible.
Disney Cast Member: They Replaced Me, Others, with Cheap Foreigners on H1B
Wrong, aurora supports read replicas, and of course client side sharding.
Is the link dead? I get a 404.
Ridiculous app ideas taken (sort of) seriously
> "People talk about the open road," she says, "but in my experience, the road is tolls and traffic cameras."

There was a time when if I was having a bad day I'd hit up the highway, roll down the windows, open up the throttle and just drive for an hour. The sound of the engine, some wind in your face, isolation and freedom.

Now there are speed cameras everywhere and everyone's driving 25mph under the speed limit. There is no open road, only frustration.

They complain that our relationship with cars has become very utilitarian... But that's what our culture has made it. There will be no risk taking. There will be no excessive pollution. There will be no fun.
Yeah. If I saw a queue like this, I'd monitor it before joining just before the next person was taken.
For my Masters' work, I needed high speed tx/rx on Windows and looked into the same things you did. I can't find the statistics for the tests I ran, but WinPcap's speeds weren't much better than Winsock's, which was fairly poor. The solution I used was an NDIS kernel filter and protocol driver which pushed the packets into user-space memory. Luigi Rizzo has recently added a Windows port of netmap to his repository, so you might want to look into that: https://github.com/luigirizzo/netmap
> The static password sitting in a database, is perhaps the dumbest idea anyone ever came up with for security. As soon as a resourceful (or even not terribly bright) hacker finds his or her way into the database, as we’ve learned time and time again, the passwords are sitting there for the taking, a giant treasure chest.

Hopefully nobody does that anymore. All passwords should be randomly salted and hashed, preferably with scrypt or bcrypt. (We use bcrypt at Userify and also sha256 in the browser before the password even crosses the wire, so we never handle your raw password.) For servers, we take the same approach: you should keep your private key private on your laptop -- we only want public keys.

Passwords are just tough to replace. They're universal and work on almost every device. Lots of things have tried and failed to dethrone passwords, such as PIN numbers (insecure), biometrics (which are not authentication), SSL client keys (abstruse), dongles/smart cards/etc (expensive, inconvenient). MFA and integrations like oauth can help.

Fortunately, there's a lot of interesting research going on in this area. We'll probably always have passwords, but they'll get stronger over time.
I'm assuming the downvotes are because claims like this are very common, and without some kind of presentation of evidence, and discussion of the explanation (if any) given by Google, they just become background noise in any discussion.
There's a distinction here between DNS hosting (telling people what address "foo.com" should point to) and domain registration (making it known that your server "owns" that domain and is where people should look for information about it). The former is just running a DNS server, anyone can do it. But the latter involves being an official "registrar" and paying alot of money to add names to the root nameservers' lists.
Maybe he had an turned the front camera on giving him a better view of the back.
One mechanism that I find very striking, is when journalists make the choice between stories like "X says Y" vs "X refuses to apologize for saying Y".
Poison-Injecting Robot Submarine Kills Sea Stars to Save Coral Reefs
if the reason to not apply YC is "time consuming and soul crashing at the end", we should not even consider starting a startup at all.

for us, we apply because we realize how much we can learn (why do we know before even get in? i have talked to a lot of YC alum, and 90% of them that i talked to are independent and in-depth thinkers, who suggest me to look at things from different angles. and we could only imagine how much more we can grow if we get in).
First off, the WiFi thing. Ffs. The difference there is literally typing "-s 0" or omitting that parameter vs "-s 64". Hardly anything evil or firable or criminal. Making them seem bad because they didn't fire someone for a trivial mistake is silly (and anyways it was public broadcasts, not that it totally excuses it but come on).

Second, Google's entire point of existence is to give an opinion on search results. Full stop. If Google decides that people searching for Clinton want to see positive articles, that's their call. Again, that's their entire product. People are trusting Google's opinion on search results.

And calling Google's response meaningless? Google's saying they're screwed if they deliberately betrayed users. And what they aren't saying is that if they ever were caught really manipulating results, they would be hit with so much regulation that Bing would have a chance.
>> Love marraiges are a more natural, a more realistic option over the arranged marriages setup

> Just for fun, it's worth pointing out that marriage itself is a human-created institution and not exactly "natural".

I would take it one step further and suggest that love itself is human-created.

I take "natural" to generally mean instinctual (raw emotional reaction), and as such any immediate (as opposed to a prolonged social feeling) reaction of sexual desire (lust) or pair-bonding instinct (nurture) can be categorized as "natural" - as opposed to socially sanctioned feeling-stories like love or institutions like marriage.
Dear Dad, send money. Dad: 404
It takes quite some big brass b^H^H^H^H^H^H^H PR skills to downplay Lexra disaster that (together with market crash and other events around year 2000) costed MIPS itself quite dearly in both money directly and more importantly in market position. Need I remind you that was right around the time of ARM's spectacular rise: Quite literally MIPS Technologies being too busy with this litigation is the only good explanation why it was blind to the real threat: ARM7TDMI taking embedded/telecom market by storm. Only burgeoning xDSL market (and good availability of established binary-only MIPS codebase for it) that saved MIPS in early 2000s.

Not to mention quite egregious fact-twisting I see in your reply on two counts: First, that wasn't really a "patent infringement" - first lawsuit was about trademark infringement - which Lexra arguably was guilty of, but quickly backpedaled, at which point case felt apart. Then MIPS, unhappy with that outcome, launched second, even bigger lawsuit that was technically about patent infringement, but Lexra never actually used the patent in question, and specifically marketed their design as free from lwl/r and swl/r instructions, making the whole thing a theater of absurd going on for years where plaintiff was alleging that Lexra was was yes, not implenting those instructions, but somehow facilitating their clients' emulating those. Hardly that can be called "ended up in court". Whopsie-daisy... "ended up", right...

Providing official Verilog code for an older MIPS core is certainly a massive feat and deserve an applause, but then again there are plenty of other HDL implementations of CPU cores around, MIPS ISA cores included [0]. And patent law have a safe haven for academia [1], so "completely open and free for university use" is just hot air, sorry. Still, it's "official", so there's value in that, of course.

[0] http://opencores.org/project,ion
[1] https://en.wikipedia.org/wiki/Research_exemption
That's exactly the idea behind packet bricks (see other comment): you have one single tool that takes all the packets directly from the NIC (say eth0) and then exposes them according to your bricks configuration to a bunch of other interfaces (eth0}0, etho0}1, etc.). Very similar to Click. This layer of indirection obviates the need for shared NIC access, which is what CloudFlare works around in a more cumbersome way.
Those are real-world speed bumps that make sense when you want to do stateful processing w/ large working sets, but not really for this "just get packets through the stack" toy benchmark that fits in cache and the workload is parallel-friendly.

And also the article is talking about handling just 10G, not 100G!
For one thing, you can never be sure if they really detected a liar or they are just lying about it. ;-)
I wouldn't attack this with memory. I'd probably just replace the sshmux binary.
I agree. But startups shouldn't be expected to do this. Startups are experiments; you want to quickly determine if there's a market for the product (and fail fast if not, so you can alter the product or move onto something new). Being conservative with design is the perfect approach for this. If you experiment with unproven layouts, and it fails, how do you know if the problem was the product or your layout?

Interactive new stories, artists' portfolios, design agency websites, web apps, and websites that are themselves art - these are all good places to push boundaries in design. Not startup product promo pages.
For C#, the book I always find myself going back to is C# In Depth by Jon Skeet. It's one of the most accessible books I've read, and it's one I always recommend to other devs that are interested in the language.

http://csharpindepth.com/
Please check out wattvision.com and let me know what you think, we share in your vision. Key features are that we work with existing utility meters and smart meters, and are consumer installed (no electrician required), and update our live data every 10 sec or so.
FWIW I find the Whistle to be a good product. I can easily find out when our dog walker dropped our dog off, and therefore how long she has been alone. At the risk of stating the obvious: just because the author doesn't have the problems that these devices purport to solve doesn't make them superfluous.
"The only disappointment I have in this otherwise lovely board is that it uses 56 ohm resistors to limit current though the LEDs…"

I know the author is geeking out, but his only disappointment should be wasting energy with less efficient wireless charging in a world where power is still created by burning hydrocarbons.
As a kid, every time I tried to hoodwink my father into bogus school supplies expenses he would recite this joke about a medieval student sending a letter to his uneducated father.
After some platitudes similar to the ones in the article, the punchline was more or less like this (loses a bit in translation):
"Three books I have to buy: Marcus, Tullius and Cicero. At three royals each, nine royals I need".

The response was:
"Marcus Tullius Cicero is one book. Here I send five royals, so you can send back two".
Community-centric Job Hunt
Cross-platform code builder and the missing library manager
How to Stress Test CPU and Memory (VM) on a Linux and Unix with Stress-Ng
True. I meant I am willing to host the site itself with free bandwidth, if interested.
The suicide rate in the US is 2.5x higher than in Vietnam. Clearly people are a lot more fucked up mentally in the US than in Vietnam.

Also, anecdotally, I was much less depressed in Vietnam than in Canada/US. You don't realize how oppressive day-to-day life is here until you've lived there. Everything in the west requires 'insurance' and 'licenses' and 'regulation' and there's always someone telling you what to do and how to do it.
Don't forget the nefarious possibility of a rogue AI governing us all from the shadows! Or how those pesky Googlers deleted the election data from the Internet but NOT before our hero and his colleagues got it safe! Surely we must sign another huge grant for this man to save the planet.
Iptables sits in the kernel and is also not available on non-Linux platforms like FreeBSD. With packet bricks you bypass the kernel and expose "virtual" interfaces to your applications by means of a simple configuration. Here's an example from the README:

bricks> lb = Brick.new("LoadBalancer", 2)
bricks> lb:connect_input("eth3")
bricks> lb:connect_output("eth3{0", "eth3{1", "eth3{2", "eth3{3", "eth2")
bricks> pe:link(lb)

This binds pkteng pe with LoadBalancer brick and asks the system to read ingress packets from eth3 and split them flow-wise based on the 2-tuple (src & dst IP addresses) metadata of the packet header. The "lb:connect_output(...)" command creates four netmap-specific pipes named "netmap:eth3{x" where 0 <= x < 4 and an egress interface named "eth2". The traffic is evenly split between all five channels based on the 2 tuple header as previously mentioned. Userland applications can now use packet-bricks to get their fair share of ingress traffic. The brick is finally linked with the packet engine.
For some domains like .io, it's possible and convenient to buy domains from the TLD registrar directly [1]. No need to involve a reseller in the middle.

Otherwise I like EuroDNS [2]. They have decent service and a pretty good web UI overall, compared to some of the other companies.

[1] https://www.nic.io

[2] https://www.eurodns.com
Programming Scala 2nd edition and Functional Programming in Scala.
I'm cynica that will be the case. On the Internet TV front we have roku, apple tv, chrome cast, kindle fire TV-- all of them empty plastic boxes doing nearly the same exact thing, and yet there is no interop to speak of. It's just more walled gardens
even without the tolls & limits and what have you... I went on a roadtrip through the Southwest ( miles of open road and few limits, ripe for enjoying the drive ) and still the whole time I was bored & rather be on Facebook or reading a book
>Like you, I once had many products that each fulfilled a separate function: a landline, a cellphone, a camera, a video recorder, a stereo, a calendar. Now, I have one product that does all of those things — a smartphone. This level of product integration was a revolution in product design.

Is the smartphone really a revolution in product design or just the inevitability of technological convergence? There is essentially no fundamental difference between products listed. Sure, the user function may differ, but the actual implementations are all based on the same phenomena: stored information manipulable through electromagnetic fields.

How early on was a device like the modern smartphone conceived? I'd wager not long after the discovery of silicon transistors.
In hospitals you have sick or very sick people and people with open injuries. You can't take hospitals as the common scenario.
Interesting that so many recommend Gandi, I wonder if there is some timezone-bias in play.

Anyways, you probably should consider actually reading the ToS for the companies you are planning to do business with. I think at least Gandi has fairly vague terms on which they can terminate the service: https://news.ycombinator.com/item?id=3388928
I don't think so. His face was fixated on his cell phone while he idled backwards for a bit. Then he finally looked out the back window and finished backing up, then pulled forward.
I suspect I'm not alone is thinking, that it's not a problem specific to OSS. The codebase at work,,, for 25% of it, basically if it worked the first time, zombie.
>Second, Google's entire point of existence is to give an opinion on search results.

Nope, their point of existence is to sell ads. Showing good results is how they create value, and you are just stretching the meaning of "opinion".

>they would be hit with so much regulation that Bing would have a chance.

This is just naïve. Google is one of the biggest companies in the world and consequently their lobbying power is huge. Besides, I don't even know how they could regulate it. Their algorithm will always be a trade secret and there is no regulation that could ever force them to publish it.
Every database supports client side sharding.
I'm assuming the downvotes are for the brevity of your answer.

I've been using NFS for years on low traffic sites and have not had any issues. For the unfamiliar, it's pay as you go for bandwidth and storage, with discounts as you start using more of each.

The interface is ancient, and they pass CC costs on to you, but for the price, I've yet to find something better.
Agreed, the static was back in the good old CRT days:

https://www.google.com/search?q=tv+static&tbm=isch
this is exactly how openonload works, it's pretty impressive that they get nearly all weird behaviour of the Linux socket API correct (correct behaviour across fork, select/poll/epoll, multicast behaviour, etc).

presentation: http://www.openonload.org/openonload-google-talk.pdf
Old school FUD! I haven't read anything like this in awhile.

they greatly underestimate the complexity of preference algorithms. Facebook is said to have more than 100,000 variables in their news feed algo; I can't imagine what's under the hood at Facebook. In a system that complex, making gross decisions trying to compromise one particular set of results without compromising everything else is not just idiotic, it's impossible.

Also, I enjoyed the yellow journalism gems in there, such as phrasing like "Google refuses to apologize for" etc.

BUT just because the idea is stupid and unworkable, does not mean we should discount the article. It will resonate with a lot of non-engineers, and it will be repeated. So I would advocate for some kind of "common carrier" laws for enormous information brokers like Google, Facebook, and Twitter. Never mind that actually manipulating the results would be prohibitively difficult and dangerous to the health of the company, and proving manipulation would be effectively impossible. If such a legal framework makes people who don't understand complex engineering sleep better, I support it.
New design, better mobile support, admin search and more
Until a few years ago, I owned a LJ4000, and it still had to stop and think for a bit if you were printing a picture or something complicated. Earlier laser printers could be incredibly slow - an Apple LaserWriter took about 30 minutes to print one page of a 'zine' we were were working on.
5+Ways+To+Split+Expenses+Without+Splitting+Up
This shouldn't have any unintended consequences, right guys?
Make a Cloud Data Logger with the Particle Photon
Darnit, acquired by Apple and shutdown!? I didn't even know! Thanks for the link. His critique is actually the first I've seen on their tech. He speculates quite a bit despite them giving plenty of detail and claiming to use many of same choices as Google's F1. If they failed, I'd love to know in detail how to improve on their successes. Some of his gripes have obvious work-arounds with others probably having work-arounds.

That said, I think props still go to Google's teams on GFS, Spanner, and F1 as the best techs out there. A F1 variant, which two teams are trying, is best approach given it's proven and with much published detail.
The essay puts them into the same group - "established commercial entity .. startup that pivots ... or if you as an individual trying to increase your chances to land your dream job through creating an interesting OSS portfolio".

There are also people like me, the owner and sole employee of a commercial organization, and employees of a company which allows 10% time to, among other thing, work on free software or whatever else interests them.

It says "next time you embark on creating an OSS project, consider the following steps to avoid a zombie".

Let me tell you my story. In 2003 I wrote PyRSS2Gen, a Python-based RSS2 generator. It took 2-3 days. I wrote documentation and put it on my web site. It's now used in a lot of packages.

I get a support question about once or twice a year. At this point the code might as well have been written by a stranger as I don't recall the details of how it works. I don't want to put more work into it. Which means it's a "zombie" according to this essay.

Or it's a dead weight keeping me from doing other things.

The essay implies that there's an obligation that I and any other distributor of free code must maintain things in perpetuity. Like unimpressive, I do not like the implicit sense of entitlement.

I have also written plenty of other software which are dead ends, but it took experience under deployment to figure out why it was dead end. Am I supposed to somehow withdraw the software from the public eye once I no longer think it's useful?

There's still other software which I developed for a client as free software, which I made available, but which I won't develop further unless I get funded for it. I haven't touched some of those packages for 5+ years. Do I work on it for free, and not do the the consulting work that pays my bills?
[meme]You can't simply use a second machine/instance.

While it's true that most companies will be fine in 256GB ram, we were talking about sharding, which it doesn't have.
Any pointers on how to flip this around and purposely use body language to consciously reinforce what I'm trying to say rather than accidentally undermine it?