mudetroit

Not necessarily wrong, but interesting test case for whether insuring the autonomous vehicle is cheaper then driving the poorly trained driver. Might still have a supervisor, but now they can put their undivided attention on the occupants.

I was more perplexed about the camouflaged vehicles being bright blue...

The point of both of these has nothing to do with increasing the speed of javascript. It has far more to do with opening the web up to other programming languages in a meaningful manner.

If we are going to be correct about this then let's actually be correct and not just say bcrypt is the only bet. You want a system that manages work rate. Off the top of my head that also includes scrypt and pbkdf2.

Having watched the video, and curled, to me it says little to nothing. Two stones thrown that far apart from one another can show wildly different amounts of curl. Every sheet has it's own characteristics, even across different pebblings things will change. Additionally, sweeping is supposed to make the stone go straighter, that;s the basic mechanics of the game.

I think if they are going to look at putting some sort of rule in place then they need to look at it from something that can be strictly scientifically measured, like the rebound velocity of a golf club face, rather then something against a specific fabric type.

It is pretty... but vastly oversimplifies the problem. If we are ever going to get something for real it needs to take into account real problems. Talking about things like actual operation of elections, not producing high numbers of different ballots because of splitting of districts.

For something to really work it is going to need to take into account things like existing political, and probably some physical, boundaries.

FWIW, I met my wife when she was living in that area. Little Traverse Bay on whe whole is a pretty affluent area. (There is some mix here, and definitely a drop in money if you move inland.) There are few manicured lawns near the bay though. Unlike Grand Traverse Bay, Little Traverse is mostly surrounded by quickly rising hills and bluffs. So while there are houses they tend to not have much in the way of yards.

It is worth noting with the structural support they have for bare js classes (or really just the js equivalent of classes since they are really just syntactic sugar); React can handle Typescript just fine.

And being an open source project, if they have strong opinions otherwise they are free to fork the project and compete with it.

The marketplace can determine if this is something that it finds to be onerous.

I wonder if this doesn't point to a market inefficiency that someone could take advantage of. A company that focused on research specifically, patenting and marketing relevant discoveries or spinning of subsidiary companies to exploit research they are doing.

I know it isn't the tenure track positions that are mentioned in the articles. But a company like this could potentially pay substantially more than the academic institutions,and give them a more immediate opportunity to publish as a primary investigator.

Those additional publishing opportunities may allow them to even return to the academic field if they chose to later on.

Just something I was mulling over while reading the article.

Be very careful thinking that they would not have attempted to prosecute them and/or punish the company for doing so. The wonderful fun of these secret courts, that we are stuck with for the moment, is that everything the do is stuck under gag order. You have to deal with the prospect of an angry judge or prosecutor at that point, and don't discount the likelihood of them being vindictive.

It is a difficult problem. Governments have a number of built in advantages over private companies trying to deliver the same services. I say this while being, in general, a supporter of the ability for municipalities to provide broadband if they choose to do so.

There are a number of complex opposing factors in allowing them to do so though. For example, Boulder has required companies leasing space on the public right of way to install, at the company's expense, fiber to be owned by the city. (http://www.branfiber.net/Conduit%20Lease%20Agreement%20betwe...) Basically, Boulder can force competitors for it's own broadband service to subsidize their own competitor. These are non-trivial problems to overcome.

Being even more pedantic, fortified and enriched flour is normally created because the base product was bleached, not because of milling.

React can handle all of your items just fine depending upon usage.

(a) Using the key property, will give React a manner to determine likeness of elements

(b) Don't calculate the expensive things at render time, do them when loading or modifying state.

(c) Is related to a, but I haven't run into large problems with this personally.

(d) React does batch changes to an extent I believe.

It's worth noting that Om uses React internally[1]. React, like almost every tool out there, can work very well when used appropriately, or poorly if use in appropriately.

[1] http://swannodette.github.io/2013/12/17/the-future-of-javasc...

This isn't necessarily the case though. I am in no way going to argue that the "tragedy of the commons" is a real phenomenon. But their is a natural counterbalance to the streets filling up with taxis.

