The media in this post is not displayed to visitors. To view it, please log in.
Posted on March 7, 2024
Tags: madeof:atoms, FreeSoftWear

I was working on what looked like a good pattern for a pair of jeans-shaped trousers, and I knew I wasnβt happy with 200-ish g/mΒ² cotton-linen for general use outside of deep summer, but I didnβt have a source for proper denim either (I had been low-key looking for it for a long time).
Then one day I looked at an article I had saved about fabric shops that sell technical fabric and while window-shopping on one I found that they had a decent selection of denim in a decent weight.
I decided it was a sign, and decided to buy the two heaviest denim they had: a 100% cotton, 355 g/mΒ² oneand a 97% cotton, 3% elastane at 385 g/mΒ²1; the latter was a bit of compromise as I shouldnβt really be buying fabric adulterated with the Scourge of Humanity, but it was heavier than the plain one, and I may be having a thing for tightly fitting jeans, so this may be one of the very few woven fabric where Iβm not morally opposed to its existence.
And, Iβd like to add, I resisted buying any of the very nice wools they also seem to carry, other than just a couple of samples.
Since the shop only sold in 1 meter increments, and I needed about 1.5 meters for each pair of jeans, I decided to buy 3 meters per type, and have enough to make a total of four pair of jeans. A bit more than I strictly needed, maybe, but I was completely out of wearable day-to-day trousers.

The shop sent everything very quickly, the courier took their time (oh, well) but eventually delivered my fabric on a sunny enough day that I could wash it and start as soon as possible on the first pair.
The pattern I did in linen was a bit too fitting, but I was afraid I had widened it a bit too much, so I did the first pair in the 100% cotton denim. Sewing them took me about a week of early mornings and late afternoons, excluding the weekend, and my worries proved false: they were mostly just fine.
The only bit that could have been a bit better is the waistband, which is a tiny bit too wide on the back: itβs designed to be so for comfort, but the next time I should pull the elastic a bit more, so that it stays closer to the body.

I wore those jeans daily for the rest of the week, and confirmed that they were indeed comfortable and the pattern was ok, so on the next Monday I started to cut the elastic denim.
I decided to cut and sew two pairs, assembly-line style, using the shaped waistband for one of them and the straight one for the other one.
I started working on them on a Monday, and on that week I had a couple of days when I just couldnβt, plus I completely skipped sewing on the weekend, but on Tuesday the next week one pair was ready and could be worn, and the other one only needed small finishes.

And I have to say, Iβm really, really happy with the ones with a shaped waistband in elastic denim, as they fit even better than the ones with a straight waistband gathered with elastic. Cutting it requires more fabric, but I think itβs definitely worth it.
But it will be a problem for a later time: right now three pairs of jeans are a good number to keep in rotation, and I hope I wonβt have to sew jeans for myself for quite some time.

I think that the leftovers of plain denim will be used for a skirt or something else, and as for the leftovers of elastic denim, well, there arenβt a lot left, but what else I did with them is the topic for another post.
Thanks to the fact that they are all slightly different, Iβve started to keep track of the times when I wash each pair, and hopefully I will be able to see whether the elastic denim is significantly less durable than the regular, or the added weight compensates for it somewhat. Iβm not sure Iβll manage to remember about saving the data until they get worn, but if I do it will be interesting to know.
Oh, and I say Iβve finished working on jeans and everything, but I still havenβt sewn the belt loops to the third pair. And Iβm currently wearing them. Itβs a sewist tradition, or something. :D
- The links are to the shop for Italy; you can copy the βCodice prodottoβ and look for it on one of the shop version for other countries (where they apply the right vat etc., but sadly they donβt allow to mix and match those settings and the language).β©οΈ
blog.trueelena.org/blog/2024/0β¦
Jakub Jirutka π¨πΏπΊπ¦
in reply to Jakub Jirutka π¨πΏπΊπ¦ • • •be at the mercy of the devs to provide the update. Not a group of active maintainers behind the distro, but many individual devs, some of whom lack the time or motivation and sustainability. The same goes for Docker containers, Flatpak and similar!
This is called static linking or bundling. Instead of rebuilding and updating a single shared library, you have to rebuild and update every single thing that links/bundles it. In the case of static linking, you usually canβt even tell which (2/3)
reshared this
Elena ``of Valhalla'' e coucouf β reshared this.
Jakub Jirutka π¨πΏπΊπ¦
in reply to Jakub Jirutka π¨πΏπΊπ¦ • • •libraries itβs linked with!
Now do you see the value of #Linux distros and dynamic linking? Please, stop this insane βsingle binaryβ mantra and work with distros, not against them.
If #rustlang wants to replace C, devs need to acknowledge this and start providing dynamically linkable libraries with stable ABI. (3/3)
reshared this
Elena ``of Valhalla'' e coucouf β reshared this.
Jakub Jirutka π¨πΏπΊπ¦
in reply to Jakub Jirutka π¨πΏπΊπ¦ • • •cvedetails.com/vulnerability-lβ¦
Golang GO : Security vulnerabilities, CVEs
www.cvedetails.comAvebury Rosetta ππ΄π©
in reply to Jakub Jirutka π¨πΏπΊπ¦ • • •federico
in reply to Avebury Rosetta ππ΄π© • • •you mean a huge blob? That's a docker image.
federico
in reply to Jakub Jirutka π¨πΏπΊπ¦ • • •Elena ``of Valhalla''
Unknown parent • •@Aleksandra Fedorova :fedora: @ITwrx @Neal Gompa (γγΌγ«γ»γ΄γ³γ) :fedora: @kravietz π¦ @Jakub Jirutka πͺπΊπΊπ¦ and even for single person projects, having a packager in each main distribution that isn't the upstream developer is a big plus, as it provides a minimum of oversight and redundancy.
Not much, especially when said maintainer(s) are overworked and demoralized, but still better than nothing.
Aleksandra Fedorova
in reply to Elena ``of Valhalla'' • • •@valhalla
Yes, that is an important point too.
When we say co-maintainer, we often implicitly assume that it should be an equally or comparably skilled person doing the same tasks.
And then we stop at a thought on how hard it is to find a duplicate.
While it doesn't have to be.
There is plenty of room for a developer to collaborate with a tester, or a packager or a build engineer, or a documentation writer.
It often can be healthier too.
@ITwrx @Conan_Kudo @kravietz @jakub
Elena ``of Valhalla'' likes this.