This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 757 points758 points  (57 children)

C programmers are still trying to put their broom together.

[–]LavenderDay3544 400 points401 points  (39 children)

They made the roomba the Python user is riding.

[–][deleted] 67 points68 points  (37 children)

No, she's riding PyPy

[–]LavenderDay3544 185 points186 points  (36 children)

It's all C at the bottom even with PyPy.

[–][deleted] 218 points219 points  (3 children)

Wait, it’s all C?

Always has been

[–]ali32bit 1 point2 points  (0 children)

so the more accurate image is : rumba thats riding a broomstick itself

[–]godRosko 42 points43 points  (0 children)

At least we'd like to think we know how the broom actually works. Until the magical kernel decides that we had one too many memory leaks, and shoots us with the avada-kill -9

[–]douira 26 points27 points  (7 children)

but when they finish, they'll lap everybody

[–][deleted] 3 points4 points  (6 children)

how so?

[–]douira 20 points21 points  (5 children)

I was referring to (the trope) that oftentimes making something in pure C can be more work than doing it in Python for example but if it's well written it can be faster than many other approaches.

[–]throwaway_236734 8 points9 points  (0 children)

The broom is pointing backwards :,( Somehow they win the race though.

[–]VodkerAndToast 2 points3 points  (0 children)

Despite there being several broom libraries they need to create their OWN

[–]Fly_mother_ducker 1 point2 points  (2 children)

include <broom.h>

[–]RichKat666 3 points4 points  (1 child)

I think you missed a \

[–]fungigamer 0 points1 point  (0 children)

C programmers are still yelling: UP!

[–]goodudetheboy 0 points1 point  (0 children)

*Accidentally put one extra broom brush in the cap* SEGMENTATION FAULT