home.social

#programming-language — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #programming-language, aggregated by home.social.

fetched live
  1. DotLox now has a small but decent standard library which includes:

    - read() for reading user input
    - readFile() for reading file contents
    - writeFile() for writing content to a file
    - mod() for doing the modulo operation

    This opens the door for alot of potential programs, though there are still gaps such as string manipulation and converting data types.

    github.com/TerrellAW/DotLox

    #programming #programminglanguage #lox #buildinpublic

  2. I finally finished Chapter 13 of #CraftingInterpreters. I've learned alot working on this project, especially since I chose to do it in #Csharp instead of directly copying the book's Java.

    Now I plan on implementing some more standard library functions, do the challenges I skipped on my first pass through the book and then move on to the next part, implementing a #compiler that outputs byte code to be ran by a virtual machine.

    github.com/TerrellAW/DotLox

    #programming #programminglanguage #lox

  3. 🤦‍♂️ Ah yes, an epic tale of Wikipedia drama over an obscure programming language that nobody asked for, told in a riveting 9,238-word saga. 🎉 Watch in awe as the author turns morning rituals into a grand odyssey of existential crises and digital bureaucracy. 📚✨
    katamari64.se/posts/2026/odin- #WikipediaDrama #ProgrammingLanguage #EpicTale #DigitalBureaucracy #ExistentialCrises #HackerNews #ngated

  4. 🤦‍♂️ Ah yes, an epic tale of Wikipedia drama over an obscure programming language that nobody asked for, told in a riveting 9,238-word saga. 🎉 Watch in awe as the author turns morning rituals into a grand odyssey of existential crises and digital bureaucracy. 📚✨
    katamari64.se/posts/2026/odin- #WikipediaDrama #ProgrammingLanguage #EpicTale #DigitalBureaucracy #ExistentialCrises #HackerNews #ngated

  5. 🚀✨ Presenting Rhombus 1.0: because what the world needs right now is yet another programming language to ignore. With a name that screams geometrical confusion, this software marvel is brought to you by a committee of 20 contributors who couldn't decide on what a 'modern' language is supposed to be. 😂🔧
    blog.racket-lang.org/2026/06/r #Rhombus1_0 #programminglanguage #softwaredevelopment #techhumor #modernlanguages #HackerNews #ngated

  6. 🚀✨ Presenting Rhombus 1.0: because what the world needs right now is yet another programming language to ignore. With a name that screams geometrical confusion, this software marvel is brought to you by a committee of 20 contributors who couldn't decide on what a 'modern' language is supposed to be. 😂🔧
    blog.racket-lang.org/2026/06/r #Rhombus1_0 #programminglanguage #softwaredevelopment #techhumor #modernlanguages #HackerNews #ngated

  7. I find myself holding perhaps strange opinions.

    Suppose there is some language that has a type for integers the platform’s native pointer width, like size_t or usize.

    Suppose there is also a mechanism for getting the bit-width of a type, like sizeof.

    Then, which of these two is better?
    A constant named e.g. USIZEWIDTH that is defined to hold the width of usize, or
    A macro or function defined using sizeof to do the same thing?

    Obviously you can always use sizeof yourself. This would be an abbreviation.

    Strangely, I find myself preferring the function or macro. It feels like this makes the fact that it does in fact represent the width of usize less coincidental.

    But, of course, the function or macro is also coincidental. Just as the USIZEWIDTH value could be (accidentally) wrong, the function or macro could be (accidentally) defined the wrong way.

    I believe that the reason for this is that a change in the platform (i.e. a change in the compiler) would automatically update the function or macro’s output. An accidental mismatch for the constant wouldn’t require actively meddling with its definition at all.

    #programming #programminglanguage

  8. I find myself holding perhaps strange opinions.

    Suppose there is some language that has a type for integers the platform’s native pointer width, like size_t or usize.

    Suppose there is also a mechanism for getting the bit-width of a type, like sizeof.

    Then, which of these two is better?
    A constant named e.g. USIZEWIDTH that is defined to hold the width of usize, or
    A macro or function defined using sizeof to do the same thing?

    Obviously you can always use sizeof yourself. This would be an abbreviation.

    Strangely, I find myself preferring the function or macro. It feels like this makes the fact that it does in fact represent the width of usize less coincidental.

    But, of course, the function or macro is also coincidental. Just as the USIZEWIDTH value could be (accidentally) wrong, the function or macro could be (accidentally) defined the wrong way.

    I believe that the reason for this is that a change in the platform (i.e. a change in the compiler) would automatically update the function or macro’s output. An accidental mismatch for the constant wouldn’t require actively meddling with its definition at all.

    #programming #programminglanguage

  9. Hello 🙂,

    How do you handle events?
    Here is a little comparison using an example: programming a button that toggles a text.

    ▶️ Event-driven (JavaScript/DOM, Gtk, Qt...)
    ------------
    label := 'state 1'
    on click:
    label := (if label = 'state2' then 'state1' else 'state2')

    ▶️ Immediate mode (ImGui, G'MIC...)
    --------------
    setup:
    label := 'state1'
    draw:
    if click:
    label := (if label = 'state2' then 'state1' else 'state2')

    ▶️ FuncSug
    --------
    while true:
    label := 'state1'
    await click
    label := 'state2'
    await click

    An example 'Cross the River': cl4cnam.github.io/try_FuncSug?
    FuncSug playground: cl4cnam.github.io/try_FuncSug

    #programmingLanguage #eventLoop #GUI

  10. La programmation événementielle n'est pas une panacée. Cela est connu depuis longtemps. Il y a une vingtaine d'année, l'article d'Andreas Gustafsson (spawn-queue.acm.org/doi/pdf/10) l'expliquait bien. Qu'en est-il aujourd'hui ? Pourquoi la programmation événementielle est-elle encore présentée de nos jours comme une évidence ou, au mieux, comme un mal nécessaire ?

    #programmingLanguage #eventLoop #GUI

  11. Was this already considered for any #programmingLanguage?

    Wouldn’t it be cool, if it was possible to use #markdown for comments in code?
    I’m borrowing from #Jupyter notebooks.

  12. Was this already considered for any #programmingLanguage?

    Wouldn’t it be cool, if it was possible to use #markdown for comments in code?
    I’m borrowing from #Jupyter notebooks.

  13. #HCL isn't a #programminglanguage, it’s a configuration syntax, meaning you can grasp its mechanics in weeks once you understand #networking concepts. #JavaScript takes longer due to its asynchronous nature, but it is necessary for decoding #web app vulnerabilities.

    Btw #HCL is HashiCorp Configuration Language.
    This is what it looks like:

    resource "aws_vpc" "v" {
    cidr_block = "10.0.0.0/16"
    tags = {
    Name = "prod"
    }
    }

  14. tested zig
    language is, as the version number suggests, unstable
    examples you find just don't work anymore
    wasn't fun to play with; revisiting in 2-5 years again

    github.com/bison--/learning-zig

    #zig #programming #programminglanguage

  15. tested zig
    language is, as the version number suggests, unstable
    examples you find just don't work anymore
    wasn't fun to play with; revisiting in 2-5 years again

    github.com/bison--/learning-zig

    #zig #programming #programminglanguage

  16. 🤔 So you decided to create your own programming language because, why not? It's not like we have enough of those already, right? 😜 Fear not, amateur linguists: the author assures us it's "easier but harder," which is super helpful! 🙄 Oh, and don't hold your breath for this "not another CC/Rust killer" to ever actually exist. 😂
    lisyarus.github.io/blog/posts/ #programminglanguage #humor #technews #softwaredevelopment #codingjokes #HackerNews #ngated

  17. J'ai ajouté un exemple dans le playground(*) de FuncSug : l'écluse du logiciel éducatif GCompris. Qu'en pensez-vous ?
    FuncSug est un langage qui permet de programmer de façon entièrement synchrone sans blocage.
    (*) Un playground permet de tester du code sans rien installer.

    ▶️ L'exemple : cl4cnam.github.io/try_FuncSug/
    ▶️ FuncSug : github.com/cl4cnam/funcSug
    ▶️ GCompris : gcompris.net

    #education #jeu #programmingLanguage #GCompris #opensource

  18. “The best people don’t quit after starting —
    no matter how many obstacles come."

    @python#begginer #coding #StartCoding #programminglanguage

  19. I was thinking to be fluent in another /framework.
    The low hanging fruit would be , but either way I'd have to learn . Even thoudh I'd love to work with .
    But I was thinking about a low level language like or .

    Any suggestions or tips? Is it even possible (or sustainable) this? How to keep up in the loop in both worlds?

  20. An idea to defeat #GenerativeAI in #FreeSoftware:

    Just use a #ProgrammingLanguage that isn’t popular (e.g. #Haskell or some #Lisp dialect) to write your code, but publish human-readable intermediate form of that code in the public code repositories (e.g. the C programming language). Share the actual source code privately with trusted contributors in non-public branches, and require GPG signatures on actual contributions.

    You could argue that not sharing source code is against the GPL, but the GPL does allow you to share the code as a hard copy printed on paper and sent over snail mail. Or you can just wait until the person asking is an actual human that you can trust not to use the source code for LLM training.

    LLMs are unable to learn unpopular programming languages because they don’t have a sufficient corpus of training data to learn how to code it, so if your receive a contribution in C, thank the contributor but inform them that they will have to rewrite the contribution in your Lisp dialect before you can accept it.

    #Scheme dialects like #Gambit , #Chicken , and #Bigloo would work well for this. So would a #CommonLisp implementation that translates to C such as #ECL . Although keep in mind that the idea is to use a less popular language, so you may have to further obscure these languages a little bit, but not in a way that would be difficult for humans. For example, using a macro system, you could use df instead of define, rename types of things like string? to utf8str?, use generic functions with mulitple dispatch so append will work on strings, lists, vectors, and bytevectors. Small tweaks like this might throw-off an LLM asked to write source code in Lisp.

    #tech #software #LLMs #LLM #FOSS #FLOSS #OpenSource #SchemeLang #R7RS