feat(icons): add lambda icon - #4017

Added or changed icons

Preview cohesion

Preview stroke widths

DPI Preview

16px (shadcn/ui)

24px (default)

32px (shadcn/ui + retina)

48px (default + retina)

Icon X-rays

Icon Diffs

Icon Symmetry

Flip Horizontal

Flip Vertical

Flip Diagonal

Rotate 180°

const LambdaIcon = createLucideIcon('Lambda', [
  ["path",{"d":"M11.38 10 5 20"}],
  ["path",{"d":"M19 18a2 2 0 01-2 2c-4.87-.003-5.052-16-10-16a2 2 0 00-2 2"}]
])

Small visual weight.

Small visual weight.

That's on purpose, see the Discord thread that led to this PR: https://discord.com/channels/723074157486800936/723088308011270186/1462728117687812196

That h is also too small, no?

My vote is for not adding icons that violate the guidelines.

That h is also too small, no?

Maybe yes, but... must all icons really be of the same weight regardless of context? I agree, that aiming for roughly the same optical volume is desirable, but surely, letters such as these also need to be in balance with each other. A lowercase i or an exclamation point ! will never be the same optical volume as an uppercase W for example, but all of these have very legit use cases as icons (information, warning, wiki).

I think we need to be a bit more flexible about bending the rules when bending the rules is common sense. 🙂

Maybe we should stop adding things that are part of typography?
I feel like you are right and there is conflict between those two types of shapes.

Maybe we should stop adding things that are part of typography? I feel like you are right and there is conflict between those two types of shapes.

I disagree. For disallowing brand icons, it's understandable, even if there's quite a bit of grumbling from some people. But disallowing typography would make less sense, lucide has icons like https://lucide.dev/icons/pi, https://lucide.dev/icons/omega, https://lucide.dev/icons/sigma, their variants, etc.

Unless if removing these icons will be done in the future (given the age of these icons, I don't think it's wise to do so, and it will look like unnecessary purism to any outside observer), adding lambda to the set makes sense.

Maybe we should stop adding things that are part of typography? I feel like you are right and there is conflict between those two types of shapes.

I disagree. For disallowing brand icons, it's understandable, even if there's quite a bit of grumbling from some people. But disallowing typography would make less sense, lucide has icons like https://lucide.dev/icons/pi, https://lucide.dev/icons/omega, https://lucide.dev/icons/sigma, their variants, etc.

Unless if removing these icons will be done in the future (given the age of these icons, I don't think it's wise to do so, and it will look like unnecessary purism to any outside observer), adding lambda to the set makes sense.

I completely disagree with the reasoning, but I'm probably much more in favour of allowing typographic icons, even single letters, since they do have very valid use cases and using text instead of them:

1. is probably not going to end up looking very consistent.
2. is probably not very good UX or devX for people to have to add two entire typesets for just a bold/heading (Comfortaa) and an italic (Courier Prime) icon

²

The above, I think is actually a pretty good illustration of heading not really being out of proportion, but maybe some others are too large (looking at you, link and message-square-share)

But should we phase out typography, my vote is for documenting Comfortaa@23pt and CourierPrime@30pt as alternates:

Maybe we should stop adding things that are part of typography? I feel like you are right and there is conflict between those two types of shapes.

I disagree. For disallowing brand icons, it's understandable, even if there's quite a bit of grumbling from some people. But disallowing typography would make less sense, lucide has icons like https://lucide.dev/icons/pi, https://lucide.dev/icons/omega, https://lucide.dev/icons/sigma, their variants, etc.
Unless if removing these icons will be done in the future (given the age of these icons, I don't think it's wise to do so, and it will look like unnecessary purism to any outside observer), adding lambda to the set makes sense.

I completely disagree with the reasoning, but I'm probably much more in favour of allowing typographic icons, even single letters, since they do have very valid use cases and using text instead of them:

1. is probably not going to end up looking very consistent.

2. is probably not very good UX or devX for people to have to add two entire typesets for just a bold/heading (Comfortaa) and an italic (Courier Prime) icon

²

The above, I think is actually a pretty good illustration of heading not really being out of proportion, but maybe some others are too large (looking at you, link and message-square-share)

But should we phase out typography, my vote is for documenting Comfortaa@23pt and CourierPrime@30pt as alternates:

Fair.

Apologies for grave bumping, is there any updates on adding lambda?