Pinned toot

writing a blog became easier when I stopped worrying about creating a perfect substrate.

I notice others fall into this trap, too. Trying to design a flexible system and burning out without ever adding any content.

Write first.

Debating whether I want to switch to the `nixos-unstable` channel.

The version of `spotifyd` is a little old and is missing some features that I need.

I suppose I could just use an overlay to update just `spotifyd` 🤔

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 `—`!

Source: maketecheasier.com/quickly-typ

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.

Remember folks, always do your website performance testing in incognito mode.

In three different languages too: F#, Elm, and Rust.

I've started three new projects in the past week alone.

I think I have a problem...

My personal site is at it's absolute peak right now. I can only make it worse.

This is fucking unbelievable.

All of this information can be retrieved from Visual Studio's intellisense when consuming the assembly, so why do we need 600MB of garbage?

You'd think that with all of this space they would have something truly stellar to show for it.

Nope.

This file alone is 385KB and only shows some next-to-useless information about a class.

It's time for some tool shaming.

At work we use this tool called GhostDoc to generate documentation for our .NET assemblies. I've known that we've used it for a while, but I never really knew much about it.

Today we're prepping a new documentation website, so someone committed GhostDoc's HTML output to the repo.

I couldn't believe my eyes. The HTML folder is 600MB!

Show more
Merveilles

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.