srrrse @withoutboats Twitter profile

Pinned Tweet

srrrse

5 years

People always ask me how do you balance being the best programmer in the world with being incredibly popular and attractive? And I always tell them, you know, it’s not easy

19

26

231

Last Seen Profiles

@TracycCoyle

@GreeN_l20l

@StacyWi98227571

@JHolme5

@Runkeeper

@nickleach0

@ArtSora238449

@uazuay

@MisterA_0

@DeanSmi47962704

@tearsforiki

@crashdayeen

@NolaAngelMediun

@Lil_cubbie

@DuboseRuby34233

@naritasprint

@JeromeAnthonyM6

@SSN_Talks

@SiphosethuSiha6

@Subnautica

@_TS_LOVE_

@Andriestshepo01

@saka_seiso

@FIILolo

@clegfx

@spitefulstar

@tanjarueedy

@Bullis_Track

@CindyNicol91911

@leadwithgather

@itsmaggiem

@NatashaRic47968

@ddaymn

@med_mum

@starchildxxxxxx

@SylvesterMbath8

srrrse

@withoutboats

3 years

The best thing young people can do early in their career is get ridiculous lucky breaks repeatedly, in my experience

6

119

1K

srrrse

@withoutboats

4 years

Firefox market share vs Mozilla Foundation chair salary (2.5 million/year in 2018)

22

396

1K

srrrse

@withoutboats

10 months

just read the phrase “if you overload the comma operator” and I’m thinking about all the people who say Rust is as complicated as C++

5

33

535

srrrse

@withoutboats

7 months

Why Rust chose async/await

8

99

488

srrrse

@withoutboats

4 years

Shamefully, Mozilla has still not addressed their absurd executive compensation. The C levels are stripping Mozilla for cash

srrrse

@withoutboats

4 years

Firefox market share vs Mozilla Foundation chair salary (2.5 million/year in 2018)

22

396

1K

7

147

433

srrrse

@withoutboats

11 days

Rust needs generators so people stop writing code like this.

zack (in SF)

@zack_overflow

12 days

Whenever someone says they think Rust is a very low-level language I show them this:

136

68

1K

24

8

414

srrrse

@withoutboats

3 years

The biggest failure in Rust‘s communication strategy has been the inability to explain to non-experts that unsafe abstractions are the *point*, not a sign of failure

13

27

365

srrrse

@withoutboats

5 years

Open source is the unpaid internship of computer programming.

15

77

357

srrrse

@withoutboats

6 years

an example of the importance of affordances for new users: i would probably be more productive if i learned how to use a debugger, but no debugger has ever been easier to start using than adding more printlns.

18

89

353

srrrse

@withoutboats

3 years

The reason I use GitHub and Twitter is actually because I am a big idiot, FYI

27

20

352

srrrse

@withoutboats

6 years

MONADS AND RUST A THREAD - or - why async/await instead of do notation

7

89

354

srrrse

@withoutboats

6 years

async/await RFC has been merged as RFC 2394!

7

124

332

srrrse

@withoutboats

5 years

Storm warning: comment hurricane incoming on the rust repo. We are stabilizing async/await

[Stabilization] async/await MVP · Issue #62149 · rust-lang/rust

Stabilization target: 1.38.0 (beta cut 2019-08-15) Executive Summary This is a proposal to stabilize a minimum viable async/await feature, which includes: async annotations on functions and blocks,...

github.com

14

78

321

srrrse

@withoutboats

3 months

Let futures be futures

5

46

310

srrrse

@withoutboats

7 months

tokio IS "thread-per-core" - the controversy in the Rust community is about a tradeoff between work-stealing and share-nothing

10

38

252

srrrse

@withoutboats

5 years

All I want for Rust 2019 is massive organizational debt clean up

Organizational Debt

We all know that classic aphorism: Year comes to an end, Rust blog post press send. This is mine. There are lots of cool technical improvements to Rust that I want the project to achieve this year, …

boats.gitlab.io

11

52

253

srrrse

@withoutboats

7 years

Lowkey personal life update: starting today I am a research engineer at Mozilla working on Rust.

21

4

246

srrrse

@withoutboats

4 years

