2,750 karma · joined February 2, 2011
Consensus protocols do not require mining. You can simply poll X random nodes and compare what they tell you. I don't understand what mining adds to the equation. Okay, instead of "I need to control 50% of all nodes" it becomes "I need to control 50% of all mining capacity". Is that the point of mining? To make inserting hordes of cheap lying nodes impossible?
Would this require globally broadcasting all transaction? If yes, wouldn't globally broadcasting all transaction give you a lot of transparency anyway?
The definition implies that if someone says "I'm on block 1000" they cannot create altered version of history without touching all the blocks after the change.
But how is this useful? If there is a disagreement about the last block, majority wins, right? So couldn't majority simply have the most up-to-date version of the database with a single signature?
I have seen plenty of universities teach Java and C++, haven't seen any that teach actual OOP. James Coplien aptly calls the current paradigm "class oriented programming".
Availability zones are a mitigation. The issues is the sequence of events and dependencies described in the postmortem. The description has six paragraphs.
Why? No mitigations/redundancy/workarounds and spoiled plans.
Example. My last job had mostly automated provisioning process and you could not do anything for the first 3 days. My current job is at a smaller company that has manual provisioning and you can get started within first couple hours.
On the other hand, they can be much harder to fix, because the sheer scale of failures and complexity of the infrastructure. There is a higher probability of complex systemic issues, as demonstrated by this very outage.
There are plenty of smaller providers that beat Azure VMs in uptime. Plus, smaller websites/services can employ much simpler failure mitigation strategies.
Nowhere near 99%.
Running a large service on top of Azure or AWS is not a walk in the park. You don't manage hardware and you deal less with provisioning, but you need a significant level of expertise in dealing with idiosyncrasies of the particular hosting you've chosen.
I've seen companies transition to AWS. Very often they spend months "figuring things out". And then it turns out that they've just traded low-level problems which everyone knows how to solve for high-level problems no one knows how to solve.
Also, just because AWS/Azure is running doesn't mean your service is up. You end up managing high-level company-specific infrastructure on top of low-level one-size-fits-all infrastructure. Both can fail.
A lot of companies jump onto AWS/Azure/other big clouds because of hype, bandwagon effect and the general feeling everything will become "world-class" by magic. In many cases there is no legitimate cost-benefits analysis that compares costs of AWS switch to costs of fixing whatever problems company's current infrastructure suffers from. Also, almost no one factors in the costs of vendor lock-in and "too big to care" effect.
There are definitely use cases where Big Cloud makes sense, but it's nowhere near 99%.
It bothers me that increasing number of large companies dump their own data centers to jump into The Cloud. Thia means future outages (which will undoubtedly happen) will have wider and wider impact on end users.
For example, if your email is hosted on AWS and it goes down, you loose access to your email. No big deal. However, if your email, VOIP and IM/chat go down at the same time, you may loose all ability to communicate electronically. This can be a very big deal in certain situations.
If the philosophy prescribes dozens of tools for managing complexity and no tools at all for reducing it than it is the problem.
"Abstractions, decoupling, and modularization of logic/responsibilty" are not some kind of universal good. They are only useful within specific contexts. A lot of software engineers do not understand this and routinely engage in premature abstraction. As a result they produce systems that are 10 times more complicated than they need to be for absolutely no reason.
Java definitely encourages this kind of mentality, because the language itself and its standard library lack in some fundamental areas. Introduction of lambdas and streams helped, a lot, but the overall mentality is still well-entrenched.
1. Aliasing/abstraction of IP addresses. Being able to change physical location or server of a service without reconfiguring everything.
2. Mnemonics for getting to a particular server.
3. Indicator that a server belongs to a particular organization or company.
4. Grouping services together so they can share resources (like cookies).
DNS solves all of those problems, but not particularly well.
#1: You need to deal with a lot of BS when all you need is stable identifier.
#2: There is a lot of contention around domain names. Users prefer to use search instead of typing long domains. There is no particular reason why my mnemonics should be the same as for everyone else.
#3: Similar-looking domain names used for phishing. Users don't understand DNS hierarchy. Expiration. Hijacking. A tree structure isn't enough anymore. And so on. This one is particularly bad. Like you said, it's not just a technical problem.
#4: Just look at HTTP security headers and all the iframe issues.
The problem #3 can be solved separately from the rest. The rest are relatively simple technical problems if you consider them in isolation and we could solve them much better than DNS does.
GUId per domain. No hierarchy. Peer-to-peer sharing. Cryptographically signed user-comprehensible metadata that's resolved through some quorum protocol or stored in a blockchain.
URLs are fine, but the idea that identity of a website is embedded into its "location" is silly. Google owns gmail.com, but Steam/valve doesn't own steam.com. How am I supposed to know that as a user?
Really, the usecases for domain names names have completely changed since the time DNS was conceived.
This is one of the things that definitely can be improved on. Having something either in the URL or in page metadata to say "this is linkable". This doesn't warrant a replacement, however.
The web is everywhere. It's time to accept that web literacy is necessary for working in an office. This includes things like working with tabs, creating bookmarks and using in-page search.
I doubt it. Smalltalk had coherent design that anticipated many needs that the web faces today (and computers in general). What we get in ad-hoc piecemeal additions would be an organic part of the overall infrastructure.
http://www.korgforums.com/forum/phpBB2/viewtopic.php?t=88665
The post says it is spliced from Sonatina Symphonic Orchestra samples and Free HQ Orchestra Soundfonts[1], so they must be pretty good. There are individual instruments, choral arrangements and orchestra sections there.
1 - https://sso.mattiaswestlund.net/
2 - http://the-filmmusic-group.deviantart.com/journal/Free-HQ-Or...
I don't know about that. Everything with deep learning seems to attract so much hype that it's hard to measure the actual progress without being a researcher.
On the other hand, "classic" AI projects seem to get no recognition, even when they deliver astounding results.
For example, how many people here heard about MIT's Genesis project?
(http://groups.csail.mit.edu/genesis/)
If you don't know your past, everything seems like progress.
Anyway, pretty cool generator.
The cynic in me says that a in lot of cases this has something to do with people ensuring their own job security. A lot of AWS technologies I've looked into seem to be way, way more complicated to get started with than they should be. There is a also this curious incongruity of people sinking tons of time into "figuring out" how to make something prod-ready in AWS, while saying the technologies they are using are "simple" and "easy to use".