shakedown.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A community for live music fans with roots in the jam scene. Shakedown Social is run by a team of volunteers (led by @clifff and @sethadam1) and funded by donations.

Administered by:

Server stats:

246
active users

#lua

3 posts3 participants0 posts today

Hello Fediverse. So I'm looking for a #remote #opensource job or project in European timezones.

I am not good in writing CVs. So I'm just listing the projects I have done:

I'm a #Linux user. I have good experience using CLI, and I have basic shell scripting skills. I also have a little experience with #FreeBSD

I am also good at reading academic papers, standards(like RFCs) and manpages.

I am up for working on #FOSS projects as freelancer or part time contracts.

Boosts appreciated :)

PS: I am also familiar with #CommonLisp. But I highly doubt if I can find a #Lisp job anywhere!

Summary card of repository farooqkz/wakegp
Codeberg.orgwakegpDetecting wake words using Linear Genetic Programming

Weekend goal: a #Lua chunk (script) to help sighted users review #Braille. It's a great way to understand how visually impaired users interact with a computer using a screen reader and a Braille display. The script is simple and easy to configure. Currently, it offers a learning mode; in the future, a challenge mode will be added, along with a blog post explaining how to set it up.

Link: gitlab.com/-/snippets/4858299

On #FreeBSD it should be executable via flua:
% flua learnbraille.lua

after installing liblouis:
# pkg install liblouis

[edit] % /usr/libexec/flua learnbraille.lua

after 25+ years of class-based OOP i'm learning to think in terms of prototype-based OOP. it's a subtle change, and wow does it ever loosen up my thought processes

instead of thinking top-down (and bottom up) about my game architecture and worrying about rational hierarchies, i'm learning how to think in terms of pure functionality and cloning and then extending objects.

it's a relief learning something new. i'm no longer forcing lua to be not-lua.

all of this is thanks to the smalltalk-80 reference book i picked up a few months ago, along with a great article on the history of smalltalk by alan kay

worrydream.com/EarlyHistoryOfS

🆕 release pandoc 3.7 ✨

Features:
• New option `--variable-json`. Structured variable values can now be passed via the command line.
• Rowspans and colspans are supported in grid-table output (#Markdown and #RST).
• Improved handling of inline TeX in #orgmode.
#Lua subsystem: the `pandoc.read` function can now be used in “sandboxed” mode, restricting file or network access.

Please see the changelog for the full list of changes and bugfixes.
github.com/jgm/pandoc/releases

GitHubRelease pandoc 3.7 · jgm/pandocI'm pleased to announce the release of pandoc 3.7, available in the usual places: Binary packages & changelog: https://github.com/jgm/pandoc/releases/tag/3.7 Source & API documentation: http://hack...

Programming languages, I've tried a few. PHP, Javascript, Python, Nim, Rust (briefly), and Go. I've variously thought they are too yucky, warty, ugly, complex, or just plain too hard for me. I've never found my fit.

I'm starting to think that #Lua might be what I've been looking for... crazy?

Ok, so I’m now a few months into building a custom (almost from scratch) #Lua implementation for @silverbulletmd dubbed #SpaceLua (for reasons).

A few things that panned out really well, and a few surprises that I did not anticipate:

0. General recommendation: don’t do this. Don’t just implement a full programming language because you think it’s a good idea. I also told this myself. It didn’t work. It was a “I’ve don’t this stuff before, I can do it again” type of deal. I was mostly right. But don’t do this.

1. Initially I opted for a custom interpreter (implemented in TypeScript) because I wanted to expose asynchronous (promise based) JS APIs to Lua, and I didn’t see how to do that nicely with a #Wasm-compiled version of the official Lua interpreter. Also I felt that having full control of the running system would turn out to be valuable down the line (I was right on this one).

2. I got the parser part mostly free. I found an existing Lua grammar for the Lezer parser library that #SilverBullet uses. Had to add a few things and had some struggles. This part was pretty seamless with a few glitches here and there.

3. Implementing the core interpreter runtime was actually quite easy. Lua is a mostly simple and small language. Again, I’ve done this before so that helped. Writing good test suites makes this doable and AI helped a lot generating those test suites (because it knows Lua).

4. What I didn’t anticipate is the pain in implementing the full Lua API, especially the `string.*` one which has its own pattern matching language (similar but distinct from regular expressions), which honestly I could do without. But it’s there, and people want to use it, so I need a full implementation. Issues keep coming up, though.

Ok. Day one of using @silverbulletmd in #Vim mode lead to already fixing some ugly UI glitches. Now thinking how to expand #Lua APIs to define Vim commands, bindings and other things. Also a reason to dive a bit deeper into @neovim which leans heavily on Lua. Also an interesting source of inspiration for Lua API design potentially.