skysight-inc/HackerNews huggingface dataset:
VR and AR, which is borderline related technology-wise, have a lot of real-world use cases and can actually improve the overall quality of life. They are not just toys to experiment and play around, they can lead to serious technological advancements. We live in the information age, if it were me I'd say that the pinnacle of this "information" age would be accessing all kind of information from everywhere. And to do that, you need to actually immerse yourself into it fully.

Imagine visiting your friends or parents or relatives in another continent, without having to move from your chair. No, not like Skype or whatnot, actually BEING there with them. VR can give you that (and in the future, it can give you force feedback and tactile feedback too!). You will be able to visit the Coliseum in Rome without moving from your NYC apartment. You will be able to commute to work in milliseconds without having to get up from your bed. People with moving disabilities (like a wheelchair or whatnot) will be able to walk again and interact with people as they never have done before.

Furthermore, VR can be used to train people in several jobs, like being a pilot, a surgeon, a firefighter or whatnot. Even put people in situations they have never been before. It can be used by psychologists and doctors to treat patients, diagnose mental problems, study and research some conditions of the mind, etc etc.

Last, but not least, AR can provide an additional layer of information on top of our everyday life. Yes, VR gets you stuck in a chair at home and you will never go outside, but when/if you do, there is AR to assist you. You will be able to interact with every terminal around you while walking down the city (or at a park, or whatnot). You will have an overlay of information and knowledge on top of reality that will not only make your life easier, it will AUGMENT it. Nevermind hiring a guide when you want to actually visit a museum, you can just pop on your AR kit and tap into the knowledgebase of every person in the world. Just there, at the tip of your fingers.

Anyhow, let's be real, AR and VR are damn cool anyway.
Failing silently should no be an option. This is a case where the best is enemy of the good. The patch is good, albeit not optimal. Hanging on to a bad solution, in presence of a good solution, because you can imagine an optimal solution was a bad call.

The patch should log a warning/error and avoid the crash. It does not preempt an optimal solution, by traversing the file tree, being developed afterwards.
I don't get the online shopping thing. What does VR contribute here? I'm sure if VR really gets going, retail will be a part of it but going there at the demo stage seems really weird.

BTW, what are the basic applications of VR headsets.

IE, a smartphone's basic jobs are text based communication (SMS, whatsapp, twitter, email etc), calls, camera, web browser, media players, games… There are an unlimited number of the jobs and different people use different things, but… well, online shopping isn't one of the big ones.

What are VR headsets for? Do we have any better understanding of this now than we did ten years ogo?

I'm not sure if this is practical, but my mind goes to 3d movies. IE, there's a movie that you watch by walking around and listening to different conversations and seeing different things.
See my post. You had the same experience as I had with my son. The old machines had less distractions - this is the problem with modern systems.
Unless they manage to lose exactly one move?
Clicked link. Hit Ctrl-F. Typed "clima". Saw this:

"I totally think climate change is involved," Lahner says. "I just don’t have evidence yet."

Closed tab.
I ran into a similar issue with data bindings on table cells. My solution was to keep a track of the cells in a service (later refactored into a directive), and then have the directive update the cells directly when they needed to be updated, rather than each cell listening for if it should be updated. Indeed this is more like jquery and less like angular, but with so many databindings it was necessary.
Ask HN: Should I Report This Security Vulnerability?
I've found a remote file inclusion vulnerability which could possibly affect every website ever written by the company I work for. Should I report this to my manager and if so, how should I approach it? I have a proof of concept that works.
Handbrake could really use some TLC on the GUI. It's so confusing (at least for me) that I was only using it in CLI mode. This ended up being a good thing : I made a script to only convert at night when electricity is cheaper.
How does this follow from you implying a JIT advantage for this use case and me asking exactly what the JIT advantage is? I think you are just arguing to win at this point.
Pushh is a free iPhone app that helps you keep track of your fitness selfies
I disagree. The tools are awful and terribly slow to execute at best. Then you occasionally get shafted with a relabel.
Huh? Black and White are not symmetrical, so it's not a matter of chucking a turn somewhere somehow.
...That makes me think of Sword Art Online.
YES! Thank you! I think I'll die if I have to read another developer arrogantly defining what should and should not be, and how he, in all his glory, hereafter defines this framework to "NOT BE WORTHY".

