skysight-inc/HackerNews huggingface dataset:
What I do is just have a ~/git/dotfiles repo, and then 'ln -s ~/git/dotfiles/vimrc ~/.vimrc' (and there is a script to dot his in the repo). Same with .bashrc, etc. You an use the same repo or different repos.

How is this better?
It would be very interesting if you could share your team's challenges and insights in creating a Chakra shim that exactly mirrors v8's C++ API so that it's a drop in replacement for v8 for Node. Is it difficult to maintain the Chakra shim against an ever-changing v8 API?
The Smallest Distributed System [video]
Apple is going to have a tough year
Weird situation with this and Sails right now.

Sails.js development has basically stagnated in the past year, and many people in the community believe Balderdash, the company behind it, aren't giving it the attention it deserves (they have a few new projects they're working on). Travis Webb and his team behind Trails were kicked out of Balderdash (not clear if fired from the company or just removed from GitHub group), and Travis blames Mike from Balderdash for doing it as a political move to keep control. Mike has said very little publicly about it, apparently not wanting to stir up more drama.

Trails seems to be an attempt at achieving what Sails has achieved (a full-stack modern MVC framework in node) with newer tools (ES6, I think Koa by default instead of Express, etc) and perhaps more modularity.

I think it's an ambitious project with good goals, but it will be a while before it will be stable and ready to use. And if it does reach that point, it's still susceptible to what's hurting Sails right now (a larger community than your developers can handle, de-prioritization, politics...).

Hopefully this turns out like the node / io.js split and is, in the end, positive for the ecosystem in some way.
linux is practically a micro kernel when it comes to ease of development. What people should be interested in is unikernels. OS is a crutch
> Im confused - is there a problem with cpu rendered fonts that needs fixing?

Performance. Even if an inefficient painting algorithm manages to paint at 60 FPS (which is very much not the case in, for example, common Web apps), improving its performance can free up the CPU to do more things and can reduce power consumption.

Think about it. If your GPU is sitting there idle, why not use it and free up the CPU to do other things? Today, most apps that aren't games are woefully underutilizing the GPU. Programs ideally should be utilizing all the silicon in your device while working so the work can be done faster and the hardware can enter low-power mode quicker.
So given your goal is "not to compete/replace but rather help Node" and you don't even have a clear crossplatform roadmap, although you have good intentions in that direction, would you say the author's claim that "the Future" of Node is in Microsoft's fork is something of a stretch?

I ask because I am getting downvoted for my other comment, but even you seem to be saying it's not what the blog author claims.
Open Letter to Hobbyists
This eliminates the ln -s ~git/dotfiles/vimrc ~/.vimrc step. Or more specifically, allows you to have any number of subsets of files contained in a single directory (or subdir) as members of different repositories.
Well, looks like he's back :)

So many people reposting his article!
excellent stuff...install and ran their package on my box with apache2 and was SSL'd in 2 minutes flat. will visit again.
I was hoping for a open source Windows x64 ABI compliant JavaScript JIT for a while now.
IM clients that steal focus when a new conversation begins are fantastic about this. More than a few times a coworker has gotten half a line of random code as a response when they try to ask me a question over Sametime.
Is some thing like Polarr online too complex for you, it also has a chrome app (works offline) https://www.polarr.co/

Disclaimer: Founder of Polarr
The article we're discussing answers this question - NAN gives you backwards compatibility with old versions of V8 (and therefore Node), while the V8 API doesn't.
I'd also recommend https://js.org/
Makes sense. Why spend several minutes rolling dice and writing stuff down when you can have the computer do the dice rolling in under a second, and then print out a character sheet?

It makes even more sense for point buy systems, where you frequently want to run a lot of "what-if" scenarios, and getting the math right is tedious.
I hired someone through this thread.
Hi MBCook the reader view works on my iPhone for this article.
Using the Force? No, it's an Apple Watch flying this drone
Life of a company from birth to death
There must be something better. Hard to be worse. But I don't know of anything.

