Created a bunch of text editors which are inferior to emacs and vim anyway

>created a bunch of text editors which are inferior to emacs and vim anyway
>worked on the supposed "successor" of unix, which failed miserably
>created a meme language
>sold his soul to G and became gay
>idolized
I don't understand.

Attached: Rob-pike-oscon.jpg (1280x853, 37K)

can someone give me a quick rundown on things he did in Plan 9? I am only aware of rio and sam/acme and probably libthread

Reject every framework created by Google.

gave us utf-8

Yep, all the worst parts of Plan9.

ken did

Attached: utf8-history.png (563x89, 11K)

>>sold his soul to G and became gay
I thought posting on G automatically made everyone gay.

Nobody needed this, ASCII is fine.

weebs do.

He is what happens when an engineer is motivated by attaching achievements to his name instead of wanting to solve problems or at least create cool shit.

I've always loved Pike's ideas of network-first computing. I think Go is a shit language, but it solved a lot of issues for people working on low level networking, and they love it.

It 2018, and we still struggle to make multi-threaded software.

He was also always a weirdo.

google is a cult

>It 2018, and we still struggle to make multi-threaded software.
Sooner or later, this fad will pass. Programming is fundamentally single-threaded. Imperative is the standard for a reason.

Google makes you into an insufferable faggot.

>did nothing
>still alive
kys

multi-threaded/distributed software is the way to go to get more performance these days since just waiting for a more powerful(for each thread/core) processor isn't going to be an effective strategy

Then don't wait for faster processors. Speed up your software by writing it in C assuming you're not a total idiot.

>I don't write my programs in C
also there is still a limit to single thread/single core processing

No Android for you.

>anyway
using that word as part of your argument means you have no argument

sure, I'll wait in the main thread for this file to open, since programming should be single-threaded
I'll also wait for this image to be rendered to compute my games physics, and then I'll be able to update the UI for some ms, before the next task
imperative is the standard because most programmers are brainlets

If you want other computations to happen, do them in another process

We already do.

Algorithms make a much bigger dent in computational speed than hardware or getting closer bare metal.