I can't stand how some articles simply s&*t on years of software architecture principles and the work of very talented engineers and simply dismisses them like it's nothing.

If you disagree with a framework's perspective, AT LEAST be respectful.

BTW, I also have used Angular for 2 years and, given the pros and cons and existing alternatives, I will choose it again for my next big project. The structure is simply too solid. This is invaluable when you have a large team that must work together.
If I was using this system I would say that it isn't up to libnih to fix the problem; inform init and let init do a complete config file(s) reload. This is very similar to the way the kernel handles interrupts; when there aren't many it handles hardware in default interrupt mode (e.g. one interrupt per packet), but when the rate of interrupts gets too high it moves to non blocking synchronous polling (e.g. keep iterating through packets until a buffer fills/reschedule or the input queue empties).
So what ? He didn't say man made climate change, just climate change.

You don't have to be a genius to see the climate is changing.

Now for the root cause, I don't know, but human pollution is certainly not helping.
Interesting. It looks like it doesn't support type information yet, but it's coming in milestone 2. I started an open-source project called srclib that's creating toolchains to type-analyze and dependency-analyze source code in multiple languages: https://srclib.org/. It might be of interest to folks working with or using Nitra.
Library of Congress Digital Gazetteer
The first one was just an early-2000s Google Now. Actually, scrap that idea, it's a beige text iGoogle.

Shepard Fairey's one isn't too bad. I can imagine Google having been like that, even if it never was.
We ended up with a similar solution as well.

Large grids were rendered using jQuery's DOM methods. The data-flow was made explicit, and the view was updated whenever any change was needed.

React embraces the explicitness of data flow instead of watching the objects in the background. This is done using `setState`, which queues up a re-render of the virtual dom.
You missed a really goid article about sea stars wasting from unknown illness. Climate change is mentioned in passing.

Also just because it is related to climate change doesn't mean it is bad...
When my son was about four years old, I gave him an old electric typewriter which I got from Freecycle. I also gave him a stack of paper and some ink ribbon.

Within days, he was "typing" away, loading new paper, working the lever to return the carriage to the start and replacing the ink ribbons. By the end of the month, it was in pieces as he tried to dismantle it to see out how it works. Luckily, I was supervising him so that he does not electrocute himself. The mind of a young child is an amazing thing to watch.
This kind of distorts the issue here. The problem is not lack of highly skilled devs but rather the fact that you need highly skills devs to digest and maintain the level of complexity that Angular produces.

I'm big believer on light frameworks that does least amount of abstractions and can get out of way if you need. You definitely want to avoid frameworks that claims to abstract everything away and especially those that requires to learn entirely new way of doing pretty much everything and its own world of lingua franca. My preference therefore gravitates towards lighweight stuff like KnockoutJS and likes. Any average dev can understand KnockoutJS in just hour or two. More importantly, most devs can immediately have intuitive understanding of how things work under the hood and therefore can anticipate performance issues or easily extend it.
That is right for safety related system. You always need a second path at least, because of single point of failure.

But, being said that, part of safety related development is, to cover any theoretically possible behavior. Because not doing it, leads to systematic failures which will decrease the overall system safety. Knowing this will prevent certification with according authorities, like FDA in medical equipment, LLoyds in ships, TÜV in off-road vehicles.

At the end, knowing that such bugs are just ignored with such blatant arguments fuels the image of bad software quality.
Why Is Bill Cosby’s Career Over, but Terry Richardson’s Isn’t?
Clicked link. Read entire article. Saw this at end:

" ... He hesitates to chalk up the wasting event to climate change. But he does worry all the same. ..."

