skysight-inc/HackerNews huggingface dataset:
This answers the protocol question, but nothing about the actual data safety. Seems kinda fishy.
I've done A LOT of research and experimentation in this space over the course of the last 5-ish years, mainly out of sheer curiosity. This sounds very, very similar to something I prototyped a while back using x264 + Broadway.js (HTML5 video streaming with low latency is a non-starter).

I'm extremely curious, has Paperspace actually developed an entirely new video codec, encoder, and efficient JS decoder for this?

I'm a little confused by the statements so far (and the comments are flowing in, so apologies if this was addressed while I was typing): "we are using a video stream", "using a JS renderer", "building a streaming protocol", "using GPU tech originally developed for video game streaming", "a remote desktop protocol that could stream HD video"

So, is just the streaming protocol you've developed and not the codec? In my expiriments, simply pushing out h264 NAL units over websockets and passing them to the decoder was a pretty solid start. Add a tiny layer of buffering over that and I imagine it'd be fairly stable. Ultimately, I backed away from h264 for licensing and performance issues.

Also, what's the transport into the browser? Websockets? WebRTC data channels? Have you encountered performance issues with Firefox not being able to handle websockets or data channels in web workers? (Which is seemingly coming in FF37.)
"dplyr is the next iteration of plyr, focussed on tools for working with data frames (hence the d in the name)."
I think the DVCS issues he mentioned are solved entirely. Just use the simple git-flow branching scheme.

master = Code that is production ready.

develop = Code for staging

feature/XXX = Feature branches.

Where is there room for confusion? It's dead simple and makes working with teams so easy and effortless. I would never join a team that uses something like Subversion or Perforce in these times.

Git sucks for large blob files - no doubt. For those I recommend using Veracity.
I disagree - I've done bisects on very large codebases, and they take a while (5-10 seconds for a checkout, perhaps). This is all immaterial compared to the time to recompile the code (possibly a minute or two to get everything recompiled (a Java project)).
Turning the database inside out
And a hip name, like Dove or Ivry.
Because everyone wants her to be the next president.
Regarding your edit, I think you are misinterpreting the author. The point of the article is that Indian food tends to pair flavors which are not alike, unlike Western food, which tends to pair flavors which are alike. However, in Indian food with milk, butter, bread and rice, they tend to be pairing flavors that are alike - similar to what Western food does in general, and the author pointed out that those are staples in Western food.
FWIW I already do this. It's not running a window manager, rather a command line, but it does what I need it to.
Networking is key! Surround yourself with people that share your interests to help network.
Sorry about that. When I first built this (many moons ago) it was unreasonably difficult to get it working in Safari. Sounds like it's time to revisit that issue.
Making $3000 in a quarter is a pipe dream?

Why do you say that? The indie game market is not all that crowded, if we're thinking about games like Dear Esther, Gone Home, The Stanley Parable, Sword and Sworcery (all of which did way better than $3000 a quarter). Gamasutra, the other day, was lamenting the fact that there aren't enough games in this space.

Assuming we're not talking about the very difficult mobile market (but just about high quality indies on the PC), why is it absurd to think that a small indie studio could be quite successful (even with a first game)?
I'm assuming you don't believe in evolution, then?

Because if you do, if you accept the reality of evolution, genetics, the slow accretion of complexity through purely random changes, some of which are positive, etc., then EITHER you implicitly accept reductionism OR you must explicitly state how it is we are not just chemistry.

We are piles of complex chemistry, and not much more. In fact, nothing more, according to our best reproducible, documentable, shareable, practical, implementable knowledge. (As opposed to slippery mystical knowledge which is hard to reproduce, document, share, do anything practical with, etc.)
>> Because they're intermediary steps of a process, regenerating them takes an hour and I don't feel like setting up everybody's environment to build them. Most people don't need the capability, but they need the result.

Put your build tools in a repo. It should be easy to set up a new developer with a complete build system by getting it from the a repo. Now use make or anything that can check dependencies so those things are not regenerated unless they need to be. Always check in a freshly generated file along with its source.
Well, actually you can, but only as part of Bulletproof SSL and TLS. OpenSSL Cookbook is Bulletproof chapters 11 and 12, plus SSL/TLS Deployment Best Practices (another guide I wrote) in the appendix.

Or, you can simply print it yourself. At 94 pages, it's easily doable.
I quit my job because we were stuck using Perforce - how's that? :P
Nobody is saying to intentionally put things wrong into the software in order to get your attention on the wrong things. They are saying that there are people who will ask for changes when there isn't value to them, but only because it allows them to make a difference.

