178 karma · joined October 4, 2013
Suppose you could transpile what is possible, then throw errors otherwise, however that would involve parsing each file in an NPM module which is probably an unreasonable task performance wise.
I am most certainly not opposed to the idea of taxes since society cannot function without the government providing some essential services. That said, I am opposed to paying a dime more than entirely necessary as it stands today because I see so much of my tax contributions being wasted.
* Medicare ineligibility to negotiate rates
* Military projects that are vastly over budget
* Government budgeting practices that promote blowing your entire budget at the end of the year so that it's not cut the next
* Excessive and abusive pension amounts for public employees
* Refusal to appropriately discipline public employees (police) for wrongful conduct
I can keep listing more, however before I am asked or required to send in another penny to be spent, I personally would expect at least some of these issues to be addressed, at least where spending is concerned. Until progress is made in these areas, then I will continue to be staunchly opposed to any tax increases and will do whatever I can to lower my own tax bill. If I feel my money is being wasted, then I may as well be the one wasting it rather than the government.
I'm sure I'll be downvoted for this, but I really couldn't care less about their feelings. At all.
In any case, I think 5 per week is extremely reasonable; I actually do less these days. I used to commit a dozen or more times per week, but these days I tend to work on the larger and harder components that people require. That means more thought and more design. It's not doing less work, it's just doing harder work.
This person may also have had review reponsibilities. Doing a truly thorough code review takes time to complete, and that time is time that you're not coding. It's important though; I may not be coding while I'm reviewing, but I'm sharing knowledge with a dozen other developers who hopefully learn from it (as I learn from others reviewing my own code). In aggregate, I hope that my lack of frequent commits actually helps the company rather than hurts it since hopefully I'm enabling many others to do better work.
Thanks!
Functions that contain a try/catch cannot currently be optimized by V8. If we migrate to using try/catch rather than `.then/.catch`, I wonder if there's going to be any perf implications since previously optimizable functions may no longer be optimized.
Where I work, I made a fairly robust image diffing utility that runs using Selenium/WebDriver on all browsers that we support. Combined with a robust test suite of many different scenarios, we can make changes to our stylesheets with a pretty high amount of confidence that if anything changed, it'll fail the build.
I've had this same argument at work a few times and although I fully admit the idea of a self driving car may be safer in the future, you will not be seeing me in the first few generations of these cars. I generally don't consider myself a luddite, but this is one area where I will prefer manual control for quite a while.
If it does any non-trivial amount of work, then I always use a function. The reason for that is in codebases that I've worked on in the past, getters were heavily overused and people ended up writing code that while at a glance seemed entirely reasonable, it was actually doing an absurd amount of redundant work and was causing performance issues. I feel that requiring the `()` to invoke it as a function at least hints that "this does stuff" rather than hiding the implementation in a getter.
Does that make sense?
In jQuery 3.0, their Promises will be fully Promises/A+ compliant as long as you're using `.then` ( `.done` and `.fail` are remaining non-compliant to remain non-breaking with sync XHR I believe )
https://gist.github.com/dcherman/4dfba0d72c008ee5b59d
It's a reduce function, but it could work as a forEach as well.
Ah yes, the ever popular "Nyah Nyah Nyah I can't hear you" scientific method. I wonder how much progress has been held back due to scientists like that.
The worst case scenario is that the doctor disagrees with the findings and continues investigation. The best case scenario is that you hit the nail on the head much more quickly than if it was an entirely manual process.
After learning about nutrition, it was horrific just how easy it is to down 1000 ( or more! ) calories of soda every single day without breaking a sweat. At 3500 calories per pound of fat, that's 3.5 lbs/week or 182 lbs worth of fat each year.
I still assert to this day that even if I completely let my diet go and ate like garbage, I doubt that I could eat enough junk to get back to the point where I was.
`on-select=handleSelection( selectedItem )` or something.
When it comes to controllers, I only have a few rules:
1. Never, EVER use $scope.$digest or $scope.$apply in any controller method. If you find yourself needing this, then you're missing a call in a spot higher up the stack ( event handler, websocket callback, etc.. ).
2. $timeout is acceptable if you legitimately need a delay - don't use it for control flow, ever. $evalAsync can be useful for coalescing multiple calls to a function into one during a digest cycle.
3. Minimal DOM manipulation. I will not say there's never a use case for DOM manip, but it should not be your first instinct most of the time. If it is, then take a step back and grab some coffee, go for a walk, and then look again. Often times, I'll use a variable instead and add a watcher on it in my directive to do the DOM manip. One can argue that it's needless overhead having the watcher, however I feel it's more in the spirit of Angular and does not contribute excessive overhead. If it does, then you can start making optimizations in the future after it's been proven that they're actually a problem.
While it may be entirely feasible to get along your entire life without financing a car by either purchasing used cars or inexpensive new ones, for 99% of people ( including myself ), it's extraordinarily difficult to purchase a home in a reasonable amount of time ( 10-15+ years saving required for a barebones house most likely ).
You could argue that prices are like this due to the easy availability of credit ( see 2008 or the problems with student loans/college prices ), but that doesn't change the reality that some things are extremely expensive and for nearly all people will require some type of loan. At that point, not having a good credit score will cost you dearly in much higher interest rates.
As for my kitchen, the reason you gave it exactly the reason that I did it. Although I did net an additional 100$ or so in interest over the course of the year as well due to it being in my savings account ( yay!...kinda? ), the primary reason was in the event of an emergency. Any emergency that would require an additional $10,000 is likely to be medical, family, or loss of job related. Since I have insurance, that means that the most likely scenario is family or job related; in either instance, the availability of cash to help a member of my family out or pay my mortgage for 6 months would be more important to me than the costs associated with financing that card for a period of time. In addition, I would still be able to pay the card off by selling a bit of stock, however I wanted the additional liquidity by having cash on hand. I don't make decisions like that lightly; all of those scenarios were considered before I decided to go the 0% card route.
There are a number of benefits to using credit cards that cash doesn't have:
1. Build a credit score
2. Fraud protection
3. Related to 2, but if I lose my card it's not a huge deal, cancel it and get a new one. If I lose 300$ cash, it's just gone.
4. Rewards! ( 1-3% back on 20K spending per year is a few hundred bucks )
5. Extended Warranties. Often times, you can get an extra year or more on warranties through your credit cards. That's why I put my new kitchen appliances on my Amex.
6. Free loans! I re-did my kitchen last year at about a 10K cost. Although I had the cash to do so, I instead signed up for a new card with 18 month 0% interest. That gave me another year and a half of saving before paying that off, so it's less of a hit to my balance at once. IMPORTANT I would not have done this if I did not have the cash to pay this off at any point in time.
It's really, really simple too - just pay off your statement balance in full each month and you'll never pay interest. I can count on one hand both how many times I've paid interest, and how much I've paid in interest. All of them were due to my own screw ups with scheduling payments ( off by a day - oops! ), however I've benefited far more from the cards than I've ever paid out. In most of those cases, the banks waived the fees anyway since there was a track record of 3-5+ years of never missing a payment, always paying in full.
(function() { var style = document.createElement( "style" );
style.innerHTML = "[data-reactid] { background: rgba(255,0,0,0.1); }";
document.head.appendChild( style );
}());"The extraterritorial reach of the income tax dates from the Civil War, when the government wanted to prevent Americans from fleeing to Britain to avoid taxes."