Elektrine
EN
Log in Register
Paige Chat Timeline Communities Gallery Videos Email DNS VPN Uptime Kairo
Back to Timeline
Remote

futurile

@futurile@mastodon.social
mastodon 4.7.0-beta.1
  • Open on mastodon.social
0 Followers
0 Following
20 Posts
Joined January 24, 2024

Posts

Open post
futurile @futurile@mastodon.social · Jul 25, 2026
futurile
@futurile@mastodon.social
mastodon.social
RE: https://infosec.exchange/@david_chisnall/116931490270096063 Some truth in this, and then the extrapolations go a bit far for me. I agree that much of original Free Software equates 'users' with (advanced) software engineers. One of the underlying realities that's hard for technologists is that a lot of people don't want to fiddle with their software. We all have things we care about, and things we don't. Heck, I don't even want to put my own winter tires on or have to upgrade my TV remote. Even if I have the capacity I may not have the desire.
Quoting
David Chisnall (*Now with 50% more sarcasm!*) @david_chisnall@infosec.exchange
The Free Software movement never escaped from its origins: the early ‘80s MIT AI Lab. Two things were true in this environment: Back when most computers had tens of KiBs of RAM and 1 MiB was a huge amount, programs were simple. Very few programs were so complex that one person could not completely understand them.The AI Lab was full of some of the most talented programmers in the world. This meant that the only obstacles for these people being able to fix bugs and add features to any program were access to the source code and the legal rights to modify it. Once you have those, any program was understandable by that group and they could modify it however they wished. For the next 40 years, the FSF focused on these two things. The world around them changed. These two prerequisites were never enough for most people (what do 90% of computer users do if you give them even a modest 10,000 line C codebase and tell them they can change it however they like?) and now they aren’t enough even for competent programmers. When Linus says ‘fork it’ to folks who don’t want LLM-extruded code in their kernel, he knows full well that it is almost impossible to fork a 40 MLoC C (and Rust now) codebase that averages more than one CVE per day and have something useful. The Free Software movement is struggling now because it obsessed over licenses, which was never a path that would succeed, and ignored the hard problems: How do you design environments that enable end users to modify their software?How do you engineer software so that it is cheap and easy for a random user to maintain a fork that meets their specific needs?How do you foster communities where people want to share improvements, so forks don’t proliferate even when it’s easy?How do you create an environment where everyone sees the benefits of user-modifiable code to such a degree that trying to sell anything that doesn’t come with these rights is commercially impossible? Instead of tackling any of these problems, they created more complex and restrictive GPL variants. And well-paid lawyers found loopholes in them that allowed corporations to keep doing what they wanted (and even pick licenses like AGPLv3 to control ecosystems, because they give the copyright owners so many more rights than everyone else that it’s hard for anyone else to compete). They said ‘don’t worry about the complexity of the licenses, you only need to understand the legal details if you’re creating and distributing derived works’ while completely forgetting that making it possible for anyone to create and distribute modified versions of the programs was the entire point of the Free Software movement.
Open quoted post
0
1
0
0
Open post
futurile @futurile@mastodon.social · Jul 01, 2026
futurile
@futurile@mastodon.social
mastodon.social
Replying to @cwebber@social.coop
@cwebber@social.coop @spritely@social.coop @dthompson@toot.cat Wow, nice job this looks fantastic. Super excited to see it. I get first feature request (LOL!) - can we get #nrepl support in the 'Open in REPL'!
1
0
0
0
Open post
futurile @futurile@mastodon.social · Jun 14, 2026
futurile
@futurile@mastodon.social
mastodon.social
There's a recording of the Guix Foundation 2026 AGM hosted on @Aquilenet@toot.aquilenet.fr platform: https://blabla.aquilenet.fr/playback/presentation/2.3/edd11ddf8684d2759a0d2b93b811701dce31dacf-1781454912133 If you couldn't attend #guix foundation, but have any questions please contact Tanguy/myself or on the mailing list.
7
0
6
0
Open post
futurile @futurile@mastodon.social · May 07, 2026
futurile
@futurile@mastodon.social
mastodon.social
Replying to @shepherd@fosstodon.org
@shepherd@fosstodon.org @Mehrad@fosstodon.org So to be clear it says something like "Calculating xxxx" but at the end it decides it doesn't need to build anything? The most common thing is that there's something in config that means it builds a derivation each time. I think Ieure (others?) on the #guix channel know what sorts of configs cause this. But it sounds like it isn't doing this, it's just the calculation of the graph is slow?
1
1
0
0
Open post
futurile @futurile@mastodon.social · May 06, 2026
futurile
@futurile@mastodon.social
mastodon.social
Replying to @futurile@mastodon.social
@shepherd@fosstodon.org @Mehrad@fosstodon.org There's no built-in way to speed it up that I know off. Some parts just seem slow. Some parts may be naive and don't cache anything: so something like a cc-cache could work I guess. Annoyingly you can't restart a long-running build.
1
6
0
0
Open post
futurile @futurile@mastodon.social · May 06, 2026
futurile
@futurile@mastodon.social
mastodon.social
Replying to @shepherd@fosstodon.org
@shepherd@fosstodon.org @Mehrad@fosstodon.org Yeah it makes sense when you _know_ what it's doing, but it's slightly counter-intuitive. The --max-jobs is for how many builds the guix daemon will do in parallel. If you are building lots of small libraries then it makes sense to use it. If you are building one big thing, then it won't help. The --cores assigns the number of cores PER BUILD. So if you have 4 builds (--max-jobs 4), and you set --cores 2, then it will use 8 in total.
1
7
0
0
Open post
futurile @futurile@mastodon.social · Apr 25, 2026
futurile
@futurile@mastodon.social
mastodon.social

