• 1 Post
  • 82 Comments
Joined 1 year ago
cake
Cake day: August 9th, 2023

help-circle
  • You can either decide by what is currently in demand in the industry and then pick a project that you can exercise that language with or you can think of a project you’d like to do and then go by what the best language is for a given project.

    In the end, languages are just like different wrenches. First you have to learn how to use a wrench, size or features don’t matter much at this point (unless you already know that you want to become an expert with one particular wrench).

    I think starting a new project is way easier than contributing to an existing one.






  • With a Blazor (serverside mode) project you could have that with a nice user experience. Blazor has a tiny js which initializes something, otherwiss it renders the site on the server and sends the component updates to the browser, so the whole site does not need to reload, only the relevant components (which is kind of interesting).

    Maybe there is some blazor serverside e-commerce project out there, I wouldn’t personally recommend it though.



  • For the site itself the most minimal thing you can do is an html file.

    Then some software to act as the “server” that serves that file to a visitor. (nginx, caddy, apache - there are many options).

    And your domain needs a domain record which points to your server.

    As you want to use a home pc, you need to figure out whether your ISP gives you a dynamic or static IP.

    If static, you can just use that.

    If dynamic, you’d need some service like dynDNS to keep pointing your domain to your changing IP.












  • I have been on arch professionally for ~5 years.

    I am a GUI fan and I don’t like fucking around with the OS. In fact, I don’t even want to think about it at all.

    So far it hardly required any maintenance (much less than Ubuntu, Windows or Mac, at least for my workflows).

    And the only fucking around I did with it was the first two days setting everything up just the way I like.

    To be fair, I already had extensive linux knowledge at the point of switching to arch - through ~4 years of constantly breaking my Debians and Ubuntus every couple of months.