jameschensmith

Joined 4 years ago

Karma

Submissions

Member since

Sep 15

Recent submissions

Thanks for your response! Regarding question 2, I think my initial understanding of FlashSpace was that it was using the macOS spaces API, which has been known to have its limitations (as documented in the Aerospace docs I shared). Now that I've played around with FlashSpace, I believe it's not using that API. So I think I'm clear on the questions.

I really like how FlashSpace plays well with macOS native tabs. One follow-up question I had is how you manage your windows? FlashSpace not managing windows on one hand is really nice for floating windows (e.g., mpv), but in your examples you have all the windows already set up with some gaps around each. Is all that set-up done by dragging windows around with your mouse? I use an accordion layout heavily, and I don't see how I can make it work with FlashSpace.

Comment · 1 year ago

This looks great! I currently use Aerospace, but your usage of macOS spaces has me curious.

1. Does FlashSpace require disabling SIP?

2. Aerospace documents the limitations of macOS spaces [1]. How does FlashSpace deal with these limitations?

3. Do you have any plans to support file-based configuration? I like syncing my dotfiles between multiple computers.

[1]: https://nikitabobko.github.io/AeroSpace/guide#emulation-of-v...

Comment · 2 years ago

Your versioning system honestly doesn't sound that bad. If you took the major version out of the picture, you could consider the minor and patch versions to line up with the major and minor versioning scheme of Compatible Versioning (ComVer) [1]. I think if you were to explain your versioning system around ComVer, including the inconveniences which currently come from major version updates of Go modules, it would be quite clear. If Go were to improve upon the major version inconveniences down the road, you could then migrate your major / minor ComVer versions from the minor / patch SemVer versions to the major / minor SemVer versions. Great work, by the way.

[1]: https://gitlab.com/staltz/comver

Comment · 2 years ago

Awesome! I recently started an "Awesome Website Paths" [1] repository. I didn't know about /ideas, and I haven't tracked /about yet. I'll add them later tonight and point both to https://aboutideasnow.com for now. In the past I've had each endpoint mention a specific page that's dedicated to the endpoint. I can make an exception until I find one of those dedicated pages, but I'll make sure to still keep a reference to your site when I do make that change. Thanks for sharing!

[1] https://github.com/jameschensmith/awesome-website-paths

Comment · 2 years ago

> So my daily routine looks like

> [...]

> 5. copy the next day's calendar items to the bottom of the text file

Interesting. For a file with 51,690 lines at the time this post was created, I'm curious why the file is not ordered with the most recent day at the top of the file.

Comment · 3 years ago

My head is already coming up with use-cases, such as JS template literals (think lit [0] for HTML and CSS templates) or the recently-shared Expr [1]. This is really neat. Thanks for sharing.

[0] https://lit.dev/

[1] https://github.com/antonmedv/expr

Comment · 3 years ago

I tend to share https://nohello.net/. It may be newer, but it's also open source, is available in multiple languages, emphasizes asynchronous communication [1][2], and uses _The Office_ as its setting which makes sharing it a bit more lighthearted.

[1]: https://en.wikipedia.org/wiki/Asynchronous_communication#Ele...

[2]: https://async.twist.com/asynchronous-communication/

Comment · 4 years ago

While I find it awesome to see Penpot getting some recognition right now, it is not at the point of being a Figma replacement just yet. But I'm very hopeful that it will eventually be. Once they get a plugin system implemented, I'll be recommending it to all my colleagues.