https://www.sec.gov/Archives/edgar/data/1652044/000165204424...
If you add a $15M one time capital expense to this then it doesn't even appear as a rounding error on this cash flow statement.
Acquiring a long term asset acting as a pillar of your marketing strategy then it begins to look like a very good deal.
Imagine that your banking website used a standard JSON+REST API with cookie based authentication to trigger & validate a transaction request.
When a request to `fetch` or XMLHTTPRequest is made from ANY site, the browser will still populate cookies for 3rd party sites.
So without CORS, then someone might be able to create a landing page, which in the background triggers a `fetch` or `ajax` request to your bank's transaction endpoint. For 99.999% of people this wouldn't be effective because they are probably not a customer of this bank and are not logged in at the time of the request. But for some very tiny fraction of users, the browser would be tricked into populating the Cookie header from a previously created session in a different tab and would send this request.
The Origin header in the CORS preflight is a signal from the server to the browser that 'yes, this request is safe for you to construct'. This way the browser doesn't let the malicious web page "trick it" in the first place to send the bad request.
tldr; they did science
HN is generally a site frequented by people with mostly software/hardware/<other-eng-backgrounds> with a slanted focus on all things software related (please forgive the generalizations here).Are there any sites focused towards other professional disciplines (other than various subreddits) with a similar model of user-content submission with the level of discussion of HN?e.g. Is there an...
https://github.com/rust-lang/rust
The git repo has over 150,000 commits, 3,000 contributors, and 9 years of release history. The last 6 years of which have been post 1.0.
Also, Mozilla has been writing large parts of firefox in Rust since ~2017. There's some interesting writeups on hacks.mozilla, including this one on reducing CVEs with Rust
https://hacks.mozilla.org/2019/02/rewriting-a-browser-compon... https://research.mozilla.org/rust/
...
Also, why is this in big-endian order?
Let's just try to kill big-endian data, it's disgusting
and should just die already.
BE is practically dead anyway, we shouldn't add new cases. Networking
has legacy reasons from the bad old days when byte order wars were
still a thing, but those days are gone.
I completely agree. I don't pay attention to a lot (or any) online economic circles, but I'm astounded at the pushback of high profile economists (Krugman, et al) against the shear novelty of the moment for their discipline.
Regardless of whether or not someone "believes" in bitcoin, the reality of the times is that cryptocurrencies are creating fantastically interesting economic experiemnts right under our noses. This seems like it would be the dream come true for an economist from an observational/curiosity perspective
This is an editorial fluff piece with a very poor core argument. I'm very surprised has risen this high on HN, usually the opinion pieces here have far better formulated arguments.
e.g. "Ok, so what do we even mean when we say “blockchain”.The answer is really that nobody knows, it’s not a term that has any precise definition and it really depends on who you talk to and the context. (Source: https://threader.app/thread/1363418896301228033)"
The irony being... the author also never bothers to spell out /which/ blockchain he is ranting against.
Again, he get's sidetracked on his own strawman argument of what a blockchain is...
"Now some introductions will tell you a blockchain is a data structure from computer science which consists of a linked list of blocks which are iteratively hashed so that subsequent blocks depend on the hashes of previous blocks. (7/)However the utility of a term of art for any piece of software that includes two of the most common concepts in computer science (hashing, linked data structures) is just bad classification. (Source: https://threader.app/thread/1363418896301228033)"
He entirely misses the point that the novelty of what a blockchain is, isn't a fancy linked list, it's a mechanism for distributed consensus. Where by distributed computing algorithms from Paxos -> RAFT and private implementations of distributed databases like BigTable, Dynamo, Cassandra, and now next generation iterations like Hazelcast, Redis Grid, Spanner, etc... have enabled the greatest leaps in computing scalability of the past 10 years. However these are all privately maintained databases.
The "blockchain"... whichever implementation to which you refer, must be defined in its usability as a trusted distributed database. The mechanism of the datastructure to represent it is the least interesting or novel part of the technology.
The rest of the author's "points" regarding utility and energy consumption are equally misinformed and poorly formulated.
All in all the author just doesn't seem very informed of what blockchain is beyond the sorts of talking head gossip you'd seen on CNBC. His own limited imagination into the possible uses are akin to people from 1995 who couldn't imagine why websites would be so big or that solar panels would ever be efficient enough to generate energy.
also, with Duck Duck Go (and I assume others) I think it's more than debatable that Google is the defacto "pro-user" choice
so when I read modern on your description I just chuckled a bit.
in any case great work on this. looks like a ton of work
2 ways to do something is more complex than 1.
But it's more than just the syntax of the code. It now means new lint rules, new coding standards in projects (some will allow => assignment, some will encourage conformity to legacy code, and others will disallow it entirely). There will be new Rubocop rules and other editor configs to update for proper syntax highlighting.
Syntactic changes like this with little obvious benefit need to be looked at skeptically. Just because something can be done, doesn't mean it should be.
You're absolutely right. There is no context outside of the few lines OP asked and the quote you highlighted shows a lack of real world experience.
Yes it's true the "right now" fixes indicate there is a problem, but in small shops it's generally the most reasonable approach. Now if you're on a team of 50 other people and you need to make "right now" fixes then there is certainly a problem. Neither of which any of us can know from the context.... but besides the point, that it's not even on topic.
https://www.youtube.com/watch?v=--c0tiIZG6o
This is by far the nerdiest channel I subscribe to and I LOVE it.
So find a bug in the implementation which can invalidate one of their claims. Lack of tests, is not a bug.
this infographic isn't exactly authoritative... but it's sort of fun to look at: https://www.tetongravity.com/story/news/your-chances-of-dyin...
This is purposefully misleading.
From the Q3 2019 10-Q: https://www.sec.gov/ix?doc=/Archives/edgar/data/1652044/0001...
Ad revenue: 33.9B Other revenue: 6.4B
"Google other revenues consist primarily of revenues from: Apps, in-app purchases, and digital content in the Google Play store; Google Cloud offerings; Hardware; and YouTube subscriptions."
"Other revenues" is up nearly 40% q/q compared to Q3 2018:
"Our Google other revenues increased $1,788 million and $4,639 million from the three and nine months ended September 30, 2018 to the three and nine months ended September 30, 2019, respectively. The growth was primarily driven by revenues from Google Cloud offerings as well as revenues from Google Play, largely relating to in-app purchases (revenues which we recognize net of payout to developers)."
install:
[ $(id -u) -ne 0 ] && echo 'please run sudo make install' || curl https//my.thing | /bin/sh