Corefxlab: Logo for Span<T> should be Spanatee the Manatee

[Eilon]

It has become clear that the new Span<T> type needs a logo. Every good type should have a logo.

I have two highly artistic ideas to toss around for the official logo of the Span<T> type. It revolves around the character of Spanatee the Manatee (it rhymes, and "Spanatee" sounds like "Span of T").

I will post each idea as its own comment so that people can vote on it. Feel free to post additional ideas (one per comment) for voting. This is not final artwork; we would presumably hire a world-renowned artist to do the final artwork.

[Eilon]

Idea 1: Bracketed manatees showing the generic shape of <T>:

[Eilon]

Idea 2: Spanatee the Manatee him/herself with <T> on its body:

[JimBobSquarePants]

[jstclair]

Clearly should be a manatee drinking a cup of tea. Preferably with a top hat and monocle

[JvanderStad]

Clearly we should ask Roland Tamayo if we may use his manatee as a mascotte for Span<T>

(Source: https://www.instagram.com/p/BB8L6jnQDIo/)

[KrzysztofCwalina]

This one even has "the cloud" in the background. Though, what's up with all the pollution? Shouldn't it be kittens and flowers coming out of the chimneyspiplelines?

[JvanderStad]

Maybe it's a visual representation of the new System.IO.Pipelines namespace? (https://github.com/dotnet/corefxlab/pull/980).. +1 on the kittens & flowers

[benaadams]

Though, what's up with all the pollution

Isn't pollution, its the air being "on fire" due to the high speed...

[KrzysztofCwalina]

"Span: the 8th wonder of the 21st century. It makes even manatees fly really really fast."

[Drawaes]

Unless there is more bounds checks... then they lose speed and can't
generate enough lift and die... wont someone please think of the poor
Manatees!

On 29 Nov 2016 4:46 p.m., "Krzysztof Cwalina" [e-mail]
wrote:

"Span: the 8th wonder of the 21st century. It makes even manatees fly
really really fast."

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dotnet/corefxlab/issues/1034#issuecomment-263626037,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APpZuZ65HHOAkbAuUiZCVSokEjb_G4oZks5rDFbOgaJpZM4K-mcs
.

[joshfree]

nice mspaint skills @Eilon! 😄

[mmanela]

@Eilon I think you are looking at this all wrong. I think of it more as referring to the incredible wingspan of the timeless Mr. T.

[Eilon]

@mmanela I can't believe I didn't think of that!

[terrajobst]

Mr T is already taken by MRT, the managed runtime :-)

[filipw]

Coincidentally Spant in German is a ship frame, which, after all, "gives the ship its shape and strength".

Very fitting (pun intended).

[richardszalay]

Related: can we use OhTheHugeSpanOfTException when the requested size is too large?

[omariom]

[CaptainEasyCode]

Spants - the superior pants.

[KrzysztofCwalina]

Now that Span moved to the corefx repo, we lost the ability to have logos for individual types, and so we cannot have a logo for Span.

Corefx does support one giant logo for all types. In this logo, some special types got 24 pixels (logolets) to use for their individual logo needs. You might want to talk to all the .net stakeholders, convince them that Span deserves a logolet, get the pixels allocated, and then come up with a way to represent a manatee in 24 pixels.

It's just better like this. The logo architecture was painstakingly designed over the last few years, and we concluded many logos are bad. Yes, the architectural we settled on results in blank reserved spaces in the giant logo, but we have plans to throw NotSupportedException when this part of the logo is decoded using our image manipulation libraries. Also, it might be hard to convince the stakeholders that your type deserves the logolet, so your type might not end up in the logo for many years, or ever.

[Eilon]

I am disappointed.

😆