bsnnkv

I'm not a USC, but I will be eligible to apply for citizenship next year.

I have made the decision to avoid international travel so that I don't run into any potential issues at the border until I've gone through the citizenship process.

I'm also keeping an eye on the situation with domestic air travel. If we start getting reports of people being detained and stripped of their LPR status while trying to board domestic flights, I'll probably just stick to ground travel.

Since we're >5 layers deep in the thread tree, feel free to hit me up off-platform if you'd like to discuss this more. Again, I'm on my phone today and limited in how much detail I can respond in - but if you are interested enough to dig into the documentation and video resources available you'll find the answers to all of these questions and more.

The main ones that I'm still waiting to see integrated into mainstream Linux twms are workspace scrolling (of course), dynamic layout rules and dynamic offset rules (important for ultrawide monitor users).

I'd also like to see container limit rules to enforce stacking after meeting a threshold (functions as a hard cap on tiles-per-workspace), and native support for Vimium-style shortcuts for every UI element on the screen (from jwno), but I could probably live without these.

I wouldn't call these particularly innovative features, in fact they are pretty low hanging fruit.

I'm on a phone for most of today so I won't be making the kind of lengthy reply you're asking for, but you can check out komorebi and jwno if you're genuinely interested

Unfortunately tiling window managers for Linux have become quite stagnant in terms of improving and iterating on workflows, which is probably why we're seeing more of the kind of sentiment expressed in this post lately (of course, the poor backwards compatibility story is not helping either)

The Windows scene is definitely the place where the most interesting workflow advances in "traditional" tiling window managers are happening right now.

I'll bite: after writing and using komorebi[1], it's very painful for me to go back to using software like yabai or aerospace - macOS programmatic UI interactions are just too slow, while on Windows they feel comparatively instant.

All of this is made possible for me as a developer by the excellent work Microsoft has done in providing Win32 bindings for Rust. If only Apple would provide the same.

[1]: https://github.com/LGUG2Z/komorebi

Someone working there has good taste to include a Nizar Qabbani poem.

The real kicker is that it wasn't even management saying this, it was "senior" developers on the team.

I wonder if these roles tend to attract people who get the most job enjoyment and satisfaction out of the (manual) investigation aspect; it might explain some of the reluctance to adopting or creating more sophisticated observability tooling.

Last month I switched from a role working on a distributed system (FAANG) to a role working on embedded software which runs on cards in data center racks.

I was in my last role for a year, and 90%+ of my time was spent investigating things that went "missing" at one of many failure points between one of the many distributed components.

I wrote less than 200 lines of code that year and I experienced the highest level of burnout in my professional career.

The technical aspect that contributed the most to this burnout was both the lack of observability tooling and the lack of organizational desire to invest in it. Whenever I would bring up this gap I would be told that we can't spend time/money and wait for people to create "magic tools".

So far the culture in my new embedded (Rust, fwiw) position is the complete opposite. If you're burnt out working on distributed systems and you care about some of the same things that I do, it's worth giving embedded software dev a shot.

Honestly, I am someone who knows nothing about the .NET / Windows ecosystem outside of the Win32 calls required to build out a tiling window manager and a hotkey daemon. These are mostly calls that go all the way back to Windows 95 (and maybe even earlier?)

However, if I as an absolute Windows programming newbie with basic competency in Rust could pick up windows-rs and build a tiling window manager, I'm sure that people who are intimately familiar with the .NET and Windows development ecosystem could develop incredible things targeting Windows with Rust.

Out of the major operating systems, Windows is probably by far my favorite to develop for[1] using Rust. windows-rs[2] is officially supported and is constantly being worked on and improved.

[1]: https://github.com/LGUG2Z/komorebi

[2]: https://github.com/microsoft/windows-rs

I saw that the YC Twitter account has now scrubbed the announcement post, I was surprised to see very little discussion about it here until now

Reading this gave me a lot of hope.

I started selling software licenses this year, and I would be very happy if I were able to write a post like this about the same software 20 years from now!

I have maintained popular edu source software (10k stars on GH - not crazy numbers, but still significant) these last 5 years and the experience has gotten better over time.

I am far more liberal in saying "no" now than I was previously. Typically when a user comes around asking for X, Y and Z, I'll ask them "do you want this enough to do something about it?" - most of the time the answer is no.