People operate taxis to make money. If the number of taxis becomes such that the roads fill with taxis, then the number or taxis should lower itself for two reasons. A.) If the taxis can't get anywhere either then people won't pay for them. B.) The ability of any single taxi to turn a positive profit will approach 0.

For a simple reason. Netflix has to pay for enough bandwidth outbound to supply their customers, regardless of anything else. Their customers are also paying for a certain amount of bandwidth.

ISPs typically possess less total bandwidth then they sell. The problem is that the typical users usage is rising faster than the ISPs are willing to handle. If I pay for 50Mb/s, and the other end of my communication has enough bandwidth to provide it, then I should be able to get to that speed.

As far as I am aware, there has been no accusations that Netflix does not have enough bandwidth to supply their customers, but that the intermediaries have oversold their networks to the point where they cannot deliver on their promises.

I actually liked mockito, when I was doing Java development a couple of years ago.

That just looks like a horrible test, I tend to argue that when you have to resort to using a verify on any mock then you are looking at something problematic.

FWIW, spying on the leader of a foreign nation is not in anyway dumping on the constitution. Not going to make commentary on other programs, those are a completely different matter, but spying on the leaders of other nations, allies or not, is not illegal nor should it be surprising.

FWIW,it can absolutely be that way, and I have visited at a few gyms that I would never go back to. I also know that at my gym, if a coach notices you breaking proper form at all they immediately work with you on it, or have you back down an bit be it in speed or weight.

I am in no way saying that the bad behaviors described above, and you can absolutely get a cult like mindset focused around entirely the wrong thing. I would also say that I think some of the nature of the workout strategies in general may attract these kind of behaviors.

I would be really curious to know what the overhead of actually creating the connection and loading the collections on each request would be. Is this anything more than a micro-optimization?

Having admittedly not descended very deeply into the rules regarding HTTP caching, why should it be harder to cache based on the cross-section of the URL and the Accept-Header and not simply upon the URL?

I am not certain which method I prefer more honestly, and could fall either way. The comment that it was nice in theory but didn't work in practice seems to more point to not following the spec as it was written then a problem with the spec itself.

I find some of these thoughts to be be a bit off in their basic premise. For example, "A function is a function. A class is a function. An anonymous method is a function."

Well There are no classes in javascript at all. A constructor is a function in most OO languages. The difference here is the underlying OO implementation.

Anonymous methods are by nature functions as well. Could there be a more succinct syntax for them? Perhaps, but of all of the complaints about javascript this is a relatively minor one.

I would never say that there are not things about JS that don't drive me nuts. But the relatively simplicity of thinking of just about everything being treated equally from a language standpoint gives you a flexibility to work that can be really refreshing.

I believe the Penske bid was actually to buy the Saturn brand from GM, not Chrysler. Could be wrong, but buying a company the size of GM at the time of the bailout would still have been a very difficult proposition.

It has been a few years since I worked there, but I am pretty sure the threshold for qualifying for benefits at Starbucks was actually 20hrs/wk. Their basic theory was that training was one of the most expensive things they had to do, so giving people an incentive to stay for a while was a net benefit.

I have been thinking about what the url space for infinite scrolling should look like, and I think that if you have meaningful titles you should probably use those as your indicators instead of numbers. Still having paging links makes sense to jump groups of posts.

As for the hashtag, it is a worthwhile thought and you could probably go either way on that one. If you think of the original purpose of the hashtag it was to jump to a specific anchor on the page.

The M in MVC has nothing to do with database persistence. That is a wonderful perception that rails and its ilk have given us, for better or worse. You could build a complete system that fully implements MVC without database persistence, or really any persistence at all.

"for node in nodes" implies you are returning the node itself and not simply a counter. This would seem to fall more under his 1 word for loop variables idea.

* NB: I am not certain whether I agree with such rules or not, but that is another discussion point.

There is a reason for the insanity you are complaining about. The vars are effectively hoisted there by the interpreter anyway, by pulling them to the top of the block you remove a possible point of confusion, and more importantly a possible point of bugs.

I read that as 24.7% of people not income, could be wrong.