22,635 karma · joined March 31, 2011
http://tools.ietf.org/html/rfc3986#section-3.3
For
example, the semicolon (";") and equals ("=") reserved characters are
often used to delimit parameters and parameter values applicable to
that segment. The comma (",") reserved character is often used for
similar purposes. For example, one URI producer might use a segment
such as "name;v=1.1" to indicate a reference to version 1.1 of
"name", whereas another might use a segment such as "name,1.1" to
indicate the same
There’s no thought given as far as I can see to the relative URL concepts this matrix proposal covers, but the idea of adding key=value data in this format is supported by the RFC, and indeed in a way that supports further adding sub resources below the current one.Which, by the way, this matrix relative URL proposal seems to ignore - how is ./subpage resolved relative to /map;x=250;y=582 ?
The semantics for your string “10.00” are complex - is it considered equal to “10”? To “10.000”? To “10.001”?
A user interacting with an API that uses such a string might make all sorts of assumptions about what it supports.
A user interacting with an API that has an explicit decimal places concept is being told ‘decimals matter! They can vary! Here be dragons!’
If they ate an average $100 margin decrease on every one of those sales, that profit number wouldn’t go down from $120bn to $119bn, it would go down to $80bn.
Now you can absolutely argue that $80bn is still an excessively large number, but just so we’re being realistic about what the difference we’re looking at here is, it’s not a tiny percentage of their profits, it’s a third.
For example: https://www.insurancebusinessmag.com/ca/news/breaking-news/d...
“One British insurance company came to the rescue of three Scottish sisters … concerned about the cost of raising the Son of God should one of them be selected to give birth to the Messiah.”
Of course the big difference is insuring yourself against the personal risk of loss in the event of a specific outcome is not seen as quite the same as merely speculating on its occurrence. Insurance is just betting against what you want to happen happening.
It wasn’t efficient it was limited.
It was an offline OS for an offline era. It ran trusted software (everything it ran was something the user had explicitly installed) so it didn’t need to work to protect the user from malicious code. It wasn’t encrypting everything it wrote tot he hard drive or all its network traffic (if it was even handling network traffic). It didn’t support Unicode or vector typeface rendering and realtime video rendering at more than 300x200 pixels.
Computers are doing so much more nowadays.
Spinning rust hard drives were slow. It took ages to launch a program - loading screens typically had time to display a progress bar and a series of notes about what they were up to - ‘loading extensions’, ‘reticulating splines’, etc. Word would stall whenever it was autosaving. Carrying out an operation like spell checking or doing a find across a whole document or getting a word count took time.
Remember windows used to have an hourglass cursor? You used to have to watch that thing flip and empty multiple times when doing things like emptying the recycle bin.
Windows 9x was typically not running on a permanently networked computer. The computer wasn’t running a bunch of background network tasks like checking for updates or polling your email - generally it was just being slow because it could barely cope with running more than one program at once.
VPSes are usually compared to full-service cloud hosting and especially to serverless offerings, with proponents usually claiming that the costs of self-management of a VPS are vastly less than the premium AWS or Google charge for providing managed compute.
I’m mostly pointing to the irony of eliminating the ‘advantage’ of a VPS (that you can self-manage it like a grown-up, you don’t need a cloud provider to babysit you) by outsourcing management to a stochastic sysadmin who charges by the keypress.
Of course the ‘nerds’ you hear about and see online are extroverted self-promoters. Of course the most visible people in the internal culture of large organizations are the ones who do more talking than doing.
Those are the people who are doing all the talking.
It is a massive over sampling problem that leads you to think, by looking at eg LinkedIn, ‘why is everyone on here writing engagement-bait algorithm-maxing posts?’
Everyone is not; The content you see is by definition the content that maxed its algorithmic exposure.
Seems that we can’t both get what we want.
A potential solution is that you get your anonymous phone line but my phone provider simply refuses to let you call me with it.
Of course then we need to extend the same principle to data and to IP traffic originating from your device. If you don’t want to be traceable it seems reasonable that services should have the right to refuse to handle IP traffic you generate.
Would such a half-baked level of network access suit your needs?