A video on "How to Install GNU Guix System (2027 Edition":

https://youtu.be/3mbCH7sBLeI?si=aoBuuR5qBpXn2_GG

Clearly, from the future! There's some fairly idiosyncratic bits, but I think "Tony" is comparing it to how they do it with #Nix so is trying to keep it comparable.

I'll be interested in the follow-up videos where they use guix-home.

3
0
1
0
Open post
futurile @futurile@mastodon.social · Apr 22, 2026
futurile
@futurile@mastodon.social
mastodon.social

Watched the Clojure documentary. It tells the story of how Rich Hickey created a functional language with the aim to be practical and situated. It tells some interesting stories about the creative process and the relationship with his partner and also the wider ecosystem. Even if you're not into Clojure it's worth watching:

https://youtu.be/Y24vK_QDLFg?si=b2enWMIb2CIVzDmb

4
0
5
0
Open post
futurile @futurile@mastodon.social · Apr 21, 2026
futurile
@futurile@mastodon.social
mastodon.social

Took me 2 days to write the #guix substitute* post which is really fast for me!

Well, technically it took about 2 years.

Technically, I drafted my Guix substitute* post in 2024. But, early 2025 I realised I needed to cover Guile regexp properly because it didn't make any sense without it.

That took me uh a year and a half. Cos regex (tutorials) is hard!

This does mean technically if I finish anything faster than two years I'm better than my worst time. So I'm winning - technically!

8
0
2
0
Open post
futurile @futurile@mastodon.social · Apr 21, 2026
futurile
@futurile@mastodon.social
mastodon.social

New post on altering the source of #guix packages using the substitute* procedure.

It searches through files using a #guile regular expression and replaces it with the specified text.

This is the most common change that packages make - substitute* is used 9500 times!

Common uses are altering test requirements, or slackening library dependencies.

https://www.futurile.net/2026/04/18/guix-package-source-alterations-using-substitute/

Post covers the procedures uses, and then a tour through different examples from the Guix archive!