I've seen cases where people have completely ruined products in ways like this. I don't think that anybody is actually saying that "broken" / "poor" features should be added just to be removed... Possibly unless you have been working with one of the people who require you to change things without unreasonably.
Nobody is saying to intentionally put things wrong into the software in order to get your attention on the wrong things. They are saying that there are people who will ask for changes when there isn't value to them, but only because it allows them to make a difference.

I've seen cases where people have completely ruined products in ways like this. I don't think that anybody is actually saying that I should add broken features.
Which is fine, but the very obvious and up-front trade-off of using servers that aren't yours is that they aren't yours, and everything that implies. There are plenty of benefits as well, but that's why it's a trade-off.
Tribler: Privacy using our Tor-inspired onion routing
Nice catch. I'll fix that. Thanks for posting about it here.
And what's exactly wrong with that???

All that means that it's crystal clear to Upper-Management that air traffic control is Hard!, and it must be properly resourced. It makes me feel safer (even if probably more risky due to human error).

The minute automation comes in, an army of Crazy! PMs will begin to demand that everything has to be done due Thursday evening, so QA can test over the weekend, and then the Bean-Counters come in and slash every specification of hardware because its not quote-Efficient!-unquote.

Would you really want to fly in a world like that????
How is this different than just renting a VPS?
Athlete Hunt - Product Hunt For Sports and Fitness
> Serious question: Do you think this is a conscious choice made by those in the tech field?

Every time I see people on HN discussing feminism, my answer leans more and more towards, "Yes." Without HN, I would never have realized the sheer depths of the deliberate sexism in tech on top of the unintentional and unconscious bits.

Really, I mostly hope that HN is non-representative.
Taken literally this is pretty bad. Wasting time to placate hands on incompetent managers is not sustainable. This is also why design by committee fails - everyone wants to seem like they have some input.

The reality is this always exists to a degree. Politics exist. It can be hard to come up with an objective definition of best, especially around usability. (A/B testing helps, but only so far) So one has to learn how to do the politics to get things done.
There is also the source code. Being able to take a look under the hood is critically important. (trying to modify is insane, but just knowing that you can see what is going on inside makes integration and bug hunting much faster)
Binary files are by definition unmergeble with a diff3 algorithm implementation that uses text tokens separated by \n. Specific software to merge a binary file format can be used with virtually any version control system if available.

You can set an svn:needs-lock property on binaries.
It is not a local option, it applies to everyone using the repository. For extra convience, use svn:auto-props (acts recursively) to set it by default on new files which match a particular filename pattern (e.g. match on file name extension).
http://subversion.apache.org/docs/release-notes/1.8.html#rep...

EDIT: That said, I agree that some types of binary files really have no place in SVN repositories. One example are release artifacts, as stored e.g. in Maven repositories.
Although you should specialize in something, sometimes its good to keep learning new fields of programming to stay fresh.
I feel like the music built up some tension that never got released.

I can feel it in my head, it's like I'm "in battle" in a video game or something.
The original source linked at the end is more informative: https://www.lhup.edu/~dsimanek/neverwrk.htm
Sir, would you rather sit by this nice, blue light or here in this stuff that feels warm like sunlight?

Sure, you can do that with the blue light, but if that were truly an answer, the blue lights would be standard in fixtures instead of a bit of equpiment for greenhouses, fishkeepers, and those with seasonal affective disorder.

Sunlight simply feels different, in the same ways that a fake fire can feel different from a real one. It is warm and inviting for most people, it heats the skin in ways normal light doesn't.

And as far as texture, I'm not sure if I can explain this properly, though I can see it and draw it in: Sunlight makes the skin's transluscence light up a bit differently: Sometimes it wavers and moves depending on what is in the air and whether or not there is a temperature difference between the inside and outside. Sometimes dust sparkles slightly as it drifts in the air. It creates a different glow than artificial light and the shadows are different - the light is steady and more diffuse because the light comes from a general direction instead of a point.

I do understand that some of this stuff are things that people just don't think they see but they are the things that help make a painting spectacular instead of just good.
Sure, but how convenient it is to just generate the resource once and for all and dump it in the file system following REST semantics, thus making it useless to waste CPU cycles computing the resource contents when it's just there.
What is the longer term target market?

Is this designed to compete with thin client offerings from the big boys when it comes to larger installs?

One big advantage for something like microsoft remote desktop services is ability to throw a beefy server into an existing infra with aging desktops and use them as thin clients/dumb terminals.

I can see an advantage of this as being able to take just that box when i travel, plug it into any random machine, and get an instant resume of my previous desktop session over VPN... but this makes it oh-so-close to Windows To Go?

Most importantly, what is the monthly cost of the actual VPC (not the hardware)? Its not listed anywhere on the site that i could find. What would you do better than Azure, Amazon VPC, rackspace, or multiple others?
Unreal Engine comes with full source updated live on GitHub, that is worth its weight in gold, sadly not even the Pro Unity subscription version comes with that option.
It could model what happens in a smoothie blender (with no heat and assuming no oxydation) but it would not account for the reactions occurring during cooking. Thinks like the Maillard reaction[0], breakdowns of various oils, etc.

