The real deal y0

  • 0 Posts
  • 30 Comments
Joined 2 years ago
cake
Cake day: July 16th, 2023

help-circle

  • You and i read different things. I hated how he worded them, but his arguments at greppable and understandable are valid arguments that go beyond rust and if he can read it or not or refuses to.
    Mixing languages in a part of a project brings complexity and is often a huge ass nono because it makes things unreadable and hard to manage on a large scale.
    He also argues that a c interface exists to connect 2 parts of a system. The person that changes the interface should not have to alter the users of that interface, if they do then you get intertwined dependencies, which is a huge ass red flag for developers that something has gone terrible wrong and the project is not going to scale or will be easy to change.
    So if he changes the interface, the rust team will need to fix it, specially since they are the minority.
    That also doesnt mean he can change it in whatever way without worry, it is an interface change, that needs discussions and approvals ahead of time ofc.


  • You seem to be in the loops of the linux kernel?
    If so, ive known hector from way before when we was part of f0f, or TT as they were known before, doing wii homebrew work.
    What you describe is what my experience was with him 14 years ago too. The guy is smart, he has a very good skill set and knowledge, but his communication skills were lacking back then too.
    Granted, both he and myself were still teenagers and students and we were wild, but i had always assumed he grew up a bit since then…

    What you said is spot on, and i hope he does read both of these. And if he does :
    Marcan, you might not know who i am anymore, but ffs man. Dont screw up your love for all of these by keep kicking the hornets nests. You did it with devkitpro, emudevs when the nier news dropped and with rossman too. Stop it, its for your own good.


  • DacoTaco@lemmy.worldtoOpen Source@lemmy.ml*Permanently Deleted*
    link
    fedilink
    arrow-up
    4
    arrow-down
    2
    ·
    edit-2
    6 months ago

    Their source code repo contains a copy of libogc for wii/gc builds because they were annoyed at us. And i do mean a copy. Not a reference, or a sub-module, a full on copy that they build before building the wii/gc executable.

    Their own issue, as long as we dont get reports of their broken shit…

    Then there are the multiple times they cloned emu repos and butchered them into cores. Or the fact they force the core interface on emulators making them bad.

    Retroarch is a nice project from a far, but the closer you look, the more you see huge ass cracks in the project, held down with duct-tape





  • 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


  • Imo github doesnt have that high of a vendor lock-in. Its git, you can clone and push it to another server. Sure, youll have to convert the ci’s and templates, but thats about it really.
    And a good yaml is easily converted as the ideas and actions are the same, only the action names are different.
    But yes, i think that is what the author was getting at.