Alright #HomeAssistant nerds, I have a question. I would like to set up a standard way to get a derived value back from a number of sensors; for example, given a sensor’s PM2.5, PM10, Ozone, CO, SO2, and/or NO2 reading, I would like to return an estimated air quality index (AQI). Ideally I could also have a standard way to map any given AQI value to a category string, e.g. 10 = Good, 75 = Moderate, 175 = Unhealthy, etc.
and lastly, maybe emacs macros could benefit from some interactive refinement editor, many times you need to run it a few times to realize you missed a state. It would be cool to be able to prototype them live.
The reason I suspect Tailwind is popular is due to the requirements placed on developers by designers and PMs. I have seen many cases of clean CSS end up a mess - even devolving to style attributes - because every page just has to be a unique work of art with each paragraph and form input its own little delightful flourish.
Developers in general like clean, reusable code. Tailwind is neither. But with such stakeholders sometimes you just want the job done by Friday afternoon.
@carlton@danjac I have been learning in harder with templatetags, but I think we are overdue for some improvements there.
Maybe you are right with "declaring tags at the template level", but I'd be curious what that looks like. I know Jinja2 supports this with macros, but I have always struggled with those. https://jinja.palletsprojects.com/en/3.1.x/templates/#macros
I've created a #gtest macro that allows Value-Parameterized Tests (P Tests) to know where their constructor is and so can report what the actual line of code in your test suite you need to pay attention to.
I couldn't find anyone anywhere who had solved this yet. Although I admit my design isn't perfect, it does however follow the escalating complexity pattern so regular test writers have the easiest interface.
ETA: Seems we found someone - thanks for boosts! ❤
Dear fedi, does anyone in my extended network know about excel macros - and how they might have changed between office 2013 and present day o365 builds - and feel up to the task of modernising/rewriting some sheets for a customer so they can move to current office (which just complains when the old documents are opened) without upending their entire workflow? This work would of course be paid! (Please boost for reach) #microsoft#excel#macros
There's a lot of hate for C++ going around the Fediverse these days, understandably. There is many reasons to hate C++, ranging from its C roots to the breadth and width of modern revisions of the language and their standard library, so extensive that it has become progressively harder for any individual developer to have a complete understanding of the whole thing.
That being said, I'm actually among the perverts that are fascinated by #templateMetaProgramming (even though I'm well aware of its limitations pertaining readability and maintainability). Which is why I took @tess venting as an opportunity to challenge myself into writing a workable approach to generic properties for C++ objects with a common interface:
tfw when you tell a schemer that your programming language's macro system is hygienic even though it fails to pass The Macro Writer's Bill of Rights, and they just hit you with that Indiana stare
Looks like I’m going to double down on #macros. The use-cases I’m seeing so far are blowing my mind. Super powerful… and the simplicity of the resulting code. 🤯❤️ #WWDC23
On a beautiful sunny day, ladybugs live intensely the last days of spring.
The lady beetle (Hippodamia variegata) are distributed throughout Europe, North Africa and Asia, but are absent from the Far North. They live in fields, meadows, at the edges of forests and along the North Sea and the Baltic Sea. #photonature#macros#macrophotography#insect#biologicaldiversity
I've been playing with #swift#macros a lot recently and have just posted my first macro: Renamed.
Apply it to a symbol and it'll generate the equivalent symbol with a different name, making it easy to rename something and deprecate it to avoid breaking API.
Macros in Swift still aren't finalised but it's been fun learning how they work! I'm working on others but this is the simplest and most complete.