I literally didn't get a job last week because I'm white and have a common white surname. They didn't ask anything technical at all.
It's tough, and I empathize. But imagine being denied these opportunities systemically, for a lifetime.
Readit Newsgchamonlive commented on Xlibre is a fork of the Xorg Xserver with lots of code cleanups x11libre.net/... · Posted by u/doener
Deleted Comment
gchamonlive commented on Xlibre is a fork of the Xorg Xserver with lots of code cleanups x11libre.net/... · Posted by u/doener
You think like this because you have the privilege of not being affected by discrimination. It's not enough to "not be a racist". You are being downvoted because of this, and thinking everyone but you is immature for this conversation just highlights this.
gchamonlive commented on Migrating Dillo from GitHub dillo-browser.org/news/mi... · Posted by u/todsacerdoti
I've been messing around with GitLab as a self hosted alternative for a few years. I do like it, but it is resource intensive!
For the past few days I've been playing with Forgejo (from the Codeberg people). It is fantastic.
The biggest difference is memory usage. GitLab is Ruby on Rails and over a dozen services (gitlab itself, then nginx, postgrest, prometheus, etc). Forgejo is written in go and is a single binary.
I have been running GitLab for several years (for my own personal use only!) and it regularly slowly starts to use up the entirety of the RAM on a 16GB VM. I have only been playing with Forgejo for a few days, but I am using only 300MB of the 8 GB of RAM I allocated, and that machine is running both the server and a runner (it is idle but...).
I'm really excited about Forgejo and dumping GitLab. The biggest difference I can see if that Forgejo does not have GraphQL support, but the REST API seems, at first glance, to be fine.
EDIT: I don't really understand the difference between gitea and forgejo. Can anyone explain? I see lots of directories inside the forgejo volume when I run using podman that clearly indicate they are the same under the hood in many ways.
EDIT 2: Looks like forgejo is a soft fork in 2022 when there were some weird things that happened to governance of the gitea project: https://forgejo.org/compare-to-gitea/#why-was-forgejo-create...
https://forgejo.org/docs/latest/user/actions/basic-concepts/
It's a shame that GitHub won the CI race by sheer force of popularity and it propagates its questionable design decisions. I wish more VCS platforms would base their CI systems on Gitlab, which is much much better than GitHub actions.
gchamonlive commented on LinkedIn is loud, and corporate is hell ramones.dev/posts/linkedi... · Posted by u/austinallegro
Indie
Indie as freelancer or as making your own product?
gchamonlive commented on LinkedIn is loud, and corporate is hell ramones.dev/posts/linkedi... · Posted by u/austinallegro
Corporate is hell, startups are insane. Is there any place to work as a developer and still keep my sanity?
gchamonlive commented on GitLab discovers widespread NPM supply chain attack about.gitlab.com/blog/git... · Posted by u/OuterVale
Phew, thought it was another one.
> Our internal monitoring system has uncovered multiple infected packages containing what appears to be an evolved version of the "Shai-Hulud" malware.
Although it's not entirely new, it's something else.
gchamonlive commented on We're losing our voice to LLMs tonyalicea.dev/blog/were-... · Posted by u/TonyAlicea10
Social media is a reminder we are losing our voice to mass media consumption way before LLMs were a thing.
Even before LLMs, if you wanted to be a big content creator on YouTube, Instagram, tiktok..., you better fall in line and produce content with the target aesthetic. Otherwise good luck.
gchamonlive commented on Agent design is still hard lucumr.pocoo.org/2025/11/... · Posted by u/the_mitsuhiko
I've started a company in this space about 2 years ago. We are doing fine. What we've learned so far is that a lot of these techniques are simply optimisations to tackle some deficiency in LLMs that is a problem "today". These are not going to be problems tomorrow because the technology will shift. As it happened many time in the span of the last 2 years.
So yah, cool, caching all of that... but give it a couple of months and a better technique will come out - or more capable models.
Many years ago when disc encryption on AWS was not an option, my team and I had to spend 3 months to come up with a way to encrypt the discs and do so well because at the time there was no standard way. It was very difficult as that required pushing encrypted images (as far as I remember). Soon after we started, AWS introduced standard disc encryption that you can turn on by clicking a button. We wasted 3 months for nothing. We should have waited!
What I've learned from this is that often times it is better to do absolutely nothing.
I think knowing when to do nothing is being able to evaluate if the problem the team is tackling is essential or tangential to the core focus of the project, and also whether the problem is something new or if it's been around for a while and there is still no standard way to solve it.
Execs have less and less shame as the years go on. Pride in artistic endeavour? That’s not going to make the shareholders happy.