15
1
10
0
Open post
futurile @futurile@mastodon.social · Apr 19, 2026
futurile
@futurile@mastodon.social
mastodon.social
Replying to @futurile@mastodon.social
It's a long series, hopefully worthwhile. I'd love to know if you found it useful? And/Or if you think it's missing anything? #guix #guile #fourbackslashesisenough #regex
4
0
1
0
Open post
futurile @futurile@mastodon.social · Apr 19, 2026
futurile
@futurile@mastodon.social
mastodon.social
Replying to @futurile@mastodon.social
The last post in my series on #guile regular expressions from a #guix packager perspective. This covers the advanced topics of alternation, grouping/capturing and back-references. Also, it's time to deal with backslash escaping and why regexs often look like a symbol salad of tomfoolery! https://www.futurile.net/2025/05/10/guile-scheme-regular-expressions-for-guix-grouping-escaping/ 3/3
5
1
2
0
Open post
futurile @futurile@mastodon.social · Apr 19, 2026
futurile
@futurile@mastodon.social
mastodon.social
Replying to @futurile@mastodon.social
The second post in my series on #guile #regex for #guix packagers: This covers all the Quantifiers, along Grep inspired interval expressions which are really cool. Also how to handle Guile's greedy matching, as there's no lazy/reluctant matching: https://www.futurile.net/2025/05/10/guile-scheme-regular-expressions-for-guix-quantifiers/ 2/3
5
2
1
0
Open post
futurile @futurile@mastodon.social · Apr 19, 2026
futurile
@futurile@mastodon.social
mastodon.social

Finished my series of posts on #guile regular expressions from the perspective of a #guix packager.

The first post covers Guile #schemes regex implementation and the main metacharacters:

https://www.futurile.net/2025/05/09/guile-scheme-regular-expressions-for-guix/

1/3

12
3
6
0
Open post
futurile @futurile@mastodon.social · Apr 11, 2026
futurile
@futurile@mastodon.social
mastodon.social
Replying to @sharlatan@mastodon.social
@fishinthecalculator @sharlatan@mastodon.social Nice job both! Great to have a well-known secrets management option in #guix
7
0
1
0
Open post
futurile @futurile@mastodon.social · Mar 30, 2026
futurile
@futurile@mastodon.social
mastodon.social
Replying to @shegeley@fosstodon.org
@shegeley@fosstodon.org Nice, they look great!
0
0
0
0
Open post
futurile @futurile@mastodon.social · Mar 15, 2026
futurile
@futurile@mastodon.social
mastodon.social
Replying to @janneke@todon.nl
@janneke @civodul @tsyesika Unfortunately, often true - why! 🤔
1
1
0
0
Open post
futurile @futurile@mastodon.social · Mar 15, 2026
futurile
@futurile@mastodon.social
mastodon.social
Replying to @civodul@toot.aquilenet.fr
@civodul @tsyesika VSCode is hugely popular, Stack Overflow had it at 70% developers use it (2024 survey). It's hard to even internalise that level of popularity! It's not really an editor, in much the same way that Emacs isn't. And some of the tech like LSP is now hugely influential.
2
2
0
0
Open post
futurile @futurile@mastodon.social · Mar 01, 2026
futurile
@futurile@mastodon.social
mastodon.social
Replying to @sharlatan@mastodon.social
@sharlatan@mastodon.social @nmeum@chaos.social And _this_ is how poor @nmeum@chaos.social became the community "voted" expert on reproducibility 🤣 I already tagged them on a different Rust reproducibility bug muhahahaha! ... don't try and steal rust-team's new shiny expert @sharlatan@mastodon.social 😉
2
0
0
0
Open post
futurile @futurile@mastodon.social · Feb 13, 2026
futurile
@futurile@mastodon.social
mastodon.social
Replying to @baleine__dup_29840@piaille.fr
@baleine@piaille.fr "Right before Guix days was FOSDEM. FOSDEM is a Guix days fringe event for me, but I still go! " Hah, that made me laugh!
1
0
0
0

Remote instance

mastodon.social
Open on original server
313k7r1n3
Elektrine

Tor hidden service

elekhj7afj4qnrr4yd3bkzslsyo5jgfxw3orgjkhlcxifueodybyiiad.onion

Platform

  • Email
  • Chat
  • Timeline
  • Communities
  • VPN
  • DNS

Company

  • About
  • Contact
  • FAQ

Legal

  • Terms of Service
  • Privacy Policy
  • Warrant Canary
  • Lite (no JS)
  • VPN Policy
  • Source code

Support

  • support@elektrine.com
  • Report Security Issue
Mail client setup IMAP mail.elektrine.com:993 POP3 mail.elektrine.com:995 SMTP mail.elektrine.com:465
© 2026 Elektrine. All rights reserved. Server: 03:20:00 UTC