The power of Rust isn’t memory safety, it’s memory-safe zero-cost abstraction. This is why “C with a borrow checker” would never work; you don’t just need the borrow checker, you need everything else Rust brings along too

3

36

245

srrrse

@withoutboats

5 years

Oh by the way we are stabilizing the futures API in 1.35

[Stabilization] Future APIs · Issue #59725 · rust-lang/rust

Feature name: futures_api Stabilization target: 1.36.0 Tracking issue: #59113 Related RFCs: rust-lang/rfcs#2592 Futures API rust-lang/rfcs#2394 async/await (closed) rust-lang/rfcs#2395 Futures API ...

github.com

12

43

247

srrrse

@withoutboats

3 years

“C with a borrow checker” simply wouldn’t work because it would not allow users to create safe abstractions. The safe abstractions are the POINT of Rust

5

26

242

srrrse

@withoutboats

3 years

“Excited” to hear about all the data races now that people will actually execute all their code under ARMs memory model

7

25

235

srrrse

@withoutboats

2 months

There are cathedrals everywhere for those with eyes to see

Kurtosis

@thekurtwk

2 months

FreeCAD's build dependency graph in Debian, made using the `debtree` tool

48

135

1K

0

18

233

srrrse

@withoutboats

4 years

We’re on our way to a WebKit only world but at least the Mozilla C levels got their “market value”

3

22

220

srrrse

@withoutboats

8 months

Absolutely bonkers to me that this take could be controversial

simp 4 satoshi

@iamgingertrash

8 months

Controversial take: GPT-4 is actually making me a really bad developer. I often have too little context on the intricacies of the code it generates and so my code is riddled with bugs and broken

173

33

837

3

31

221

srrrse

@withoutboats

1 year

I’m going to write some blog posts with my thoughts on Rust in 2023. The first post is here, about control-flow effects and the idea that programming languages have “registers”

9

38

219

srrrse

@withoutboats

8 months

What I love about “premature optimization is the root of all evil” is that it comes from Knuth, and it was written in the context of arguing for using GOTO to optimize code, an opinion no one repeating the quote would agree with.

6

19

217

srrrse

@withoutboats

6 months

how I think async Rust should evolve over the next few years:

3

27

205

srrrse

@withoutboats

3 years

At least once a week I think about deciding to make async/await the highest possible priority in 2018 and how well that has payed off for Rust.

12

7

204

srrrse

@withoutboats

6 months

I believe the Rust project should immediately stabilize AsyncIterator with poll_next. Here I explain why:

7

34

201

srrrse

@withoutboats

4 years

A lot of Rust users seem to think the point of Rust is that it’s harder, but the point is actually that it’s easier

8

20

195

srrrse

@withoutboats

4 years

The worst thing the free software movement did was convince was convince every dev w a half-ass understanding of law and politics that software licensing could be an effective tool for political change

3

23

191

srrrse

@withoutboats

3 years

Time to own up to it: I was wrong about .await

2

11

196

srrrse

@withoutboats

4 years

Shipping const generics in 2020

7

60

192

srrrse

@withoutboats

6 years

Hot take: I agree that it would be a waste of time to rewrite UNIX in Rust when instead you could write something better than UNIX.

6

34

184

srrrse

@withoutboats

3 years

Traditional tools like C have trained software engineers to have such low expectations that they can’t imagine upgrading their tool chain every 6 weeks to be a non-issue

2

13

183

srrrse

@withoutboats

4 years

Not to be evangelistic but this week alone these projects indicated they are looking at writing components in Rust: Linux, Android, React.

1

23

182

srrrse

@withoutboats

4 years

Is there a lua to wasm compiler called waluigi yet? You’re welcome

3

42

179

srrrse

@withoutboats

4 years

5 years ago I was sleeping on couches teaching myself to code. Mostly learning Rust even tho I knew I should focus on algorithms and web dev to get a job. I remember wishing I could get a mega bus to SF for the release party. What a wild ride!

3

6

181

srrrse

@withoutboats

8 months

“Thread per core” arguments conflate two stories: - I have carefully optimized my tasks to guarantee balanced work among threads and therefore can avoid the synchronization costs of work stealing - wahh wahh wahh sharing state in a thread safe way is hard I don’t wanna

