Why would a farmer own a combine? Aren't they owned by specialized harvest outfits? I don't have any experience in the business but when I was a kid and we needed the hay cut and baled we called the guy who brought in the hay baler on a low-boy. Nobody owned their own.
Rent vs. Own comes down to controlling your own harvest: renting means you may miss out, sometimes by weeks, of optimal harvest. You may have had to book a harvest weeks or months in advance. You may have to fork over cash months in advance. You may have to pay even if a field's yield is ruined due to summer floods.
If you own, you can select even segments of fields to harvest at more optimal times (a down grade, or wetter, portion of a field may harvest differently than an uphill, drier portion).
Perhaps, but the impression is reinforced when the police organize themselves to break the law in an organized fashion. For example, consider the police of Oakland, California. Every one of their patrol motorcycles is modified with a loud, unlawful exhaust muffler, through actions that body deliberately undertook. Clearly there are numerous criminals among the ranks of that police department, but it's also true that the department itself is corrupt and makes corrupt decisions as an organized body.
Edit: which is to overlook the most glaring examples of NYPD corruption: parking placards and get-out-of-jail-free cards for friends and family (recently reduced from 30 to 20 per officer!). It is not a great exaggeration to claim that the NYPD is America's largest criminal gang.
There should be some kind of cooling-off period between when these can hit the front page and when the comments begin, proportional to the length of the document. This one is 200 pages, so the first useful comment on this report will appear tomorrow at the earliest.
The only conclusion we can draw right now is that some software company has an exclusive contract to provide the government with PDF export applications that do not generate hyperlinked tables of contents, and that publishing such a document is in fact a crime against the people.
This post groks QUIC. The most important thing about QUIC is it frees applications from the tyranny of the kernel TCP state machine. Today all TCP sockets (at least, on Linux) are subject to the same system-wide parameters of the TCP state machine, none of which are appropriate for any particular application. With QUIC we will finally have each application in control of its own retry timers and other parameters. That is going to be quite beneficial, especially on mobile where packet loss is so common.
Those do not affect TCP state machine parameters like RTO(min), ATO, and TLP timeout. These are internal to the kernel and are either static, or can only be set systemwide. For example the minimum delayed ack timeout in Linux is just 40ms and can't be changed except by recompiling the kernel. 40ms is a totally inappropriate number for ATO in a datacenter or other low-latency setting. Other numbers like RTO(min) are specified in RFCs as 200ms, again completely inappropriate in a low-latency setting.
QUIC also frees us from other outdated misfeatures of TCP such as timestamps in milliseconds when they should be in microseconds.
Again, as someone who does not completely grok QUIC I am not dismissing it. I was hoping if some parameters were not exposed work would be put toward making these available through existing interfaces.
Linux network maintainers have repeatedly rejected attempts by Eric Dumazet and others to expose delack_min and other parameters to userspace. This is the kernel tyranny to which I refer.
Notably many of the people whose proposals have been shot down by linux netdev are currently working on QUIC.
Somewhat related: I do hope userspace network stacks get easier to stand up (with strict testing). It would be nice to move an attack surface like that out of the kernel.
QUIC is somewhat comparable to SCTP. But in both situations you wouldn't be using HTTP/2 on top of it. One of the main points of HTTP/2 is multiplexing several streams over a single transport stream. This isn't needed anymore with QUIC or SCTP, since they already perform stream multiplexing. The only thing which is left is transferring HTTP semantics over those QUIC or SCTP streams. The most simple way to do that would be doing HTTP/1.1 over them. However as far as I know (haven't read the latest state) QUIC uses a more sophisticated mechanism, which also provides header compression and caching across multiple streams, similar to HTTP/2. So it adopted some parts of HTTP/2, but isn't really HTTP/2 over QUIC/SCTP.
The shorter timeout would likely be for downstream app servers in the same datacenter, not for the general internet. That is, adding a route for a specific network not because the default route doesn't work, but for tuning that setting only for that network.
This is backwards. Google rescued Deja’s archives which were going to be deleted and then expanded the archives back to 1981. Without Google’s interventions you’d all be left wondering what was in Usenet.
A lot of these are pretty silly. 100% of Songza features were rolled into Google Music. Listing every phone they no longer market doesn’t make a lot of sense either. You might as well list Maps for Series 60 phones if you wanted to get down to that level.
(googler on maps here)
the maps backend team makes an explicit effort to keep old things going, I wouldn't be surprised if old gmaps on some really ancient phones still worked.
Last I checked the pre-2012 Apple Maps (the one that used google tiles, iOS5 and below) still works.
Having all the Android devices they no longer sell is also pretty silly. I doubt anyone wants to buy a Nexus One today. Also Nexus Q never made it past user testing (they never sold them, they were a free gift for IO, it was a horrible Chromecast/Nexus player precursor)
Well, it was sold, and then unsold. They took money for preorders, and then changed their minds and gave everyone who preordered their money back along with a free Nexus Q.
Creator here. And I agree. Listing every phone is silly. A lot of these were added during Hacktoberfest. Going to go through and prune/combine/edit this weekend sometime.
That’s not the reason. Vic Gundotra, the mastermind/moron behind Google+ would not tolerate any other Google properties with social features. Since you could share feeds and articles on Reader, and because it had followers and comments and whatnot, it had to be sacrificed on the altar of Google+.
In the US you may exclude up to half a million dollars of gains from your taxable income if you owned and lived in a property for at least two years. Otherwise gains on the sale of real property are taxed as ordinary income.
Specifically, 250K for single filers, 500K for married couples. Also, if you're married by Dec 31st, the IRS counts that the same as being married all year in terms of filing status eligibility, so it may pay off to get hitched before you sell and divorce after ;-)
It's not harsh, it's acknowledging that windfall income is unearned. That half a million exemption (or half that for unmarried people) is in addition to deductions for all depreciation and expenses.
Unions are definitely the primary driver. Construction unions in New York are using current contracts to pay for their pension liabilities. In other words, taxpayers today are paying for work that was done 30 years ago. This guy is sort of irritating if you have to read him for more than a few hours, but his blog is full of evidence and analysis on this topic.
This article is about capital costs, not labor costs.
>One point construction experts are making, however, is that taxpayers are paying premiums for these public projects since they aren’t being done open shop. The Empire Center report calculated that the government ends up paying 25 percent more for public projects in New York City because of the high prevailing wages.
This is the cost no one wants to talk about.
Good! Living in NYC costs more than living just about anywhere in the USA. Well over 25% more than where I live, a top 50 metro.