If you can go non-graphical, there's rsync. Then for diffing inside files, if you have Xcode, there's FileMerge which is hiding in /Applications/Xcode.app/Contents/Applications/FileMerge.app

It's not an integrated solution, though, as Kaleidoscope aspires to be.
There is the multi-part ISO-9241 that covers the ergonomics of human-computer interaction. It even provides a definition of usability.
That's what Netflix got from using Reactjs. Facebook people search on mobile page version uses React too. It worked very well as a traditional AJAX search. Then they changed to to use React and now it takes a second or two to initialize and load the page (even it is in cache). And the search textbox doesn't feel like a native textbox, it's very laggy and shows inputs way too many milliseconds later. And on top of this the search result adds another delay. So searching for "Joe doe" means a laggy delay for every character as you try to type it in. Why? It tries to guess the person after every keyboard change event. Something that worked fine with the original AJAX version (Facebook optimized that version a lot an blogged about it / wrote a paper). Sadly with the React rewrite the forgot to read their own blog and probably React is an overkill for such a type of page and consumes to much CPU cycles on mobile devices. If you have to refresh 90% of the search results page anyway, why use React? Building and diffing a VirtualDOM isn't cheap (and ShadowDOM isn't supported), and it would be a lot faster to simply overwrite the DIV with innerHTML and traditional vanilla Javascript AJAX. Use the right tool, don't use a hammer for everything.
Can you share how?
FYI, the trailsjs.io official site listed on Github is just a Namecheap landing page.
Are you aware that NAN2's API is incompatible with NAN1's API? How is that backwards compatible?
Courseware MOOC platform nests things it's so amazingly bad. I forgot how bad it was.
Yes :) thanks anyway!
Apple: always so beleaguered.

I do agree that their software has taken a huge nosedive. Their major attempts at initiatives have been poorly executed.
> Hopefully this turns out like the node / io.js split and is, in the end, positive for the ecosystem in some way.

I agree. I commented earlier that the Node community seems to prefer small modules over Rails-like frameworks, but I think a solid web framework would be good for Node adoption by people who prefer them and beginners.
Strange he quotes Ben Thompson as bearish on Apple. Ben says exactly the opposite in his podcast. He has a very favorable outlook on Apple.
Can someone define "modern" in this context for me?
Nice to see that C++ is picking up speed after C++11. In my previous job I had to work with "legacy" C++, but now I'm working with "modern" C++. The difference is huge. C++11 features allow me to do more with less headache and I'm more confident in code correctness.
am I the only one who considers the markets obsession of endless growth as absurd?

Both sides in the smart phone market have been growing thru beating down the weaker competitors then just by market growth, the smart phone market in developed countries is largely reaching saturation - where is the place to grow now?

I work in a market where volume matters little - margin is the key - my division for example produces a product with a gross margin of ~50%
We plan to do a blog post about this when we submit a PR to mainline, but you can see the session at Node Interactive where we discussed some of these - https://www.youtube.com/watch?v=Zbc3SwMDWf0&index=14&list=PL....
I think this is an interesting problem. Facebook, Twitter, Tumblr et al dominate the internet. They are mostly used for garbage. There are more people on the web now than ever and they use these platforms like they use a permanent marker and a bathroom stall. At the same time, as has been mentioned elsewhere in these comments, it hasn't gotten much easier to run a blog. There are hosting costs to consider and the technical barrier is still there, although it is lower than it used to be. Also, perhaps most importantly, it is not immediately clear whether one can or cannot gain traction with a blog. People don't seem to read them as much as they used to and they don't have a fancy interface to subscribe and follow (at least not one that most people are familiar with today). Maybe someone could make a platform for people who want to make a blog but are dealing with these issues. Some kind of intellectual Tumlr? A place where making a blog is simple and you are sure to make traction because of the large readership of the platform. A place like Hacker News but with blog posts perhaps.
How Stories Deceive
"We’ll likely see a new release of the spec every year"

I don't understand why the specification needs updating so often. Or is this a case of new features in Microsoft’s Chakra being side slipped into the specification by default. So that over time ECMAScript becomes Microsoft ECMAScript. This is how Suns JAVA became Microsoft's JAVA. Or even over time 'license' the spec back to Google.

