I think the only thing that is really outstanding for Windows is SSH support.
Everything largely "just works" and my experience getting a plugin with syntax highlighting working and merged for a DSL I maintain was very smooth.
2,138 karma · joined July 28, 2016
https://notado.app/feeds/jado/hacker-news-comments
https://github.com/LGUG2Z/komorebi/
https://hachyderm.io/@LGUG2Z
https://bsky.app/profile/lgug2z.com
I think the only thing that is really outstanding for Windows is SSH support.
Everything largely "just works" and my experience getting a plugin with syntax highlighting working and merged for a DSL I maintain was very smooth.
This is a really detailed post about adding the scrolling functionality you may have seen in PaperWM or Niri.
I have been very clear with the community from the beginning that this is software that I develop first and foremost for myself - new features and bug fixes get prioritized largely according to this.
Additionally, support is not offered as part of the commercial use license and is largely community-driven. Nevertheless, I still spend many hours a week helping out both personal use and commercial use users.
I do not believe I could have achieved what I have in the last half-decade if I had stayed in the UK. There is something deeply rooted in the UK's contemporary culture (which I cannot yet fully explain in words) that serves to crush the individual ambitions of the working and middle classes.
As the software is of the nature that it will require updates indefinitely (as OS updates come and go), and given the fact that the license is specifically for commercial use, I decided to go with a subscription model instead of a one-time payment model to ensure its long-term sustainability.
I am lucky that this specific software is very "sticky" and already has a die-hard fan base. It also helps that people in the Windows ecosystem are used to paying for commercial use software licenses.
This month to date I have made $800 on license sales. It will be interesting to see how the license sales continue to progress (or don't?) throughout the rest of the year.
I've worked on this issue a little in a different context, where you can follow posts from people on Bluesky related to specific topics, and this is ideally what I would like to be able to do more of with RSS.[1]
I pair this with my tiling window manager[1] which treats ultrawides as a first class citizen (not all twms do this unfortunately) and I'm very happy with this setup.
The biggest cost of RSS feed items as a consumer is figuring out whether something is worth reading. A lot of feeds these days don't provide anything useful in the body to make a determination on this, and others just dump the entire contents in the body, which means you're wasting a bunch of time reading N% of something until you realize you're not interested in it and it can be skipped.
In addition to this, RSS feeds tend to be structured to just throw everything at you, regardless of the topics you are interested in.
For a few years I have been publishing my own topic-specific feeds[1] for others to consume where I fill the body with my own personal highlights from the source, with a link through to the source (ie. the things I found interesting, the "hooks" that give a quick signal to a consumer if this might be something they want to invest time in reading). They have a couple of die-hard consumers, but ultimately this really a case of a niche within a niche.
I wish there were more feeds like this for me as a consumer, but unfortunately I get the feeling that this idea will never really become popular enough to catch on widely as RSS becomes less and less relevant to the mainstream.
[1]: my software development topic RSS feed for example: https://notado.app/feeds/jado/software-development
[1]: https://www.comradeworkwear.com/products/swoletariat-tee
It's very hard to go back to an app with a poor FYP algorithm (ie. Reels, Shorts) after using an app with a good FYP algorithm, and this, along with a knee-jerk reaction against Meta for its perceived role in lobbying for the "TikTok ban" will make capturing ex-TikTok users an uphill struggle for Meta's products.
The migration of US TikTok users to Xiaohongshu this week, to the point where it is #1 on the US app store while still having half of its UI in Mandarin has been particularly eye opening.
The text-based tech internet has become incredibly hostile to people sharing their work over the past decade, so a few years ago I decided to try and engage people through YouTube instead and I think this has been a decision that has really paid off. For people interested in pursuing something like this I'd definitely recommend trying out video format communication over blog posts and articles if the latter aren't doing well for you.
I have done a lot of "building in public" on YouTube over the past few years and have built up a really solid product that people have been actively asking me to release a commercial license for so that they can use it at work. I feel pretty good about things right now!
[1]: https://polyformproject.org/licenses/strict/1.0.0/ (hn discussion: https://news.ycombinator.com/item?id=24804223)
I've re-read this a few times and I'm still not sure what "harmful to open source" means in this sentence, could you expand on this a bit when you have time? (readings I considered: this will dissuade people from using OSI licenses, this will dissuade people from trying to monetize open source components, this will dissuade people from using open source components in their products all together, this will dissuade people from contributing to open source)
> Many people had contributed their efforts to the Redis project for free
This one is not directly addressed at OP but I would be interested to see what the contribution numbers are like for Redis and other projects post-license change.
In my own limited experience (project with >10k, <100k end users), I received no meaningful code contributions when the project was MIT licensed, but contributions of significant features and large bug fixes skyrocketed after switching away from it (not saying that the license change is the reason for that, just that it didn't dissuade some people who are willing to contribute significant effort from contributing to the project).
Editing this post to say thanks for the response and clarity, I don't have anything else to add!
(Snippets from the article below)
> I wrote open source software for almost my whole life. Yet, as I’m an atheist and still I’m happy when I see other people believing in God, if this helps them to survive life’s hardships, I also don’t believe that open source is the only way to write software.
> Moreover, I don’t believe that openness and licensing are only what the OSI tells us they are. I see licensing as a spectrum of things you can and can’t do.
Nit: At this point you're better off starting a separate comment thread since you yourself already know that what you are about to talk about is not what my comment is talking about.
[1]: https://github.com/LGUG2Z/komorebi/blob/master/justfile example justfile on my biggest and most active Windows project- might not seem like a lot but this has probably cumulatively saved me months of time
I wrote earlier this week on HN[1] about my very recent experience trying to ship _something_ (in the "product" category) to alpha testers in <1d and to an open beta in <7d, and it's something I recommend highly for people who are stuck wanting to go from "almost done" to "done" before shipping.
There is so much valuable feedback to be gained by shipping _something_ as soon as possible, and often just the act of getting that feedback goes a long way towards breathing fresh life into a project you might be starting to feel a little burnt out on.