• 2 Posts
  • 30 Comments
Joined 1 year ago
cake
Cake day: June 23rd, 2023

help-circle



  • It’s more the fault of the implementation and documentation.

    Yea sure. Though it’s slightly XMLs fault for allowing that kinda implementations. Every random thing is in it’s own obscure namespace with 20 levels of nested objects in different namespaces, and if you get anything wrong it barely explains what’s wrong, and just refuses to work.

    It’s mostly WCFs fault. I just automatically associate XML with nightmare flashbacks of implementing WCF stuff












  • I suppose in the days of ‘Cloud Hosting’ a lot of people (hopefully) don’t just randomly upload new files (manually) on a server anymore.

    Even if you still just use normal servers that behave like this, a better practice would be to have a build server that creates builds, like whenever you check code into the Main branch, it’ll create a deploy for the server, and you deploy it from there - instead of compiling locally, opening filezilla and doing an upload.

    If you’re using ‘Cloud Hosting’ - for example AWS - If you use VMs or bare metal - you’d maybe create Elastic Beanstalk images and upload a new Application or Machine Image as a new version, and deploy that in a more managed way. Or if you’re using Docker, you just upload a new Docker image into a Docker registry and deploy those.




  • There should be, that’s just how fiber works. If they lay a 10 Gb line in the street, they’ll probably sell a 1 Gb connection to a 100 households. (Margins depend per provider and location)

    If they give you an uncapped connection to the entire wire, you’ll DoS the rest of the neighborhood

    That’s why people are complaining “I bought 1Gb internet, but I’m only getting 100Mb!” - They oversold bandwidth in a busy area. 1Gb would probably be the max speed if everyone else was idle. If they gave everyone uncapped connections the problem would get even worse


  • I believe there are a large number of feature requests on Lemmy’s GitHub page, making it difficult for developers to prioritize what’s truly important to users.

    Github issues are annoying that way. You could solve it by closing down “issues” and using discussions instead. People can up and downvote discussions, and you can see that from the listview, unlike with issues.

    And you can have threaded conversations in discussions.