pinchy

u/pinchy@lemmy.world
1 posts · 32 comments

Recent posts

Recent comments

When the review bottleneck is solved by being bypassed the client/end-user becomes the "bottleneck". Why can’t he just approve whatever I’m throwing at him and call it a day? \s

There is no such proposal I’m aware of. @function will enable a finite combination in a more convenient way and maybe the ident() function can help building comma separated values in new ways. In general using classes for this is tricky though because the position of each value in the list matters (if you want something like layer-1 = gradient-blue, layer-2 = gradient-red, …). Each class would need to represent a tuple (index, image) so you would need every permutation ( layer-1-gradient-blue, layer-2-gradient-blue, …)

You can compose layering backgrounds in the way you described by using using custom properties:

@property --gradient-1 {
  syntax: "<image> | none";
  inherits: false;
  initial-value: none;
}

@property --gradient-2 {
  syntax: "<image> | none";
  inherits: false;
  initial-value: none;
}

.gradient-1, .gradient-2 {
  background-image: var(--gradient-2), var(--gradient-1);
}

.gradient-1 {
 --gradient-1: linear-gradient(60deg, red 0%, orange 50%, red 100%);
}

.gradient-2 {
  --gradient-2: radial-gradient(at center, blue 10%, teal 50%, transparent 50%);
}

Using the @property syntax with ’inherits: falseā€˜ prevents that the parents value for this property get inherited, so that arbitrary nesting is possible.

on hmmm · c/programmer_humor · 37 pts · 321d

SO: ā€œthat’s a stupid question!ā€ GPT: ā€œthat’s a great question!ā€

Yep, the Venn diagram for this would certainly be gloomy. Would also have a decent overlap with the ā€œlonging for a zombie apocalypse in which I would totally be the leader everyone obeysā€-folks.

Psychologically accurate lion meme: ā€œAs a narcissistic wacko I yearn for a strictly hierarchical system, and I deserve to be at the top of itā€