Just saw this, I know its a bit pedantic, but damn is it really so hard to make sure your numbering is right for your distro? This is the main one 25.04, the one that the ‘download’ button downloads.
You must log in or register to comment.
Ubuntu moment
They should just remove the numbering. It’s less maintenance, and it’s not that important anyway, is it?
Shouldn’t the numbering be rendered programmatically? What are they manually adding this text to each slide??
You’d think, but there’s always so much jank.
I’m guessing what happened is that they didn’t have numbering, and then later the people making the slides decided to add the numbers. There might be a ticket for programmatic numbers, but it’d be buried under a thousand other ones that are more important.
09 / 12, 11 / 13, 11 / 12
The 11 is probably also wrong. Make a slide show with 13 slides. Remove one slide before 11. Update your static images, but miss the slide formerly known as 11/13, which should ben10/12.
What’s your point?
They aren’t rendered programnatically.
Or there is some terrible bug. But either way the questions I was asking were obviously rhetorical. The answer to both questions is “yes.” The intent is more to suggest shock and disbelief rather than to elicit an answer.
I agree, but at the same time I love the Kubuntu installation slides, they feel so early 2000s PowerPoint.
The single hardest problem in computer science is naming things.
And counting things.
I’ve always heard this as
“the two hardest problems in computer science are naming variables, cache invalidation, and off-by-one errors”
Yours is a nice subtle variant, I like it.
Chalk it up to cache invalidation issues 🙃
Different slides using 0 indexed, the other 1. Just choose!
Likely caused by a revision change in the slide show, one was taken out before slide 11, most of the slides were updated, but this one got missed.
Lodge a bug report.
I’m unsure this is the proper place for this, since its such a minor, non debilitating problem, I think the Kubuntu forums is the better choice? What do you think?
As another dev I agree with the other reply. Even if it seems really small, it still is something that should eventually get fixed and therefore can be considered a bug. It makes it easier to track everything that needs to be done if it is all in thr bug tracker. Worst case scenario if it is considered irrelevant it will just be given an extremely low priority in the bug tracker.
A bug is a bug. Someone needs to deal with it. The forum is for discussion, a bug report is to advise developers that there is a problem.
As a developer, I’m not looking at forums for bug reports, I’m looking at bug trackers.
Well, okay then, ill send it when I can.
Looks like the windows school of counting
To be fair, estimating file copy/move progress correctly is hard.
The most correct way would probably be to group small, medium and large files , so you don’t get random small access, then cross-reference that with prior saved disk benchmarks. But you know, a bit over the top.
Although the grouping (and tar-ing the small files) would speed up the copy/move.
From the new AI powered excel?
