Also crypto currencies, are not currencies. They are commodities. It is far more accurate, conceptually to think about them the same as precious metals and grains, not dollars.
205 karma · joined April 26, 2017
Also crypto currencies, are not currencies. They are commodities. It is far more accurate, conceptually to think about them the same as precious metals and grains, not dollars.
My first reading is as a veiled threat: honour our agreement or I bring trouble to your heart.
Money is a social construct. It isn't a thing, mined out of the ground or a cryptographic nonce that satisfies a a constraint on a hashing algorithm. Money is a social agreement that expresses credit worthiness as assessed by people regarded as reliable assessors credit worthiness.
Crypto, which repudiates centralised control, cannot be money. Not until someone figures out a way to guarantee that credit worthiness can somehow be reliably encoded into a trustless p2p algorithm. Given that crypto currency can barely scrape through with a solution to the double spend problem, extending to a solution to assessing credit in a decentralized, anonymous way might as well be on the other side of the galaxy. It is impossibly inaccessible.
Crypto currency view of money is that money is a store of value. Money is far more subtle and interesting than that. Money is has always has been a system of control. Those that can issue money, wield incredible power of the economy, and have done so since monies inception.
On Cloud vs baremetal arguments. I respect people find cloud works and is valuable for them. This inspite of my own personal experiences, direct or indirect with cloud have been adverse. I agree with author, for me, for dollar and time effort, baremetal is just better economically and performance.
Most recent. A web service I use heavily migrated from bare metal to cloud and their performance / reliability dropped significantly with numerous outages which tied me up on the phones to my clients. I gave them 6 months to get their act together, as a loyal client then gave up and moved elsewhere. Being a reasonably big client their sales tried to retain then win me back. Conversations were always the same:
Me: Moved because you guys stopped being reliable, reliability is important to me. Ever since you moved to AWS you have been unreliable.
Sales: we had to move to scale and grow
Me: whats the point in moving if moving weakens your product. there are other ways to scale.
Sale: we had to move to scale and grow
This article framing the paradox in context of climate change is simply doing the same thing, framing it in context of our most pressing existential threats of the day. Also, like Sagan, implicitly overstating the impacts of those threats to us as a species.
Its a useless exercise and brings no new information to understanding the Fermi paradox and doesn't bring us anywhere closer to resolving it.
Edit and clarification, since I think some people take issue with what I wrote above:
========
Existential threats I mentioned, nuclear and climate change, are in their worst possible realizations will be planetary wide catastrophes which have the power to cause us, as a species, enormous harm.
But they do not measure up as the existential threats implied by Sagan or author of this article : so they are not answers to the Fermi paradox.
I am looking at these two things strictly from POV of the paradox, not as pressing policy issues.
He was raided because he is a tax cheat who has been under investigation for years for multiple unrelated tax compliance events.
* edit. Typo/grammar.
https://pdfs.semanticscholar.org/7735/865e2ea8fd8d9662f3916f...
OT but hopefully interesting: Paypal doesn't care about many things. Like keeping their callback JVMs up2date, or changing their UAs from defaults to disguise their enabling tech.
2019.05.20 xxxx|173.0.81.33|xxxx|POST xxxx/paypal/callback HTTP/1.1|200|954|-|Java/1.8.0_60|xxx|xxxxxxx 2
Many of authors most significant criticisms on retained GUIs are implementation considerations. GUI frameworks exist that solve his key criticisms of complexity and are pleasant to work with.
Criticisms that target core architecture of retained GUI I don't consider to be valuable design goals, at least in settings where I work on GUIs. e.g. memory usage.
Alot of things are glossed over that remain challenges in both, e.g. layout management.
HTML is an interesting example. First iteration of HTML was essentially immediate mode if you think about a single client/server interaction as a GUI update cycle. Server sends draws to client browser and client browser sends back to server user selections. There is no retained state on gui side. Now with programmatic access to DOM, ability to attach events to DOM elements from client side it is now a retained GUI. Seems to be where things evolve to naturally.
The GUI framework I use nearly daily is retained and very pleasant to work with in terms of ease of belting out screens & readability/maintainability of code. The simplicity comes with compromises though as there are limits on GUI idioms that can be expressed. Occasionally run into those boundaries and resulting GUI does look a little plain and unexciting, but for something that is substantially about data entry its fine.
Small niche software doesn't suck : if you love that niche, if you can create something that that niche loves and that what you create is difficult for others to replicate.
I have small business with small client base that will forever remain small. ~ 140 clients. A couple of staff members now days.
Cost of acquisition is high. I need to retain a client for 2 years to achieve ROI. That bit is hard work. But you structure things accordingly. From the clients perspective, changing competitors products is very disruptive so I need to make sure I create something that makes it worth their while. The product itself and its capabilities compared to competitors, where the product is headed, support etc around that product and whether or not their is a genuine need for the product.
Making good money. Now bringing home more than market salary, but only after many years of sitting under so probably not at net break even just yet. In a few years all going well I'll sell out and will live very comfortably in retirement off what I expect to be able to sell for.
Fairly happy with my lifestyle. Flexible and generally a little less hours than full time. Can be pressured/stressful at times but no more than I remember when I worked for others.
I'll never be Peter Thiel wealthy but I am on track to achieve my financial goals.
From 2007:
https://www.reuters.com/article/us-philippines-textmessages/...
Another. Undated. Avg sms per month per subscriber = 600. Or 20 a day. Which seems low, I'm sure I've seen figures alot higher than this.
https://www.techwalla.com/articles/how-to-send-a-text-to-the...
The key point which is laboured a couple of times is that some seat results are different than plurality outcomes. But that is a feature of IRV, not a bug.
Had the election been run under plurality rules voters would of voted differently and this fact seems to of escaped the author of this website.
Voters who preferenced greens first, recognising a minor parties zero chance of winning under plurality would of instead cast votes according to two party preferred lineup, who mostly would ideologically align with labour. But under IRV they can vote for anyone they feel more closely represents them but still have meaningful input into a 2PP outcome.
Show me a critique of an IRV outcome where 2PP outcome violates Monotonicity and you'll have a real critique of IRV.
In EVA 1, Conrad and Bean carry on like kids at an amusement park. There is a genuine sense of joy and amazement.
Their partnership was unique in Apollo, a genuine and moving warmth and friendship. In defense of other crews, the work schedule was gruelling and hyper-competitive, with alot of people vying for seats seeking opportunity to advance their chances.
I enjoy watching recent interviews with Bean, he comes across as an 80+ year old man-child. Had Apollo 12 been the first crew to land on the moon, at the time this was a distinct possibility, then the very human aspect of how we connect with that extraordinary event in history would be markedly different to how things are. RIP Alan Bean.
All of them acknowledge difficulty in computation. It's like trying to solve the drake equation. Unless you know all the terms in the equation accurately the number at the end isn't terribly useful.
Many different computations seem to be in same order of magnitude.
The result of high energy consumption is unsurprising and intuitive, given the design principal of PoW. It's all about who is prepared to do the most work, up until economic limits set by current BTC rate.
My definition of "blockchain" is a distributed ledger in a entirely trustless p2p network. To which PoW is the most widely deployed mechanism in use to secure against the double spend problem. Pow being a mechanism that remains un-superseded inspite of significant efforts to do so. All this making PoW hardly orthogonal.
Of course this definition of a "blockchain" can be loosened. One of two tweaks and suddenly we need to label prosaic everyday items such as a git repos as "blockchains".
At which point it becomes difficult to even have conversation about "blockchains" since our industry has yet to bring to bear a sufficient amount of focus to even define the term with any sort of useful precision.
Proof of stake at this time is purely theoretical. It lacks strong proof that it solves the problem it sets out to solve. I personally doubt it is a viable solution and my belief it is a dead end avenue of research. Notable there are no large scale implementations yet, even eth rolled back the clock on POS.
Never heard of XRP before. Very briefly scanning, looks like a distributed consensus type protocol, which isn't anything new doesn't attempt to solve the core concern about decentralised trust. Realise am being a bit flippant here, I need to study more which I will, but this is my initial impression.
>> I assume you mean "there are other better solutions [to the problem of creating a decentralized ledger, or whatever]". What are those better solutions?
No I am not saying this at all. Why is it incumbent on me to solve this problem merely because I advance a critique of the current solution? Does my failure to bring an alternative to the table make my critique invalid? I don't think so. I have been puzzling over this problem space and exploring some ideas for alternatives. The problem is hard and honestly I am probably not smart enough to solve it. But the problems are interesting so I'll keep turning it over.
In terms of my thinking right now, I am not even confident that problems solved blockchains are even problems worth solving, that blockchains provide us, as a society, anything of value at all. Too much is given up: notably for example dispute resolution. Look at all the long parade of thefts and errors that have happened on Eth, the legacy to date of the idea of "the code is law" is problematic at best. To date I can only think of one real use case that has made me think blockchain/bitcoin is actually even useful : when US DoJ leaning on Visa/Mastercard to cutoff funding to Wikileaks, bitcoin provided good stopgap technical solution to this grotesque legal excess.
Firstly Proof of Work is incredibly energy inefficient, to extent that electricity consumed to append to public blockchains is comparable to electricity used by nation states.
Secondly POW by its inherent design recentralises trust. When mining evolves to deploying on ASIC and deploying it where electricity is cheap you are recentralising trust to a tiny few who are willing and able to fulfil the ever higher and steadily increasing bar that POW, by design, demands. The trust model at this point has evolved from technical difficulty of fabricating & maintaining long duration forked chains to one where key block creators are too financially invested in success of the chain overall to allow fraud to happen. At this point, when your trust model is essentially too much to loose to cheat, there are scant distinguishing features between a blockchain ledger and a traditional centralised clearing house.
To steal a line from a good book I read recently about blockchains: "The good bits of blockchain are not original, and the original bits of blockchain turn out to be much good."
[Edit: grammar / readability]
Mann's name against this synopsis is really remarkable given his relentless and unyielding rejection of anything that contradicts his held position on climate change being dangerous and imminent. Specifically this very claim that models to not replicate/overstate warming that is observed is something he has spoken out on often. e.g. a paper he co-authors (http://onlinelibrary.wiley.com/doi/10.1002/2015GL064888/abst...) seeks to square the circle between models and observations. I wonder to what extent the synopsis captures the content of the paper itself or if it is another paper that seeks to explain variation according to Mann's strong preference towards a more aggressive characterisation of climate change effects & impacts.
On KSP itself, huge weakness for me in the game is that it is virtually unplayable stock. Absolute minimum you need to install a data providing mod like Kerbal Engineer Redux for both building rockets to quickly assess dVs and TWRs etc and in flight to help with figuring out burns etc. In stock you are reduced to having to use spreadsheets to build rockets and trying to land from visual clues only. The stock game badly needs something like KER. KAC is also helpful to quickly find transfer windows etc.
I have a sprawling codebase written in a 80s/90s era closed 4gl. Crossroads. a) keep kicking this can down the road using what I have inspite of its obvious and increasingly imposing limitations, b) discard it and rewrite or code in something else inspite of loss of hard won business rules, logic, behaviours and feel of the code over the years or c) develop a compiler/runtime and evolve it from there.
Went with c). In hindsight was incredibly ambitious but glad I did it. Been evolving compiler and runtime steadily. Now at point where I am starting to think about how to bend the language to discourage certain anti-patterns the language by design encourages and move the code base away from these anti-patterns (excessive use of global variables for one).
Alot of consequences I have to accept with this approach though, one obvious one is it is hard to find and hire programmers who want to work on the frankenstein's monster I've created here. Programming seems easy when it's all new and shiny and you are minting things for the first time. Old code is challenging, there are no obvious solutions forward, none I've found at least.
Although the internet has empowered mail order brides to some extent, there are still a long ways from guaranteed happily ever afters. From what I've observed the power balance is still heavily against women and such "transactions" fail and largely to the disadvantage of the women involved.
Also alot of cultural disconnects between Phils and OECD nations. Reflecting upon my past relationship, neither of our needs were being met in any meaningful way; by standards of relationships I've had since and currently enjoy. It wasn't a healthy relationship for either of us and when I observe many other Filipino/foreigner relationships I see alot of similarities with my own direct experiences.