This is usually followed by something I see a lot in the open source community (but I don't entertain _at all_ as an edu source developer), some variation of "this is a deal breaker for me." or "but pwease this is the only thing I am missing!"

Ultimately I write software for myself, not for anyone else. I allow individuals to use it for personal use and to look at the source code to learn from it. That's it.

This year I started selling commercial use licenses to fill the gap for people who wanted to be able to use my edu source software at work, and my approach is largely the same; I am allowing people to use the software under certain conditions and that's it.

I'm not selling feature development, I'm not selling support, I'm not selling any kind of prioritization.

I work on the things that I want to work on, sometimes those things include ideas pitched by others that excite me, sometimes those ideas come from people who pay for a license or sponsor, but ultimately I always work on what I want to work on, just like I did when I was the only person using my software.

In this specific case, Reddit makes an API[1] available for developers.

And again, there is no crawling involved.

Crawling is a very specific, well defined behavior. I'll assume with good intent that you aren't familiar with the definition of crawling, in which case you probably should become familiar with it before making inaccurate comments like these in the future.

If you had taken the time to do some relevant reading before writing your inaccurate comments, you would have seen:

> Our [Reddit] robots.txt is for search engines, not Data API users.

[1]: https://old.reddit.com/r/reddit.com/wiki/api

Look harder Simba, there is no crawling involved

I have personally opted out of the arms race for at least one service that I operate.[1]

If AI agents figure out how to buy a subscription and transfer money from their operators to me, they are more than welcome to scrape away.

[1]: https://lgug2z.com/articles/in-the-age-of-ai-crawlers-i-have...

This is probably the joint most important piece of software on my system next to my window manager.

The elevator pitch I give for this software is "QMK for any keyboard" - you can use layers, tap dance etc. with regular keyboards that have programming symbols in sane locations with dedicated keys.

I use this with a Logitech Ergo K860, and have taken it a step further to integrate with my window manager so that layers change automatically based on the focused application[1].

[1]: https://github.com/LGUG2Z/komokana

Trying to use Reels after experiencing the (superior) UX of TikTok was hard enough, but trying to use Reels after experiencing the UX of XHS is pretty much impossible for me.

Relevant article from a few years ago: https://blog.hiler.eu/win32-the-only-stable-abi/

It's odd to me that anyone would describe this point of view as "seemingly obvious"

It's quite impressive to see how much the Windows experience has improved for developers since this was written.

I love being able to both do all of my web application work in a deeply integrated NixOS WSL VM and develop my own desktop environment power tools against a stable DWM using an officially supported Win32 API crate in Rust.

Honestly I dread booting up my M1 MacBook Pro for work, the experience feels sluggish, slow and unresponsive in comparison. In particular the experience of using a wireless mouse is like dragging the cursor through heavy sludge.

If anyone is trying to reach mouseless nirvana on Windows, I maintain a tiling window manager[1] and a hotkey daemon[2] (though you can bring your own thanks to the architecture choices I made), the former of which provides a very robust event subscription system which you can integrate with using any language of your choice.

One of the cooler parts of my little mouseless ecosystem is that I automatically have different keyboard layers (QMK style) activate depending on which application is currently focused, saving me a whole bunch of time fumbling around with obscure hotkey combinations for changing layers![3]

[1]: https://github.com/LGUG2Z/komorebi

[2]: https://github.com/LGUG2Z/whkd

[3]: https://github.com/LGUG2Z/komokana

Since I see Helix being mentioned here, I'll start this comment by noting that I am the author of the helix-vim[1] repo which has been shared very widely at this point.

I still stand by everything I wrote in that repo, but these days I'm a very happy NixVim user, with my own little mini NeoVim distro, JeezyVim.[2]

I hate to do the "Nix fixes this" meme, but in this case, it really does fix this particular issue of the NeoVim plugin ecosystem and its constant breaking change update culture being a nightmare for end users.

You can build something that works and pin the dependencies all the way down and have a NeoVim config which will pretty much work forever.

Yes, the initial investment is significant, but for me it's absolutely worth it to be able to provision any machine, any VM, any bare metal server and have my entire NeoVim config completely at the ready with all required dependencies in place.

[1]: https://github.com/LGUG2Z/helix-vim

[2]: https://github.com/LGUG2Z/JeezyVim

I love seeing tiling window managers in unexpected languages as someone who is mostly know for maintaining a twm!

I recently also became aware of a tiling window manager written in Janet which I'm sure will be a hit with Emacs and lisp fans![1]

[1]: https://agentkilo.itch.io/jwno/devlog/871672/scroll-jwno-scr...

I run a service[1] that was getting hit pretty hard by these crawlers.

Ultimately instead of going down this path, I decided to just start charging for access to the service (it was long overdue)[2].

Users who are logged out can still see old cached content (which is a single DB read op), but to aggregate new content requires an account. I feel like this is a good (enough) middleground solution for now.

[1]: https://kulli.sh

[2]: https://lgug2z.com/articles/in-the-age-of-ai-crawlers-i-have...

This is why I ultimately ended up on Windows after switching from macOS and focusing my free time development work on improving the power user/developer experience on Windows with a tiling window manager ecosystem.[1]

One of the really cool things that has come out of this is seeing how people are adding accessibility workflows on top of the ecosystem. There is one person who controls their entire desktop via the tiling window manager using voice control![2]

[1]: https://github.com/LGUG2Z/awesome-komorebi

[2]: https://youtu.be/fiPJLmhnnXM

This and the child comment are a great example of why I always read the comments first :)

> Undoubtedly, the sloppification of the internet will likely get worse over the next few years. And as such, the returns to curating quality sources of content will only increase. My advice? Use an RSS feed reader, read Twitter lists instead of feeds, and find spaces where real discussion still happens (e.g. LessWrong and Lobsters still both seem slop-free).

I had not heard of LessWrong before - thanks for the recommendation!

Whenever I see a potentially interesting link (based on the title and synopsis if one is available) I feed it into my comment aggregator[1] and have a quick scan through (mostly) human commentary before committing to reading the full content, especially if it is a longer piece.

The reasons behind this are two-fold; one, comments from forums tend to call out AI slop pretty quickly, and two, even if the content body itself is slop, the interesting hook (title or summary) is often enough to spark some actually meaningful discussion on the topic that is worth reading.

[1]: https://kulli.sh

Looking at the responses here, I'm glad I just chose to paywall to protect against LLM training data collection crawling abuse.[1]

[1]: https://lgug2z.com/articles/in-the-age-of-ai-crawlers-i-have...