canvas would be a pain to have automated test. https://github.com/openfin/fin-hypergrid/issues/540

Maybe that's the compromise for a good user experience?

even with sikulix ?

the main problem with npm is just when its used internally. It is painful really. Using it when you have internet connection is just seamless

explanation here https://www.reddit.com/r/ProgrammerHumor/comments/3nhk5e/sec...?

Why not just repost an explanation here?

Maybe because the answer is a whole thread that includes comments and other pieces of context that a simple copy&paste of just an explanation wouldn't have?

Then that should be the main link.

there was a very informative episode on Planet Money with regards to setting up shell companies. A lot of info here with regards to how names are hidden etc...it is worth a listen. The hosts setup their own shell companies:

http://www.npr.org/sections/money/2016/03/30/472452808/episo...

will this affect jvm languages as well?

probably on separate repos which something like npm and bower does as well.

in Java you always have this.. Impl Impl Impl.. Impl everywhere. I feel it's being passed from a senior and a junior dev who interprets the "program to an interface" idiom. Its so annoying to follow a code that is deeply nested with calls on a very basic controller call. It seems to be program to think that calls will be dynamically "replaced" and "reloaded".

So much complexity in the Java world and I don't know if its because of the language has not evolved throughout the years or the quality of developers (majority) that it has produced. Reminds me of this https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...

We also have the same developers coding in javascript. I literally need to refactor once a 7k+ lines single ExtJS controller. Yeah Extjs is so popular in the enterprise java world.

To be fair about Interfaces and implementations- when you're using DI and Aspects, or really any type of framework that is going to be proxying your classes it is a good idea to code to an Interface, even if you only have one implementation.

I read a few great articles on this a long time ago and unfortunately I don't have the references at hand, but it was compelling enough that I Interface anything that's going to be proxied or injected.

That being said, I REFUSE to call anything an Impl. If I have an interface called FileSavingService, I'll have a LocalFileSavingService or an S3FileSavingService, but I'll chop my fingers off before I add Impl to the end of them.

I generally like coding things to interfaces, as you often implement the interface twice; once for the real system, once for unit tests of other dependent components. Not using interfaces leads to either compiling test code into your production binary, or other more-horrifying hacks (mocks!).

I wonder if in the future node will enable swappable js engine edit: ok just found this https://news.ycombinator.com/item?id=9534138

I've hoped for this since it's inception.

It gives the benefits of having multiple competing implementations but unlike the browser platform we (the developers) get to choose which one we use.

Native addons and even Node core are too tightly coupled with v8. NAN will need an overhaul.

I wonder what was the basis for Japan becoming the top economy given that they have twice as much unsustainable debt that the US plus they have a population problem.

It was 25 years ago. They didn't have either of those problems then.