6

8

174

srrrse

@withoutboats

7 years

Rust's secret weapon is actually that there are many people who aren't writing low level code yet who could be.

6

45

171

srrrse

@withoutboats

3 years

It’s so crazy that software engineering practices are determined in forums filled with dilettantes and cranks making statements to one another that are completely wrong

2

19

170

srrrse

@withoutboats

5 years

What I would do if I were designing an application language

Notes on a smaller Rust

Many people who use Rust for a bit - especially those who like the language but do not fall in love with it - feel a sense that there must be a smaller, simpler variation on the same theme which...

boats.gitlab.io

11

36

168

srrrse

@withoutboats

5 years

A final proposal for await syntax

This is an announcement regarding the resolution of the syntax for the await operator in Rust. This is one of the last major unresolved questions blocking the stabilization of the async/await...

boats.gitlab.io

14

50

164

srrrse

@withoutboats

4 years

Low key getting const generics shipped this year in my free time for fun 💅

2

4

163

srrrse

@withoutboats

5 years

If I were creating a programming language, I would simply make it memory safe and free of data races without any garbage collection.

7

8

161

srrrse

@withoutboats

6 years

Almost as excruciatingly painful as watching you reinvent severly-impaired axiology to justify inviting white supremacists to your crappy conference

6

21

152

srrrse

@withoutboats

1 year

It should be embarrassing to every language other than rust that so many people want to use it to write single threaded web servers. Literally all you should need to capture this mindshare is ADTs and decent generics

10

14

159

srrrse

@withoutboats

4 years

I am looking for work. 😇 reach out if you think you have an opportunity that would interest me

7

119

150

srrrse

@withoutboats

1 year

Seems like Graydon doesn't tweet these days so I'll share this here. Graydon Hoare on Rust governance & culture:

3

35

150

srrrse

@withoutboats

4 years

Mozilla’s financials for 2019 are not yet online, but here is some candid information about their financial position (gleaned from their public reports) up to December 31, 2018.

1

58

138

srrrse

@withoutboats

6 months

I bought Berkeley Mono and I’m loving it (also, async iterator blog post preview)

4

1

138

srrrse

@withoutboats

5 years

Rust doesn’t have exceptions

GitHub - withoutboats/fehler: Rust doesn't have exceptions

Rust doesn't have exceptions. Contribute to withoutboats/fehler development by creating an account on GitHub.

github.com

10

31

137

srrrse

@withoutboats

1 year

eventually, you have to say something. My thoughts on the governance of the Rust project:

2

25

135

srrrse

@withoutboats

5 years

Tired of moralizing about the way people write software when we should be moralizing about the power relations that determine how people write software

3

20

128

srrrse

@withoutboats

4 years

you love to see it

2

0

132

srrrse

@withoutboats

6 years

async/await is now on nightly! We're still waiting on futures 0.3 for it to really be usable, but if you do enough legwork you can test it on the playground:

6

36

132

srrrse

@withoutboats

6 years

Super stoked to share with everyone this project I've been working on. I've implemented a garbage collector as a Rust library

Shifgrethor I: Garbage collection as a Rust library

I’m really excited to share with you an experiment that I’ve been working on for the past 5 or 6 weeks. It’s a Rust library called shifgrethor. shifgrethor implements a garbage …

boats.gitlab.io

6

23

130

srrrse

@withoutboats

7 years

the C apologism strikeforce, ready to protect C from the evil Rust conspiracy of making C a hard language to use in 1973

4

30

129

srrrse

@withoutboats

5 years

Futures + async/await is an enormous achievement by the Rust project, with considerable resources and the insights of at least a half dozen of the biggest contributors to a Rust behind it.

3

15

125

srrrse

@withoutboats

6 years

I Blogged a Blog about explicit being better than implicit

Not Explicit

Oftentimes when I am conversing about the design of Rust with other users - as on RFCs or the internals forum - I witness a peculiar remark about “explicitness.” It usually goes something …

boats.gitlab.io

13

49

127

srrrse

@withoutboats

4 years

Would people be interested in watching a stream explaining how pin works (up to and including the recent soundness issue)

16

3

124