[0]http://en.wikipedia.org/wiki/Maillard_reaction
So, like existing products like ThinLinc? Which can stream HD1080 over 8Mbps connection? Doesn’t seem like you actually provide some new product...
Those require a fission trigger and have existed for a long time. The proliferation nightmare would be if we could figure out how to build one that didn't need fission, but I have never heard even a hint of success with that. If there is, it's classified -- and in this case for good reason.
If you're not going to contribute to the discussion, then don't post. Nobody is going to steal your idea.
This problem isn't isolated to non-native English speakers. The potential cost of poorly named methods/variables/classes, etc. is high enough on a complex product that it's almost always worth raising the issue in reviews. If your reviews are run positively it really shouldn't be an issue.

As an aside, I recently saw a job listing that included the requirement to be able to "defend your code in reviews" - I would say that's an environment where reviews probably aren't positive experiences.
That's pretty amazing when you consider that Apple Watch will be about 12.4mm thick with the heart sensor included and high end traditional watches can be anywhere between 11 and 13mm.
> There are countless fables about record company executives dropping by the mastering studio to hear the new hit in its finished form.

There are, but equally, there are tales of real genius among record company bosses too. Here's an awesome example, which I read in soundonsound a few years ago. From an interview with Giorgio Moroder on how he created the disco single "Love To Love You Baby", and the instrumental role of record boss Neil Bogart:

> This then provided us with a four‑minute, metronomic beat that had a kind of groove going on, and that really was the origin of drum machines, and the thing that enabled us to stretch it to a 16‑minute version, kept in perfect time, when Neil Bogart requested it.”

> According to Moroder, it was on a Friday that Bogart called him, at about three o'clock in the morning LA time, ecstatic over the number and insisting that it should be extended to cover the entire side of an album. Bellotte fills in the details...

> "Bogart was having an orgy at his house, there was a lot of coke going on and, to use his own language, they were all 'f*cking to this track' and the crowd there had him replay the song over and over again. Suddenly, a 'Eureka' thought hit Bogart; he recalled 'In‑A‑Gadda‑Da‑Vida' by Iron Butterfly, which had taken up a whole side. In a flash he came up with the idea of doing the same with 'Love To Love You Baby' and he needed it within a week. So we just proceeded to get down to it on that weekend, and since things always went very fast back then, within the week he had what he wanted.”

....

> The last song on the album, recorded in two to three hours and designed to transport listeners into the future, 'I Feel Love' would quickly become a gay anthem, not least because of Neil Bogart's astute marketing, while topping the UK singles chart and climbing to number six on the Billboard Hot 100. However, it was considered to be nothing more than a filler when the record was finished.

>"We never thought of it as a stand-out track, we just thought it part of a good album,” Bellotte comments. "However, when we sent the album off to LA, Neil Bogart called back straight away and said, 'The single is 'I Feel Love', it needs three edits and these are the edits.' Doing these immediately improved the fluidity of the track no end. He was that kind of a record man. And, of course, those edits no longer exist, because they would have been sliced from the quarter‑inch master and simply thrown on the floor. That's how it was then. If you ever did any editing, the floor was cluttered with all the stuff you didn't use. We never saved anything, it was just discarded. However, because of his uncanny feel for the music, Bogart knew exactly where the track should be edited and, of course, the improvement was fantastic.”

Crazy story, isn't it?
Why Are Geospatial Databases So Hard to Build?
Unity’s new approach to Web delivery is made possible by using a combination of IL2CPP and a cross-compiler named Emscripten to port its content. IL2CPP was developed at Unity Technologies and converts all ingame scripts to C++. This approach has performance benefits when porting to multiple platforms, including the Web. Unity then uses Emscripten to convert the resulting C++ to asm.js, a subset of JavaScript that can be optimized to run at near native speeds in the browser.
Heh. Take a look at the EEVblog form for 'dogy crowdfunded projects' for some fun reading (http://www.eevblog.com/forum/crowd-funded-projects/). The experienced people there can often rate a project's "bull$hit factor" just by costing out the BOM and assembly and comparing it to the offer price.

Regarding Bluetooth (LE), I've got a history with ARM stuff so stuck with Nordic's offerings. Cypress & CSI have nice stuff, but they really lock you into their environments, IMHO. I've got a nice full-stack gcc-4.9 based dev/debug flow for the full Nordic stack, and that makes my development way easier (and much, much cheaper since I don't need to hassle with IAR or Keil).

Mind you, I'm also comfortable with writing newlib CRT routines from scratch, so what's "comfortable and cost-effective" for me may not match your dev team's experience.

