dinomug

Miguel, aka mickie. Code, Science, Politics, etc.

EN | ES_MX

blog: mugcake.gitlab.io/blog/ (ES/ desactualizado)

pleroma: migue@kawen.space (no existe mas)

mastodon: miguel@mstdn.mx

Mexico-Tenochtitlan

  • 298 Posts
  • 333 Comments
Joined 5 years ago
cake
Cake day: January 22nd, 2020

help-circle






  • As @yogthos@lemmy.ml mentioned, they differ in implementation:

    • The Hy compiler works by reading the Hy source code into Hy model objects and compiling the Hy model objects into Python abstract syntax tree (ast) objects. In other words, at runtime it is essentially Python source code. Similar to Typescript and CoffeScript (JS).
    • Basilisp is hosted on the Python virtual machine, so its compiler generates native Python bytecode. Similar to Clojure and Scala (Java/JVM) or Elixir (Erlang/BEAM).

    Personally in these cases, I prefer the second approach, because the first one is basically “syntactic sugar”: a Python lispy syntax (embedded), on the other hand Basilisp is a “more complete implementation”, that is, a language independent of the host language with all the strengths and weaknesses of its host system/VM.


  • Its seems pretty interesting. Now day MediaWiki is one of the largest codebases in PHP out there. But Wikimedia has excellent resources, somewhat extensive, but very good, from the lowest level sections (database, backend) to the style (css), plugins and frontend, including the scripts (lua). Although as @CriticalResist8@lemmygrad.ml comments that much is done in a very artisanal way, I think more than anything that the correct organization of the main dev, including admins and contributors, a lot of progress can be made with the limited resources available.



















  • Basically divide it in two main sections: for USERS and for DEVELOPERS. The first one like a guide/manual: about how this platform works for the average user (less tech stuff), graphical content, clients, etc. And the second one like a documentation/resources module: about how the platform works in-depth (API, Frontend/Backend dev, etc.).








  • dinomugtoPleromaStill empty here
    link
    fedilink
    arrow-up
    4
    ·
    1 year ago

    For several years I’ve been using Pleroma as my main social plataform along with Lemmy. Switching to Pleroma for new users is more difficult than it seems:

    • Minimalistic UI that might confuse people in some ways (maybe people might interpret the look as an old site from the early 2000s).
    • Many instances with controversial content: NSFW, Lollicon/Shotacon/Hentai, Shitposting, Politics (especially alt right), etc.
    • Lack of moderation (related to the previous point).
    • More instances for personal/private use than focused on growing a community.

    Pleroma has many features (eg Gopher support) that I recommend it for experienced/advanced users, people who know exactly what they want. Not for those who want a “simple twitter/facebook replacement”.



  • dinomugtoAsklemmy*Permanently Deleted*
    link
    fedilink
    arrow-up
    3
    ·
    2 years ago

    Huawei has one of the largest Innovation and Development , I+D, departments in the world; With a large number of patents in both software and hardware, registered trademarks, intellectual property and a presence in many fields of science: artificial intelligence, bioinformatics, aeronautics, energy, defense, semiconductors, etc. practically comparable to the giants in the sector such as Intel, AMD, Google, Oracle, Microsoft, Apple, etc. but with the added value of being a manufacturing corporation and having all the raw materials, as well as a large amount of cheap labor. Little dependent on the West.

    Huawei is more strategic in geopolitical terms, Xiaomi and other similar companies to a greater or lesser extent use patents or indirectly depend on Huawei, especially in IoT and Telecommunications