or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Syncing
xxxxxxxxxx
Five years on the Rust core team: a retrospective - Steve Klabnik
由於場地問題,第二天我們移動到另一棟大樓啦!議程教室變動請見網站上的議程表。
歡迎來到 https://hackmd.io/@coscup/2019 共筆
- The image file may be corrupted
- The server hosting the image is unavailable
- The image path is incorrect
- The image format is not supported
Learn More →點擊本頁上方的 開始用 Markdown 一起寫筆記!
手機版請點選上方 按鈕展開議程列表。
What is Rust
to build reliable and effucuent software
2010: Rust began
2015: Rust version 1.0
2018: Working groups
2019: We are here!
Steve Klabnik have 7 years write Rust experience
Rust Language Blog
Rust and Rust Governance
who makes decision?
2010 <=> informal
As projects grow => who make decision? (because some Enterprise like facebook start to use it)
Problem
BDFL "Benevolent Dictator For Life"
Core Team
Rust: Core Team
____: "I don't want to be the BDFL."
No oppunity to go BDFL: the origional guy quits.
Core Team
Problem: Core Team don't scales. Too many decidions to make.
Solution: Add even more teams.
Sub teams:
Core Team: Make sure the groups do their work.
Problems: Inflexible, and not every team wants RFCs.
Solution: Even more teams + Working Groups
Working Groups: sort of like teams but not have the power to make desicions.
Over 100 people have the to decide the way how Rust goes.
240 Comments on one RFC of renaming int/uint
"No new rationals" rule: only make decisions that has been debated in public.
"A final proposal for await syntax" becomes a better decition making process then the int/uint problem
Say what you want to do first
Problem: Comments are like DDoS attack. Just one person writes the RFC, but have to reply to all the problems.
有能力設計好好語言 和有時間回覆大量留言 的是不同種人
Do We Need a "Rust Foundation"?
Huge distraciton. Become nesty.
Leadership im more places
Currently leadership is mostly based in the US and Europe. Not so global.
Welcomeing.
But harder to schedule meetings.
QA
Q: How do you decide how to accept members?
Every team can decide the way they accepts new members.
e.g.: Core Team: If everyone agrees, you can join.
–
Q: Who is responsible to do things like, merge PRs?
There're many repos.
…
There is a bot. No one have actual control to merge code. The bot will confirmation the tasts passes, …etc. and merge the code.
"I want it to be exists, but I don't want to do the process"
雞生蛋蛋生雞:沒有錢無法成立基金會、沒有基金會無法收錢
夢想:大企業直接拿一筆錢請他們成立基金會
小問題:Rust 的商標在 Mozilla 手上
還沒跟 Mozilla 問(?
tags:
COSCUP2019
綜合
IB101