I think I stumbled upon a beautiful error(?) in #dotgrid. Upon exporting it as .png the effect disappeared.
@ian I have some Buttondown-related questions, if you have a moment. What would be the preferred medium for contact?
Nice little article about hobbies and how/why they may be difficult for us to cultivate these days.
"Young people are trying to reclaim their time from the pressures of capitalism."
It quotes from Jenny Odell:
“It may still be hard not to see even your free time as money—in which case hobbies appear ‘expensive’ if they produce nothing but personal enjoyment and satisfaction.”
A part of me likes those discussions about CSS bundle sizes, but the other part feels that setting arbitrary sizes may not be the way to go.
Now that CSS can do print-like layouts with things like GRID, I want more innovative, art directed, well thought UX/UI design for content, stories, images, etc. I want more diversity, I'm tired of themeforest eating the world.
To me the challenge is dryer code, reducing the ratio of CSS per design element, not going under a set number. What do you think?
Although apparently this doesn't work everywhere.
Works in Chrome and VS Code (probably because it's Chromium-based).
Does not work in urxvt, Telegram, or Spotify.
Update: I have discovered that on Linux you can press `Ctrl + Shift + U` and then type the code point of the desired unicode character!
So `Ctrl + Shift + U` + `2014` + `Enter` gives me `—`!
It's 2020 and I still don't have a better solution than copy-pasting an em dash from Google every time I need one when I'm on a keyboard without a numpad.
Note that on macOS you can use the modifier keys to get em and en dashes.
One of the reasons why I like Markdown is that I can use the `&mdash` HTML entity to work around this. If only Markdown was ubiquitously supported...
@neauoire I agree that this is unacceptable.
This is why we need better tools that provide good DX but not at the cost of UX.
Take Rust for example. It gives us the power and efficiency of C/C++, but with all the affordances of a higher-level language.
To me, this is the way forward: building languages and tools that provide developers with an amazing experience and allow them to write software that offers a great user experience.
@neauoire This goes along with the idea of "make it work, make it right, make it fast (in that order)", which I very much adhere to. Providing more powerful tools and higher levels of abstraction leads to better DX, which in turn allows us to "make it work" quicker.
There is definitely a balance to be had here, one that I think has been shifting a bit too much towards DX at the cost of UX. Just look at the mess of Electron apps that consume vast amounts of memory even when idle.
@neauoire I wanted to clarify my thoughts in regards to performance.
Firstly, I want to say that your enthusiasm for and commitment to performance, especially on lower-end hardware, is admirable.
That being said, I think that eschewing the developer experience (DX) in lieu of a better user experience (UX) is not the correct solution.
For me, DX is equally important as UX. As developers, we shouldn't have to unduly suffer just so that we can eke out every last bit of performance for the user.
In three different languages too: F#, Elm, and Rust.
宝霞龙. 25. Conjurer of code. Devourer of art. Pursuer of æsthetics. Soli Deo gloria. He/him.
Revel in the marvels of the universe. We are a collective of forward-thinking individuals who strive to better ourselves and our surroundings through constant creation. We express ourselves through music, art, games, and writing. We also put great value in play. A warm welcome to any like-minded people who feel these ideals resonate with them. Check out our Patreon to see our donations.