Closed tab with still open mind.
It's pretty simple really, co2 causes heating, co2 is increasing, increase in co2 is from fossil fuels.
Reminds ne of Google's project Grok.
I am on the same boat.

I chose to use AngularJS in our team a year ago for quite a large web-app. It isn't perfect, but it is leagues ahead of whatever other choices I was and still aware of.

Regarding the brought up problems, they indeed exist. I think the true fault of Angular is that it gives the impression easy and friendly, while it is really, nothing of the sort:

"Come" it says, "Use my nice bindings. You don't need to worry, just bind all your data and will magically appear, no need to read the docs". Gladly you comply and all your data appears there. Magic.

"I see you have a lot of objects", says Angular, "go ahead and use ng-repeat to show them all... They will all manifest by themselves, no need to write anything." So you do that too, and it works.

Then a week later, when faced with real data in production, you have huge delays and the browser freezes for customers. "What have you done, Angular?" you shout angrily. "Now, now", it replies, "I thought you understood what you're doing, perhaps you should, after all, read all the docs, and maybe some blogs and videos about AngularJS performance tips, and of course, it is always suggested to read the source."

P.S I haven't played too much with React yet and I should definitely do so.
Not sure why you're downvoted. That's bad science regardless of how you look at it. The use of the word "climate" in a quote is a big indicator of bad science as it happens to pay the bills and make a good quote in the press before all other concerns at the moment.

If it turns up in a paper at the end and is peer reviewed, then it has some credence but before that, nada.

Feynman is rolling in his grave again...

Edit: if you downvote, explain yourself or you're a coward and a hypocrite.
Unless one is writting device drivers, kernel modules, signal processing algorithms or anything else that needs to fit in 16ms, there is hardly any reason to use C or C++.

Languages like Object Pascal, Modula-2 and Ada that don't use garbage collection and many that do, like Modula-3 provide much more control about value types and GC behavior than what Java and C# are known for.

Finally many of the garbage collection jitter issues are caused by developers clueless about writing GC friendly algorithms or simply how to use a profiler.
Hrm. I think there are some decent xounter arguments. I will agree that pure academic systems research is being superceded by industry development or academic commercialization. As a trend I think commoditization, parallelism, and management are where effort (and sucess) has gone, as opposed to novel research. Make it cheaper, wider, and possible to manage.

Influential counterpoints: distributed systems management/configuration/orchestration, distributed datastores (CAP, CALVIN, Dynamo, etc), system languages (Go, Rust), distributed processing (tilera, niagra, larrabe, gpus), network fabrics instead of trees, &stream processing jnstead of batch (kinesis, millwheel).
Advanced Functional Programming in Industry: Chordify [pdf]
The JIT advantage is the runtime information. Only benchmarks will always run the code in same way. Any useful piece of software runs under different conditions in different invocations and situations.

JIT can remove code from inner loops that is unnecessary for the current invocation. It can also use any instructions available on the CPU it's running on. It can use more registers if the CPU has them.

JIT advantage is higher performance, which is mostly untapped today.

I don't care about winning any points. I just want people to understand it's not black and white. JIT as an acronym causes them to jump to conclusions without even thinking about it.

Statically compiled code is suboptimal for all but the idealized case the code was compiled for. It has to take general case into account. Wasting cycles checking the condition that's always false anyways for current problem. Setting up the inner loop that's executed just once or twice every time.

