est.social on üks paljudest sõltumatutest Mastodoni serveritest, mida saab fediversumis osalemiseks kasutada.
est.social on mõeldud Eestis üldkasutatavaks Mastodoni serveriks. est.social is meant to be a general use Mastodon server for Estonia.

Administraator:

Serveri statistika:

90
aktiivsed kasutajad

#rustlang

22 postitusega18 osalejaga0 postitust täna

my final project as part of my tenure at Microsoft, aside from that NPM patch (lol), is this lil' guy: github.com/microsoft/libsyncrpc

Just a small, but v v fast IPC lib that lets you make synchronous calls to a child process from node, while the child can execute callbacks from you before you return.

I optimized the everloving shit out of this thing, and it ended up being fast enough that the #TypeScript team will be able to use it for the thing that will let you use the Go typescript compiler from JS: you'll just be calling out directly to a Go child.

Literally hundreds of thousands of ops/s :)

synchronous RPC communication with callbacks for Node.js - microsoft/libsyncrpc
GitHubGitHub - microsoft/libsyncrpc: synchronous RPC communication with callbacks for Node.jssynchronous RPC communication with callbacks for Node.js - microsoft/libsyncrpc

Alright!

I just released a first functional version of a new crate:

🔧 test-dsl at 0.1.0

🦀 github.com/TheNeikos/test-dsl/

To paraphrase the readme: test-dsl allows you to easily author tests by decoupling between the 'test harness', 'verbs' and 'conditions'.

It's role in your testing infra would be as boilerplate reduction, so that you can focus on just writing tests around the behaviour of your system. I'm using this pattern for example in a client-server context. So I have verbs like start_server 1, start_client 2, connect_client 2 1 etc...

Of course the meaning of these verbs is highly project-specific.

If a verb does fail, either by panicking or returning an error, you get a nice error output telling you exactly which file and which verb caused the error. Allowing you to more easily pin-point directly what went wrong, rather than potentially searching through a log.

It works great together with datatest-stable from the nextest project, but it works just as fine standalone.

It uses #KDL as the language to write your testcases in, so its fairly nice to read.

It's still missing more comprehensive documentation, but as a prototype it should work just fine!

It actually sprung out from having used this pattern a few times, and I didn't want to re-write the boilerplate around it, and maybe re-use some code between projects.

Contribute to TheNeikos/test-dsl development by creating an account on GitHub.
GitHubGitHub - TheNeikos/test-dslContribute to TheNeikos/test-dsl development by creating an account on GitHub.

I'm proud to announce the project I've been working on for the last two years - Xee: a modern implementation of XPath and XSLT in Rust.

I know XML isn't hip anymore but this is a programming language implementation in Rust, according to extensive specifications!

blog.startifact.com/posts/xee/

#RustLang #xml @thisweekinrust

Secret WeblogXee: A Modern XPath and XSLT Engine in RustI announce Xee, the implementation of XPath and XSLT in Rust that I've been working on for the last two years.

Garage - An open-source distributed object storage service

Does any of you know about this and also use it professionally and if so in what context and how? Honestly, I'm standing up a little.

📦 garagehq.deuxfleurs.fr

garagehq.deuxfleurs.frGarage - An open-source distributed object storage serviceAn open-source distributed storage service you can self-host to fullfill many needs.

When I started writing a tiling simplex noise function in #RustLang two weeks ago, it ran in about 100 milliseconds for a block of 2048×2048 pixels.

Now it runs in 1.3 milliseconds. That's 13 GB/s throughput; maybe memory is even the bottleneck now.

Lessons learned:
- AVX2 is awesome
- simdeez makes it relatively easy to use
- simdnoise is damn clever
- iterators are slow
- collecting into a Vec first is faster
- iterating over coordinates manually is the fastest
- rayon is awesome

🔥 Keep your commits consistent!
🔥 forgejo-commit-path-rules v0.2.3 ensures your commit messages align with your file changes.

🧩 Enforce commit message and file path rules in your repo!

🦀 Written in Rust
⭐ Repo: https://codeberg.org/kemitix/forgejo-commit-path-rules
🎬 A ForgeJo Action/CLI Tool

✨ What's New:

- Coloured highlights in logging (supports --no-colour)
- all matching strategy for paths (default is any)
- Built in templates: docs, feature, tests and fixes

🛠 Usage:

- Define rules in .forgejo/commit-path-rules.toml
- Run via CLI or ForgeJo Action

Install:
cargo install forgejo-commit-path-rules

CLI Usage:
forgejo-commit-path-rules --workspace . --no-colour

Forgejo Action:

 jobs:
  validate:
   steps:
    - uses: actions/checkout@v3
      with:
        fetch-depth: 0
    - name: Run forgejo-commit-path-rules
      uses: kemitix/commit-path-rules@v0.2.3
      with:
        args: --verbose
Summary card of repository kemitix/forgejo-commit-path-rules
Codeberg.orgforgejo-commit-path-rulesEnforce consistency between commit messages and file changes in your repository.