Thanks for the response. It sucks to not have language being set in some implementations of ActivityPub. I think separating the write language settings from the read language settings would help a bit to set the corrent language when writing, at least. But I suspect that needs to be fixed in the core Lemmy (not instance specific).
Yeah, that's what I meant by non-elegant. I think the way Lemmy assigns IDs to posts and comments should be re-thought. Dictionary lookup is a solution, but not a good one.
This is great. I think "instance post/comment links" would be a great addition to Lemmy core in general, but don't know how easy it would be to implement. What I have in mind is: when someone provides a link to a post/comment in another instance, it would be converted to a link the person is logged in from. I think it would be OK to leave the link as is but add an icon next to it that goes to the correct URL for that instance.
I would add Ars Technica to that list and call it a day.
For programming I follow YouTube channels of the conferences relevant for my tech stack (YouTube natively supports RSS). They are generally 1 hour talks but it's a great way to stay up to date.
Thanks for sharing. This looks really low level. The advantage of PlantUml and Mermaid is that they are supported by many systems. So, integration is a non-issue.
I agree that this is a challenge. One needs to slice the domain such that it can be covered this way. But this also means more people. In my experience, moving from "activity oriented" teams to "business centric" teams require an increase of the headcount.
Yeah, I don't know if it's a bug or a feature. I got a similar problem before with one of my posts. I think a workaround would be to post it as a link and paste the image in the Body.
-1 is what you get back from fork() when it fails. Normally, it returns a pid_t which is positive if you're the parent, or zero if you're the child.
-1, when handed to kill() on Linux, means "target every process but myself and init". Therefore, when you take the return value from fork(), fail to check for an error, and later hand that value to kill(), you might just kill everything else on the machine.
As long as that growth curve continues there will not be enough teachers, role models, and leaders. It means that most software teams will remain relatively unguided, unsupervised, and inexperienced. [...] It means that the industry as a whole will remain dominated by novices, and exist in a state of perpetual immaturity.
Not sure if the data can be confirmed or not, but if that's the case it will be difficult to maintain the best practices in our industry.
And because Windows and it’s eco system of applications he listed gets worse, he extrapolates this to all software.
They admit that bias in the article:
[...] since I've always been working in the Microsoft tech stack, I use a lot of it. Thus, selection bias clearly is at work here.
Now, I mentioned free software as the exception. I don't have any data as to how big free software vs proprietary software. But I think his points extends at least to other proprietary software and is not limited to Windows.
canpolat @ canpolat @programming.dev Posts 60Comments 74Joined 2 yr. ago 
Please consider posting language specific questions to language specific communities in the future. For example, !c_lang@programming.dev