Ephera

  • 102 Posts
  • 5.39K Comments
Joined 5 年前
cake
Cake day: 2020年5月31日

help-circle



  • Epheratoich_iel@feddit.orgich_iel
    link
    fedilink
    Deutsch
    arrow-up
    3
    ·
    1 天前

    Naja, die Aussage war, dass eine vegane Ernährung nicht so sehr einschränkt und dafür muss man per Definition auf Eier und Milchprodukte verzichten.

    Oder war das eine ernsthafte moralische Frage? Falls Vegetarismus für dich moralisch nachvollziehbar ist, kann ich Argumente liefern, warum Veganismus meines Erachtens eine logische Schlussfolgerung aus den selben moralischen Werten ist.




  • EpheratoProgrammer Humor@programming.devSenior Wisdom
    link
    fedilink
    English
    arrow-up
    52
    ·
    1 天前

    Which is why making code readable is so very important. Our juniors and students will think we’re ridiculous, when we spend a long time cleaning up some code or choosing the least misunderstandable name for a type. But you fuck that up and then others, as well as your future self, will be wasting many more minutes misunderstanding what your code does.


  • EpheratoProgrammer Humor@programming.devSenior Wisdom
    link
    fedilink
    English
    arrow-up
    26
    ·
    1 天前

    Spamming comments is rather controversial, especially in high-level languages. Problem is, they only show up in one place, so they’re just not very useful, but also have a high chance of becoming inaccurate over time. In particular when you spam them to explain relatively trivial stuff, people will stop reading them, meaning they won’t update them.

    The ‘what’ can be documented with meaningful variable/function names, log/error/assert messages and perhaps most importantly unit/integration tests (which should be understood like a specification that checks automatically that it’s applied correctly).

    Comments are indispensible for explaining the ‘why’, though, whenever that is not obvious.









  • Epheratoich_iel@feddit.orgich🥇​🥇​🥇​iel
    link
    fedilink
    Deutsch
    arrow-up
    10
    ·
    1 天前

    Musste in der Schule einen Vortrag machen und hatte da das Thema “Desertec” mir rausgesucht. Das war so der total geile Masterplan, man baut einfach in der Sahara ein paar Solaranlagen auf, legt Stromleitungen nach Deutschland und zack, unendlich Strom.

    Ich hatte mich damals dann auch informiert, bei den besten Quellen: Deren Webseite und Wikipedia.
    Da wurde dann auch erwähnt, dass das DLR das auch für voll die geile Idee hält, was ich dann für eine ausreichend valide Quelle gehalten habe.

    Wir mussten dann so eine Zusammenfassung im Voraus einreichen, woraufhin meine Lehrerin meinte, dass das bei mir schon recht einseitig klingt.
    Also nochmal reingeschaut und gemerkt, dass der Wikipedia-Text teilweise einfach 1-zu-1 von deren Webseite copy-pasted ist. Dass das DLR das für eine geile Idee hält, sagt dadurch eben auch immer die Desertec Foundation selbst. Also ja, es gibt ein Paper, wo das DLR das Thema bespricht, aber so überragend positiv ist das nicht, und selbst das ist ja schon von Desertec vorselektiert.

    Dann eben mal ganz normal 'ne Websuche gemacht und direkt so Einwände gefunden, wie hey, wenn man so ein langes Kabel legt, dann braucht man da ordentlich Spannung drauf, um die Verluste gering zu halten. Und hey, die Sahara ist jetzt nicht gerade für ihre politische Stabilität bekannt. Oder für ihre Wasservorkommen, die man bräuchte, um die Solarpanele von Staub frei zu halten.

    Also kein Plan, vielleicht ist das trotzdem in einem gewissen Rahmen eine sinnvolle Idee, aber bin eben voll in’s Messer einer Lobbying-Gruppe reingerannt, die bewusst verzerrte Informationen verbreitet.


  • EpheratoFirefoxTell Mozilla: It’s time to ditch Google
    link
    fedilink
    English
    arrow-up
    11
    ·
    2 天前

    Your donation money does not go towards the salary of the Mozilla Corporation CEO. But yes, it does not go to Firefox development either. The Mozilla Corporation, which develops Firefox, needs to have enough money independent of donations, because the devs’ livelihoods depend on that. Well, and the donation money isn’t nearly enough to cover those costs anyways.
    So, the Mozilla Foundation (which owns the Mozilla Corporation and which you donate to) uses the donation money instead for political activism, for community work (which may lead to more contributors to Firefox) and sometimes they award some of that money to other open-source projects, which are also vital for an open web, but which are not visible enough to collect donations.



  • Well, it’s also not really a brand new OS. In many ways, postmarketOS picks up where desktop Linux stands. There’s some general integration tasks to solve, like how you can talk to the modem to make phone calls or how to deal with touch inputs, and then you may need to either update or rewrite desktop applications to make them responsive, so that they fit onto a phone screen, but then you end up with a pretty good OS relatively quickly. That is why I like the Plasma Mobile UI so much, because it’s just KDE Plasma from desktop Linux with some different configurations.

    There will still be certain drawbacks, for example some people rely on proprietary apps on their Android phone to interact with their banking or whatever, which are unlikely to become available for postmarketOS. But personally, I wouldn’t use these apps anyways, because they are so user hostile, so I won’t miss them anyways.


  • At $DAYJOB, we develop an application for basically linking up low-level devices over the internet. And yeah, in one codebase, we have:

    • A backend
    • A distributed system client/peer
    • A CLI
    • A web frontend
    • And simulation software to flash to those low-level devices

    All of that is in Rust, so it’s not just not wanting to learn different languages, it’s genuinely useful.
    We can use the same model types in the various clients and the backend, meaning it’s compile-time guaranteed that they work together. Just as well, we can generally use the same libraries. And while e.g. the web frontend and low-level software use frameworks, making it not entirely trivial to just jump into that part of the codebase, the barrier for entry is a lot lower.

    And yeah, ultimately that flexibility is something I find hard to give up, especially when customer requirements are as nebulous as they usually are.
    Honestly, we never had a hard reason why we should be using Rust. It was just that maybe we’d need such low-level simulation software, maybe we need the performance to process each individual network package, maybe we need to do things in the Linux kernel. The rest was just that we wanted to use Rust, because it’s a cool language.