MattPie

:) As far as I can tell, npm is a Node.js version of things like apt or yum for OSs. There's a bunch of libraries and modules in npm, that you can 'npm install foomatic' and then use the foomatic library in your own code. Similar how you can do 'yum install emacs' to install a software package on an OS. NPM should take care of dependencies, so if the foomatic library needs the barorama package to function, it'll install both for you. It's a cool way to manage software libraries, but it has some pitfalls. The main pitfall is when the package you install changes, it might break your code. Or, a while back some guy rage-quit one of the package manager tools and pulled his packages, but one of his packages was required by tons of sites and broke things. That's where something like (as far as I can tell) the npm "yarn" package comes it. It acts as a proxy and cache for npm, so you're only downloading packages from your local yarn cache. That way, if a package disappears off the internet, you still have a copy so your stuff doesn't break. And, from what I understand you can keep the package versions stable so something doesn't change under you without warning and break everything. But I'm just a network/system guy, not a developer so there may be glaring errors in all that. :)

One correction: we have Net Neutrality now (thanks, Obama). The current FCC head wants to destroy it. "Once Net Neutrality dies and your ISP get to decide what you can conveniently access..." is more apt. To put it in local terms, here's a scenario: HFboards decides to cozy up with FIOS and give them a bunch of money to make them their "preferred" hockey discussion site. FIOS comes by to tell SDS, implying that if he ponies up, they won't limit the bandwidth FIOS subscribers get to SS. Then Comcast comes along and limits the bandwidth (or blocks) everyone other than the NBCSports Hockey Forum. Obviously, hockey sites aren't the issue, but Netflix, Amazon Prime Video, Goodle TV/Music, Youtube, etc. all care about this. It's letting your ISP to sell your access to the highest bidder. And since there's only one option in many places, you're stuck with it. I want my ISP to be a utility. The water and electric don't care what I do with their product. My ISP doesn't get to adjust what I do on the internet. If you think it's far-fetched, it's already happened to Netflix which is why the rule is in place. Comcast slowed Netflix down unless Netflix paid up. Extortion: nice internet service you got there, shame if anything slowed it down. I forget where it ended up, but that was the idea with ISPs. They wanted to/did classify it as a utility so the ISPs couldn't mess with it. Now that there's a suitably anti-consumer administration in place, they're tossing that rule.

Oh, either we're talking about different things or I've completely missed the point of the tool. This is the npm I'm looking at: https://www.npmjs.com/

I don't think it's Kane's "fault", but Kane with Eichel means Eichel shoots less, and with his shot, that's not a good thing for the team. Eichel's shooting is down 10% from his career average this year.

Eichel has 5 goals in 21 games. It's not working.

Updated. It's not looking good. I'd be pretty surprised if this team has it in them to win-out 2017, or on-average be the 5th-best team in the league until April (based on last year's finishing standings).

So Pokey for President of Hockey Operations? :unsure:

Not in any useful manner, but yes to npm. I just spent a few minutes reading through the Yarn package docs to see if it made sense for the isolated dev system we're running, as well as the very-isolated system that'll be deployed at to the customer. NPM itself seems similar to repos for other languages (CPAN for perl, PIP for Python, etc.).

Are you talking the bar like Swannie House or the bar like NY State Bar?

Over at TBD they still use +1? Those cretins!

Wait, what? The Leafs won 7 of their 13 cups 70+ years ago. In the last 70 years, they one a few in the late 40s/1951, then 4 in the 60s, and nothing since. That's not a winning team.

I thought we had seen all the ways the Bills can go into a mid-late season collapse, but purposely starting a rookie QB after a disastrous first NFL start the week before is a whole new level of Bill-i-ness. Shark, I jump at thee.

I'm a little unclear on how you're labeling franchise QB, but I think we're on the same page for the most part. Other than maybe Baltimore/Flacco, teams that contenders have top-10 QBs, what I'd call "franchise" regardless of where they were picked in the draft. I think there's an OK chance of finding that guy in the 3rd or 5th round, but no QB is going to be good behind the terrible line the Bills have.

I think blowing early picks on QBs that require "a flyer" is part of what has gotten the team to this point. Take players that *will* (within reason) be good (line, LB, secondary, etc.) with early picks, and take flyers late in the draft. There isn't nearly as much correlation with early pick QBs and success as other positions.

It's quite the conundrum; if there's a guy that's good enough to be worth moving up for, the team that's in that spot probably wants him too. And, is it worth the cost to have another promising QB in the system only to be disappointed? The rest of the team (which is weaker from not having all those picks) is just going to "ruin" him with bad play. I'm in the camp that says pick linemen until both lines are good, and then worry about a QB unless there's an absolute can't miss guy that doesn't require mortgaging the farm. I saw Ryan Fitzpatrick had a good day yesterday; I don't know if that's unusual for him and his team or not.

I see what y'all done did there.

I thought I'd stop in to throw a little shade at the coaching staff. Tyrod has definite issues and weaknesses, but the coaching staff apparently has no clue how to adjust for what the Jets and now Saints did. I have a tough time believing that there wasn't any adjustment that could have at least given Taylor a fighting chance.

One of the articles mentions OSP's house is assessed at $5M+. SF doesn't matter.

8 games, now.

I have some bad news for you on that subject.

Yep: “I have always believed that government has a responsibility to protect people,” Golisano stated in a release put out Monday. “We are not talking about a few geese who occasionally land for lunch. We are talking about up to 200 geese at a time that refuse to leave."

This is true; in various places I've worked they've hired a guy with a dog to come walk around every day and chase the geese. The geese figure it out before long. it's way cheaper to bribe the locals, and make them foot the bill for all the legwork to eventually get denied. yep, playing games with kids' education is a right an noble thing to do. :rolleyes:

The Wheel (of QBs) keeps turning.I expect big things from the Bills in 2019! (Am I doing this right?)

Hmm, I may see some unrequite-ese in there. Of course, I don't know you, him, or your working relationship but: - Boyfriend: boyfriends can be temporary. My guess is if you became single he'd make a move after a respectful amount of time - Age: you seem to be young at heart, active, and outgoing, age probably doesn't factor in as much as you think - Introduce to friends: This one is a classic. "Maybe one of your friends is as cool as you; no, that's impossible; I'd settle for half as cool, because that's still awesome". There's a more forward version (and possibly creepy), "Do you have a sister?" I may be speaking from experience here. :blush:

I'm not sure what it says when I guy calling himself "Frieda" uses a female name to demean another guy. Misogynist: Sure. Self-loathing: Maybe?