skysight-inc/HackerNews huggingface dataset:
> With VR, you can effectively simulate an infinitely large screen infinitely far away.

In theory.

But the "further" away you project the virtual movie screen, the higher the resolution of the VR headset needs to be to support it. And considering that VR screens are already an inch from your face (and thus require a high-ish resolution to just basically "work") we're talking about better-than-exist resolution screens for that form-factor.

I don't legitimately consider IMAX's business threatened by VR headsets in the next ten or so years, and even then we'll have to see how well people like wearing a VR headset on their face (which might hurt necks, feel uncomfortable, suck for glasses wearers, etc).

VR is better now than at any point in history. But people are pretending like it will definitely succeed. But Google already cancelled Google Glass (and, no, Google Cardboard isn't the same thing). This might be another "3D" flop all over again.
Facebook profiles that are private are in the deep web.

Facebook profiles that can only be found by using Tor (which I don't believe exist) would be in the dark web.
Hanging paintings with nails is typically considered part of legally defined normal wear-and-tear. If your landlord is getting angry at you using the place you're renting in a reasonable manner, than perhaps you're renting from the wrong people.
Close-up on the 'most ambitious video game'
Eh, sorry. I do basically agree with you.
Canadians: Should You Cancel Your 3-Year Wireless Contract?
As long as you don't step out of line:

http://www.bbc.com/news/world-europe-26265230
> I think the majority of people on our team don't like rebasing because it makes spelunking harder in some cases.

Would you elaborate on that please? I don't know what your situation is like that would cause rebasing to make spelunking harder.

> reverting a merge is possible but harder

Funny, someone else further down claimed reverting merges is easier. :)
Серьезно? Нет. Владимир Владимирович хочет, чтобы вы поверили в это. Не верю.
Even in this case, isn’t there a reasonably good chance the person could have sold it for 10% more than ($X+$Y+$Z)[1] at the time of the crisis? The lender and the loaner will part with the equity based on the mortgage payments over the years.

Based on cursory look into Redfin data, homes in the Bay Area are vanishing in 5-12 days, selling at 100-300K above the listed price.

[1] I hope we don’t cite recession here.
The Twitter revolution: project lightning
In the above example, say Feature A gets the go-ahead from the business user/product owner/whatever, and Feature B doesn't. From the dev standpoint both are complete but there may be some business reason to hold up Feature B. The owner(s) of Feature A are likely not going to understand why anything to do with Feature B has to hold up their release.
I would also like to point out that for a lot of "web projects", the entry and deployment barrier is relatively low, one can mostly try those out on a browser. I think this is another important reason for more popularity of web based projects.
> its much easier to revert a feature if you have a merge commit for it

I like this theory, and generally like merge commits because of it -- but in practice, I've found it still _really really hard_ to revert a feature even if I have a merge commit. Simply reverting the SHA of the merge commit does not, I think, do it, git complains/warns about that. I have to admit I still havent' figured out how to do it reliably even with a merge commit!
The same way you're not free being game in a religiously conservative population that did not undergo sexual revolution of the 60s. Gay people are not hunted and jailed like someone might want you believe. In regards to gay freedoms, Russia is where US was in the 80s, things are changing.
Forget Google and unicorns, Asian dragons are going to dominate robotics
Because when you run into OOP that doesn't use the sugar, you'll have trouble if you'd only learned "class", rather than what it's syntactic sugar for.
Some people don't buy to, in their words, avoid being exposed to the property market or some variation thereof. This a fallacy. As long as you need somewhere to live you are exposed to the property market.

A good way of looking at this is: not owning is equivalent to having a large short position in the property market. If prices go down, you "win" by not losing money and/or your rent going down. If prices go up, you "lose" because your rent goes up and what you can buy now is less than what you could've before.

That's a fine position to take but my point is that it IS a position.

You don't necessarily need to own where you live but you should own _something_. It could be in the area you plan to retire to (to hedge against rising prices), an investment property to generate income or whatever.

IMHO REITs aren't the answer here. Residential and commercial real estate are different beasts. Commercial real estate is generally a means of generating income. Residential is far more speculative.

Some people compare long term returns on property vs equities. These compare reasonably favourably.

In all those cases borrowing to buy property is far more favourable. In the US at least you can get 30 year fixed mortgages that are currently hovering about 4% for 80%+ of the purchase price. You just can't get those terms on anything else.

Even on day 1 your mortgage payment is ~30% principal at these interest rates.

Property tends to be a great hedge against inflation too and higher interest rates and higher inflation seems to be a risk with the amount of quantitative easing occurring in the developed world.

Lastly, the ability to essentially fix your housing costs is (IMHO) huge, particularly in major urban centers.
joegrammer sounds awesome!
That is the "warranty" section of the license. Most software contracts as a standard have the warranty section in all caps. Source - I sell a database and deal with software contracts on a weekly basis.
The author's point was that memorization is how you pass these silly interviews.

There's a wonderful paragraph in Skienna's algorithm book, where he states that if you can reduce your problem to a graph problem you should do so, and that you should never invent your own graph algorithm - the standard ones will solve whatever problem you have. Perhaps a bit overstated, but by and large true. There is definitely value in having all of that information at hand so you can fairly quickly perform the mental gymnastics to find a good solution.

I think most people complaining about interviews would agree with that. The thing is that so many people don't work in areas where they need at at the front of their brains, but they do work in areas where similar levels of ability are needed. Product design, finding difficult bugs, working with customers, leading teams, and so on. Bad interviews test memorization.

I'm doing almost all linear algebra these days. I can talk to you about matrix computations, round off errors of various implementations, and so on. You probably can't. But only because you are not doing it, and I am. I TA'ed a graduate level Algorithms class. At the time I could do whatever graph algorithm you wanted, now I can't because it is not what I work on now and most of the details have fled my brain. Doesn't mean I can't do it, just like you not being able to implement a Cholesky decomposition on a whiteboard means that you couldn't do linear algebra programming if it became your job.
I know you're just making a joke, but obviously Russia is not free from vendor lock-in any more than any country.

Even ignoring the context, Russia is more free than US in anarchical sense, as you can do more things without repercussions there than in US. US jails population vastly outnumbers Russias, and you don't need a fishing license in Russia :)
I think the quotee (not the article author, mind you) was, albeit indirectly, comparing the VR product to IMAX.
Edit: There's a well-written solution for that here: https://news.ycombinator.com/item?id=9745367
You're very welcome.

When you accept a merge request the title, description and a link to the merge request are stored as the commit message. For example see https://gitlab.com/gitlab-org/gitlab-ce/commit/6c0db42951d65... This allows you to see any other things that were discussed. Hopefully any line comments were resolved with a commit (thus documenting them) or were based on a misunderstanding.

Thanks for the pricing tip, we'll fix it https://gitlab.com/gitlab-com/www-gitlab-com/issues/348
>> in practice they tend to spent the extra money. Once they reach retirement, they have fewer assets.

They presumably spend the money on things they want. Forced savings means forced forgone consumption.

Every marginal dollar into savings isn't always a net positive. It depends on a lot of different factors including: life expectancy, whether or not you have dependents, how much you already have saved, your income, your alternatives, and not least of all your intertemporal discount rate.

There seems to be some sort of savings fundamentalism backlash against a culturally low savings rate. In a sound bite situation there may be no choice but to pick a simple message and go with it, but in a longer form discussion there's room for more nuance.
The convention is to make sure that the stable branch is the left parent, and the feature branch is the right, and that the merge commit log messages are decent (Gitb web UIs do this fairly decently by default). Now you can get a log of left-parent merge commits to see the log of features that shipped (or releases that shipped if you have multiple tiers of stability).
I have often wondered if the adaptive nature of the brain is what's confusing things. In other words, if someone is suffering the systems of major depression or bipolar disorder, and you "shock" that system with a change in brain chemistry, you're going to get change, and that often the change is enough to snap people out of whatever depressive/manic rut they're in. Problem is, that's not a cure.
Sure, but 100% of web developers need web stuff, whereas not all of them use a database, not all of them use linux, and so on.
The counter argument though is when your feature branch doesn't only have _one_ creator/maintainer. Mine often don't, especially on open source projects, two or three people can be working collaboratively, or others that aren't the lead on the feature can come in to make a helpful commit here or there.

And when one person rebases the feature branch it wreaks havoc for collaborators on the feature branch.

Which is why I limit my "rebasing is okay" on a feature branch to only _right before_ it's merged into master and then deleted. It still doesn't get rid of all the problems, but it gets rid of most of them.
Curious here: has anyone tried using GitLab + forks to replace development branches? Would it needlessly overcomplicated?
> and the size was gratuitous with most of it wasted to peripheral vision

From what I understand, movies shot specifically for IMAX are meant to be framed something like a stage play, with your eyes wandering around the screen rather than staying fixed near the center.

Of course, that presumes the movie was made for it (or had a cut framed specifically for it), rather than just being "normal theatrical cut but bigger".
Sure, but that doesn't provide any more information than any other server log.
Why will rents go up, when they could have gone up already?
An Interview with Neal Stephenson
What would be an example where master differs from production?
EeGeo 3D maps updates North American Coverage
There are locations, and I live on one of them, where finding an accomodation, even with stable long term 150k USD/year single pet-less guy is a few month effort of chasing 100s of appartments, until one will work out. You are nto in position to actually pick anything.

On this thread it's visible that people try to promote their own decisions in this topic (and we all have been into it deep down). Let me put mine - I took loan 8 years ago, in a different country, on a small appartment that when looking back, wasn't the best idea (but neither really bad). Mind you, it was in 2007 :) Surprisingly the price didn't drop below the one I paid, but the pressure to bring every month enough cash to make it through was... not nice. THe perspective to have similar setup for next 20 years was a bit sould-crushing though (it was 50m appartment, so nothing to raise your family in).

