Newest at the top
2025-05-16 22:06:17 +0200 | <wbrawner> | having minimal dependencies means I'm less subject to changes that I don't care about but can still stay on top of security updates and not have to hunt down an Ubuntu 10.04 iso to build it :P |
2025-05-16 22:05:15 +0200 | <EvanR> | that's why I avoid "make numbers go up" update policy |
2025-05-16 22:04:39 +0200 | <wbrawner> | EvanR that's not a bad idea. another thing I just thought of was early in my programming career I got burned by Angular (a JS web framework) doing massive changes over the course of several years and I got tired of having to refactor my otherwise perfectly fine code to adapt to Google's whims |
2025-05-16 22:01:42 +0200 | <EvanR> | I would go a step further and write a script which creates this dummy project, because inevitably you will lose the seed somehow. (And making sure you don't lose the bootstrapping script is an exercise for the reader) |
2025-05-16 21:59:48 +0200 | <EvanR> | it really helps even if you have always on internet |
2025-05-16 21:59:29 +0200 | <EvanR> | wbrawner, making a dummy project which includes all the "usual suspects" downloaded and ready, that is then cloned to another directory to really start, is a really handy trick in any language |
2025-05-16 21:58:18 +0200 | tromp | (~textual@2001:1c00:3487:1b00:a44a:50e6:3df5:3b66) |
2025-05-16 21:58:13 +0200 | <__monty__> | I like that destination : ) |
2025-05-16 21:58:12 +0200 | <monochrom> | And down that road^2 is Smalltalk. >:) |
2025-05-16 21:58:00 +0200 | <monochrom> | Down that road is "one package per function". |
2025-05-16 21:57:52 +0200 | <EvanR> | includung Parsec is really nice even if I might prefer any of the 10 other alternatives |
2025-05-16 21:56:32 +0200 | <__monty__> | leftToMaybe the package when? |
2025-05-16 21:55:56 +0200 | <Rembane> | I think both need to exist |
2025-05-16 21:55:43 +0200 | <monochrom> | But perhaps an acme-kmettverse would work better. |
2025-05-16 21:55:16 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 252 seconds) |
2025-05-16 21:54:47 +0200 | <monochrom> | But the motivation was funny. "The joke started when a colleague liked the leftToMaybe :: Either a b -> Maybe a function from either, which has a *huge* footprint compared to the utility it provides." |
2025-05-16 21:53:51 +0200 | <Rembane> | :( |
2025-05-16 21:53:10 +0200 | <monochrom> | "There is no free download" |
2025-05-16 21:52:54 +0200 | <monochrom> | OK, "Could not resolve dependencies" and it quits, no download. :( |
2025-05-16 21:51:48 +0200 | <__monty__> | `acme-everything`? |
2025-05-16 21:51:47 +0200 | <monochrom> | acme-everything |
2025-05-16 21:51:17 +0200 | <monochrom> | OK, what is its exact name so I can test it? |
2025-05-16 21:51:09 +0200 | <__monty__> | *Everything*? |
2025-05-16 21:51:02 +0200 | <monochrom> | Ooops, the other of you may be right. |
2025-05-16 21:50:52 +0200 | <Rembane> | Sweet! :D |
2025-05-16 21:50:36 +0200 | <monochrom> | Oops, you're right, `cabal fetch acme-???` just downloads everything, no conflict. |
2025-05-16 21:48:57 +0200 | <Rembane> | Then my case falls. |
2025-05-16 21:47:24 +0200 | <__monty__> | I think Cabal doesn't download any sources unless it can figure out a plan? |
2025-05-16 21:46:20 +0200 | <Rembane> | I was trying to make the case that the acme-??? package was useful, but when I started to write this it struck me that the dependencies might have their own dependencies that aren't ... hey ... will cabal download all transitive dependencies so you have them available? Because then the acme-??? package is actually useful as long as you don't compile it. |
2025-05-16 21:45:09 +0200 | <geekosaur> | I thought that was the one encased in concrete and dropped into the Marianas Trench |
2025-05-16 21:44:42 +0200 | <Rembane> | Yes! The best computer! |
2025-05-16 21:44:04 +0200 | <monochrom> | Well yeah, I mean if you don't turn on your computer, it works, and it is secure too. |
2025-05-16 21:43:35 +0200 | <Rembane> | As long as you don't compile it + dependencies it should work, right? |
2025-05-16 21:43:22 +0200 | <monochrom> | The joke was just to depend on everything, not to expose conflicts. |
2025-05-16 21:43:04 +0200 | <monochrom> | Haha OK I haven't tested it. |
2025-05-16 21:43:00 +0200 | <__monty__> | Or is that the joke? |
2025-05-16 21:42:49 +0200 | <__monty__> | Surely it doesn't? There have to be incompatible version constraints across all of Hackage. |
2025-05-16 21:42:46 +0200 | ttybitnik | (~ttybitnik@user/wolper) ttybitnik |
2025-05-16 21:41:33 +0200 | <monochrom> | I think there is a acme-??? package that acts as a joke meta package that depends on all of hackage. If you're going to Mars, be sure to preload it before you board the rocket. >:) |
2025-05-16 21:40:24 +0200 | <__monty__> | But I prefer megaparsec! |
2025-05-16 21:39:35 +0200 | <monochrom> | Oh, parsec too. Used to be not included. You can now cold-start a parser project on the moon. |
2025-05-16 21:39:29 +0200 | tromp | (~textual@2001:1c00:3487:1b00:a44a:50e6:3df5:3b66) (Quit: My iMac has gone to sleep. ZZZzzz…) |
2025-05-16 21:39:25 +0200 | <__monty__> | I know leftpad is often joked about but if I had to audit my dependencies I'd prefer auditing leftpad over auditing text. |
2025-05-16 21:38:48 +0200 | <monochrom> | (And then they used to be included prehistory. OK text didn't exist prehistory.) |
2025-05-16 21:38:22 +0200 | <monochrom> | For example text, containers, mtl now comes with GHC. They used to be not included. |
2025-05-16 21:37:48 +0200 | mistivia_ | (~mistivia@user/mistivia) mistivia |
2025-05-16 21:37:43 +0200 | <monochrom> | OK, I misspoke. We landed near the minimal side but not extremely. |
2025-05-16 21:37:42 +0200 | mistivia | (~mistivia@user/mistivia) (Read error: Connection reset by peer) |
2025-05-16 21:37:28 +0200 | <wbrawner> | I think that's sensible |
2025-05-16 21:37:09 +0200 | <monochrom> | We landed in the middle. |