Egads! My eyes.
I’d rather it was just written in assembly. It’s the do { opening a block under the case 0, but then proceeding to have further case statements inside that block. You now have case statements in two different scopes that are part of the same switch.
In most CPU instruction sets, the only conditional instruction is branch (aka goto).
…or the research is flawed. Gender identity was gained from social media accounts. So maybe it’s a general bias against social media users (half joking).
Not high. It tends to result in one of a few things.
They take the fix as offered. Probably it’s a smaller quiet project where the number of PRs is small. That, or very well run.
It remains forever open and gets lost in the masses of other out of date PRs. Maybe a bot comes along and closes it as stale. Biggest group, and these ones just tell me that I’ve got very little chance of getting the maintainer’s attention. I can see that 100s of others have experienced the same fate.
Somebody else finds it useful and adopts it, fighting for it to go in. Sometimes that someone is the maintainer. As you say, it can be inspiration for a rewrite of my contribution. That’s fine by me. Whatever works.
The maintainer makes a bunch of rework demands leading to rejection, or it gets rejected straight off. “My way or the highway” is always going to be highway. I offered a small piece of help, and if it’s not wanted I’ll happily go away.
Maybe 20% get in, but it depends on so many things.
Honestly, I run and gun. I make the change I want, and submit a merge request. I then move on. It’s then up to the maintainer to accept or reject it.
I’m not going to debate it. I’m not going to rework it over the course of months to make it perfect in the maintainer’s eyes. I don’t care enough about it. I’ve solved my problem. I’m just sharing it for others.
The things I submit are normally big fixes with the smallest possible code change, not refactorings to solve an underlying problem.
Second diagram, yes absolutely.
Short lived (1-2 day) branches, and a strong CI systems to catch regressions.
Be warned, the strength in the CI lies in its capacity to detect when some functionality that previously worked doesn’t work anymore. So, the flow must be green always, and it must evolve as the features evolve. Without good CI you’re destined for failure.
I don’t think anything works in that situation.
Comparing base model to base model I think Cascade is quite a lot better than SDXL, but …and it’s an enormous but… It seems to have been shunned by the community.
Maybe nobody with resources to do training is interested in a model with commercial restrictions, or the multi-model flow was just too different for people. Not sure, but the output of the base model can be really nice. Not always, but I find the biggest errors are people taking on a painterly/waxy appearance rather than the arm turning into a leg body horror you can get with SDXL. I think the “compressed” Stage C works to keep the composition together across the whole image more.
In the centre, Hyde park and St. James park I expect.
In the south west, Richmond Park + Bushy Park + Old Deer Park + Kew gardens all in close proximity to each other.
Does this mean, that because you’re now liberated from the dimensions of the training data, that all training data will apply to all sizes? e.g. generated portrait images will be influenced by landscape training data.
Similar situation, and I follow the Forgejo development. I’ve found the codeberg individuals that I’ve interacted with to be very good at what they do. They give me confidence in the wider platform.
Most companies structure layoffs so that they retain as many high skilled workers as possible. That means that in times like these the market is awash in underperforming candidates. Finding good hires can be even harder than normal.
Doesn’t having it private mean it wasn’t a community of 150k? It was a community of 1.
I understood taking subs NSFW to keep advertising out, but taking them private was causing the community to die. Once that went beyond a few days it was time to shift platform.
I don’t think he was drawing a comparison.
Mobile development sucks in general.
This is my number one. I hate having everything in one subscription list, battling each other for my attention. My local communities can’t stand up to lemmyworld or beehaw communities in my sub list, and “local” puts all local communities in, most of which don’t interest me.
That’s just one example though, and it’s not all about instances. News about energy policy can’t battle with world politics, so keeping the two in separate lists is important to me even though they are both remote sets of communities for me.
I wouldn’t be so quick to write it off.
It’s a proof of concept showing the weaknesses in Microsoft’s vetting process for extensions published on the store. They then used the process to get pseudo-malicious code inside hundreds of organisations (not hundred of installs) some of which are high profile.