But, this pressure forced me off my lazy but, I temporarily moved to another country to earn more and pay it off asap, realized that this country is SO much better than previous one (which wasn't my home anyway), so I decided to stay. 5 years forward, probably the best decision of my life (and there were heaps of people saying I should settle where I am instead of move).
That's super easy to get around. It only replaces the first occurrence of each.
JavaScript and Ruby on Rails: 7  Resources
Of course, the real reason is to extract more revenue, reduce piracy, etc. At the very least Adobe offers the option to download an older version from CC.

But SaaS is a bleak future where we are completely at the mercy of such companies.
> Sorry about not catching this before the release. We have a fix and are trying to get this out as soon as we can. Hopefully in the next 4-6 weeks.

When I read that quote I thought for a second you might be parodying them, but that is actually what they said...

4-6 weeks is bonkers. It isn't like they're spending that time doing QA, as is self-evident by this issue.
Going from lock-free to wait-free
>No, it's almost impossible without being a jerk. This personality trait is a requirement for succeeding.

Every successful person is a jerk?

>Customers also become your worst enemy. They are forced by the market to buy cheap instead of good.

Price is not the only metric by which people buy a product. There are a large amount of variables which play into a purchasing decision. Also, no one is forced. You choose what to purchase.

>So when your entire success is built on a tower of cards,

Another large and untrue generalisation.

>We could have had megabit internet 30 years ago. But instead we got AOL and Comcast.

Please explain this further.
If it is pushed other people can cherry-pick, CI generates results and other people might push commits on the same branch (when using the same repo). We think pushing indicates you want to work in public. We even made a Work In Progress (WIP) function for it in GitLab http://doc.gitlab.com/ce/workflow/wip_merge_requests.html
What does the origin of the company have to do with this?
But who is calling just any theater "IMAX"? If I say to my wife, "hey let's go to the IMAX", she's going to ask me why we would pay that much when we can just go to the theater instead. If there's any dilution of the IMAX brand going on, it's by IMAX themselves by constantly lowering their standards.

Something else you have to consider is intent. It doesn't seem that Ars intended to dilute IMAX's brand by publishing a quote, and it doesn't seem to be the intent of the person quoted either. It was simply a frame of reference.

> IMAX doesn't want people calling any large format theater IMAX

Here's the thing: Nobody did that in the Ars article. A piece of VR tech was casually compared to the IMAX experience by someone being interviewed by Ars.
Snowden's status in Russia is more that of a pet, or a trophy -- up for trade at any moment, for a high enough price -- than that of a political refugee.

And he knows it, which is why he's trying to GTHO of there (even at the price of a reasonably short prison sentence in the U.S.).
the film industry standards are just weird.. Why are there a zillion privately owned standards? IMAX, THX, DTS (HD, X etc), Dolby (Cinema, Digital Cinema, Atmos etc)
Do you have a citation for any of those claims?
Yeah because apple has never created new business opportunities for anyone else - all they do is cause people to lose their livelyhoods. /s
If you have a handful of people, you simply communicate with them, check that there's a good reason to rebase and that you're not creating unnecessary burden and do it when everyone is happy.

When you have more than a handful of people, then your feature branch is not a feature branch, but a project, which should have feature branches of its own.

Scale, dynamic adaption to it and situational awareness are a requirement in team work. :)
For example, a piece titled "'Considered Harmful' Essays Considered Harmful" would very likely be a case of using the "considered harmful" format to draw attention for its own sake. We will ignore such essays in this commentary.

