i've heard that vulkan allows bindless textures now, so the descriptor nonsense is a bit less awful that it used to be
vulkan is appealing, but there's a high initial cost that i don't want to pay
316 karma · joined March 23, 2013
i've heard that vulkan allows bindless textures now, so the descriptor nonsense is a bit less awful that it used to be
vulkan is appealing, but there's a high initial cost that i don't want to pay
i don't think i'm going to get into the practice of doing it to that extreme, but i'll probably adopt the multiple-things-per-line part for side projects, and skip the shortening of keywords
with a wide monitor, you can have 3 files like this open at a time. you can fit a surprisingly large program on the screen at once, which is the benefit of coding like that
maybe because you're more likely to have the same generation for different paths, because it's not a hash? an ETag also isn't guaranteed to be a hash, though, so idk
i wish it had a CAS mechanism, though. (google's does, with the x-goog-if-generation-match header)
whether i use them or not is basically a function of how much i think there will be consequences for not using them. if i do use them without coercion, it's for Emphasis, or acronyms (like AI), or maybe sPoNgEbOb CaSe
i'm not sure where AI CEOs, or younger generations picked it up. but the "only use capitals when coerced" part seems similar
an expressive language (clojure, python, C#, etc.) is good when you're iterating "what problem am i even trying to solve?"
a less expressive language is typically better when you more or less know a high level solution to your business problem, and you're iterating on "how do i make the machine actually do it". like "how do i reduce my AWS bill" or "how do i render it in 16ms?"
for something like gamedev, enough of the problem is in the second category that you might not even reach for the expressive language. (many do, though. with lua, or artisanal lisp dialects)
tutorial/example video: https://www.youtube.com/watch?v=SgAWGh1s9zg