As much as I like FOSS it’s significantly harder to fund.

With proprietary you keep the source code, ship the app, collect data & sell it, and charge for a premium /subscription. They then use that money to fund talented devs and give them deadlines to make good software.

With FOSS it’s largely contribution work by people who work on it in their free time. They use donations or paying for enterprise support, and if they do add a subscription service / premium version you can just modify the code and get it for free.

That’s largely why FOSS software is behind, what’s the direct incentive for someone to make it good?

Sounds more like they don’t want any users

Honestly I don’t think there’s a truly good git hosting website right now.

GitLab works if you wanna get away from Micro$oft but the UI is all over the place. Every other alternative either has an infinitely worse UI or charges money to use

Almost every web developer I’ve met tests if their site works in Firefox and other browsers. The problem is when websites (aka Google sites) deliberately design their sites to not work in Firefox to get people to switch to Chrome

If you’re networked with the right people in the US, laws don’t matter

Virgin Bill Gates: “The covid vaccine doesn’t contain any microchips…I-I promise!”

Chad Elon Musk: “I will literally microchip your brain”

1. Learn coding from YouTube videos/books/etc whatever you prefer

2. Break the information you learn down into small, applicable chunks. For example: How do you add heading in HTML? Use <h1> tag.

3. Write that information down. Handwrite it, don’t type it. This is because handwriting things helps you memorize it a lot better. Focus on what you write and try to understand what its doing and why it was designed that way.

4. Use the information in small projects, using the stuff you wrote as a reference. Those small projects can be like “simple python script that uses a for loop to print text”, aka simple things you don’t release to the public and solely exist for practice

5. Revisit the stuff you learned after a couple days aka try making the same projects again or a new project that uses the same concepts.

Using this pattern I’ve been able to learn things much faster than most others. It’s based on a lot of tricks people use for memorize things better, such as writing things down and spaced repetition.</h1>

LunarVim is great but I really think its better to make your own config and spend the initial investment of getting that set up.

You’ll understand the editor better and because of that can configure it to exactly how you want, and integrate things you regularly use into it (such as plugin features and bash functions) and also learn some Lua along the way