Bruno Croci

into graphics programming, creative coding, gamedev and photography. currently audio programmer @ Ubisoft Düsseldorf; he/him/his.

[Bruno Croci @CrociDB]

I implement themes in bulletty, the TUI feed reader. The good thing about using base16 theme format, is that I instantly have so many harmonic themes! This was so fun doing that I had to come here and brag 📷 #rust #rss

[Bruno Croci @CrociDB]

New blog post: This blog ran on Ubuntu 16.04 for 10 years. I migrated it to FreeBSD

https://t.co/jytn0s9B64

[Bruno Croci @CrociDB]

Posted about my journey to get rid of caps lock on all my devices:

https://t.co/Vurh38Udoy

[Bruno Croci @CrociDB]

Wrapping up FOSDEM today with @raysan5! #raylib

[Bruno Croci @CrociDB]

https://t.co/BsS6W1mmco

[Bruno Croci @CrociDB]

btw, it runs on android too:

[Bruno Croci @CrociDB]

bulletty v0.2.0 released with new exciting features! 🎉

- Theme support
- Read Later category
- Reader width customization
- .. and more!

https://t.co/iAkfh8xnwq

#rss #reader #tui #rust

[Bruno Croci @CrociDB]

It's already published as a nightly build. Or alternatively you can install with:

`cargo install --git https://t.co/DqfcsqaAfV --force`

from the unstable main branch, if you wanna try it. :)

[Bruno Croci @CrociDB]

I implement themes in bulletty, the TUI feed reader. The good thing about using base16 theme format, is that I instantly have so many harmonic themes! This was so fun doing that I had to come here and brag 📷 #rust #rss

[Bruno Croci @CrociDB]

Nothing is apolitical. One thing is not being aware of the political content in your discourse. Now, convincing others that your discourse is apolitical is actually a big political agenda. And a very mainstream one.

[Bruno Croci @CrociDB]

Been working on bulletty, a pretty TUI feed reader that stores the articles as markdown.

It's usable, but there are still many features I want to implement, such as article notes and highlight, themes, terminal images, etc.

Check it out: https://t.co/DqfcsqaAfV

#rust #tui

[Bruno Croci @CrociDB]

As someone who also worked in this project, I share many of Mark's feelings. =/

[Mark Rubin @PixelsofMark]

It’s a sad day for fans of XDefiant and for all of the passionate devs that worked so hard on this game. I want to thank everyone who played it and everyone who promoted it whether you were a big content creator or just a fan. Every voice mattered.
In fact, I would say something remarkable happened with this game in that although we had very little marketing, we still had the fastest acquisition of players in the first few weeks for a Ubisoft title just from you guys all talking about and promoting the game. But unfortunately, with little to no marketing, especially after launch, we weren’t acquiring new players after the initial launch.
We had other issues though as well that we tried to be transparent about. For one we had crippling tech debt using an engine that wasn’t designed for what we were doing, and we didn’t have the engineering resources to ever correct that. I do personally think that in-house engines are not the valuable investment that they used to be and they are often doomed to fall behind big engines like Unreal. This tech debt included the dreaded netcode issues that we could just not solve given the architecture we were dealing with. And so, for many players with solid network connections (in both speed and consistent reliability) the game played well but if your connection had even the smallest amount of inconsistency the engine just couldn’t handle it and you would have a bad experience. Normally, you should be able to weather those bad moments on your network. But this was a major issue with XDefiant.
Another issue we had was having the right resources to make content for the game. What we saw at Season 3 wasn’t even enough content in my mind for launch. There were some really cool features coming later in Season 4 or even 5 that would have completed the game in a way that I felt it should have been for launch. I can say everyone’s (devs, HQ leadership, etc.) heart was in the right place but we just didn’t have the gas to go the distance for a free-to-play game.
So again, I really want to praise and salute all of the devs that worked on XDefiant! The cards were heavily stacked against you, but you managed to produce a really fun and terrific game! And I like to call it out every time I talk about it, but I think our maps were some of the best maps ever made for an arcade shooter. So, congrats to everyone for what they accomplished.
I also think we made a decent impact in the space. We saw a lot of reactions from other games to what we were doing and that to me speaks volumes. I’m really sorry we couldn’t quite deliver and maintain this game for a longer time.
In case everyone doesn’t know, the team behind XDefiant was all let go at the end of last year and I know many people have moved on to other studios, which is great, and I hope that for all of those still looking, that they find something quickly. As for me, I’ve decided to leave the industry and spend more time with my family so unfortunately you won’t be hearing about me making another game. I do care passionately about the shooter space and hope that someone else can pick up the flag that I was trying to carry and make games again that care about the players, treat them with respect and listen to what they have to say.
Thank you again to everyone who had so much passion for XDefiant.

[Bruno Croci @CrociDB]

New blog post: Demystifying the #! (shebang): Kernel Adventures

https://t.co/hYYLxJc7tb

[Bruno Croci @CrociDB]

@PotHix Thanks for the comment, man! It's better now, but I've come to understand that it's a cycle, and it's just fine. We all will have good and bad moments and making peace with it is the best way to navigate through the worst parts.

Hope you're also better!

[Bruno Croci @CrociDB]

New blog post: Retrospective 2024

https://t.co/HZZpIIDAWh

[Bruno Croci @CrociDB]

Day 5:

[Bruno Croci @CrociDB]

Trying to do the #AdventOfCode this year in Haskell. Let's see how it goes. This is 2024/1:

[Bruno Croci @CrociDB]

Day 4: when part2 is simpler than part1!