Does anyone know what they mean when they say that Apps will be sandboxed? It can't be similar if the phone is running a desktop OS masquerading as mobile OS.
55 karma · joined April 19, 2019
Does anyone know what they mean when they say that Apps will be sandboxed? It can't be similar if the phone is running a desktop OS masquerading as mobile OS.
For example, imagine being undocumented and wanting to protest. You may second guess going to a protest (even if it benefits you to do so), because you learned law enforcement is tracking the communications and movements of protesters.
The open code to the software we use should not be a handout or a gift ex post facto.
The open code to the software should be an invitation: to collaborate on it, audit it, or frankly do anything you want with it (e.g. WTFPL); before, during, and after using it.
I think this is where crypto currency shines, as it doesn't require a deep stack of agents to facilitate a payments. It requires two parties (maybe a third for escrow), and money can move with less friction.
if(foo) doX() doY();
Intuitively, as a someone who uses C style languages, this becomes:
if(foo) doX(); doY();
Can someone confirm which intuition is correct?
I ask because, to me: it not being intuitive is a problem--even if it is not classified as ambiguous.
It being only contextually intuitive, also seems somewhat problematic--but maybe excusable if it is assumed you know some similar language going into it and it behaves similarly to that other language.
Pick a certain starting point and follow it down the rabbit hole. Rinse and repeat.
A couple things I find helpful about this practice is: one, it let's you compare the over all architecture against the true implementation (which can vary), and two, it gets you comfortable with the implied standards--the things that can't/don't get written on a style guide (e.g. they keep prepared statements in a separate, common file)
I think this is moot, because human financial advisors are not trying to beat anything, they are trying to spend your money. Read "Where Are the Customer's Yachts?" By Fred Shwed
Also Jack Bogle used to talk about the S&P 500 would be most people trading individual stocks (sorry I need to dig up the source for this).
Point being: you may not need fancy algorithms to outperform humans at the market, if your goal is only to outperform most humans. You may need something fancy to outperform all humans.
If you are designing the web for people of all abilities, then consideration of space bar scrolling is important.
Imagine the frustration of a user that expects certain behavior of the space bar and experiences something else.
Is there a hypothetical world where the modeling software failed to show this scenario for the correct input parameters?
Either way, I agree, based on the links presented in the OP, there is no evidence presented of it being a software bug.
When I got to college I retook the remedial math courses (starting with the equivelent of Algebra II) before I could take calculus (and the other math courses for a CS degree).
Not a single professor of a math course let us use a graphing calculator, and infact, most had a "no calculator" policy.
I never really put that together: you can learn the same curriculum with or without a calculator.
[1] https://www.amazon.com/dp/0982789742/ref=cm_sw_r_cp_awdb_t1_...
I remember paddling out at C-Street in Ventura in 14-17ft swell...didn't surf a thing and thought I was going to die. Go on a 4ft day and you will be lucky to find a place in the line-up.
Another comment mentions training for center of mass, and I would assume that's what they do.
Let's say 80% of your shots constitute a "tight grouping", 20% being somewhere other than where you were aiming. Aiming for the middle of the body would likely mean you have a very high success rate of hitting your target individual. Aiming for the shoulder/leg/arm (each one harder than the last to hit) you are looking at a very low success rate of hitting your target. If you choose to use your weapon, I would hope you are confident you will hit your target and only your target.
Opinion (don't read on if you are looking for hard facts):
The way I look at it, AMEX designed a closed loop payment system to easily ensure payments between customers and merchants.
Square and Stripe seem to be trying to accomplish the same goal, but in the 21st century.
Strictly calling Square a tech company, would be like calling 20th century AMEX a paper processing company--or maybe I am misinterpreting the founder's point.
I think that the nature of wire transfers makes them somewhat risky. The institutions facilitating the transfers assume some of that risk for their consumers. If a large some of money is moved from your account to someone else's, and you dispute the transfer, the institution sending the wire may have to refund you the money.
The cost of a single transfer offsets the risk of the aggregation of fraudulent transfers. This could be a calculation of volume, fraud rates, average amount transferred on that channel, etc.
This is all in addition to network costs as payment processors (third party inbetween financial institutions)
So, fees = portion of network cost + risk offset
Hope this sheds a little light.
Reading the mistakes made in the hack itself makes me wonder if black markets and money laundering are a skill they posses.
Anecdotally: you could argue that a car that drives itself is outlandish, or rentable electric scooters is stupid, or X other idea is ridiculous, but those smart/rich investors are still making money at the end of the day.
[1] https://www.forbes.com/sites/neilpatel/2015/01/16/90-of-star...