@orowith2os - eviltoast

Oro [she/they]

Queer individual from southeast Texas. Helping to work on the Linux desktop - currently contributing to Flatpak and Flathub, getting familiar with GNOME.

Can find me at:

https://orowith2os.gitlab.io/ https://tech.lgbt/@orowith2os https://github.com/orowith2os/ https://gitlab.com/OroWith2Os/

  • 0 Posts
  • 9 Comments
Joined 1 year ago
cake
Cake day: July 8th, 2023

help-circle




  • Doing everything explicitly can get to be annoying, especially when it comes to what you had to do before without Vulkan’s VK_EXT_shader_object.

    It’s clear that some stuff should be implicit - most types in programming languages, for example; needing to specify a struct type and then the struct itself can be annoying - and other stuff explicit, like low level operations.

    Returns are something that usually fall into that “implicit” category. Why should I do let a = function(); return a; when I can just do function()? It’s shorter, simpler, and I don’t waste keystrokes.