Now I'm just confused.
Three data points(whether they're true or not) is not any indicator of the necessity to be a 'jerk'.
Likewise. It was more like if I wanted to watch the whole movie, I had to pan my head constantly through an arc.

It's a horrible experience. You can buy a horribly cheap TV, a 5.1 sound system and plop it in your living room and get a better experience. Getting the sound right takes a long time, but my end conclusion was that suspending bunch of cardboard everywhere seemed to negate the poor acoustics of the room.
I have had this ideological debate about "fast forwarding" more times that I can count. I agree with the author "no-ff" is silly. I've been working on professional software teams for over a decade. When I encountered fast forwarding/rebasing it was absolutely a breath of fresh air. I've been using git now for 5 years and I have not encountered a single instance where using either of these tools has presented any sort of problem. I can't remember a week where having a concise, readable history hasn't proven its value. I also can't remember a single time I've said "Man I'm glad I had all these merge commits around they really saved my proverbial bacon"

From what I can tell no-ff exists to satisfy the aesthetic preference of your local team pedant. It gives them something to do between harping on whether your behavior is in the correct "domain", deciding if a list comprehensions are truly "pythonic", and spending that extra month perfecting the event sourcing engine to revolutionize the "contact us" section of your site.
That's the name I knew them by (mostly from watching Altered States), but apparently they're now called isolation tanks: https://en.wikipedia.org/wiki/Isolation_tank
It seems like it wasn't all that long ago that people were up in arms about companies considering everything an employee said on their own time to potentially represent the company. This is why companies did that, because interlopers come along and threaten you bad publicity if you don't do something about the person with the wrongthink.

There was never a general reciprocity principle at play with these people, it was always about who has power over whom. if they have power, they punish people they dislike. If they don't have power, they appeal to fairness until they can get into a position of power. Don't give them power by acceding to threats.
http://www.theguardian.com/commentisfree/2015/jun/17/napoleo...
You'r belief on the likelihood probability is not factual, it's based on claims of a side in geopolitical confrontation, the one you choose to believe, because that's where you live.

It is certainly true that standard of living is lower in Russia, but is better than many other countries you consider "free".
Why would someone do that? To what end?
Why isn't anyone re-writing Redis in assembler to have it kick ass like pros?
Can you write Windows in rust?
Taking "mental health days" once in a while can really help
Adobe just made snap.svg[1] last year. If they have a long-term plan to kill and supplant the format like you describe, then I guess somebody missed a memo.

[1] http://snapsvg.io/
To add to that, Redis is a TCP server so you can speak to it from multiple processes on multiple machines (and Redis will easily support huge loads)

Its data structure cover a good part of what you'd need with generic data structures, which makes Redis an easy way to do the logic of, say, List intersection of friends common between multiple people, sorted set of goods ranked by their amount, all of this shared with other processes.

Redis also offers pubsub capabilities in two forms:

- A standard PUB/SUB couple which does what you think it does

- Blocking pop on a list for a client, and a push for another client, which will "wake up" the first one with the value.

It's a very versatile swiss knife.
Zapya Download for Windows PC and Laptop
There are a whole lot of other factors that increase friction more than owning your domicile, and those factors tend to be stronger with people who are motivated to buy:

- Deep networks of friends
- Strong community ties
- Strong local family ties
- Children with their attendant social networks
- General aversion to moving frequently

Also, the idea that "most" homeowners never leave is antiquated. Nearly everyone I know who has bought a property has bought more than one before 40.
Thanks a lot :) Mostly confirms what I was thinking.
Reversals based on further evidence are part of science, inherently. Science shouldn't have a magical reputation, because it's not magic. Like all other means of explaining there material world, it's guesswork. There only difference is that science is guesswork with systematic effort to find holes in the guesses and improve them and reject there ones that don't work, while every other approach to explaining material phenomena had some form of guesswork and some method of closing which guesses to accept that is not based on what demonstrably works or fails.
> but the heritability (in the technical sense) of being a slave in the mid 1800's USA was rather high.

No, it wouldn't be. Monozygotic black twins would have the exact same chance as dizygotic black twins of being slaves, and slavery would cluster in families, with whole families tending to be free or slave, leading to very high shared/nonshared environment estimates.
I was surprised that they do allow for downloading previous versions. Counts for something. But it actually hurts their argument for their new pricing model, because they really stressed how they can't keep supporting old versions while innovating.
I received an alert in my browser while using this site - should I be worried?