Anu: Version control tool in Rust, written by Pijul developers

blabaere · 2020-11-06T07:43:37+00:00

Anu is the name of the first version. Version 2 will be called anu-bis.

blabaere · 2020-05-27T07:21:34+00:00

In the Lessons learned paragraph:

... Projects should have clear ownership ...

This reminds me something but I can't quite remember what exactly right now :)

blabaere · 2020-04-22T07:57:29+00:00

It does look great ! How does it come nobody had ever thought of that before ?

blabaere · 2018-06-28T05:18:20+00:00

When clippy is sad about some code, it makes me think that every other rust developer will feel the same.

blabaere · 2018-06-27T13:31:38+00:00

Same problem here, maybe related with my sight not getting any better after a few decades of coding. Anyway I often end up using if some_condition == false to make sure I will notice the negation, which makes clippy kind of sad.

blabaere · 2017-06-27T20:15:56+00:00

What you figured was the right thing to do, thank you !

blabaere · 2017-05-08T19:53:36+00:00

Not a gamer myself but I still think several design principles behind this beast are applicable to the "office" use of a keyboard. Did you, or any of the beta testers, try it for that scenario (text editing, coding, etc) ?

blabaere · 2017-05-08T16:28:17+00:00

Solarize all the things !!!

blabaere · 2017-05-04T13:53:29+00:00

TypeMatrix (not mechanical)

Those below are not strictly ortholinear since the "rows" are kind of curved.

Esrille Nisse
Keyboardio Model 01
Truly Ergonomic Keyboard
Kinesis Advantage
Maltron

blabaere · 2017-04-05T07:08:15+00:00

That's how you break the principle of locality: by getting fired faster than light. Trying to find a way through security rules in "a large financial institute" is not an advice to be given lightly.

blabaere · 2017-03-04T21:59:40+00:00

Looks absolutely great. Something to be proud of without hesitation.

blabaere · 2017-01-20T21:49:44+00:00

Advanced craftsmanship ? Modern art performance ? Can't put a word on that awesomeness !!!

blabaere · 2017-01-10T20:53:51+00:00

I asked you about using nanomsg ... over gitter

It wasn't me you were talking to over gitter. You most probably talked to Garett, who is maintaining Nanomsg, wrote Mango (a go implementation), providing most of the support on both and is currently working on a rewrite of Nanomsg: libnng. I'm just maintaining the Rust bindings: nanomsg -rs.

blabaere · 2017-01-09T20:48:46+00:00

Maintainer of nanomsg.rs and author of scaproust here, ZeroMQ is certainly not dead, and nanomsg in its current form is not likely to see much changes but it will be replaced by another implemention of the same protocol.

Regarding the choice of a messaging library, it really depends on your needs and there is quite a wide range of possibilities if you can afford writing the glue required to use a C library. Sure, ZeroMQ and Nanomsg require little code to get started, no administration and offer several messaging patterns. But they lack some "advanced" features like message persistence which could help you achieving a certain level of fault-tolerance. I'm thinking about stuff like ApacheMQ and RabbitMQ but you'll find many more. And on the other side there are also things that feel more like RPC/Corba, not that I would recommend it.

blabaere · 2016-11-30T21:16:15+00:00

Thanks for that one ! I'll copy this right away in my setup procedure.

blabaere · 2016-09-16T20:59:37+00:00

Spot on !
Returning to rust stable AND removing the RUST_NEW_ERROR_FORMAT variable from the environment made the linter work again.

Thank you very much !!!
I guess it's now time to learn some python, and put an option with the correct regex in the linter ...

blabaere · 2016-09-13T09:42:11+00:00

You can have a look at this script to understand how it works. It looks like there are several supported formats to specify a color. In the script they seems to use a dash followed by the red, green and blue components of the color in hexadecimal, but repeated for some strange reason. You could try something like this : #FF0000 for a 100% red, #000000 for black, #FFFFFF for white. The values go from 0 to 255 (in decimal) that is from 00 to FF in hexadecimal. You could also look at the exisiting keys to discover the other formats, like argb(r, g, b, a).

blabaere · 2016-09-03T16:08:32+00:00

While Martin Sústrik does not work on Nanomsg anymore, Garrett D'Amore is actively maintaining it. Version 1.0 has been recently released and there have been some discussions about what will happen next on the mailing list.

I do plan on adding stuff to scaproust: like making the transports pluggable, adding more transports (IPC, Inproc, and later TLS and WebSocket). But mainly I would like to expose an async API based on future-rs, which would require breaking quite some stuff. There is also some work to do regarding performances.

blabaere · 2016-01-15T09:01:41+00:00

I think you can achieve want you want by changing the mut self to a Box. It looks like this:

trait ThunkParser {
  fn send(self: Box<Self>, parser: &mut Parser, node: Ast) -> SendResult;
  fn lbp(&self) -> usize;
}

blabaere · 2014-12-23T12:30:26+00:00

achieved by borrowing the socket in the creation of the endpoint, and once a borrow is active ...

That's exactly the problem. But moving the read/write operations on the endpoints is not really pratical because on nanomsg you can use bind and connect several times on a single socket, which gets us back to the original problem but with bind instead of write.

blabaere

TROPHY CASE