So what? They’re still responsible for complying with the law.
Following the law isn't black and white. I'm sure each of us as individuals broke the several times today without even knowing it.
Readit Newsanameaname commented on State of Washington sues Facebook and Google over failure to disclose spending techcrunch.com/2018/06/05... · Posted by u/confiscate
Someone actually tried to follow this advice starting in September 2007: https://www.bogleheads.org/forum/viewtopic.php?t=5934 . Needless to say, it did not work out well for them and they almost went bankrupt due to spiraling margin debt.
The difference between a mortgage and margin debt is that mortgages aren't constantly marked to market, and you can continue to own the house even if you're temporarily underwater on the mortgage. Whereas with margin, you can be forced to sell if the value of the assets you've bought underperforms.
The paper that was linked suggests using derivatives rather than directly taking out loans, which are financially convertible. Specifically it says buying deeply ITM call options for several years out strike date.
In Item 10 it says:
> One study I remember showed that young investors should use 2x leverage in the stock market, because – statistically – even if you get wiped out you’re still likely to earn superior returns over time.
And the linked paper says:
> The mistake in translating this theory into practice is that young people invest only a fraction of their current savings, not their discounted lifetime savings. For someone in their 30's, investing even 100% of current savings is still likely to be less than 10% of their lifetime savings
This makes a lot of sense to me and says what I haven't been able to about my own risk tolerance. What is OPs counter to this? That the paper's conclusions are flawed, or that no 20-something could execute it?
anameaname commented on Java’s Mysterious Interrupt carlmastrangelo.com/blog/... · Posted by u/mattiemass
It's more like thread cancellation than an interrupt.
Few languages do cancellation well. Either it doesn't work right, or it does something overly elaborate like LISP breaks.
I've use Go's context based cancellation, and while I like the paradigm, it's kind of verbose. There are some that say that since it has to be passed everywhere, and can store values, it's equal to Goroutine-local storage. I'm would be surprised if they don't include a formalization in the language itself in version 2.
anameaname commented on Java’s Mysterious Interrupt carlmastrangelo.com/blog/... · Posted by u/mattiemass
> calling isInterrupted() actually clears the interrupted bit.
Thats incorrect. Calling Thread#interrupted[0] clears the interrupt status and returns true if the current thread was interrupted. Thread#isInterrupted()[1] only returns the value of the interrupt status on the thread receiving the method call. The interrupt status is unaffected by that method call.
[0] https://docs.oracle.com/javase/8/docs/api/java/lang/Thread.h...
[1] https://docs.oracle.com/javase/8/docs/api/java/lang/Thread.h...
You are right, editted.
anameaname commented on Java’s Mysterious Interrupt carlmastrangelo.com/blog/... · Posted by u/mattiemass
As another surprising thing, calling interrupted() actually clears the interrupted bit. If it's true, you pretty much have to throw InterruptedException. Otherwise, you have to re set the bit, and exit quietly.
anameaname commented on Facebook Q1 2018 Earnings Slides [pdf] investor.fb.com/files/doc... · Posted by u/uptown
Reported 2018 Q1 Net Income:
Alphabet: $9.4 Billion [0]
Facebook: $5.0 Billion [1]
[1] https://s21.q4cdn.com/399680738/files/doc_financials/2018/Q1...
Net income is not that useful of a metric since both companies are still growing.
anameaname commented on Alphabet Q1 2018 Earnings [pdf] abc.xyz/investor/pdf/2018... · Posted by u/haberdasher
Yes if you don't have any support staff it is easier to reach such numbers.
This is on purpose. If the number of support people is a linear function of the number of users, the business cannot grow past half the worlds population.
Their user focus is shockingly poor.
I followed the link from the blog post that said "check out the demo on our product website". Then there's a big button that says "TRY IT FREE". Good, I say. That leads me through a signup process that involves credit cards and whatnot, and then dumps me out on what I guess is the equivalent of the AWS console, not some nice audio test page.
So then I root around in the console, finally find the text to speech stuff, and screw around with various interfaces. None of them seems to be the right thing. Eventually I decide I must have missed something, go back to the product website, and scroll down further to find the "convert your speech to text right now". Great, say I.
The blog post explicitly talks about video. I want to see if it can transcribe a talk I did, so I tried uploading a file; nothing appears to happen on Firefox. I try a couple more times. I sigh heavily and switch to Chrome.
It does appear to work on Chrome, but it's entirely infuriating. I tried uploading a video file, which was over 50MB, so it refused. I then figured out how to extract the audio alone and uploaded that, at which point it complained it was over a minute. Then I find another incantation to chop my audio to a minute (which they just should have done for me, and which anyway should be explained in the interface).
Finally, I upload 60 seconds of audio. And nothing fucking happens. After all that, the thing just doesn't doesn't work. No error messages, no anything.
This is my first impression of the Google Cloud Platform, and all I hear is the squeaking of clown shoes. I'm sure the rest of it can't be this bad, but if they can't make a simple demo work, I'm unlikely to find out.
This is what you get when you don't have a top-down management style. Teams are given too much freedom, leading to inconsistency. No one has the whole vision of how a product should work. Even if they did have that, they likely don't have the authority to make it happen.
I've no idea what techniques will actually be applied by operators - I never expected middleboxes to go to the extremes they currently do either. But the technique I mentioned, of briefly delaying a short burst of packets, if done only occasionally, isn't really going to be noticed during a large transfer. I'm not claiming its a good idea though!
Large transfer's wouldn't be the place where the effect would be noticeable, it would be JSON payloads that can fit in a few packets. If operators would do this seldomly enough to not be noticed, why do they need the bit at all? It feels like a blank (albeit single digit) check.