You can keep bringing it up. But, in my exp, if you dont have anyone high up that can support your perspective, it's just gonna be an uphill battle. And is likely just going to make the other devs unhappy with you.

It's unfortunate but most devs dont really like anything that's going to cause them more work (e.g. more code reviews, higher quality changes, looking at the bigger impact of their changes etc).

If you don't have someone higher up —maybe the manager of the managers of those problematic engineers—I'd just make more tests around the areas that are breaking and require those tests to pass before merging code changes. Devs may not like to work harder, but they damn sure dont like seeing a bunch of red X's when they open a PR lol 😃

The instances may have different versions of the Lemmy software, which may be causing the inconsistencies.

I use the feeds Open RSS provides for Lemmy and looks like it includes images. If it doesnt, just hit them up and ask if they can implement. They're pretty chill and resolve RSS feed issue pretty quickly.

http://openrss.org/lemmy.ml/

I make my websites with Wix and a PHP backend like a boss 😎

deleted by creator

deleted by creator

This is helpful. Thanks. Didnt even realize it. No need to use something to point out how its not a good look. It's still good to bring more awareness around how sites like Github are becoming a more of walled gardens. I agree with everything else you said though.

You can try an RSS feed. Here's a link to the RSS feed to this post:

https://openrss.org/lemm.ee/post/14418714

Have you tried returning 404 response status codes for the requested URLs? I think federated requests will need for your server to tell them the URLs don't exist anymore.

Dude, who in their right mind would add scheduling infra to a client like that? 😆 I'm going to need these Lemmy devs to have a tad bit more experience before they start being so dismissive, especially to someone who's just trying to help.

This isnt the first time Nutomic has reacted in such a egotistical way, especially when someone points out a flaw in the software. I've seen a few issues that were actual issues with the software--not feature requests--that he's closed and dismissed. One of the issues were mine. He definitely needs help with maintaining the software but I dont know how he expects anyone to help with the way he's been acting.

Thought it was the best way to meet hot guys

Express, JavaScript (with JSDocs+TS for type-checking) and Postgres

This is 👍. For those wondering, RFCs have been around for years in software engineering--since the beginning of the internet, practically.

As a software engineer myself, I can confidently say they're a great way to build complex software in a more democratic way.

They require a certain level of agreement and consensus, which makes them take a while to ratify. But you almost always end up with better software in the end.

Looks like a decent setup. Vanilla JS is the way to go for the best performance. Avoids vendor lock-in and those skills never go out of date. 👍

Take that, Stack Overflow! Programming.dev on deck!!!! Let's gooooooo

The issue with node is the single threading and having to scale with worker threads AFAIK

People always say this but its not technically correct and can be misleading.

Technically, JavaScript runs single threaded but not Node.js itself and certainly not when using it on the backend in something like Express. IO operations and other things tooling libraries do can cause you to run out of a thread pool. But Node.js, when handling requests, gives you much of the benefit of multithreading without having to deal with multithreaded code.

Yeah, JavaScript/TS doesn't get a great rep being used on the backend. But I use it on quite a few of my projects, one of which gets thousands of requests per minute. I was skeptical of whether or not using Node on the backend would hold up, but the performance has been stellar.. pretty surprising, actually.

Inoreader. Syncs across multiple devices too.

This is a duplicate post of https://lemm.ee/post/4849736. Was that intentional?

This was always a no-brainer imo. Love what node has been doing so far 👏