Python has a built-in logging library which is utilised for displaying logs with different levels and formats. The Rich

A lot has been discussed about JSX since its introduction, but I’ll allow myself a quick consideration of it for the sake of elucidating my point. JSX is messy, but it is also a reality. It comes from a natural evolution of front-end technologies, which have since their beginning some form of XML language to define markup. What makes it different is that JSX usually lives inside your JavaScript code.,You have to challenge the cis- and heterosexist (and racist, and ableist, and classist) underpinnings of the systems designers work in to make meaningful change. And if you do, the output will change as well.,At the same time, I think the queer community deserves better than to be defined in opposition to our cisgender, heterosexual peers. Challenging -isms in design is important, but it’s also table stakes.,With cars and houses, the stakes are high and tangible. Being stranded in the middle of nowhere or having a roof collapse isn’t something you want to bestow on yourself. So, you leave it to the experts. With design, not so much. Everyone is entitled to have a certain taste and a personal preference. And everyone knows what they like, and what they don’t like.,Making a rough comparison with spoken languages, JSX is as if the speakers of a particular language started using a whole set of words and expressions from other languages to express themselves. This frequently happens when a specific subject is innate to a given culture, for example. When people outside that culture, speakers of a different language, face that challenge of expressing ideas about that subject, they’ll often lack the vocabulary to deal with it, recurring to the language spoken by those who “gave birth” to the topic as a way to solve it. Language purists soon get angry and point out how you could say those things without the need for imported words. But people would still use those words, and some of those words will eventually be incorporated into the official language. JSX was born from the need for JavaScript speakers to express UI markup.,At its heart, I think of being outwardly queer as a process of owning who you are. Growing more comfortable in that identity, or learning to enjoy the discomfort, and sharing it with the world.,My answers to this question are more often than not something else that not React. But every once in a while, you compare every trade-off; you look at your project from different perspectives; you try to rethink the features you envisioned and the requirements you had; and still, at the end of the day, React will be your answer. With those cases in mind, I reframed the original question to: “how far can I go to make my React code more pleasing to view while still keeping it React code?”,I was really amazed by this feature. I’m sure you’ll, too. The Rich library can show the traceback of any expectation in a very readable way. This feature is out-of-box that is actually a combination of all of the above features.,While reflecting on this topic one day, a question arose: Can I write React code that is aesthetically delightful while still keeping my productivity high? I know there are tremendously valuable answers to this question out there in the way of other programming languages and frameworks. All of those will have varying degrees of the same trade-offs, like how hard it is to learn, how much can I still benefit from the React ecosystem, how is the tooling around it, and so on. And all those trade-offs need to be measured differently depending on the project’s objective.,The consequence is that sometimes, although I might find one programming language, or framework, or tool, unpleasant to see or use, it is the one I need to see my code taking the shape of something real in a reasonable time. Maybe this is due to some tooling, the big community creating things around it, or some other technical trait. Regardless of the reason, my coding-as-a-hobby time is scarce, and although I want it to be enjoyable, I also want to make the best of it, which means using things that do not always comply with my aesthetic standards. This is the case with React.,And this is the point where things get subjective: I find this code unpleasant. Again I’m not talking about the technical attributes of this code. When I say it is ugly, I’m trying to express a set of feelings it evokes in me, which are heavily based on my own experience of the world in general and programming specifically. It is from this perspective that I’ll move on to say that the first problem that screams to me is JSX.,To illustrate all the elements of the pretty traceback, we need to have relatively complex code. So, please allow me to use the screenshot from the official GitHub readme page.,If you have LGBTQ people doing work that doesn’t change the systems they are working in, that’s not queering anything, that’s assimilating. Assimilation will always to be contingent on playing by a set of established rules. And it’s always going to require leaving someone behind. There has to be an out group in this model of the world.,To start answering the question, I created a Create React App project with a simple React code as a reference. I wanted it to have at least a bit of real-lifeless but still be simple enough, so it wouldn’t get in the way of testing different things. I chose the official React tutorial code, which you can find here: Tic Tac Toe.,When I look at designs created by the queer community, there are qualities I think can help clarify what it means to “queer design” in practice. would put hope we can bring forward in our work.