[prev in list] [next in list] [prev in thread] [next in thread] 

List:       hyperledger-technical-discuss
Subject:    [technical-discuss] Golang
From:       linkgeorg () gmail ! com (Georg Link)
Date:       2016-02-17 1:21:20
Message-ID: CAGaP0dgwzskPQbVTw8pdbiDurTcBuaBEiQ5we86bbGkDxNLJfA () mail ! gmail ! com
[Download RAW message or body]

Thane, you bring up an important point. Use cases and resulting
specifications precede implementation. If you like to help with developing
these prerequisites, the TSC mailing list is the right place to
participate. We might discuss this more on Thursday at the next open
conference call, feel free to join.
On Feb 16, 2016 4:56 AM, "Thane Thomson via hyperledger-technical-discuss" <
hyperledger-technical-discuss at lists.hyperledger.org> wrote:

> When will this sort of information be solidified? If it?s related to
> personal preferences I?d recommend Go, but it?s just as easy to use any of
> the other languages. But isn?t it also really important to establish what
> the exact protocol is first? That way it opens it up to being implemented
> in different languages. Allows for benchmarks.
> 
> So far the project?s been pretty light on specifics. I?m personally quite
> keen to contribute, but without specifics (use cases, architecture,
> protocol, intended platforms, etc.) it?s pretty much pointless to start
> anything tangible. I?m assuming we?re waiting for those high-level
> specifics to come from the TSC? (Like use cases, guiding principles,
> collaboration processes, milestones, seed code, etc.)
> _______________________________________________
> hyperledger-technical-discuss mailing list
> hyperledger-technical-discuss at lists.hyperledger.org
> 
> https://lists.hyperledger.org/mailman/listinfo/hyperledger-technical-discuss
> 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.hyperledger.org/mailman/private/hyperledger-technical-discuss/attachments/20160216/9c908ef4/attachment.html>



[prev in list] [next in list] [prev in thread] [next in thread]