http://edge-op.org/iowa/www.iowaconsumercase.org/011607/2000...
whatever modern actually means.

Following whatever trend is fashionable at the moment, most likely.
The Radical History of 1960s Adult Coloring Books
#11: microkernel advocates use seizure-inducing black backgrounds with white text
"iPhone sales could go negative for the first time in history."

Growth. You mean sales growth. So call it that. There's enough innumeracy and economic illiteracy out there -- let's not add to it, eh.
> When Chakra is open-source and cross-platform, its differentiating "killer" features will be merged into node's V8.

You don't just merge features between JS engines - there may be one or two big wins that others will copy, but they're not like, say, C compilers, where different compilers by and large produce fairly similar machine code, because for the most part the language semantics correspond reasonably directly to machine semantics and the problems involved are well-studied, so the machine code is pretty close to optimal. JS has higher level semantics that admit varying implementation strategies - for example, all major engines use tagged pointers, but they all do it somewhat differently (e.g. V8 does not use NaN-boxing but others do); or on a macro level, those semantics require a garbage collector, which has a ton of implementation choices. Because JS engines are JITs, they perform optimizations informed by runtime information, which are more flexible but for that reason far more prone to guesswork, e.g. about what information to record, what kinds of assumptions to make about types mostly being static in practice, etc. And all JS engines have to balance runtime against compilation time, even to some extent for very hot loops, so they tend to have relatively simple optimization pipelines that value pragmatism over being able to cover every possibility.

The result is a lot of idiosyncrasy and a large number of little decisions and strategies that together can be highly significant but are hard to just port from one engine to another.

Notably, perhaps as a result, there seems to be a trend to basically rewrite JS engines' JITs while keeping the same name. V8 did this with Crankshaft in 2010 and is in the process of doing it again with Turbofan (dunno whether it will ultimately replace Crankshaft or just complement it, but I wouldn't be surprised at the former, considering that there is currently a large amount of duplicated functionality between them). I know SpiderMonkey has done it too but not the details.

> SpiderMonkey has been beating V8 in ES2015 adoption and V8s own benchmarks, but even that wasn't enough for it to become the new node.js runtime. We have yet to see if what Microsoft brings to the table is more convincing.

citation needed. "V8's own benchmarks" would be Octane, so this, which seems to be about evenly split between V8 and SpiderMonkey in the lead:

http://arewefastyet.com/#machine=28&view=breakdown&suite=oct...
One thing about Apple is this: they _always_ have a plan. Count on it. It's not like Business Insider is uncovering something they don't know here. All this doomsaying is due to the fact that Apple does not pre-announce anything. This, understandably, drives mass media nuts, so they just make things up. But that doesn't change the basic truth of the issue: Apple always has a plan.
The last time I checked in on Sails.js about 9 months ago, Mike McNeil, Cody Stoltman, and Scott Gress had just gotten back from YC for Treeline (http://treeline.io).[1]

[1] https://www.crunchbase.com/organization/the-treeline-company
Ah it's that time of year again; it's all over guys, time to go home.
I've heard this almost every year, and almost every year it turns out to be an incorrect assumption and as Aloha pointed out here - what is the obsession with growth?

Growth does not equal stability.
Symbolic calculates the symbolic representation of the derivative, autodiff just calculates the (numerical value of the) derivative by adjusting the computation graph.
apple stock will hit a high of $144.42 USD per share this year. You heard it here first.

EDIT add "this year"
Have you tried Elixir? If so, just wondering if you found the learning curve to be as difficult as Erlang.
If I were an investor in your company and I got a healthy dividend from that gross margin then that'd be great. But public stocks largely don't pay significant dividend and are valued off of growth. Growth expectations which are already factored into the price, whatever it may be.
I guess that's what Medium is aiming for. It's certainly how I use it.
> It is intuitively obvious that requiring probabilities to sum to 1 is rather arbitrary (any other number would seem to do as well)

Well, you have basically two choices -- one and zero. Any nonzero real number is trivially equivalent to 1.

It's not obvious to me, though, that 0 would work just as well?
I'm pretty sure nobody had a seizure staring at a DOS prompt; and that "white on black" is one of the settings in iBooks, Pocket, etc. for a reason.
Double virus infection to the prefrontal network of the macaque brain
But not for signing into the website, and adding notes for a pull request, or filing a bug/issue/feature request.
The original Wiki / WikiWiki / WikiWikiWeb started way before Google, in 1995: https://en.wikipedia.org/wiki/WikiWikiWeb

Even Wikipedia used that software in the beginning, as did many other projects. As MediaWiki and Wikipedia got more well known, many sites upgraded their Wiki to MediaWiki.
Not sure what gave you the impression of not having a clear roadmap. All I said was we'll disclose the full roadmap at the same time when we open up the sources. Once we open the sources and the roadmap at GitHub, we'd love to get feedback from the community to clarify or improve things further.
Two points:

One, it's pretty absurd to say that the IPhone is the "best" smartphone on the market. It did a lot well as far as marketing and design, but the rest of the market has caught up and now surpassed Apple.

Two, it's well documented that Apple can't even execute on their strengths anymore. They've made a series of poor design choices, and they've been largely unable to create new markets with items like the Apple Watch.

Bubble or not, the economy as a whole is certainly up. There is plenty of room for it to go crashing down, and with it things like emerging markets and discretionary income to be spent on iphones. Despite the surprisingly reasonable P/E, I'm bearish on Apple on a timeframe of more than a year or two.
First, they do increase. Capped at 2%, correlated to inflation.

Second, I agree on the inheritance piece. That is a problem.
I'm no Apple fan or user, but these reasons are vapid:

- iPhone in the "negative" which sounds, well, negative but actually means that GROWTH has stopped. However it remains one of the most profitable smartphones with a giant market share, so shareholders may wish to change their medium term valuations, but frankly any valuation which ignores market saturation isn't worth considering anyway.

- Apple Watch isn't a hit... Alright, but Apple Watch 1.0 was NEVER going to be a hit. A lot of people skip the first gen because they look at history (iPhone 1, iPad 1, etc) and with a smartwatch in particular there's a lot of reason to think the technology can move forward (12 hours battery life?!). Apple Watch 2 is due out this year, and while I have no idea if that will be a hit, it COULD be.

- "Apple's software and services — Apple Music, Maps, Health, Photos — are just OK." Maps, Health, and Photos were never profit makers. Everything I've read about Apple Music has been quite positive and they've already grabbed a large amount of market for being a relatively new player. Why is the article bundling profitable business avenues with unprofitable freebies? Why is it just "ok?"

I agree with the article that 2015 was a boring year for Apple, but I think they're jumping to a lot of conclusions about 2016, and if half the rumours about the next iPhone turn out to be true then it could be popular. With the 2016 Apple Watch, it needs at minimum to have better battery life, maybe round, maybe new functionality/sensors.

This entire article only exists because the market has a fetish for growth. Even if Apple becomes completely stagnant, it is stagnant for a HUGELY successful company that competes in multiple sectors. And it isn't like they're getting eaten by things like inflation (prices have risen) or actual decline (in real terms or not), so I think rumours of Apple's demise or even having a bad 2016 are greatly exaggerated.

PS - And don't get me started on how massively successful Apple has been with vertical integration as a growth vector.
> I think if you made up a DAG-adapted symbolic differentiator

That's essentially what autodiff is. It works on the DAG, whereas "symbolic" diff insists that the DAG is a tree (so reused components have to be duplicated, which leads to blowup).
Don't know why you're getting downvoted. More performance is certainly always good, but without subpixel anti-aliasing the text will tend to look pretty crappy absent a ridiculously high resolution display.
> monolithic kernels ... are the only type that have been commercially successful

Both Windows and OSX have (somewhat-compromised) microkernels at their core. As do the operating systems for most game consoles.
a) there are microkernel-based operating systems that are available right now. QNX and Green Hills, for example. There aren't any free ones that I know about, so the cost might be hindering adoption.