A JIT can spend a few microseconds optimizing for that and running the code for 10 milliseconds. Instead of running the generic statically compiled case for 20 milliseconds. JIT can produce code more native than the "native" statically compiled presentation.
While true, out of bounds errors, pointer misuse and undefined behaviors are the top exploits of any C code base, removing them would already be a big improvement in security.
So what? That's not science, that's religion. That is 'god of the gaps' stuff. I suppose we can add it to the list (http://www.numberwatch.co.uk/warmlist.htm).
Maybe the story was interesting, maybe it was important, whatever. I'm not reading it on principle if they're going to cross themselves and pray to their green god mid way through. There are a number of people like myself who would actually care about ecology/environmental issues if they weren't crowded out by absolute wank like that.
Did all of the inital commit code is written by Linux Torvalds ?
proc ProcessInputData {data} {
set line [string map {"{" "(" "}" ")"} $data]
set newData ""
foreach char [split $line {}] {
if {[string is ascii $char] && [string is control $char] == 0} {
append newData $char
}
}
set newData [string map {\/ " " \; " . " \* " " \^ " " " = " " " " - " " " \< " " \> " " \{ " " \} " " \( " " \) " " \| " " \` "" \' "" \\ " " \" "" \, " " \? " . " \! " . " \[ " " \] " "} $newData]
return $newData
}

ProcessInputData cool
Downloaded without realising this was a c# project, and requires visual studio. I'm on linux dammit.
Actually he's attempting to dissuade people from leaping to conclusions based on little-to-no data and their own biases.

He doesn't say it's not the US, he just says that the data is not enough to support that conclusion.

It might be time for another HN article on Bayes' Theorem.
You never know with git. Which is one of my big problems with it. The picture on master doesn't necessarily represent what happens on other repos across your organisation.
Sure, but I have a separate alias for streams.
alias -g even, zsh-style.
Just do fast-forward merges. This means before pushing into the central repo, you rebase your feature branch onto origin/master. Cleaner history and easier to bisect.

However, I prefer non-fast-forward merges for features branches which break in between. Although rebase on origin/master is still good, because you find merge-bugs locally.
Conversations with some of lifes most inspiring 'unknown' people
Ikea for Food: Indian DIY Cooking Service
> If I was using this system I would say that it isn't up to libnih to fix the problem

It isn't up to libnih to handle the overflow, but the problem right now is in libnih itself[0] and only libnih can fix that.

[0] and is twofold: libnih blows up on inotify overflow instead of not blowing up on a relatively normal (if rare) situation, and consequently (and obviously) libnih doesn't provide any way for its caller to handle the overflow.
My kids absolutely love our 8-bit rig!!

Fire up some Defence Force, Harrier Attack, Doggy, or Zorgon's Revenge, from the good old days! YAY, 8-bit party! Space 1999, 1337, Pulsoids, Skool Daze .. STORMLORD! W00t!

:)

What's really great, is that the 8-bit days are not over. I see this now, with my kids getting attracted very much to programming on the 8-bit machines. "10 PING:WAIT 10 20 GOTO 10", represent!!
Unfortunately, this is true for adults too. I used to code for hours and now I have such a hard time to stay focused...
5 Top Gadgets That Are Essential When Traveling – DanylkoWeb
I think the keyword here is "state". A lot of bad code is written because people think they need to access (global) state all the time.

Maybe you drunk too much good practice-aid ;)
CryptoPHP: Analysis of a hidden threat inside popular content management systems
But if you use an async transducer on a channel, it fails. (Actual tested code, sadly.)

Which might be okay, but my basic point that it's definitionally fuzzy still holds.
If the output is getting parsed in some way then it can get really slow. For example, automatic highlighting of matching-parenthesis is great 99% of the time, but can hang the process for several minutes on large outputs (eg. a MySQL dump of serialised PHP objects).

On a related note, the "clear" function at http://www.khngai.com/emacs/eshell.php can help speed things up when your buffer gets large; it's basically like "reset" in bash. The reason it's useful is that the shell prompts in an eshell buffer are marked as read-only, so trying to clear a region containing prompts will fail. I'm sure there are other workaround for this, but running a "clear" command is easy enough :)
I came here to say, well, something.

Obviously, the patch sucks -- it just ignores the error, instead of doing the right thing.

OTOH, init not shitting the bed and taking your whole OS down is probably a good thing, even if getting there is imperfect.
I am always conflicted about writing about Angular on a negative light because the team has put some great work into it while raising the bar in how rich apps could be built on the web. Being a back-end developer for a long time, it let me build some great interfaces on the front-end really quickly, and I'm very thankful for that.

But we should also learn from where Angular succeeded and where it failed. Making XML declarative is fraught with difficulties. Things like ng-repeat are but a thin declarative veneer over the fundamentally imperative nature of constructing views. The biggest difference between most existing templating frameworks and React is in this world view: is the view constructed imperatively, or is it declared?

The other question of contention is how much implicit magic should the framework supply vs how much explicitness the user should bring into the code. Angular's design decision is to make bindings work magically, while React identifies explicitness as a virtue.

Having used both, I'm liking the imperative+explict camp.
I can play blindfolded and I'm nowhere near Kramnik. I've been around 17 hundreds in ELO when I played the most. I usually beat my beginner family members playing blindfolded against them.

I don't think about individual pieces placed in a board but rather interactions and moves. Pieces are not located at random, you can remember where pieces are because you remember the plans, the threats and the moves that lead to a setup. If I had to remember seemingly random arrangements of pieces it would be a completely different story and much harder.

Might help that I also played Shogi rather intensely and after being used to Shogi, the chess board feels very small.
Websense Security Labs Reveals Cybersecurity Predictions for 2015
Give them a working 8-bit system with hundreds of games and apps from the days before the Internet. There is still just as much working 8-bit and non-Internet software out there as there ever was: you just have to find the hardware.

Then, most important of all: don't leave them alone with it. Stay there and play with them. Maybe you'll enjoy a return to the 8-bit software development days too, just for the heck of it. Disclaimer: this worked for my two boys.
It's bad, irresponsible science. And it's bad, irresponsible journalism to make it a giant orange pull quote.

"I think it's X. But I don't have any evidence yet."

If you don't have any evidence, you shouldn't be talking about it to a journalist. Who, quite predictably, is going to make a big deal out of it.

This sort of thing actively hurts the climate change cause. It's bad, and shouldn't be done.
I can't speak of Angular since I haven't used it but one problem that is recurring with use frameworks, in general, is that thinking or getting used to "their" way takes a significant amount of time and seeing the continuous change of technology, I am not sure that time is justifiable in the longer run.

Take example of rails. I was trying to learn it sometime ago and was really amazed how it has a process for nearly everything. Migrations, asset pipelines, generators, and very extensive command line. Sure it does make it seem like "Once I learn it, it will be so much easy to make the next app" but it is easy to realize after sometime that you have to cross usual hurdles of Googling everything, learning these processes, facing issues, digging out new ways of debugging to finally be good at it.

My idea is that frameworks should be minimal which only ensure a basic working architecture and everything else should be extensible (via packages).
loud suicide rather than quiet misbehavior (nobody reads logs until someone notices something wrong) is often preferred, at least for distributed systems.
For real-time aspects, have a look at PubNub: lots of features, very low latency, many global data centers, SDKs for every language/platform, good docs and support. You can easily replace FireBase with PubNub (I did on a project and results were positive). Really depends on what real-time needs you have (simple data synching or more complex persistence requirements).
What is a proof, really?
Not quite, atoms in the universe is in the range of 10^80, which is a bit less than 2^266.

On the other hand, 2^80 is "only" approx. 1.2 * 10^24. Still, good luck colliding with that without big effort.
The sad reality that I came to realize from this year's CppCon is that most C++ developers out there will just keep on writing pre-C++98 code, due to multiple reasons like style guides, company policy, old code bases and so on.

Only greefield projects can benefit from modern C++ and there are very few out there.

After reading the updated version of Effective C++, I doubt the average C++ developer will be able to deal with a mixed codebase of pre-C++98, C++98, C++03, C++11 and C++14.
If nothing else I found this helpful so thanks for typing it
I'm a "collector" too and think a visible indication of whether I'd drunk such and such before would be extremely useful.
Just spent the past 3 weeks with my parents in their cabin 2 hours from civilization. Only internet connection is slow $60/4 GB 3G that's only stable in the early AM and late PM.

Haven't been this productive in AGES.
I seem to recall that IEEE or some such have a rule about there being 2 independent implementations of a spec before they consider it complete.