Anyway, back to BLE and KS. I found that the vast majority of 'small BLE device' Kickstarters seemed to massively underestimate the cost and complexity of both EMC design/certification, and Bluetooth SIG compliance/certification. That stuff is expensive!

As you may or may not know, if you design your own circuitry, you need to qualify your entire radio PHY and do a hardware re-qual. That's on top of FCC/IC/CE/TELEC certifications. It ain't cheap and it ain't a pretty process.

I ended up going with an Insight SiP ISP130301 Bluetooth LE Module because they had awesome antenna characteristics, were mechanically robust, they included the optional timing crystal that I wanted, and were relatively inexpensive (~8 USD in Q1000).

Using one of those, you do NOT have to do B-SIG qualifications (as long as you use the qualified vendor BLE stack), and as long as you use an approved antenna (usually fixed and included on the module) you only have to do FCC (or equivalent) testing that any/all consumer electronics need to go through.

For under Q10k, that's a no-brainer in price and ease-of-integration.
Yes! Perfectly captured.
Killer app? I don't know about killer, but here are some super useful things I can imagine smartwatches doing:...Basically, most of the potential with this device is doing things which phones can already do but in a less intrusive manner.

We shouldn't ever dismiss this avenue for product/business development: Duplicating an existing functionality/service but with greater convenience. One of the charges raised against both the iPhone and iPad, was that they merely duplicated functionality that was already in other devices. However, making that functionality more convenient and mobile turned out to be of incredible value to the market.
The author gives an excellent opening summary of the fundamental architecture of common VCSes over time, and then accurately identifies the most painful points of (eg) git, but then dramatically understates the benefits of a good DVCS.

If you need binary files or otherwise very large repos, or centralized control and auditing, or non-developers to work with it, then git has major drawbacks. However there is so much code in the world—probably the majority—that works incredibly well with the full benefits of having it all in a single git repo.

Having the whole history and the ability to mutilate it at will in a very fine-grained fashion is a power tool. I like it for the same reason I like vim: the learning curve is steep, but the idea is that this is a core tool I can use across programming languages for the duration of a 40, 50, 60 year career. I don't want to conflate something as horrible as svn with a theoretical good centralized VCS, but I have to say that using svn for 5 years I had much less idea how it worked then I did after 1 year of using git. Even though git was a steeper learning curve, the concepts in it are well-defined and the low-level pieces in it have a clarity of purpose which allows some implicit reasoning about the way things work without having to go in and actually read the source. This allows the fluent practitioner to devise flexible approaches to individual problems that a less modular system can not provide.

I see commit messages and history as a fine craft. With git you can commit everything in small units that make sense only during construction as you are still exploring the problem space, then you can rebase it into cohesive changesets with deep documentation and a continuously unbroken build. A centralized VCS user could only achieve the same by withholding intermediate commits; that's okay, but it can become unwieldy for large changes. With git you can use initial commits like a master woodworker uses scrap wood, structuring them one way for building, and then discarding them in favor of finished pieces built to stand the test of time, providing massive forward benefit in terms of documentation/bisectability. Having worked on at least one project with a 7-year history, I can testify that investing in history curation pays huge dividends and can well make the difference between your successors thinking of you as a solid developer or a shotgun-programming hack.
You sure about that? Your system will be full of proprietary firmwares, drivers, etc.
I could believe that the original sound actually does seem different after the 3 or 4 other sounds were priming the brain. Our senses don't operate in isolation. Just think of #thedress, or a note played in isolation vs played after a sequence of notes in a key in which the original note does not appear.
They want to convince you it's easy because they feel deep inside that if they were to explain things to you they'd realize they don't understand those things themselves.

A person who understands something doesn't shout at you that it's easy (nor that it's hard). It just goes and explains it to you.
> Nothing precludes you from using the patch model with DVCS (I mean, Linux kernel development uses Git just fine with this)

Technically, no. But how many projects out there would accept an email patch? They'd probably reject it and tell you to issue a Pull Request instead.

I think his greatest argument is comparing the steps of contributing to github vs contributing to an svn repo.
Because most of them aren't? You're naming the hits, but it's a lot harder to remember the games that failed (or the ones that didn't even make it out of development).
Akamai Addresses CVE 2015-0204 Vulnerability
Does it say what the computer is full with? I would probably be not that interested if it is bees. In contrast, if it is dark chocolate, I would be very interested.
I'd suggest: Starting free trial on the highest plan.

Also, there's no comparison of plans, or how long does the free plan last.

Looks nice, congrats on shipping.
Show HN: Limitd – simple daemon for rate limiting HA applications
Well the NSA does employ more cryptographers than anyone else in the world, so that's kind of logical.