b) agree with you on this point that monolithic is 'good enough' these days. There are specific benefits to my particular application, but for a general desktop user I don't see the point. Even on a server the benefits are not very visible.
The point is that NAN2 is compatible with old versions of Node and io.js, not that NAN2 is compatible with NAN1.

This is bolded in the article we're discussing:

> NAN's promise is to provide a single API to develop against, not a forever-stable API, it was always anticipated that it would change and adapt to V8 but do so in a way that you get to remain compatible with older versions of V8.
That was the trend five years ago. We're on unikernels now.
Hey guys, It's great to see even more progress on Chakra since we last talked.

As a hardcore node dev I don't care for too much with engine x, y, z. As long as the community is given the keys from "dad". Adoption must be made part of the conversation, and we should have say over fixes, enhancements, and roadmap.

Seems like a lot but we saw the issues with Node pre-io and other products in tech when one voice is the majority or when a puppet board is put in place.
Guanfacine, but Not Clonidine, Improves Planning and Working Memory Performance
Effects of strategy on visual working memory capacity [pdf]
I dont know if i agree (im on the fence), but he did mebtiob spammy click bait titles.

There would be a hell of ablot less of those if there were no ad revenue(as ads are loaded when you enter they authors dobt care if you read those spammy articles, just load the damn page).

I would like to velieve this is true, but im not sure it would be(in the case of getting well written articles without ads).
Cognitive enhancement through real-time fMRI neurofeedback
Hopefully. We've actually seen some (mostly superficial) activity in Sails recently, which is surprising and encouraging.

Trails is actually much more modular than Sails. The goal is the same -- to make your life easier -- and the conventions are rails-like (indeed, compatible wiyh Sails) but the technical design is completely different and actually quite a bit more "node-like".

Keep in mind that Trails is not a fork, but a Sails-compatible re-write. So there's no upstream code-level reconciliation that can happen, but I'm sure both projects can coexist and compete in the framework market on their merits.
I'm interested in the Miami one. Any information?
The iPhone 6S is truly an amazing piece of hardware; there is so much internal enhancement over the iPhone 6. Yet Apple hardly hyped it in that way. I got my wife a 6S for Christmas and what convinced me was what I know about it that didn't come from Apple.
An integrative theory of anterior cingulate cortex function [pdf]
If the first machines which had segmentation existed in the early '60s, why did it take so long to discover that memory segmentation is an anti-feature?

AFAIK segments were put in the 386 because Intel thought people would like them, but they didn't. Now segmentation only exists on x86 hardware for backward compatibility, and all modern OS's essentially disable segmentation in software (basically putting all of memory into a single segment) and using paging to implement process isolation, no-write / no-execute, shared memory, and the like.

I'm not talking about 8086 / 8088 style segmentation, which was a different beast, a somewhat reasonable way to allow a 16-bit processor to access more than 64k of memory.
Windows 3.1 had a VMM that could have isolated drivers just fine. But the drivers that people needed to run were DOS drivers that were shoddily written with precisely-controllable (i.e. non-virtualizable) interrupts in mind. "Consumer" Windows couldn't get around the fact that they had to support hardware that came with crap drivers. The reason NT worked so well was that it targeted an extremely reduced machine profile in the form of "workstations", where Microsoft could write all the drivers themselves.

It took Microsoft until XP to actually be able to stop supporting the old crap VXDs and just force all the hardware manufacturers to "write a new driver or else". That they then also instituted the WHQL program to certify those drivers—and later added tooling to make that certifying job more rigorous—was just icing. It was moving away from VXD drivers that solved most of the problem.
What town?
It will be awhile before it's fully production-ready of course, but we'll begin using it internally for developing new projects after our 1.0-beta release in February.

One note: we're using Hapi by default, but koa and express4 will be supported as well. This is part of our modularity difference.
Contrary to what he writes, I don't see how well this translates to disciplines doing pure rather than applied work.