|
1 | | -<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>40Ants</title><link>https://40ants.com/</link><description>Just an example of the static file generated by StatiCL.</description><guid isPermaLink="false">https://40ants.com/</guid><lastBuildDate>Mon, 24 Nov 2025 10:26:45 +0000</lastBuildDate><item><title>Pushing your pulls faster!</title><link>https://40ants.com/posts/push-your-pulls/</link><description><p>Today I’m going to share an idea I’ve been nurturing for a long time, my friends. It came into my mind many years ago. It’s core message has to do with development of a service, which would aggregate and conveniently display all communications related to your favorite GitHub projects. This service will be very helpful for users having many own GitHub projects. It’ll also help GitHub users with numerous pulls and tickets for third party projects.</p> |
| 1 | +<?xml version="1.0" encoding="UTF-8"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>40Ants</title><link>https://40ants.com/</link><description>Just an example of the static file generated by StatiCL.</description><guid isPermaLink="false">https://40ants.com/</guid><lastBuildDate>Wed, 10 Dec 2025 07:20:00 +0000</lastBuildDate><item><title>Pushing your pulls faster!</title><link>https://40ants.com/posts/push-your-pulls/</link><description><p>Today I’m going to share an idea I’ve been nurturing for a long time, my friends. It came into my mind many years ago. It’s core message has to do with development of a service, which would aggregate and conveniently display all communications related to your favorite GitHub projects. This service will be very helpful for users having many own GitHub projects. It’ll also help GitHub users with numerous pulls and tickets for third party projects.</p> |
2 | 2 |
|
3 | 3 | <p>I believe that tickets and pulls creators create them to improve their open source projects of interest. In order to do that, tickets must become pulls. The pulls in turn should merge in a timely manner. The faster this process will be, the quicker open source projects will be developed.</p> |
4 | | -</description><guid isPermaLink="false">https://40ants.com/posts/push-your-pulls/</guid><lastBuildDate>Mon, 24 Nov 2025 10:26:45 +0000</lastBuildDate><content:encoded><p>Today I’m going to share an idea I’ve been nurturing for a long time, my friends. It came into my mind many years ago. It’s core message has to do with development of a service, which would aggregate and conveniently display all communications related to your favorite GitHub projects. This service will be very helpful for users having many own GitHub projects. It’ll also help GitHub users with numerous pulls and tickets for third party projects.</p> |
| 4 | +</description><guid isPermaLink="false">https://40ants.com/posts/push-your-pulls/</guid><lastBuildDate>Wed, 10 Dec 2025 07:20:00 +0000</lastBuildDate><content:encoded><p>Today I’m going to share an idea I’ve been nurturing for a long time, my friends. It came into my mind many years ago. It’s core message has to do with development of a service, which would aggregate and conveniently display all communications related to your favorite GitHub projects. This service will be very helpful for users having many own GitHub projects. It’ll also help GitHub users with numerous pulls and tickets for third party projects.</p> |
5 | 5 |
|
6 | 6 | <p>I believe that tickets and pulls creators create them to improve their open source projects of interest. In order to do that, tickets must become pulls. The pulls in turn should merge in a timely manner. The faster this process will be, the quicker open source projects will be developed.</p> |
7 | 7 |
|
@@ -34,7 +34,7 @@ to other common lispers.</p> |
34 | 34 |
|
35 | 35 | <p>Just pretend that you've made a brand new library and want to show it to |
36 | 36 | the world. Now you have two options.</p> |
37 | | -</description><guid isPermaLink="false">https://40ants.com/posts/ultralisp/</guid><lastBuildDate>Mon, 24 Nov 2025 10:26:45 +0000</lastBuildDate><content:encoded><p>I believe, that software should evolve and evolve quickly. |
| 37 | +</description><guid isPermaLink="false">https://40ants.com/posts/ultralisp/</guid><lastBuildDate>Wed, 10 Dec 2025 07:20:00 +0000</lastBuildDate><content:encoded><p>I believe, that software should evolve and evolve quickly. |
38 | 38 | One of the reasons why Common Lisp seems strange to newcomers is its |
39 | 39 | ecosystem. It takes a long time to add a new library and make it useful |
40 | 40 | to other common lispers.</p> |
|
0 commit comments