buc.ci is a Fediverse instance that uses the ActivityPub protocol. In other words, users at this host can communicate with people that use software like Mastodon, Pleroma, Friendica, etc. all around the world.

This server runs the snac software and there is no automatic sign-up process.

Admin email
abucci@bucci.onl
Admin account
@abucci@buc.ci

Search results for tag #lisp

AodeRelay boosted

[?]mintbug » 🌐
@mintbug@mastodon.ml

хоть немного зашарить за лисп стоит хотя бы ради того, чтобы распробовать kebab-case и начать использовать его везде, где только можно. В частности, в названиях файлов.

    AodeRelay boosted

    [?]Farooq [Master Patata] » 🌐
    @farooqkz@mastodon.bsd.cafe

    @david_chisnall

    I very much am interested in looking OS designs beyond .

    For instance I felt a real need for a different programming interface, OS and filesystem while I was doing research. I thought I wanted a Machine comeback(hence title of the blog post below). But after research, I found the precise term to be "residential style developement". Below is me blog post:

    far.chickenkiller.com/computin

    I have also seen other software developers complaining about storage interface in Operating Systems and programming languages. For instance, here's a quote from Viktor who developers search engine complaining about this:

    > This is mostly a post to complain about something > that chafes. I wish there was a programming language (ideally several) that acknowledged that computers have hard drives, not just a processor, RAM and other_devices[].

    His blog post is here:

    marginalia.nu/log/53-better-ha

      AodeRelay boosted

      [?]Ramin Honary » 🌐
      @ramin_hal9001@fe.disroot.org

      Apropos of nothing: Big thanks to Shiro Kawai for creating Gauche Scheme, which so far has been one of the best Scheme implementations I have used. It has worked well on every computer I have tried it on so far ({Linux, FreeBSD, MacOS} x {x86_64, i386, aarch64}). It is stable, very fast, and supports a large number of the more recent SRFIs (Scheme language extensions), it has very good compatibility with the R7RS language standard, and the Gauche REPL gosh is pretty easy to use as well.

      I always run the REPL in R7RS mode, so gosh -r7 -I. -i . Scheme people, give it a try sometime if you haven’t already!

      https://practical-scheme.net/gauche/

      #tech #software #Scheme #R7RS #Lisp #SchemeLang #FunctionalProgramming #Gauche

        [?]Aaron » 🌐
        @hosford42@techhub.social

        I wonder why genetic programming so often uses a Lisp-inspired paradigm instead of a Forth-inspired one. They are both extremely simple to implement, but Forth has the advantage of being expressible as a linear sequence, so standard genetic algorithm operators can be used on it. If you find Lisp syntax more readable, it would be easy to translate, since they are both inherently nested.




          AodeRelay boosted

          [?]Paolo Amoroso » 🌐
          @amoroso@oldbytes.space

          At almost 800 pages The Architecture of Symbolic Computers by Peter Kogge (McGraw-Hill, 1991) is a massive tome on Lisp Machines, logic systems, and other symbolic computer architectures.

          archive.org/details/architectu

            AodeRelay boosted

            [?]Paolo Amoroso » 🌐
            @amoroso@oldbytes.space

            Reminder to self: the classic 1978 book Anatomy of LISP by John Allen is available online, so add it to the reading list.

            archive.org/details/mc-graw-hi

            archive.org/details/anatomyofl

              [?]mx alex tax1a - 2020 (6) » 🌐
              @atax1a@infosec.exchange

              about to commit a heresy:

              car and cdr were obsoleted by destructuring-bind and it's time to say goodbye

              where the clhs goes wrong is preventing us from writing (defun teh ((a . b)) (cons b a)) and calling it as (teh (3 . 2)) to get (2 . 3) back, instead we have to write (defmacro teh ((a . b)) (cons ,b ,a))

              if they just removed ordinary lambda lists and declared them all to destructure, we could be rid of a 60 year hangover from an ibm architecture

                AodeRelay boosted

                [?]Radio_Azureus » 🌐
                @Radio_Azureus@ioc.exchange

                The agonizing slow death of the power user

                This is a fascinating article to read. The facts are nailed to the wall in clear and easy to comprehend jargon, even for the non-grey beards

                Some quotes

                Ask a twenty-two-year-old to connect to a remote server via SSH. Ask them to explain what DNS is at a conceptual level. Ask them to tell you the difference between their router’s public IP and the local IP of their laptop. Ask them to open a terminal and list the contents of a directory. These are not advanced topics. Twenty years ago these were things you learned in the first week of any serious engagement with computers. Today they’re exotic knowledge that even a lot of working software developers don’t have, because you can go a long way in modern development without ever leaving the managed abstractions your platform provides.

                And that’s the real damage. It’s not just end users who don’t know this stuff. It’s developers. People who write software for a living who’ve never had to think about what happens between their API call and the response. Who’ve never had to debug something at the network layer. Who’ve never had to read a full stack trace and understand every frame of it. Because the frameworks handle all of that, and the frameworks are good enough, and figuring out how things actually work is optional.

                Some facts

                Power User

                A power user is a user of computers, software and other electronic devices who uses advanced features of computer hardware,[1][2][3] operating systems,[4] programs, or websites[5] which are not used by the average user. A power user might not have extensive technical knowledge of the systems they use[6] but is rather characterized by competence or desire to make the most intensive use of computer programs or systems.

                Term use

                The term came into use in the 1980s, as advocates for computing developed special skills for working with or customizing existing hardware and software. Power users knew the best ways to perform common tasks and find advanced information before the arrival of the commercial Internet. On PC platforms, power users read magazines like Byte or PC Magazine, and knew enough about operating systems to create and edit batch files, write short programs in BASIC, and adjust system settings. They tended to customize or "supercharge" existing systems, rather than create new software.[7]

                Notes

                This is systematically done by the factories of technology. I am baffled that a 41 year old litterate person, with secondary school and partial tertiary school, cant tell the difference between an email account, a FB account, a local machine account, a table, notebook and Android phone, from the basic technological perspective. This happened a couple of hours ago, which makes this article very relevant to me.

                This person was born two generations ago!

                WTF happened to reading manuals!?

                I read all manuals I get with hardware I buy, go online to fetch and read, PRINT IF I HAVE TO!

                Power Users are a sub-species of homosapiens which is in the greybeard stage.

                Eventually we will drop our current corpus and move on to other energy levels of existence

                Power users will become extinct in the next generation or two

                A bleak future for those left

                Z

                sources

                en.wikipedia.org/wiki/Power_Us

                fireborn.mataroa.blog/blog/the

                screencap of site

                Alt...screencap of site

                screencap of site

                Alt...screencap of site

                screencap of site

                Alt...screencap of site

                screencap of site

                Alt...screencap of site

                  AodeRelay boosted

                  [?]Tomáš » 🌐
                  @prahou@merveilles.town

                  A compact interpreter for a minimal lisp/scheme dialect. A street lisp.
                  git.sr.ht/~ft/sl

                  lisp accurate streetlisp alien

                  Alt...lisp accurate streetlisp alien

                    AodeRelay boosted

                    [?]Paolo Amoroso » 🌐
                    @amoroso@oldbytes.space

                    The book A Programmer's Guide to COMMON LISP by Deborah Tatar (Digital Press, 1987), along with the errata, is now online with permission from the author.

                    archive.org/details/a-programm

                    My review of the book:

                    journal.paoloamoroso.com/readi

                      [?]Yukari Hafner :v_lesbian: » 🌐
                      @shinmera@mastodon.tymoon.eu

                      New blog post: On , LLMs, and Community
                      reader.tymoon.eu/article/444

                        28 ★ 9 ↺
                        planetscape boosted

                        [?]Anthony » 🌐
                        @abucci@buc.ci

                        A weird thing about being 50 is that there are programming languages that I've used regularly for longer than some of the software developers I work with have been alive. I first wrote BASIC code in the 1980s. The first time I wrote an expression evaluator--a fairly standard programming puzzle or homework--was in 1990. I wrote it in Pascal for an undergraduate homework assignment. I first wrote perl in the early 1990s, when it was still perl 4.036 (5.38.2 now). I first wrote java in 1995-ish, when it was still java 1.0 (1.21 now). I first wrote scala, which I still use for most things today, in 2013-ish, when it was still scala 2.8 (3.4.0 now). At various times I've been "fluent" in 8086 assembly, BASIC, C, Pascal, perl, python, java, scala; and passable in LISP/Scheme, Prolog, old school Mathematica, (early days) Objective C, matlab/octave, and R. I've written a few lines of Fortran and more than a few lines of COBOL that I ran in a production system once. I could probably write a bit of Haskell if pressed but for some reason I really dislike its syntax so I've never been enthusiastic about learning it well. I've experimented with Clean, Flix, Curry, Unison, Factor, and Joy and learned bits and pieces of each of those. I'm trying to decide whether I should try learning Idris, Agda, and/or Lean. I'm pretty sure I'm forgetting a few languages. Bit of 6502 assembly long ago. Bit of Unix/Linux shell scripting languages (old enough to have lived and breathed tcsh before switching to bash; I use fish now mostly).

                        When I say passable: in graduate school I wrote a Prolog interpreter in java (including parsing source code or REPL input), within which I could run the classic examples like append or (very simple) symbolic differentiation/integration. As an undergraduate I wrote a Mathematica program to solve the word recognition problem for context-free formal languages. But I'd need some study time to be able to write these languages again.

                        I don't know what the hell prompted me to reminisce about programming languages. I hope it doesn't come off as a humblebrag but rather like old guy spinning yarns. I think I've been through so many because I'm never quite happy with any one of them and because I've had a varied career that started when I was pretty young.

                        I guess I'm also half hoping to find people on here who have similar interests so I'm going to riddle this post with hashtags:


                          about this site - powered by snac/2.86