lmao, basically, yes. except when you bring this up ppl think it's not a big deal / a means for self-expression. having to sort through which libraries you prefer to glue together is a kind of freedom, if you squint hard enough.

if you oppose a far-right project, what are they going to call you? lol. here is your membership card for the cultural marxist party, welcome aboard comrade!

i just think it's folly for people to complain that "not destroying the environment" is a partisan issue in 2026. being a nice person is a partisan issue in 2026.

the far-right is literally trying to make it illegal for companies to say they're taking environmental concerns seriously (i.e. ESG bans in tx, fl, etc). in 2026, sustainability is not apolitical.

(it's _never_ been apolitical but i will spare you that lecture.)

if you can get a Rack compatible web server to build… i'd waste some serious time playing with this.

on data i would never ever want to upload to any vendor if i can avoid it

My unsolicited advice is: whether they realize it or not, _everyone transitions_ ;) http://okayfail.com/garden/everyone-transitions.html

I came out socially for most of a year before I committed to hormones, and it took me another year and a half to commit to removing my facial hair. At some point it really is a leap of faith. But you can do a lot of exploring and trying things out until you feel comfortable – or decide it's not really what you want.

Either way, good luck!

We were never actually poor, poor, at risk. I never skipped meals, or lacked for clothing, though certainly that was a living memory my grandparents had. It was never in question that I would attend university.

Privilege is intersectional blah blah, there are layers to things. I'm not of the dominant Anglo culture, I have an "ethnic" last name, I don't have the same connections people who grew up upper-middle class do. But people certainly see me as white, I'm smart, and I built my career as a bearded guy.

Living as a bearded white guy is just a lot easier, it presents a lot less friction, than being gender non-conforming. That's it, really.

a) they don't like Ruby for whatever reason, b) they probably only deal in backend or only deal in frontend, and so don't understand the value of the bundled dev experience rails delivers, and therefore c) because of a + b they find the moderate learning curve to be extra painful, so they lash out.

at the end of the day it's all just code. why would it be harder to integrate a service in Rails than in Go? of course it isn't.

source: i cut the releases ;)

https://github.com/github/cmark-gfm/commit/ac80f7b56522ffa15...

1. Package managers are very hard! The same problems wrt dependency resolution pop up again and again. Whatever you do, I recommend uhm, copying whatever Yehuda et al did for Ruby, Rust, Yarn, i.e. bundler/cargo/yarn

There's lots of prior art out there, and a few days of reading can save you months of terrible effort! Here's one example but there's loads more out there https://yehudakatz.com/2016/10/11/im-excited-to-work-on-yarn...

2. Namely, I don't see any lock files! I didn't look very hard. But get yourself some lockfiles. I also can't stress this enough.

3. Packaging signing really needs to be baked in from the get go, re: https://news.ycombinator.com/item?id=19733085).

Good luck!