srrrse

@withoutboats

6 years

The Rust standard library will have a Future trait starting in the next nightly!

Auto merge of #51263 - cramertj:futures-in-core, r=aturon · rust-lang/rust@19d0b53

Add Future and task system to the standard library This adds preliminary versions of the `std::future` and `std::task` modules in order to unblock development of async/await (https://github.com/ru...

github.com

3

28

122

srrrse

@withoutboats

6 years

The culmination of our work the last 4 months: an RFC for async/await notation in Rust!!!

Async & Await in Rust: a full proposal

I’m really excited to announce the culmination of much of our work over the last four months: a pair of RFCs for supporting async & await notation in Rust. This will be very impactful for …

boats.gitlab.io

5

35

124

srrrse

@withoutboats

6 years

In Rust we don't say "what's the most terrible program that compiles" we say `fn main()where for<'a>():'a+,{match(){|(..)=>{},}}` and i think thats beautiful

7

36

117

srrrse

@withoutboats

10 months

when I was a child I stole an amulet from an evil witch and so now I am cursed forever to read takes on how Rust shouldn’t have async from people who don’t know that the stackless coroutine state machine transform exists or the performance pitfalls of segmented stacks

1

5

122

srrrse

@withoutboats

7 years

when a C programmer talks about how Rust is too hard to use I'm like.. we have a hashmap in our standard library tho

4

13

121

srrrse

@withoutboats

6 years

Blogging about async/await in Rust (will be a series):

Async/Await I: Self-Referential Structs

This is the first in a series of blog posts about generators, async & await in Rust. By the end of this series, I will have a proposal for how we could expediently (within the next 12 months) …

boats.gitlab.io

4

43

119

srrrse

@withoutboats

2 years

Rust should be the best memory unsafe language.

4

9

119

srrrse

@withoutboats

4 years

Since people are going to talk about this now, I might as well make my definitive contribution to the discussion:

A brief apology of Ok-Wrapping

I’ve long been a proponent of having some sort of syntax in Rust for writing functions which return results which “ok-wrap” the happy path. This is has also always been a feature …

boats.gitlab.io

22

30

119

srrrse

@withoutboats

6 years

IN CONCLUSION: a design that works in a pure FP which lazily evaluates and boxes everything by default doesn't necessarily work in an eager imperative language with no runtime.

4

17

115

srrrse

@withoutboats

4 years

the Rust small std philosophy made a lot of sense at 1.0, and there are many areas where it still makes sense, but when a widely used 3rd party library has had a stable, successful API for several years, we should consider incorporating it into std.

8

6

118

srrrse

@withoutboats

5 years

Update on await syntax

In my previous post I said that the lang team would be making our final decision about the syntax of the await operator in the May 23 meeting. That was last Thursday, and we did reach a decision. In …

boats.gitlab.io

6

33

116

srrrse

@withoutboats

5 years

A thing I’ve loved about working on async/await is how analogous it’s felt to the rest of Rust. An accessible UX to write apps built on top of little bits of low level abstractions. It’s really enforced how well designed the rest of Rust is

1

14

115

srrrse

@withoutboats

6 years

A PR has just landed to make methods with custom self types (like `self: Rc<Self>`) object safe. This was the biggest implementation blocker for stabilizing the Future API. mikeyhew's been working on this epic since April! 🥳🎉

Take 2: Implement object-safety and dynamic dispatch for arbitrary_self_types by mikeyhew · Pull...

This replaces #50173. Over the months that that PR was open, we made a lot of changes to the way this was going to be implemented, and the long, meandering comment thread and commit history would h...

github.com

3

19

116

srrrse

@withoutboats

3 years

And what this also means is that any two correctly implemented safe abstractions can be *composed* together and it is guaranteed to also be safe. Composable safe zero cost abstractions is the value that Rust brings

1

8

114

srrrse

@withoutboats

8 months

programming languages should have creative directors

1

14

114

srrrse

@withoutboats

5 years

One thing I learned about myself on my break from Rust was that I enjoy hanging out with my friends more than I like talking about programming on the internet with people who don’t seem to respect me or my time. 🙃

1

113

srrrse

@withoutboats

6 years

(🤔 (🤔🤔))

4

12

107

srrrse

@withoutboats

6 years

github was never a "neutral third party" lol its a private company with a 2bn dollar valuation. hacker newsies believe some wild stuff

3

13

112

srrrse

@withoutboats

3 years

I’m really envious of Zig and Swift’s C integration experience. There’s no reason Rust couldn’t ship clang and bindgen and give you a simple include syntax too

6

111

srrrse

@withoutboats

8 months

Some thoughts about auto traits, linear types, and changing the rules of Rust

6

16

109

srrrse

@withoutboats

3 years

Thinking about my favorite piece of code I ever wrote 💞

8

5

109

srrrse

@withoutboats

4 years

Safe bindings to io-uring. Gonna blog about this later but since idk how much I’ll do on this I thought I’d just open source it immediately:

GitHub - ringbahn/ringbahn: safe bindings to io-uring

safe bindings to io-uring. Contribute to ringbahn/ringbahn development by creating an account on GitHub.

github.com

7

17

108

srrrse

@withoutboats

5 years

Things I’ve been thinking about zero cost abstractions:

Zero Cost Abstractions

The idea of a zero cost abstraction is very important to certain programming languages, like Rust and C++, which intend to enable users to write programs with excellent performance profiles with …

boats.gitlab.io

4

22

104

srrrse

@withoutboats

6 years

My only opinion about trains stations is,, they should have the name of the station on Every surface I can see from the train

1

19

102

srrrse

@withoutboats

3 months

How to support asynchronous clean-up in Rust

3

18

105

srrrse

@withoutboats

4 years

personal announcement: from 2020 onward I’m living permanently (i hope 😅) in Berlin 🥳

6

0

103

srrrse

@withoutboats

6 years

The problem with rustc and cargo is that sometimes I have to use other tools and when I do I am constantly mad

4

13

104

srrrse

@withoutboats

6 years

3

15

101

srrrse

@withoutboats

4 years

Revisiting a “smaller Rust” with a new idea: data types vs resource types

10

18

102

srrrse

@withoutboats

11 months

Every few weeks I get to read on hacker news how my work would have been so much better if I had just thought of this idea that I was definitely aware of. It’s a great experience I recommend to everyone.

1

4

103

srrrse

@withoutboats

8 months

@fasterthanlime Completely exhausted by these posts that basically don’t want Rust’s performance profile and aren’t willing to learn how it works to get that and then blame the language for being what it is.

4

3

103

srrrse

@withoutboats

6 years

The last few weeks I've been working on a side project: signing my git commits without using GPG.

Signing my git commits without GPG

Unlike most git users, I try to sign my commits. Unfortunately, the only way to do this right now is to use PGP signatures, because that is all that git is able to integrate with. This has meant that...

boats.gitlab.io

7

35

100

srrrse

@withoutboats

4 years

Ringbahn is a new take on using io-uring with async/await in Rust. Here I start to explain how it works

Ringbahn: a safe, ergonomic API for io-uring in Rust

In my previous post, I discussed the new io-uring interface for Linux, and how to create a safe API for using io-uring from Rust. In the time since that post, I have implemented a prototype of such...

boats.gitlab.io

2

26

102

srrrse

@withoutboats

3 years

People who say the unsafe superset proves ruins rust’s guarantees are missing the point in exactly the same way: the language has been designed to support safe abstractions with unsafe implementations. That’s the whole idea!

1

6

101

srrrse

@withoutboats

6 years

how is this website free

13

11

98

srrrse

@withoutboats

4 years

From failure to Fehler:

From failure to Fehler

About two and a half years ago I wrote a Rust library called failure, which quickly became one of the most popular error handling libraries in Rust. This week, its current maintainer decided to …

boats.gitlab.io

0

31

97

srrrse

@withoutboats

1 year

1

9

98

srrrse

@withoutboats

5 years

For the last month and a half or so I’ve been looking at integrating io_uring into Rusts async ecosystem. Here’s the first step

iou: Rust bindings for liburing

Today I’m releasing a library called iou. This library provides idiomatic Rust bindings to the C library called liburing, which itself is a higher interface for interacting with the io_uring …

boats.gitlab.io

3

24

96