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

  • 299 Posts
  • 341 Comments
Joined 5 年前
cake
Cake day: 2020年1月22日

help-circle



  • For the moment I see unnecessary to close the community or delete it, both because it is the first community of Minetest/Luanti to be created in lemmy (of any instance), which implies that by age, being in the first and largest instance of this network, number of members, posts, etc. appears first in all searches of the different instances in everything concerning Minetest/Luanti.

    And secondly because of the recent change of image and name. Only until ‘Luanti’ as a brand name surpasses the ‘Minetest’ brand name, can the latter be discarded. As mentioned in the blog post:

    you’ll probably still hear “Minetest” occasionally in reference to Minetest Game which will remain a testament to the project’s roots. Otherwise, Luanti now represents the future of the platform.

    BTW, you can be a mod here, and unify efforts with the community of your instance :D













  • 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.