From: Eric Lombrozo <elombrozo@gmail.com>
To: Dr Adam Back <adam@cypherspace.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] improving development model (Re: Concerns Regarding Threats by a Developer to Remove Commit Access from Other Developers
Date: Fri, 19 Jun 2015 05:02:40 -0700 [thread overview]
Message-ID: <378F00E0-9F14-45E7-9395-B5C1324A81F2@gmail.com> (raw)
In-Reply-To: <CALqxMTFx6DF0Re+pCwB1AjYo6eYuKtX1cqUpo=wXmHSOsN74dQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1364 bytes --]
> On Jun 19, 2015, at 3:45 AM, Dr Adam Back <adam@cypherspace.org> wrote:
>
> That wont be good for the companies either, but they may not see that
> until they've killed it, many companies operate on a1 or 2 year
> time-horizon. They may say screw layer2, I have a runway and I need
> micropayments to the wazoo and I dont have the dev resources for that.
Exactly, Adam.
Except, I think the genie is out of the bottle - these ideas are too powerful for them to be killed forever. They will probably survive even if this scenario comes to pass…but in a different network under a different name…and Bitcoin will be relegated to the history books and walls of museums.
Most of the potential brainpower available on this Earth to make serious, profound contributions to this movement haven’t even begun to touch it. Just because you happen to run a Bitcoin startup right now…even if you’ve received millions of dollars in funding…don’t think that the whole world has low standards and is lazy! Someone WILL eventually build something better than we can presently imagine.
First mover advantage and the network effect are vastly overrated. At the risk of stating cliches, the Mac came before the Windows PC…Yahoo! came before Google…MySpace came before Facebook…Bitcoin came before <we don’t know yet>.
- Eric Lombrozo
[-- Attachment #1.2: Type: text/html, Size: 4530 bytes --]
[-- Attachment #2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 842 bytes --]
next prev parent reply other threads:[~2015-06-19 12:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-19 9:22 [Bitcoin-development] improving development model (Re: Concerns Regarding Threats by a Developer to Remove Commit Access from Other Developers Dr Adam Back
2015-06-19 10:45 ` Dr Adam Back
2015-06-19 11:35 ` Bryan Bishop
2015-06-19 12:02 ` Eric Lombrozo [this message]
2015-06-19 12:48 ` Marcel Jamin
2015-06-19 12:49 ` Eric Lombrozo
2015-06-19 12:02 ` Eric Lombrozo
2015-06-19 13:43 ` Mike Hearn
2015-06-20 2:59 ` Tom Harding
2015-06-19 16:05 ` Milly Bitcoin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=378F00E0-9F14-45E7-9395-B5C1324A81F2@gmail.com \
--to=elombrozo@gmail.com \
--cc=adam@cypherspace.org \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox