As it turns out, unreliable storage is not as valuable as reliable storage.
1,037 karma · joined May 13, 2018
Mining rewards are incentive to secure the network. Security increases the net welfare of the system.
Let's compare apples to apples. If you're including mining rewards in the cost for a bitcoin transaction, you should also includes Wells Fargo's payroll in the costs for a "free" ACH
This isn't as clear cut as it sounds. The Jevons paradox: as enegry efficiency goes up, enegry demand goes up by more. Or, put another way: humans wasted less electricity 20 years ago with incandescent bulbs than we do now with LEDs. One could also say that LED efficiency is counteracted by tech improvements. But in reality, we may be using more energy, but we're also doing more, and doing things we couldn't have done 20 years ago.
I'm skeptical of assigning a value judgment to things that a lot of people find valuable. LEDs are used for bigger, brighter advertisements. If I don't personally like ads, does that mean energy efficient LEDs are a waste? Bitcoin mining is used to secure a ledger from attackers with the resources of a nation state. If I don't personally care about a secure ledger, does that mean mining is a waste?
And about profitability, this is important, and new within just the past few years: renewable energy is the cheapest energy. [1] Anyone mining with coal is behind the times and will be competed out of the market in due time. The more incentive people have to seek out the cheapest energy, the higher the demand for renewables will be, and the faster the world will get on board. I for one welcome this catalyst.
This is the one that got me. Yeah thanks, I've been using text boxes since the 90s, I know how to undo.
Now we'll get to find out if _they_ know how to undo.
I remember the days before HTTPS was widespread. I watched as Google and other players systematically adjusted incentives, slowly but surely over many years, to reach where we are today: 90% of all web traffic is encrypted.[1] There's no reason the same couldn't happen with phone calls, other than perverse incentives.
Someone get me in a room with Ajit Pai and the CTOs of the major US carriers, I could have a system in place in five years, tops. Unfortunately there's no incentive for them to fix this, because (1) upgrading infrastructure costs money, and (2) carriers large and small are making BANK off these robocalls. ITSPs do typically charge to route calls (similar to internet peering), and robocallers are happy to pay because they're making so much money.
I've had my eye on this issue[1] for a while. I'm excited about the idea behind Svelte, but without static typing support, there's no way I could feel comfortable using it on a real project.
There are 50-year-old cars still in service today. I wouldn't drive one, because I want to take advantage of the tech advancements of the past 50 years. But that doesn't mean cars aren't durable goods.
And even though computing is barely 50 years old, there are 50-year-old computers in service today. I wouldn't use one, because I want to take advantage of the tech advancements of the past 50 years. But that doesn't mean computers aren't durable goods.
This applies even if a 50-year-old car, which predates bluetooth, doesn't have built-in bluetooth. And it applies even if a 50-year-old computer, which predates HTTP, can't load websites.
- It is stringly typed. All over the place you're globally registering names as strings (or worse, using strings that implicitly resolve to filenames). You'll write `store.createRecord('mymodel')` instead of just importing things using standard ECMAScript imports.[1] This means static analysis is out the window, which makes it labor-intensive to find usages or do even simple refactors like renames.
- It leans on global state and object mutation way too much, instead of using functional state updating. This was the way older frameworks like Backbone, YUI, etc worked. Web development is moving away from this paradigm, and for good reason.
- Static typing support is non-negotiable in 2019 (and 2015 for that matter, but I digress). Support in Ember is just not there, and I don't see much promise for the future either. React and Angular have had good support for Typescript and/or Flow for a good 5 years now.
- One high point for Ember: the in-browser testing beat the pants off any of the other frameworks. We ended up going with React/Jest/Puppeteer, but this meant we (meaning, I) had to write 150 lines of boilerplate that Ember gives you for free.
Overall working in Ember honestly felt like being transported back in time by 10 years. I guess if you're a solo dev it's easy to whip up a quick demo that seems fine, but you'll hit the wall very quickly where the project becomes write-only. I think it's unlikely a brand new build system, no matter how fancy, can make up for these architectural problems.
[1]: https://guides.emberjs.com/release/getting-started/creating-...
EDIT: I regret taking the time to write this. Should have checked submission history first…
In other words, not all functions in the stdlib of Ada, Pascal, C and C++ can be used in all possible target environments? Sounds like a failure to quality gate those standard libraries.
>JSON.stringify(1n)
TypeError: BigInt value can't be serialized in JSON
>JSON.stringify(1n)
Uncaught TypeError: Do not know how to serialize a BigInt
at JSON.stringify (<anonymous>)
at <anonymous>:1:6
You might also like:
- Polar bear shot dead in Iceland
I guess this is as good a place as any to ask – what's the value of interrupting the article halfway through to link me to other articles? It's something I expect from the likes of Buzzfeed, but now the BBC is doing it too. Did they think I'd get bored halfway through?
This is a gross abuse of html, but if you really want that syntax, you can have it.
I can't say I understand all the complaining here. You want to make $200K a year sitting at a desk, but learning flexbox or googling when you need it is too much effort?
In your first snippet, would you expect a candidate to tell you that `f` might be undefined?
(I didn't downvote you, btw)