• 1 Post
  • 29 Comments
Joined 2 years ago
Cake day: July 20th, 2023
  • mryessir@lemmy.sdf.orgtoOpen Source@lemmy.ml•Ladybird Browser Team Selects Swift as Preferred Language
    2·
    8 months ago

    Hehe. You came from a different direction. My main point is that reading, thinking and contributing in Swift is more familiar with the majority of developers. Currently.

    Swift usage is largely isolated to Apple’s ecosystem, which doesn’t have a ton of overlap with the open-source ecosystem.

    I agree that the usage is isolated and it is not represented in the FOSS community. And I am not an advocate for doing so. Though it is compatible and if it is a possible alternative it can be considered. If you compare it to other Syntax it is reading very easily and you can pick it up in 20 Minutes. They could even require to explicilty use type annotations to further aid accessibility for possible contributors or audits.

    … creating libraries which can be called from virtually any other language, like you can with C and C++. Which means you’re not locked into the Rust/Apple/whatever ecosystem …

    Let’s agree that a lock-in should not be dependend on the implementation language. There are other implications on the build which may arise. I am neither familiar with rust nor Swift. Comparing implications for building and linking can’t be compared by me on a professional level.

    I further - without research - call out that Rust comes with implications on either library implementation or linkable procedures for an author in order to link to it. Neglecting thinks like nested interop between host/implementation language here.

    But even if Rust was the most overhyped garbage, it would still be garbage that people are familiar with. ¯\_(ツ)_/¯

    Two things: Every developer I have met in person whishes to get some project in Rust. No one has seriously started pushing or even learned it thoroughly. Second point: I didn’t called it garbage! The language as it is awesome. I don’t like its readability and its packaging.

    When I read Rust sources it isn’t fluent in my inner mind. Sure it is due to familiarity but I would also argue that the over-expressiveness kills reading speed as well. Though that should be inspected by more objective and competent people though.

  • mryessir@lemmy.sdf.orgtoLinux@programming.dev•GUI options for KVM?
    2·
    10 months ago

    If you run qemu from CLI you get a window which grabs keyboard and mouse automatically. Ctrl+Alt+G (from the top of my head) releases the input devices so you can again navigate the host. The window is otherwise a default window for you display server.

    I find qemu from CLI way more transparent then these GUI-Applications since each vm is a readable, single script. So I recommend this.

    Regarding installation on iMac bare metal: If the kernel supporta virtualization you can expect to work flawlessly. If you have a dedicated graphics card you can only pass this (as well as dedicated devices like hdd’s) if you main board supports IOMMU.

    If it does all you need is the qemu man page to setup your vm.

    Why I prefer a qemu script to any GUI alternative:

    The entire script for passing RAM, GPU and a HDD is about 10 lines max. A default vm with tcg-emulation e.g. via libvirt etc. can pass 50 lines of xml easily.

    I recommend giving it a try. My workflow is: Place the install script in some directory. The default run script is placed in my ~/.bin/ You can combine these scripts but I find it way simpler to separate them (you would need more elaborate options mounting devices).

  • mryessir@lemmy.sdf.orgtoOpen Source@lemmy.ml•Why FOSS projects are using proprietary, privacy invasive infrastructure?
    2·
    11 months ago

    I think he’s coming from here:

    As an developer you create a solution to a problem from yours. You release it under a FOSS license.

    Your job is done - You shared your work. The community may find your project useful and builds upon it. Their interest is to get their changes upstream. You have no obligation to help with onboarding and implementing features for others.

    So if they are requesting a merge you may reject it since it does not meet your standards. Maybe you have to make your stance clear and create a CONTRIBUTION alongside your code.

    With this mindset you wouldn’t hang out on a non-indexable platform.

    Your project mostlikely is requesting explicit participation. Maybe this is the point in between you guys.

    Now go on with the discussion :)

  • mryessir@lemmy.sdf.orgtoOpen Source@lemmy.ml•it is what it is
    14·
    11 months ago

    I see where you came from.

    There are people submitting code with wrong licenses or no attribution. There are people just submitting for the sake of submitting - I dare github profiles for this. There are people who could need some feedback on their code, so that future contributions have better quality.

    And it can be very burdensome for a maintainer, assuming he maintains within its free time, to perfectly communicate and elaborate on each contribution.

    Also, maybe the project has a feature freeze because in the aimed architecture the same solution would be implemented externally.

    Its just not that simple and people generalizing or concluding too fast are mostlikely in the wrong. Bad PR travles faster and further though.