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

EN | ES_MX

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

pleroma: [email protected] (no existe mas)

mastodon: [email protected]

Mexico-Tenochtitlan

  • 103 Posts
  • 23 Comments
Joined 6 years ago
cake
Cake day: January 22nd, 2020

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 @[email protected] 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 @[email protected] 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.



  • By simple logic it is not feasible to have a POSITION in a place that is soon under water (the threat of blowing up the dam is real if the liberation forces are still there). Kherson/Kherson is the city, not the oblast. It’s one thing to regroup (fix to secure more advantageous positions) and another to retreat (surrender leaving critical positions and outposts).

    What I see here is a huge booby trap; a Pyrrhic victory (reconquer the CITY) having already decimated Ukrainian forces, without human (civilian) shields, the adequate distance from your artillery (the local soldiers left but the other rear positions are intact) without the restriction of containing yourself to avoid civilian casualties and the enormous problem of trying to advance across the Dnieper (the bridges are just bait). In fact, it is attached to the strategy described by a Cuban commander who follows and is studying the events of this conflict; weaken the ukronazi positions, not even destroy them in their entirety, just affect them in such a way that they cannot maintain the positions in the rest of the black sea river (with the icing on the cake called Odessa).

    The media even plays for Russia indirectly (they can’t beat the Dombass and now they think they’re going for Crimea lol). Since most of the decisions that are being made on the Ukrainian/NATO side are based more on media consensus than military consensus.





  • It is a double-edged sword: Where is the Apache Foundation registered and operating? In the United States. The company that found the exploit, Alibaba, is Chinese. Even the department that found it (security team) is located in the offices of Alibaba Cloud, in Singapore. In short, the Chinese government was very close to having a tool to seriously damage the Western technology infrastructure, without the other side ever knowing where exactly they were being hit from. And if it had been the other way around? if that information had reached the Singaporean authorities earlier? we must not forget that it is a very servile government to the United States. Or in the worst case scenario the report was intercepted at the Apache Foundation, remember PRISM? one of their goals is to find potential vulnerabilities and exploit them against “hostile forces” even forcing companies registered on US soil and several beyond their borders to leave “backdoors” in their products/systems without public knowledge.

    Fortunately or unfortunately it was reported and announced publicly, without prior knowledge of the respective governments, so neither side gained a considerable advantage in this new field of warfare that is the cyberspace.