mirror of
https://github.com/LCTT/TranslateProject.git
synced 2026-08-23 04:03:29 +08:00
Merge remote-tracking branch 'LCTT/master'
This commit is contained in:
Xingyu Wang
@@ -76,8 +76,6 @@
|
||||
|
||||
Purism 是一个总部设在美国的企业，以提供确保数据安全和隐私的产品和服务为荣。这就是为什么 Purism 称自己为 “效力社会的公司”。
|
||||
|
||||
[][14]
|
||||
|
||||
Purism 是从一个众筹项目开始的，该项目旨在创造一个几乎没有任何专有软件的高端开源笔记本。2015年，从这个 [成功的 25 万美元的众筹项目][15] 中诞生了 [Librem 15][16] 笔记本。
|
||||
|
||||
![Purism Librem 13][17]
|
||||
@@ -148,8 +146,6 @@ Vikings 还有包括路由器、扩展坞等在内的其它配件。他们的产
|
||||
|
||||
Ubuntushop 的一个独特之处在于，它的所有电脑都带有默认的 Tails OS live 选项。即使你安装了某个其它的 Linux 发行版作为日常使用的系统，也随时可以选择启动到 Tails OS（不需要使用 live USB）。[Tails OS][43] 是一个基于 Debian 的发行版，它在用户注销后会删除所有使用痕迹，并且在默认情况下使用 Tor 网络。
|
||||
|
||||
[][44]
|
||||
|
||||
和此列表中的许多其他重要玩家不同，我觉得 Ubuntushop 所提供的更像是一种“家庭工艺”。商家手动组装一个电脑，安装 Linux 然后卖给你。不过他们也在一些可选项上下了功夫，比如说轻松的重装系统，拥有自己的云服务器等等。
|
||||
|
||||
你可以找一台旧电脑快递给他们，就可以变成一台新安装 Linux 的电脑，他们就会在你的旧电脑上安装 [轻量级 Linux][45] 系统然后快递回来，这样你这台旧电脑就可以重新投入使用了。
|
||||
|
||||
@@ -0,0 +1,146 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (geekpi)
|
||||
[#]: reviewer: (wxy)
|
||||
[#]: publisher: (wxy)
|
||||
[#]: url: (https://linux.cn/article-10983-1.html)
|
||||
[#]: subject: (Expand And Unexpand Commands Tutorial With Examples)
|
||||
[#]: via: (https://www.ostechnix.com/expand-and-unexpand-commands-tutorial-with-examples/)
|
||||
[#]: author: (sk https://www.ostechnix.com/author/sk/)
|
||||
|
||||
expand 与 unexpand 命令实例教程
|
||||
======
|
||||
|
||||
![Expand And Unexpand Commands Explained][1]
|
||||
|
||||
本指南通过实际的例子解释两个 Linux 命令，即 `expand` 和 `unexpand`。对于好奇的人，`expand` 和 `unexpand` 命令用于将文件中的 `TAB` 字符替换为空格，反之亦然。在 MS-DOS 中也有一个名为 `expand` 的命令，它用于解压压缩文件。但 Linux 的 `expand` 命令只是将 `TAB` 转换为空格。这两个命令是 GNU coreutils 包的一部分，由 David MacKenzie 编写。
|
||||
|
||||
为了演示，我将在本文使用名为 `ostechnix.txt` 的文本文件。下面给出的所有命令都在 Arch Linux 中进行测试。
|
||||
|
||||
### expand 命令示例
|
||||
|
||||
与我之前提到的一样，`expand` 命令使用空格替换文件中的 `TAB` 字符。
|
||||
|
||||
现在，让我们将 `ostechnix.txt` 中的 `TAB` 转换为空格，并将结果写入标准输出：
|
||||
|
||||
```
|
||||
$ expand ostechnix.txt
|
||||
```
|
||||
|
||||
如果你不想在标准输出中显示结果，只需将其写入另一个文件，如下所示。
|
||||
|
||||
```
|
||||
$ expand ostechnix.txt>output.txt
|
||||
```
|
||||
|
||||
我们还可以将标准输入中的 `TAB` 转换为空格。为此，只需运行 `expand` 命令而不带文件名：
|
||||
|
||||
```
|
||||
$ expand
|
||||
```
|
||||
|
||||
只需输入文本并按回车键就能将 `TAB` 转换为空格。按 `CTRL+C` 退出。
|
||||
|
||||
如果你不想转换非空白字符后的 `TAB`，请使用 `-i` 标记，如下所示。
|
||||
|
||||
```
|
||||
$ expand -i ostechnix.txt
|
||||
```
|
||||
|
||||
我们还可以设置每个 `TAB` 为指定数字的宽度，而不是 `8`（默认值）。
|
||||
|
||||
```
|
||||
$ expand -t=5 ostechnix.txt
|
||||
```
|
||||
|
||||
我们甚至可以使用逗号分隔指定多个 `TAB` 位置，如下所示。
|
||||
|
||||
```
|
||||
$ expand -t 5,10,15 ostechnix.txt
|
||||
```
|
||||
|
||||
或者，
|
||||
|
||||
```
|
||||
$ expand -t "5 10 15" ostechnix.txt
|
||||
```
|
||||
|
||||
有关更多详细信息，请参阅手册页。
|
||||
|
||||
```
|
||||
$ man expand
|
||||
```
|
||||
|
||||
### unexpand 命令示例
|
||||
|
||||
正如你可能已经猜到的那样，`unexpand` 命令将执行与 `expand` 命令相反的操作。即它会将空格转换为 `TAB`。让我向你展示一些例子，以了解如何使用 `unexpand` 命令。
|
||||
|
||||
要将文件中的空白（当然是空格）转换为 `TAB` 并将输出写入标准输出，请执行以下操作：
|
||||
|
||||
```
|
||||
$ unexpand ostechnix.txt
|
||||
```
|
||||
|
||||
如果要将输出写入文件而不是仅将其显示到标准输出，请使用以下命令：
|
||||
|
||||
```
|
||||
$ unexpand ostechnix.txt>output.txt
|
||||
```
|
||||
|
||||
从标准输出读取内容，将空格转换为制表符：
|
||||
|
||||
```
|
||||
$ unexpand
|
||||
```
|
||||
|
||||
默认情况下，`unexpand` 命令仅转换初始的空格。如果你想转换所有空格而不是只是一行开头的空格，请使用 `-a` 标志：
|
||||
|
||||
```
|
||||
$ unexpand -a ostechnix.txt
|
||||
```
|
||||
|
||||
仅转换一行开头的空格（请注意它会覆盖 `-a`）：
|
||||
|
||||
```
|
||||
$ unexpand --first-only ostechnix.txt
|
||||
```
|
||||
|
||||
使多少个空格替换成一个 `TAB`，而不是 `8`（会启用 `-a`）：
|
||||
|
||||
```
|
||||
$ unexpand -t 5 ostechnix.txt
|
||||
```
|
||||
|
||||
相似地，我们可以使用逗号分隔指定多个 `TAB` 的位置。
|
||||
|
||||
```
|
||||
$ unexpand -t 5,10,15 ostechnix.txt
|
||||
```
|
||||
|
||||
或者，
|
||||
|
||||
```
|
||||
$ unexpand -t "5 10 15" ostechnix.txt
|
||||
```
|
||||
|
||||
有关更多详细信息，请参阅手册页。
|
||||
|
||||
```
|
||||
$ man unexpand
|
||||
```
|
||||
|
||||
在处理大量文件时，`expand` 和 `unexpand` 命令对于用空格替换不需要的 `TAB` 时非常有用，反之亦然。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.ostechnix.com/expand-and-unexpand-commands-tutorial-with-examples/
|
||||
|
||||
作者：[sk][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[wxy](https://github.com/wxy)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.ostechnix.com/author/sk/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://www.ostechnix.com/wp-content/uploads/2019/05/Expand-And-Unexpand-Commands-720x340.png
|
||||
@@ -1,85 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (arrowfeng)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (5 essential values for the DevOps mindset)
|
||||
[#]: via: (https://opensource.com/article/19/5/values-devops-mindset)
|
||||
[#]: author: (Brent Aaron Reed https://opensource.com/users/brentaaronreed/users/wpschaub/users/wpschaub/users/wpschaub/users/cobiacomm/users/marcobravo/users/brentaaronreed)
|
||||
|
||||
5 essential values for the DevOps mindset
|
||||
======
|
||||
People and process take more time but are more important than any
|
||||
technology "silver bullet" in solving business problems.
|
||||
![human head, brain outlined with computer hardware background][1]
|
||||
|
||||
Many IT professionals today struggle with adapting to change and disruption. Are you struggling with just trying to keep the lights on, so to speak? Do you feel overwhelmed? This is not uncommon. Today, the status quo is not enough, so IT constantly tries to re-invent itself.
|
||||
|
||||
With over 30 years of combined IT experience, we have witnessed how important people and relationships are to IT's ability to be effective and help the business thrive. However, most of the time, our conversations about IT solutions start with technology rather than people and process. The propensity to look for a "silver bullet" to address business and IT challenges is far too common. But you can't just buy innovation, DevOps, or effective teams and ways of working; they need to be nurtured, supported, and guided.
|
||||
|
||||
With disruption so prevalent and there being such a critical demand for speed of change, we need both discipline and guardrails. The five essential values for the DevOps mindset, described below, will support the practices that will get us there. These values are not new ideas; they are refactored as we've learned from our experience. Some of the values may be interchangeable, they are flexible, and they guide overall principles that support (like a pillar) these five values.
|
||||
|
||||
![5 essential values for the DevOps mindset][2]
|
||||
|
||||
### 1\. Feedback from stakeholders is essential
|
||||
|
||||
How do we know if we are creating more value for us than for our stakeholders? We need persistent quality data to analyze, inform, and drive better decisions. Relevant information from trusted sources is vital for any business to thrive. We need to listen to and understand what our stakeholders are saying—and not saying—and we need to implement changes in a way that enables us to adjust our thinking—and our processes and technologies—and adapt them as needed to delight our stakeholders. Too often, we see little change, or lots of change for the wrong reasons, because of incorrect information (data). Therefore, aligning change to our stakeholders' feedback is an essential value and helps us focus on what is most important to making our company successful.
|
||||
|
||||
> Focus on our stakeholders and their feedback rather than simply changing for the sake of change.
|
||||
|
||||
### 2\. Improve beyond the limits of today's processes
|
||||
|
||||
We want our products and services to continuously delight our customers—our most important stakeholders—therefore, we need to improve continually. This is not only about quality; it could also mean costs, availability, relevance, and many other goals and factors. Creating repeatable processes or utilizing a common framework is great—they can improve governance and a host of other issues—however, that should not be our end goal. As we look for ways to improve, we must adjust our processes, complemented by the right tech and tools. There may be reasons to throw out a "so-called" framework because not doing so could add waste—or worse, simply "cargo culting" (doing something with of no value or purpose).
|
||||
|
||||
> Strive to always innovate and improve beyond repeatable processes and frameworks.
|
||||
|
||||
### 3\. No new silos to break down silos
|
||||
|
||||
Silos and DevOps are incompatible. We see this all the time: an IT director brings in so-called "experts" to implement agile and DevOps, and what do they do? These "experts" create a new problem on top of the existing problem, which is another silo added to an IT department and a business riddled with silos. Creating "DevOps" titles goes against the very principles of agile and DevOps, which are based on the concept of breaking down silos. In both agile and DevOps, teamwork is essential, and if you don't work in a self-organizing team, you're doing neither of them.
|
||||
|
||||
> Inspire and share collaboratively instead of becoming a hero or creating a silo.
|
||||
|
||||
### 4\. Knowing your customer means cross-organization collaboration
|
||||
|
||||
No part of the business is an independent entity because they all have stakeholders, and the primary stakeholder is always the customer. "The customer is always right" (or the king, as I like to say). The point is, without the customer, there really is no business, and to stay in business today, we need to "differentiate" from our competitors. We also need to know how our customers feel about us and what they want from us. Knowing what the customer wants is imperative and requires timely feedback to ensure the business addresses these primary stakeholders' needs and concerns quickly and responsibly.
|
||||
|
||||
![Minimize time spent with build-measure-learn process][3]
|
||||
|
||||
Whether it comes from an idea, a concept, an assumption, or direct stakeholder feedback, we need to identify and measure the feature or service our product delivers by using the explore, build, test, deliver lifecycle. Fundamentally, this means that we need to be "plugged into" our organization across the organization. There are no borders in continuous innovation, learning, and DevOps. Thus when we measure across the enterprise, we can understand the whole and take actionable, meaningful steps to improve.
|
||||
|
||||
> Measure performance across the organization, not just in a line of business.
|
||||
|
||||
### 5\. Inspire adoption through enthusiasm
|
||||
|
||||
Not everyone is driven to learn, adapt, and change; however, just like smiles can be infectious, so can learning and wanting to be part of a culture of change. Adapting and evolving within a culture of learning provides a natural mechanism for a group of people to learn and pass on information (i.e., cultural transmission). Learning styles, attitudes, methods, and processes continually evolve so we can improve upon them. The next step is to apply what was learned and improved and share the information with colleagues. Learning does not happen automatically; it takes effort, evaluation, discipline, awareness, and especially communication; unfortunately these are things that tools and automation alone will not provide. Review your processes, automation, tool strategies, and implementation work, make it transparent, and collaborate with your colleagues on reuse and improvement.
|
||||
|
||||
> Promote a culture of learning through lean quality deliverables, not just tools and automation.
|
||||
|
||||
### Summary
|
||||
|
||||
![Continuous goals of DevOps mindset][4]
|
||||
|
||||
As our companies adopt DevOps, we continue to champion these five values over any book, website, or automation software. It takes time to adopt this mindset, and this is very different than what we used to do as sysadmins. It's a wholly new way of working that will take many years to mature. Do these principles align with your own? Share them in the comments or on our website, [Agents of chaos][5].
|
||||
|
||||
* * *
|
||||
|
||||
Can you really do DevOps without sharing scripts or code? DevOps manifesto proponents value cross-...
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/5/values-devops-mindset
|
||||
|
||||
作者：[Brent Aaron Reed][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/brentaaronreed/users/wpschaub/users/wpschaub/users/wpschaub/users/cobiacomm/users/marcobravo/users/brentaaronreed
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/brain_data.png?itok=RH6NA32X (human head, brain outlined with computer hardware background)
|
||||
[2]: https://opensource.com/sites/default/files/uploads/devops_mindset_values.png (5 essential values for the DevOps mindset)
|
||||
[3]: https://opensource.com/sites/default/files/uploads/devops_mindset_minimze-time.jpg (Minimize time spent with build-measure-learn process)
|
||||
[4]: https://opensource.com/sites/default/files/uploads/devops_mindset_continuous.png (Continuous goals of DevOps mindset)
|
||||
[5]: http://agents-of-chaos.org
|
||||
@@ -1,113 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (murphyzhao)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Welcoming Blockchain 3.0)
|
||||
[#]: via: (https://www.ostechnix.com/welcoming-blockchain-3-0/)
|
||||
[#]: author: (sk https://www.ostechnix.com/author/sk/)
|
||||
|
||||
Welcoming Blockchain 3.0
|
||||
======
|
||||
|
||||
![Welcoming blockchain 3.0][1]
|
||||
|
||||
Image credit : <https://pixabay.com/illustrations/blockchain-network-business-3448502/>
|
||||
|
||||
The series of posts [**“Blockchain 2.0”**][2] discussed about the evolution of blockchain technology since the advent of cryptocurrencies since the Bitcoin in 2008. This post will seek to explore the future of blockchains. Lovably called **blockchain 3.0** , this new wave of DLT evolution will answer the issues faced with blockchains currently (each of which will be summarized here). The next version of the tech standard will also bring new applications and use cases. At the end of the post we will also look at a few examples of these principles currently applied.
|
||||
|
||||
Few of the shortcomings of blockchain platforms in existence are listed below with some proposed solutions to those answered afterward.
|
||||
|
||||
### Problem 1: Scalability[1]
|
||||
|
||||
This is seen as the first major hurdle to mainstream adoption. As previously discussed, a lot of limiting factors contribute to the blockchain’s in-capacity to process a lot of transactions at the same time. Existing networks such as [**Ethereum**][3] are capable of measly 10-15 transactions per second (TPS) whereas mainstream networks such as those employed by Visa for instance are capable of more than 2000 TPS. **Scalability** is an issue that plagues all modern database systems. Improved consensus algorithms and better blockchain architecture designs are improving it though as we see here.
|
||||
|
||||
**Solving scalability**
|
||||
|
||||
Implementing leaner and more efficient consensus algorithms have been proposed for solving issues of scalability without disturbing the primary structure of the blockchain. While most cryptocurrencies and blockchain platforms use resource intensive PoW algorithms (For instance, Bitcoin & Ethereum) to generate blocks, newer DPoS and PoET algorithms exist to solve this issue. DPoS and PoET algorithms (there are some more in development) require less resources to maintain the blockchain and have shown to have throughputs ranging up to 1000s of TPS rivalling that of popular non-blockchain systems.
|
||||
|
||||
The second solution to scalability is altering the blockchain structure[1] and functionality altogether. We won’t get into finer details of this, but alternative architectures such as **Directed Acyclic Graph** ( **DAG** ) have been proposed to handle this issue. Essentially, the assumption for this to work is that not all network nodes need to have a copy of the entire blockchain for the blockchain to work or the participants to reap the benefits of a DLT system. The system does not require transactions to be validated by the entirety of the participants and simply requires the transactions to happen in a common frame of reference and be linked to each other.
|
||||
|
||||
The DAG[2] approach is implemented in the Bitcoin system using an implementation called the **Lightning network** and Ethereum implements the same using their **Sharding** [3] protocol. At its heart a DAG implementation is not technically a blockchain. It’s more like a tangled maze, but still retains the peer to peer and distributed database properties of the blockchain. We will explore DAG and Tangle networks in a separate post later.
|
||||
|
||||
### Problem 2: Interoperability[4][5]
|
||||
|
||||
**Interoperability** is called cross-chain interaction is basically different blockchains being able to talk to each other to exchange metrics and information. With so many platforms that is hard to keep a count on at the moment and different companies coming up with proprietary systems for all the myriad of applications, interoperability between platforms is key. For instance, at the moment, someone who owns digital identities on one platform will not be able to exploit features presented by other platforms because the individual blockchains do not understand or know each other. Problems pertaining to lack of credible verifications, token exchange etc. still persist. A global roll out of [**smart contracts**][4] is also not viable without platforms being able to communicate with each other.
|
||||
|
||||
**Solving Interoperability**
|
||||
|
||||
There are protocols and platforms designed just for enabling interoperability at the moment. Such platforms implement atomic swaps protocols and provide open stages for different blockchain systems to communicate and exchange information between them. An example would be **“0x (ZRX)”** which is described later on.
|
||||
|
||||
### Problem 3: Governance[6]
|
||||
|
||||
Not a limitation in its own, **governance** in a public blockchain needs to act as a community moral compass where everyone’s opinion is taken into account on the operation of the blockchain. Combined and seen with scale this presents a problem where in either the protocols change far too frequently or the protocols are changed at the whims of a “central” authority who holds the most tokens. This is not an issue that most public blockchains are working to avoid right now since the scale at their operating in and the nature of their operations don’t require stricter supervision.
|
||||
|
||||
**Solving Governance issues**
|
||||
|
||||
The Tangled framework or the DAG mentioned above would almost eliminate the need and use for global (platform wide) governance laws. Instead a program can automatically oversee the transaction and user type and decide on the laws that need to be implemented.
|
||||
|
||||
### Problem 4: Sustainability
|
||||
|
||||
**Sustainability** builds on the scalability issue again. Current blockchains and cryptocurrencies are notorious for being not sustainable in the long run owing to the significant oversight that is still required and the amount of resources required to keep the systems running. If you’ve read reports of how “mining cryptocurrencies” have not been so profitable lately, this is what it was. The amount of resources required to keep up existing platforms running is simply not practical at a global scale with mainstream use.
|
||||
|
||||
**Solving non-sustainability**
|
||||
|
||||
From a resources or economic point of view the answer to sustainability would be similar to the one for scalability. However, for the system to be implemented on a global scale, laws and regulations need to endorse it. This however depends on the governments of the world. Favourable moves from the American and European governments have however renewed hopes in this aspect.
|
||||
|
||||
### Problem 5: User adoption[7]
|
||||
|
||||
Currently a hindrance to widespread consumer adoption of blockchain based applications is consumer unfamiliarity with the platform and the tech underneath it. The fact that most applications require some sort of a tech and computing background to figure out how they work does not help in this aspect either. The third wave of blockchain developments seek to lessen the gap between consumer knowledge and platform usability.
|
||||
|
||||
**Solving the user adoption issue**
|
||||
|
||||
The internet took a lot of time to be the way it is now. A lot of work has been done on developing a standardized internet technology stack over the years that has allowed the web to function the way it is now. Developers are working on user facing front end distributed applications that should act as a layer on top of existing web 3.0 technology while being supported by blockchains and open protocols underneath. Such [**distributed applications**][5] will make the underlying technology more familiar to users, hence increasing mainstream adoption.
|
||||
|
||||
We’ve discussed about the solutions to the above issues theoretically, and now we proceed to show these being applied in the present scenario.
|
||||
|
||||
**[0x][6]** – is a decentralized token exchange where users from different platforms can exchange tokens without the need of a central authority to vet the same. Their breakthrough comes in how they’ve designed the system to record and vet the blocks only after transactions are settled and not in between (to verify context, blocks preceding the transaction order is also verified normally) as is normally done. This allows for a more liquid faster exchange of digitized assets online.
|
||||
|
||||
**[Cardano][7]** – founded by one of the co-founders of Ethereum, Cardano boasts of being a truly “scientific” platform with multiple reviews and strict protocols for the developed code and algorithms. Everything out of Cardano is assumed to be mathematically as optimized as possible. Their consensus algorithm called **Ouroboros** , is a modified Proof of Stake algorithm. Cardano is developed in [**Haskell**][8] and the smart contract engine uses a derivative of Haskell called **Plutus** for operating. Both are functional programming languages which guarantee secure transactions without compromising efficiency.
|
||||
|
||||
**EOS** – We’ve already described EOS here in [**this post**][9].
|
||||
|
||||
**[COTI][10]** – a rather obscure architecture, COTI entails no mining, and next to zero power consumption in operating. It also stores assets in offline wallets localized on user’s devices rather than a pure peer to peer network. They also follow a DAG based architecture and claim of processing throughputs of up to 10000 TPS. Their platform allows enterprises to build their own cryptocurrency and digitized currency wallets without exploiting a blockchain.
|
||||
|
||||
**References:**
|
||||
|
||||
* [1] **A. P. Paper, K. Croman, C. Decker, I. Eyal, A. E. Gencer, and A. Juels, “On Scaling Decentralized Blockchains | SpringerLink,” 2018.**
|
||||
* [2] [**Going Beyond Blockchain with Directed Acyclic Graphs (DAG)**][11]
|
||||
* [3] [**Ethreum/wiki – On sharding blockchains**][12]
|
||||
* [4] [**Why is blockchain interoperability important**][13]
|
||||
* [5] [**The Importance of Blockchain Interoperability**][14]
|
||||
* [6] **R. Beck, C. Müller-Bloch, and J. L. King, “Governance in the Blockchain Economy: A Framework and Research Agenda,” J. Assoc. Inf. Syst., pp. 1020–1034, 2018.**
|
||||
* [7] **J. M. Woodside, F. K. A. Jr, W. Giberson, F. K. J. Augustine, and W. Giberson, “Blockchain Technology Adoption Status and Strategies,” J. Int. Technol. Inf. Manag., vol. 26, no. 2, pp. 65–93, 2017.**
|
||||
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.ostechnix.com/welcoming-blockchain-3-0/
|
||||
|
||||
作者：[sk][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/译者ID)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.ostechnix.com/author/sk/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://www.ostechnix.com/wp-content/uploads/2019/06/blockchain-720x340.jpg
|
||||
[2]: https://www.ostechnix.com/blockchain-2-0-an-introduction/
|
||||
[3]: https://www.ostechnix.com/blockchain-2-0-what-is-ethereum/
|
||||
[4]: https://www.ostechnix.com/blockchain-2-0-explaining-smart-contracts-and-its-types/
|
||||
[5]: https://www.ostechnix.com/blockchain-2-0-explaining-distributed-computing-and-distributed-applications/
|
||||
[6]: https://0x.org/
|
||||
[7]: https://www.cardano.org/en/home/
|
||||
[8]: https://www.ostechnix.com/getting-started-haskell-programming-language/
|
||||
[9]: https://www.ostechnix.com/blockchain-2-0-eos-io-is-building-infrastructure-for-developing-dapps/
|
||||
[10]: https://coti.io/
|
||||
[11]: https://cryptoslate.com/beyond-blockchain-directed-acylic-graphs-dag/
|
||||
[12]: https://github.com/ethereum/wiki/wiki/Sharding-FAQ#introduction
|
||||
[13]: https://www.capgemini.com/2019/02/can-the-interoperability-of-blockchains-change-the-world/
|
||||
[14]: https://medium.com/wanchain-foundation/the-importance-of-blockchain-interoperability-b6a0bbd06d11
|
||||
@@ -0,0 +1,83 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (arrowfeng)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (5 essential values for the DevOps mindset)
|
||||
[#]: via: (https://opensource.com/article/19/5/values-devops-mindset)
|
||||
[#]: author: (Brent Aaron Reed https://opensource.com/users/brentaaronreed/users/wpschaub/users/wpschaub/users/wpschaub/users/cobiacomm/users/marcobravo/users/brentaaronreed)
|
||||
|
||||
关于 DevOps 思维模式所需具备的5个基本价值观
|
||||
======
|
||||
人和流程比在解决的业务问题的任何技术“银弹”更重要，且需要花更多的时间。
|
||||
![human head, brain outlined with computer hardware background][1]
|
||||
|
||||
今天的许多 IT 专业人士都在努力适应变化和扰动。您是否正在努力适应变化，可以这么说？ 你觉得不堪重负吗？这并不罕见。今天，IT 的现状还不够好，所以需要不断尝试重新自我演进。
|
||||
|
||||
凭借30多年的IT综合经验，我们见证了人们和人际关系的重要性，它有让 IT有效和帮助业务蓬勃发展的能力。但是，在大多数情况下，我们关于IT解决方案的对话始于技术而非人员和流程。寻找“银弹”来解决业务和IT挑战的倾向非常普遍。但你不能只关心创新，DevOps或有效的团队和工作方式;他们需要得到培养，支持和引导。
|
||||
|
||||
由于扰动如此普遍，并且对变革速度存在如此迫切的需求，我们需要纪律和围栏。下面描述的 DevOps 思维模式的五个基本价值观将支持将我们带到那里的实践。这些价值观不是新观念;我们从经验中学到了它们并重构它们。一些值可以互换，它们是灵活的，并且它们指导支持（如支柱）这五个价值观的整体原则。
|
||||
|
||||
![5 essential values for the DevOps mindset][2]
|
||||
|
||||
### 1\. 利益相关方的反馈至关重要
|
||||
|
||||
我们如何知道我们是否为我们创造了比利益相关者更多的价值？ 我们需要持久的质量数据来分析，通知并推动更好的决策。 来自可靠来源的相关信息对于任何业务的蓬勃发展至关重要。 我们需要倾听并理解我们的利益相关者所说的，而不是说我们需要以一种方式实施变革，使我们能够调整我们的思维、我们的流程和技术，并根据需要对其进行调整以使我们的利益相关者满意。由于信息（数据）不正确，我们常常看到很少的变化，或者由于错误的原因而发生的很多变化。因此，将变更与利益相关方的反馈结合起来是一项重要的价值，并有助我们专注于使公司成功最重要的事情。
|
||||
|
||||
|
||||
> 关注我们的利益相关者及其反馈，而不仅仅是为了改变而改变。
|
||||
|
||||
### 2\. 超越当今流程的极限
|
||||
|
||||
我们希望我们的产品和服务能够不断让客户满意——我们最重要的利益相关者。因此，我们需要不断改进。这不仅仅是关于质量;它还可能意味着成本，可用性，相关性以及许多其他目标和因素。创建可重复的流程或使用通用框架是非常棒的，它们可以改善治理和许多其他问题。但是，这不应该是我们的最终目标。在寻找改进方法时，我们必须调整我们的流程，并辅以正确的技术和工具。可能有理由抛弃“所谓的”框架，因为不这样做可能会增加浪费,更糟糕的是只是“货物结果”（做一些没有价值或目的的东西）。
|
||||
|
||||
> 力争始终创新并改进可重复的流程和框架。
|
||||
|
||||
### 3\. 无需新的筒仓来打破旧的筒仓
|
||||
|
||||
筒仓和DevOps是不兼容的。我们始终看到这一点：IT 主管带来了所谓的“专家”来实施敏捷和DevOps，他们做了什么？这些“专家”在现有问题的基础上创建了一个新问题，这是另一个加入 IT 部门的筒仓和一个充满筒仓的企业。创建“DevOps”标题违背了敏捷和DevOps的原则，这些原则基于打破筒仓的概念。在敏捷和DevOps中，团队合作是必不可少的，如果你不在自组织团队中工作，那么你就不会做任何事情。
|
||||
|
||||
> 相互激励和共享，而不是成为英雄或创建一个筒仓。
|
||||
|
||||
### 4\. 了解您的客户意味着跨组织协作
|
||||
|
||||
业务的任何部分都不是一个独立的实体，因为它们都有利益相关者，主要利益相关者始终是客户。“客户永远是对的”（正如我想说的那样，或者是国王）。关键是，没有客户，真的没有业务，而且为了保持业务，如今我们需要与竞争对手“区别对待”。我们还需要了解客户对我们的看法以及他们对我们的期望。了解客户的需求势在必行，需要及时反馈，以确保业务能够快速，负责地满足这些主要利益相关者的需求和关注。
|
||||
|
||||
![Minimize time spent with build-measure-learn process][3]
|
||||
|
||||
无论是想法，概念，假设还是直接的利益相关者反馈，我们都需要通过使用探索，构建，测试和交付生命周期来识别和衡量我们的产品提供的功能或服务。从根本上说，这意味着我们需要在整个组织中“插入”我们的组织。在持续创新，学习和DevOps方面没有任何边界。因此，当我们在整个企业中进行衡量时，我们可以理解整体并采取可行的，有意义的步骤来改进。
|
||||
|
||||
> 衡量整个组织的绩效，而不仅仅是在业务范围内。
|
||||
|
||||
### 5\. 热情鼓舞采纳
|
||||
|
||||
不是每个人都被驱使去学习，适应和改变;然而，就像微笑可能具有传染性一样，学习和意愿成为变革文化的一部分也是如此。在学习文化中适应和演化为一群人提供了学习和传递信息（即文化传播）的自然机制。学习风格，态度，方法和过程不断演化，因此我们可以改进它们。下一步是应用所学和改进的内容并与同事分享信息。学习不会自动发生;它需要努力，评估，纪律，意识，特别是沟通;遗憾的是，这些都是工具和自动化无法提供的。检查您的流程，自动化，工具策略和实施工作，使其透明化，并与您的同事协作重复使用和改进。
|
||||
|
||||
> 通过精益质量的可交付成果促进学习文化，而不仅仅是工具和自动化。
|
||||
|
||||
### 总结
|
||||
|
||||
![Continuous goals of DevOps mindset][4]
|
||||
|
||||
随着我们的公司采用DevOps，我们继续在任何书籍，网站或自动化软件上支持这五个价值观。采用这种思维方式需要时间，这与我们以前作为系统管理员所做的完全不同。这是一种全新的工作方式，需要很多年才能成熟。这些原则是否与您自己的原则一致？在评论或我们的网站上分享。[混乱特工]
|
||||
|
||||
* * *
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://opensource.com/article/19/5/values-devops-mindset
|
||||
|
||||
作者：[Brent Aaron Reed][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[译者ID](https://github.com/arrowfeng)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://opensource.com/users/brentaaronreed/users/wpschaub/users/wpschaub/users/wpschaub/users/cobiacomm/users/marcobravo/users/brentaaronreed
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://opensource.com/sites/default/files/styles/image-full-size/public/lead-images/brain_data.png?itok=RH6NA32X (human head, brain outlined with computer hardware background)
|
||||
[2]: https://opensource.com/sites/default/files/uploads/devops_mindset_values.png (5 essential values for the DevOps mindset)
|
||||
[3]: https://opensource.com/sites/default/files/uploads/devops_mindset_minimze-time.jpg (Minimize time spent with build-measure-learn process)
|
||||
[4]: https://opensource.com/sites/default/files/uploads/devops_mindset_continuous.png (Continuous goals of DevOps mindset)
|
||||
[5]: http://agents-of-chaos.org
|
||||
@@ -1,148 +0,0 @@
|
||||
[#]: collector: (lujun9972)
|
||||
[#]: translator: (geekpi)
|
||||
[#]: reviewer: ( )
|
||||
[#]: publisher: ( )
|
||||
[#]: url: ( )
|
||||
[#]: subject: (Expand And Unexpand Commands Tutorial With Examples)
|
||||
[#]: via: (https://www.ostechnix.com/expand-and-unexpand-commands-tutorial-with-examples/)
|
||||
[#]: author: (sk https://www.ostechnix.com/author/sk/)
|
||||
|
||||
expand 与 unexpand 命令教程与示例
|
||||
======
|
||||
|
||||
![Expand And Unexpand Commands Explained][1]
|
||||
|
||||
本指南通过实际的例子解释两个 Linux 命令，即 **expand** 和 **unexpand**。对于好奇的人，expand 和 unexpand 命令用于将文件中的 TAB 字符替换为空格，反之亦然。在 MS-DOS 中也有一个名为 “expand” 的命令，它用于解压压缩文件。但 Linux expand 命令只是将 tab 转换为空格。这两个命令是 **GNU coreutils** 的一部分，由 **David MacKenzie** 编写。
|
||||
|
||||
为了演示，我将在本文使用名为 “ostechnix.txt” 的文本文件。下面给出的所有命令都在 Arch Linux 中进行测试。
|
||||
|
||||
### expand 命令示例
|
||||
|
||||
与我之前提到的一样，expand 命令使用空格替换文件中的 TAB 字符。
|
||||
|
||||
现在，让我们将ostechnix.txt 中的 tab 转换为空格，并将结果写入标准输出：
|
||||
|
||||
```
|
||||
$ expand ostechnix.txt
|
||||
```
|
||||
|
||||
如果你不想在标准输出中显示结果，只需将其写入另一个文件，如下所示。
|
||||
|
||||
```
|
||||
$ expand ostechnix.txt>output.txt
|
||||
```
|
||||
|
||||
我们还可以将标准输入中的 tab 转换为空格。为此，只需运行 “expand” 命令而不带文件名：
|
||||
|
||||
```
|
||||
$ expand
|
||||
```
|
||||
|
||||
只需输入文本并按回车键就能将 tab 转换为空格。按 **CTRL+C** 退出。
|
||||
|
||||
|
||||
如果你不想在非空白符后转换 tab，请使用 **-i** 标记，如下所示。
|
||||
|
||||
```
|
||||
$ expand -i ostechnix.txt
|
||||
```
|
||||
|
||||
我们还可以设置每个 tab 为指定数字的宽度，而不是 8（默认值）。
|
||||
|
||||
```
|
||||
$ expand -t=5 ostechnix.txt
|
||||
```
|
||||
|
||||
我们甚至可以使用逗号分隔指定多个 tab 位置，如下所示
|
||||
|
||||
```
|
||||
$ expand -t 5,10,15 ostechnix.txt
|
||||
```
|
||||
|
||||
或者，
|
||||
|
||||
```
|
||||
$ expand -t "5 10 15" ostechnix.txt
|
||||
```
|
||||
|
||||
有关更多详细信息，请参阅手册页。
|
||||
|
||||
```
|
||||
$ man expand
|
||||
```
|
||||
|
||||
### unexpand 命令示例
|
||||
|
||||
正如你可能已经猜到的那样，**unexpand** 命令将执行与 expand 命令相反的操作。即它会将空格转换为 TAB。让我向你展示一些例子，以了解如何使用 unexpand 命令。
|
||||
|
||||
要将文件中的空白（当然是空格）转换为 tab 并将输出写入标准输出，请执行以下操作：
|
||||
|
||||
```
|
||||
$ unexpand ostechnix.txt
|
||||
```
|
||||
|
||||
如果要将输出写入文件而不是仅将其显示到标准输出，请使用以下命令：
|
||||
|
||||
```
|
||||
$ unexpand ostechnix.txt>output.txt
|
||||
```
|
||||
|
||||
从标准输出读取内容，将空格转换为制表符：
|
||||
|
||||
```
|
||||
$ unexpand
|
||||
```
|
||||
|
||||
默认情况下，unexpand 命令仅转换初始的空格。如果你想转换所有空格而不是只是初始空格，请使用 **-a** 标志：
|
||||
|
||||
```
|
||||
$ unexpand -a ostechnix.txt
|
||||
```
|
||||
|
||||
仅转换开头的空白（请注意它会覆盖 **-a**）：
|
||||
|
||||
```
|
||||
$ unexpand --first-only ostechnix.txt
|
||||
```
|
||||
|
||||
使多少个空格替换成一个 tab，而不是 **8**（启用 **-a** ）：
|
||||
|
||||
```
|
||||
$ unexpand -t 5 ostechnix.txt
|
||||
```
|
||||
|
||||
相似地，我们可以使用逗号分隔指定多个tab的位置。
|
||||
|
||||
```
|
||||
$ unexpand -t 5,10,15 ostechnix.txt
|
||||
```
|
||||
|
||||
或者，
|
||||
|
||||
```
|
||||
$ unexpand -t "5 10 15" ostechnix.txt
|
||||
```
|
||||
|
||||
有关更多详细信息，请参阅手册页。
|
||||
|
||||
```
|
||||
$ man unexpand
|
||||
```
|
||||
|
||||
|
||||
在处理大量文件时，expand 和 unexpand 命令对于用空格替换不需要的 TAB 时非常有用，反之亦然。
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.ostechnix.com/expand-and-unexpand-commands-tutorial-with-examples/
|
||||
|
||||
作者：[sk][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[geekpi](https://github.com/geekpi)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.ostechnix.com/author/sk/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://www.ostechnix.com/wp-content/uploads/2019/05/Expand-And-Unexpand-Commands-720x340.png
|
||||
105
translated/tech/20190610 Welcoming Blockchain 3.0.md
Normal file
105
translated/tech/20190610 Welcoming Blockchain 3.0.md
Normal file
@@ -0,0 +1,105 @@
|
||||
|
||||
欢迎区块链 3.0
|
||||
======
|
||||
|
||||
![欢迎区块链 3.0][1]
|
||||
|
||||
图片来源：<https://pixabay.com/illustrations/blockchain-network-business-3448502/>
|
||||
|
||||
“Blockchain 2.0” 系列文章讨论了自 2008 年比特币等加密货币问世以来区块链技术的发展。本文将探讨区块链的未来发展。**区块链 3.0** 这一新的 DLT（Distributed Ledger Technology：分布式分类帐技术）技术演进浪潮将回答当前区块链所面临的问题（每一个问题都会在这里总结）。下一版本的技术标准也将带来全新的应用和使用案例。在本文的最后，我们也会看一些当前使用这些原则的案例。
|
||||
|
||||
以下是现有区块链平台的几个缺点，并针对这些缺点给出了建议的解决方案。
|
||||
|
||||
### 问题 1：可扩展性[1]
|
||||
|
||||
这个问题是被普遍认为的第一个主要障碍。正如之前所讨论的，很多因素限制了区块链同时处理大量交易的能力。诸如 [**以太坊**][3] 之类的现有网络每秒能够进行 10-15 次交易（TPS），而像 Visa 所使用的主流网络每秒能够进行超过 2000 次交易。**可伸缩性**是困扰所有现代数据库系统的问题。正如我们在这里看到的那样，改进的共识算法和更好的区块链架构设计正在改进它。
|
||||
|
||||
**解决可扩展性**
|
||||
|
||||
已经提出了更精简、更有效的一致性算法来解决可伸缩性问题，并且不会影响区块链的主要结构。虽然大多数加密货币和区块链平台使用资源密集型的 PoW 算法（例如，比特币和以太坊）来生成区块，但是存在更新的 DPoS 和 PoET 算法来解决这个问题。DPoS 和 PoET 算法（还有一些正在开发中）需要更少的资源来维持区块链，并且已显示具有高达 1000 TPS 的吞吐量，可与流行的非区块链系统相媲美。
|
||||
|
||||
可伸缩性问题的第二个解决方案是完全改变区块链结构[1]和功能。我们不会详细介绍这一点，但已经提出了诸如**有向无环图**（**DAG**）之类的替代架构来处理这个问题。从本质上讲，这项工作假设并非所有网络节点都需要整个区块链的副本才能使区块链正常工作，或者并非所有的参与者需要从 DLT 系统获得好处。系统不要求整个参与者验证交易，只需要交易发生在共同的参考框架中并相互链接。系统不要求通过所有的参与者验证交易，只需要交易发生在共同的参考框架中并相互链接。
|
||||
|
||||
在比特币系统中使用 **Lightning network** 来实现 DAG[2]，而以太坊使用他们的 **Sharding** [3] 协议来实现 DAG。本质上，从技术上来看 DAG 实现并不是区块链。它更像是一个错综复杂的迷宫，只是仍然保留了区块链的点对点和分布式数据库属性。稍后我们将在另一篇文章中探讨 DAG 和 Tangle 网络。
|
||||
|
||||
### 问题 2：互通性[4][5]
|
||||
|
||||
**互通性**被称为跨链访问，是不同区块链之间能够彼此相互通信以交换指标和信息的基础。由于目前很难平衡众多的平台，不同公司为所有无数应用提供专有系统，平台之间的互操作性就至关重要。例如，目前，在一个平台上拥有数字身份的人无法利用其他平台提供的功能，因为各个区块链不理解或了解彼此。这是由于缺乏可靠的验证、令牌交换等有关的问题仍然存在。如果平台之间不能够相互通信，全球推出 [**智能合约**][4] 也是不可行的。
|
||||
|
||||
**解决互通性**
|
||||
|
||||
有一些协议和平台专为实现互操作性而设计。这些平台实现了原子交换协议，并向不同的区块链系统提供开放，以便在它们之间进行通信和交换信息。**“0x (ZRX)”** 就是其中的一个例子，稍后将对进行描述。
|
||||
|
||||
### 问题 3：治理[6]
|
||||
|
||||
公共区块链中的治理不是自身的限制，而是需要像社区道德指罗盘一样，在区块链的运作中考虑每个人的意见。结合规模，能预见这样一个问题，即要么协议更改太频繁，要么协议被拥有最多代币的“中央”权威一时冲动下修改。不过这不是大多数公共区块链目前正在努力避免的问题，因为其运营规模和运营性质不需要更严格的监管。
|
||||
|
||||
**解决治理问题**
|
||||
|
||||
上面提到的复杂的框架或 DAG 几乎可以消除对全球（平台范围）治理法的需要和使用。相反，程序可以自动监督事务和用户类型，并决定需要执行的法律。
|
||||
|
||||
### 问题 4：可持续发展
|
||||
|
||||
可持续性再次建立在可扩展性问题的基础上。当前的区块链和加密货币因长期不可持续而臭名昭著，这是由于仍然需要大量的监督和保持系统运行所需的资源。如果你读过 `最近“挖掘加密货币”已经没有这么大利润` 的相关报道，你就知道“挖矿”图利就是它的本来面目。在主流使用的全球范围内，保持现有平台运行所需的资源量是不现实。
|
||||
|
||||
**解决非可持续性问题**
|
||||
|
||||
从资源或经济角度来看，可持续性的答案与可扩展性的答案类似。但是，要在全球范围内实施这一制度，法律和法规必须予以认可。然而，这取决于世界各国政府。来自美国和欧洲政府的有利举措重新燃起了对这方面的希望。
|
||||
|
||||
### 问题 5：用户采用[7]
|
||||
|
||||
目前，阻止消费者广泛采用基于区块链的应用程序的一个障碍是消费者对平台及其下的技术不熟悉。事实上，大多数应用程序都需要某种技术和计算背景来弄清楚它们是如何工作的，这在这方面也没有帮助。第三波区块链开发旨在缩小消费者知识与平台可用性之间的差距。
|
||||
|
||||
**解决用户采用问题**
|
||||
|
||||
互联网花了很长的时间才发展成现在的样子。多年来，人们在开发标准化互联网技术栈方面做了大量的工作，使网络能够像现在这样运作。开发人员正在开发面向用户的前端分布式应用程序，这些应用程序应作为现有 Web 3.0 技术之上的一层，同时受到下面的区块链和开放协议的支持。这样的 [**分布式应用**][5] 将使用户更熟悉底层技术，从而增加主流采用。
|
||||
|
||||
我们已经从理论上讨论了上述问题的解决方法，现在我们将继续展示这些方法在当前场景中的应用。
|
||||
|
||||
**[0x][6]** – 是一种去中心化的令牌交换，不同平台的用户可以在不需要中央权威机构审查的情况下交换令牌。他们的突破在于，他们如何设计系统使得仅在交易结算后才记录和审查数据块而不是之间（为了验证上下文，通常也会验证交易之前的数据块）。这使在线数字资产交换更快速。
|
||||
|
||||
**[Cardano][7]** – 由以太坊的联合创始人之一创建，Cardano 自诩为一个真正的“科学”平台，拥有大量的审查和严格的协议，用于他们开发的代码和算法。假设 Cardano 的所有内容都在数学上尽可能优化。他们的共识算法叫做 **Ouroboros**，是一种改进的权益证明算法（PoS：Proof of Stake）。Cardano 是在 [**haskell**][8] 开发的，智能合约引擎使用 haskell 的衍生工具 **plutus** 进行操作。这两者都是函数式编程语言，可以保证安全交易而不会影响效率。
|
||||
|
||||
**EOS** – 我们已经在 [**这篇文章**][9] 中描述了 EOS。
|
||||
|
||||
**[COTI][10]** – 一个鲜为人知的架构，COTI 不需要挖矿，而且在运行过程中趋近于零功耗。它还将资产存储在本地用户设备上的离线钱包中，而不是纯粹的对等网络。它们也遵循基于 DAG 的架构，并声称处理吞吐量高达 10000 TPS。他们的平台允许企业在不利用区块链的情况下建立自己的加密货币和数字化货币钱包。
|
||||
|
||||
**参考:**
|
||||
|
||||
* [1] **A. P. Paper, K. Croman, C. Decker, I. Eyal, A. E. Gencer, and A. Juels, “On Scaling Decentralized Blockchains | SpringerLink,” 2018.**
|
||||
* [2] [**Going Beyond Blockchain with Directed Acyclic Graphs (DAG)**][11]
|
||||
* [3] [**Ethreum/wiki – On sharding blockchains**][12]
|
||||
* [4] [**Why is blockchain interoperability important**][13]
|
||||
* [5] [**The Importance of Blockchain Interoperability**][14]
|
||||
* [6] **R. Beck, C. Müller-Bloch, and J. L. King, “Governance in the Blockchain Economy: A Framework and Research Agenda,” J. Assoc. Inf. Syst., pp. 1020–1034, 2018.**
|
||||
* [7] **J. M. Woodside, F. K. A. Jr, W. Giberson, F. K. J. Augustine, and W. Giberson, “Blockchain Technology Adoption Status and Strategies,” J. Int. Technol. Inf. Manag., vol. 26, no. 2, pp. 65–93, 2017.**
|
||||
|
||||
|
||||
|
||||
--------------------------------------------------------------------------------
|
||||
|
||||
via: https://www.ostechnix.com/welcoming-blockchain-3-0/
|
||||
|
||||
作者：[sk][a]
|
||||
选题：[lujun9972][b]
|
||||
译者：[murphyzhao](https://github.com/murphyzhao)
|
||||
校对：[校对者ID](https://github.com/校对者ID)
|
||||
|
||||
本文由 [LCTT](https://github.com/LCTT/TranslateProject) 原创编译，[Linux中国](https://linux.cn/) 荣誉推出
|
||||
|
||||
[a]: https://www.ostechnix.com/author/sk/
|
||||
[b]: https://github.com/lujun9972
|
||||
[1]: https://www.ostechnix.com/wp-content/uploads/2019/06/blockchain-720x340.jpg
|
||||
[2]: https://www.ostechnix.com/blockchain-2-0-an-introduction/
|
||||
[3]: https://www.ostechnix.com/blockchain-2-0-what-is-ethereum/
|
||||
[4]: https://www.ostechnix.com/blockchain-2-0-explaining-smart-contracts-and-its-types/
|
||||
[5]: https://www.ostechnix.com/blockchain-2-0-explaining-distributed-computing-and-distributed-applications/
|
||||
[6]: https://0x.org/
|
||||
[7]: https://www.cardano.org/en/home/
|
||||
[8]: https://www.ostechnix.com/getting-started-haskell-programming-language/
|
||||
[9]: https://www.ostechnix.com/blockchain-2-0-eos-io-is-building-infrastructure-for-developing-dapps/
|
||||
[10]: https://coti.io/
|
||||
[11]: https://cryptoslate.com/beyond-blockchain-directed-acylic-graphs-dag/
|
||||
[12]: https://github.com/ethereum/wiki/wiki/Sharding-FAQ#introduction
|
||||
[13]: https://www.capgemini.com/2019/02/can-the-interoperability-of-blockchains-change-the-world/
|
||||
[14]: https://medium.com/wanchain-foundation/the-importance-of-blockchain-interoperability-b6a0bbd06d11
|
||||
Reference in New Issue
Block a user