The real deal y0

  • 0 Posts
  • 79 Comments
Joined 1 year ago
cake
Cake day: July 16th, 2023

help-circle











  • Yes!
    They have released multiple new mainboards for the framework 13 which upgraded the cpu. This is a new mainboard with the latest intel cpus. They have always allowed everyone to just buy the board so they can upgrade their existing framework 13’s, thats their whole stick : modularity.
    This time they also have a new screen panel and battery you could get to upgrade your system.

    Also obviously new systems can be bought with the new hardware from the get go too.

    I have a framework 16 that my boss got for me. Im a trial to see if we can save money by going framework instead of dell for the laptops developers use as things like the ports on the side, batteries and mainboards are easily replaced and upgraded. No need to waste +2600 euro every 3 years per laptop either if we can just swap the mainboard. They didnt want to finance the gpu, but when the laptop is mine after 3 years i will probably get the gpu for it :)
    (In a framework 16 a gpu can be plugged in or replaced. Framework 13’s always use integrated gpu )



  • I can understand with what youre saying, and to each their own tastes. However, id like to point out that asus tried to get them to pay 200$ for something that wasnt broken is something that is relevant to us as consumers. Specially since they started the investigation after a lot of people started mailing GN about their issues and… questionable practices






  • Ye fair, it all depends on what markup you have and what features you use. Personally i dont think my markup of priiloader has any weird stuff that is specific to github, but i will have to check to be honest. If there was any special stuff id try to steer away from github specifics as much as i can, because i believe and work in a way it should always be possible to take away any part of a project and replace it with something else. It makes projects very flexible to change


  • Ye, some of these i started thinking of after i made my comment, which is my bad. Its true a project that uses the full github stack is harder to move, its its still relatively easy. The only problem you’d have is redirecting traffic to a new host, but this problem exists in all platforms and not only in project management sites like github.
    As for your bulletpoints, i have a few remarks. Mainly that github pages are silly and they should not be used as a website. And even if you are, there are tools out there to convert the markdown from github pages into html/css/js so moving that is easy. Same with wiki pages, they are just markdown. 90% of markdown is compatible with other sites, and the parts that arent probably have a site specific syntax that youll need to look up, nothing bad. Review comments i will disregard, as those are part of the PR process. Once a project is moved you could hide the PR tab on github or close all new ones redirecting them to the new host. All older ones can be handled and phased out. Once a pr is merged, get the commit from github and push it to the new host. Thanks git!
    Random contributers have nothing to say imo. If a project’s team feels the need to move away from github a true contributer/side team member/helper will move with them, and if they dont then so be it. Once a project team feels the need to move, something bad must be going on and moving will always be the better move for their mental health than to keep working with bad stuff.
    As mentioned before ci/release pipelines are all yaml. Their odeas stay the same, only action names & their patameters change. Nothing complex there to move there…

    So im short : only moving your traffic is a real problem, but is a problem on all websites and all communities, not just github or a project on github