Shrinkwrap is ridiculous. I'm expected to go look at every resolved dependency and individually add them if I want to update or not? No thanks; one app at my workplace defines ~50 top level dependencies, but this balloons to almost 1300 - and this is with npm v3 - after npm install. Ain't nobody got time for that.
Deep nesting is not 'solved' it just doesn't happen 100% of the time anymore. If you have conflicts, you still have deep trees. I suppose range operators help with this a little, but looking at what gets installed it doesn't seem to help that much; I still have duplicated dependencies.
I was mentally comparing npm to tools like maven, ivy and nuget, all of which are faster but also not interpreted. Not a fair comparison I guess.
I think it's not bashing of npm specifically so much as it is the node ecosystem it serves and depends on; at least in my mind it's difficult to separate node from npm. That said, for what it's trying to do (read a list of deps, resolve vs. registry, download and unpack) it seems to do a fine job of it.
My major complaint about npm is the choice to allow version range operators on dependency declarations. We know the node.js ecosystem places a high value on composability, so using lots of tiny modules which themselves depend on lots of tiny modules is the norm. This is a problem though because range operators get used liberally everywhere, so getting reproducible builds is like winning the lottery.
There are other things I don't like about using npm: node_modules/ is big and has a lot of duplication (even with npmv3), it's pretty slow, historically it has been unstable, its still crap on Windows, etc. - but for someone who has 'ensures reproducible builds' as part of their job description, the way its modules get versioned is its worst feature.
Is there a meaningful performance difference between ZFS in FreeBSD or Illumos and ZoL?
Edit: this is a legitimate question. I know previously Linux-related ZFS efforts used FUSE, but ZoL is native. I assume performance should be roughly equivalent between Linux and FreeBSD, certainly.
I think this is overstating the risk a little bit.
Looking at the video linked elsewhere, this was run in a bedroom on the second or even third floor of a single-family residence. He mentions not being able to detect x-rays more than 35ft from the device. I think a neighbor would have to be trying to get in range to be affected.
It has data from 1994 to 2014, including this plus several other statistics. In particular, it looks like they are tracking on the order of trillions of miles driven per year, so you're right, making any kind of statement after only 100 million is more shameful marketing than anything else.
Edit: this is US-only, while Tesla is claiming vs. worldwide. Clearly more miles driven worldwide, and probably higher deaths per 100m miles.
Unless you're OK with breaking compatibility with all existing Windows apps - most of which you have no control over - rewriting the kernel as a POSIX thing is going to look a lot like 'bash on windows' in reverse. You'd have to have some kind of shim layer to translate all the old system calls, so most everyone's existing software is going to be slower and there will be bugs, etc. Including your own, since Windows is a kernel, a ton of drivers, a userland (including basic runtimes), a windowing system, a basic set of productivity tools and games, etc.
I think this would be a total disaster that killed Windows, personally.
I don't know the answer to that, or about Roth 401(k) plans, but I think there are a lot of people overall with one or the other. I think that threatening either would have an effect similar to threats on Social Security, without the justification of it being insolvent.
IMO, at worst, Roth plans could get phased out for new contributions with existing deposits and the tax-free withdrawals honored.
This doesn't make sense to me. The entire point of Roth is that you pay tax up front, and then the retirement proceeds are tax-free (assuming you withdraw after proper age, etc.). To then go and tax these withdrawals is basically neutering the entire Roth deal - I think there would be some pretty major political backlash on that.
I don't know if it's universal, but it's at least extremely common for there to be a psych eval prior to receiving a badge. Not sure why the parent thinks otherwise.
"Two days earlier, at 11.30pm on December 26, Murdock was arrested after drunkenly banging on a neighbor's front door with such force it was as if he were trying to break inside. He reportedly fought with cops when they showed up, and was ticketed for resisting arrest and assaulting an officer. He was taken to hospital after banging his head on the inside of the police car he was being held in.
Just a few hours later, at 2.40am on December 27, Murdock left the hospital and went back to the neighbor's home to bang on the door again."
I assumed the police beating was administered as he was drunk and resisting arrest.
Why are you being such a jackass with your replies? You asked an ambiguous question not really relevant to the article, people are trying to answer, and you're attacking their answers for not addressing the exact meaning of your question. Do you want answers or not?
Maybe if you edited your original post to better explain the answer you're looking for, someone could give it to you.
My own guess, as not-a-physicist, is that physicists expect the predictions made by existing science and their hypotheses to eventually be observed through experimentation. Given what we know, we can predict that some particles/types of particles should exist; projects like the LHC are created to test these predictions.
Or to put it simply: physicists might expect an upper bound on particle types because the available science doesn't suggest there should be an unlimited number of types of particles.
This wasn't exactly a fuel economy issue, it was more of an emissions cheat. I get great economy out of my Golf - higher than advertised. I agree that if they'd done the right thing w/ emissions that economy might have been worse and the car not as attractive.
"Owners will have two years to decide whether to sell back vehicles..."
So the rumor is I can drive my affected Golf TDI for ~2 more years, and then get compensated @9/2015 value plus up to $5k on top of that? Honestly, that's a terrible deal for VW.
Edit: thinking more, maybe this is better for VW than an alternative where they have to make good right away. They don't have to scramble to get 500k cars repaired or off the road as quickly, and they can spread whatever makes up the rest of their hit over a longer period as well.
To me, this does signal that we're a lot more upset about the dishonesty than we are about the emissions themselves.
I refrained from commenting earlier but I've upvoted you because something about that thin font + red + gray background was very difficult to look at, i.e. literally my eyes were moving elsewhere involuntarily. I'd be interested to know if there's a known color selection phenomena that causes this kind of reaction.
This blog post, and my reply, was about the powder. 1.6 introduces soy as a major component for the first time, which is what I was trying to say earlier.
Edit: to clarify, 2.0 is a prepared soy-protein-based drink which, until now, had a very different formulation from the 1.x powder product.
Deep nesting is not 'solved' it just doesn't happen 100% of the time anymore. If you have conflicts, you still have deep trees. I suppose range operators help with this a little, but looking at what gets installed it doesn't seem to help that much; I still have duplicated dependencies.
I was mentally comparing npm to tools like maven, ivy and nuget, all of which are faster but also not interpreted. Not a fair comparison I guess.