• 1 Post
  • 7 Comments
Joined 1Y ago
cake
Cake day: Jul 10, 2023

help-circle
rss

It’s a front-end project written in C++; a desktop environment for Unix-like systems.


SourceForge went to shit when it was the de-facto location for free and open source software, now GitHub is where Sourceforge used to be. When will people learn?



How do you wrap your head around large established software projects in order to contribute to them?
Hey there, I have been a hobbyist programmer for quite some years and have a few smaller projects under my belt: mostly smaller GUI applications that have a few classes at maximum, make use of one or two external libraries and are very thoroughly documented and commented. Since I love the free software movement and philosophy, I wanted to start contributing to projects I like and help them out. The thing is, the jump from "hobbyist" to "being able to understand super-efficient compact established repos"... seems to be very hard? Like, looking into some of these projects, I see dozens upon dozens of classes, header files, with most of them being totally oblique to me. They use syntactic constructs I cannot decipher very well because they have been optimized to irrecognizability, sometimes I cannot even find the starting point of a program properly. The code bases are decades old, use half the obscure compiler and language features, and the maintainers seem to be intimately familiar with everything to the point where I don't even know what's what or where to start. My projects were usually like four source files or so, not massive repositories with hundreds of scattered files, external configurations, edge cases, factories of factories, and so on. If I want to change a simple thing like a placement of a button or - god knows! - introduce a new feature, I would not even remotely know where to start. Is it just an extreme difficulty spike at this point that I have to trial-and-error through, or am I doing anything wrong?
fedilink

As a hobbyist web dev:

  • I want to support niche browsers that might not support WASM such as Dillo or NetSurf.
  • Most of the resources out there are Javascript-only.
  • I don’t even use scripting most of the time in order to be accessible to text-only, old and minimalist browsers.

I can also imagine that people who are more professional than me in their development require existing JS frameworks, libraries, tutorials and whatever, and were taught in Javascript; there is no reason for them to change. There is also probably no real money in developing WASM applications commercially.


Mail. It’s almost impossible to find a server hoster that hasn’t yet been ip-range-banned from most mail gates, and I cannot host from my own house due to ISP terms and conditions.


Wait, it isn’t in the USA? That’s nuts. I knew the American healthcare system was bad, but…