Earlier quoted context omitted.
Cryptocurrencies aren't going away. Which means that if your primary motivation to not work on cryptocurrency is that it wastes energy, then there's a whole lot of room for you to be making it better, and that is a stupid motivation. I'm not saying that they are obligated to work on it because it wastes energy. But the comment I was responding to implied that distributed systems engineers didn't want to work on block…
No that's not illogical, Why would I work to bend something like block chain, that was designed to be inefficent, to my will when I can just start from scratch using projects that were designed to be efficient first? That's very logical, the kind of decision that an engineer that's getting paid the make the best distributed system for the least money would make.
Why aren’t distributed systems engineers working on blockchain technology?
131–140 of 204 posts
Re: Why aren’t distributed systems engineers working on blockchain technology?
#132Earlier quoted context omitted.
The Ethereum team is serious about proof of stake.
Ethereum has not shown a particularly strong track record when it comes to security, so I think the comment stands until they address that or get replaced by the next hotness.
Re: Why aren’t distributed systems engineers working on blockchain technology?
#133Earlier quoted context omitted.
>Proof-of-work is simply not sustainable (energy-wise), IMO, for the foundation of a global system. What have you found that is cheaper to proof-of-work that works on a global system?[1] [1] "Nothing is Cheaper than Proof of Work" http://www.truthcoin.info/blog/pow-cheapest/
Centralized authority. With the obvious tradeoffs. :-/ Maybe there's a happy medium where trustworthiness of central authorities is appropriately distributed, but common operations are quicker and less wasteful.
Heck, everywhere you look there's a solution to the trust problem; it's fundamental to human interactions.
- There are courts. If you try to screw me, I can drag you into one. Nothing's perfect and there's probably a minimum amount I'd not bother Judge Judy for, but it's a solution a LOT of people rely on. And I can tack all sorts of things on to this like warranties and insurances.
- Brands. Look, we burn all this money on getting sports stars to pose for pictures. And there's reviews of our product in papers. If we did something stupid, you'd know. Again, it ain't perfect.
- Escrow. Don't trust me? Trust this guy.
Re: Why aren’t distributed systems engineers working on blockchain technology?
#134>The blockchain community is immature and historically unwelcoming. >It feels like a get rich quick scheme - https://twitter.com/naval/status/878018839044161536 This is what it comes down to IMO. Anything cryptocurrency related is just surrounded by a cloud of shady characters and scammers, even though the tech is legit. You just can't trust anyone, nor their intentions. Living your life and working in a constant sta…
I've spent a decent amount of time understanding blockchain at this point. Am I wrong in saying that it's really just a data structure for solving a problem (like a tree or array), but a lot of the hype seems to be people trying to find commercial applications to use the specific data structure? I mean, no one says 'lets go find a good use for an array,' you sort of pick the array after you have an idea
The problem it seems to me is that, although the idea of trustless systems seem really cool and applicable to a lot of domains, it turns out that there are actually way fewer useful applications than people originally thought. But no one is letting go, and a lot of people are wrongly convincing themselves and others that most systems are better off trustless.
Re: Why aren’t distributed systems engineers working on blockchain technology?
#135Earlier quoted context omitted.
I think that statement is a little disingenuous. There haven't been any attacks that target Etherium proper, only bugs in smart contracts riding on top of Eth.
Only a 31MM dollar bug, nothing to see here, we're secure. WAT?
Re: Why aren’t distributed systems engineers working on blockchain technology?
#136>The blockchain community is immature and historically unwelcoming. >It feels like a get rich quick scheme - https://twitter.com/naval/status/878018839044161536 This is what it comes down to IMO. Anything cryptocurrency related is just surrounded by a cloud of shady characters and scammers, even though the tech is legit. You just can't trust anyone, nor their intentions. Living your life and working in a constant sta…
This is true of any new burgeoning technology. Were you around for the Internet boom in the 90s?
Yeah I sent my first emails to a system that connected to neighboring systems via modem at a pre determined time to ftp mail bundles around.
Re: Why aren’t distributed systems engineers working on blockchain technology?
#137>The blockchain community is immature and historically unwelcoming. >It feels like a get rich quick scheme - https://twitter.com/naval/status/878018839044161536 This is what it comes down to IMO. Anything cryptocurrency related is just surrounded by a cloud of shady characters and scammers, even though the tech is legit. You just can't trust anyone, nor their intentions. Living your life and working in a constant sta…
Even if the tech is "legit" it's encredibly inefficient. We're spewing off tons of CO2 just to verify the block chain, but we have plenty of technologies that can do the same with a minuscule amount of energy. The problem is that they want a system that's trustless and that's simply not what most engineers care about. We want a system that's fast and efficient.
Re: Why aren’t distributed systems engineers working on blockchain technology?
#138I just have a well-paying job and I don't see any opportunities lucrative enough for me to jump away. Why? Bitcoin is an experiment. Reading through the paper, Bitcoin does not scale to general purpose commerce. All of the other technology appears to be "me too." When I first heard about Etherium, the bullshit smelt so bad that I couldn't even look at the paper.
What will get me really interested? Pay me to implement a real-world use case that fits the scalability constrains of blockchain. This isn't things like general-purpose currency, or general-purpose contracts. Someone needs to pay me to implement something that requires blockchain; instead of someone paying me to implement a blockchain and then going and finding a use for it.
Re: Why aren’t distributed systems engineers working on blockchain technology?
#139Earlier quoted context omitted.
Proof-of-work is simply not sustainable (energy-wise), IMO, for the foundation of a global system. The stability of whole ecosystems is predicated upon those ecosystems being attractive to people who want to make money by competing to solve hard problems by brute force. That's a lot of energy going into a system that can commit a new block of transactions once every 10 minutes on average. It solves a problem in an in…
>Proof-of-work is simply not sustainable (energy-wise), IMO, for the foundation of a global system. What have you found that is cheaper to proof-of-work that works on a global system?[1] [1] "Nothing is Cheaper than Proof of Work" http://www.truthcoin.info/blog/pow-cheapest/
Re: Why aren’t distributed systems engineers working on blockchain technology?
#140I work in distributed systems, and I consider blockchain very interesting. It's so interesting I click on a lot of links on Hacker News, and sometimes I take an afternoon on a weekend or vacation to read through some of the papers. I just have a well-paying job and I don't see any opportunities lucrative enough for me to jump away. Why? Bitcoin is an experiment. Reading through the paper, Bitcoin does not scale to ge…