recursed

joined 1 year ago
[–] recursed@lemmy.recursed.net 17 points 1 year ago (2 children)

I'd be interested in seeing the code and checking it out. Open Source it only if you're comfortable and there's no sensitive data in the repo though.

It wouldn't hurt and there's no down-voting a repo so I see no downsides besides fellow developer engagement and learning from one another.

[–] recursed@lemmy.recursed.net 1 points 1 year ago

Personally using Lemmy as I find the interface, syntax (linking users and communities), and deployment easy to use.

Also I personally want to contribute to Lemmy and learning Rust is a high priority in my personal and work life.

[–] recursed@lemmy.recursed.net 19 points 1 year ago (1 children)

This made me chuckle for a good 10 minutes!

At work we’re currently in the last layer of the iceberg with 35+ microservices, with ten different Kubernetes instances for different uses and a supported OnPrem version.

It is bit of a learning curve and we definitely have two “mono-services” that we’re actively braking down due to it accumulating seven years worth of different ideas and implementations.

I think currently I’m still heavily in favor in microservices in a project of our scale as it easily let’s us enhance, trash, or reimplement different areas of the app; but man is it a pain in the ass to manage sometimes 😂

[–] recursed@lemmy.recursed.net 1 points 1 year ago

I joined early last week and the joinfediverse wiki helped me better understand how it's federation worked. Maybe that would be a good place to start 👍

[–] recursed@lemmy.recursed.net 0 points 1 year ago (1 children)

Very awesome! I'm excited to hear more fellow developers are creating more tools to browse Lemmy! Persistent cache seems really interesting! Excited for the future!

[–] recursed@lemmy.recursed.net 2 points 1 year ago

Neovim with coc-rust-analyzer.

There’s also coc-rls.

[–] recursed@lemmy.recursed.net 3 points 1 year ago

Given this project has been around for many years, (looking at their releases), I wouldn’t say it’s “early” to modularize their code. It’s very common practice to abstract out / move commonly executed code into their own packages and modules to allow ease of reuse across the app. This way if an entire subpackage needs to be moved or deleted, all related code could be affected at once and code which references it, simply needs to be edited. Typically these places to edit are much easier to handle since most of “calling code” wouldn’t touch the modularized / abstracted code, only their callables.

[–] recursed@lemmy.recursed.net 2 points 1 year ago

As someone who’s been on reddit for almost 12 years, who’s also a developer. It really has saddened me to hear so many I’ll things he’s said to other dev teams.

This is the main reason why I’m trying to go all in with Lemmy, subscribing to different communities, etc.

At this point, if Reddit doesn’t make him step down and all these popular third party apps go under because of the API pricing, i will rarely be visiting reddit in the future.