897 karma · joined September 14, 2011
Funny, I learned the exact opposite lesson. Almost all software suck, and a good way for it not to suck is to know where the developer is and go tell them their shit is broken, in person.
If you want a large scale example, one of the two main law enforcement agency in france spun off libreoffice into their own legal writing software. Developped by LEOs that can take up to two weeks a year to work on that. Awesome software. Would cost litterally millions if bought on the market.
Take a look at this
https://guix-hosting.com/docs/tuto/getting-started.html
To see how one can use macros to redefine the syntax to get an imperative-like syntax for defining services.
Disclaimer: i run guix-hosting.com
- van buren https://en.wikipedia.org/wiki/Fort_Cass
- Wilson https://en.wikipedia.org/wiki/Internment_of_German_Americans
- Bush https://en.wikipedia.org/wiki/Guantanamo_Bay_detention_camp
And i must forget a lot of others, but I think you get the gist. "Great again" indeed.
Add to that that our most tough-on-crime, tough-on-immigration president is in prison because, on contrast with the vast majority of immigrants, he is an actual criminal, and you will see how the GP's hypocrisy can be very grating.
This is true for every national muséum in France and it is awesome !
People who like to dress up can also join the order of Malta, which can actually boast continuous existence since 1099.
https://gitlab.com/edouardklein/acheron
Still a wip though. You may find it interesting
On the other hand, I can't stop myself from thinking about "Greenspun's tenth rule":
> Any sufficiently complicated C or Fortran program contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Common Lisp.
This doesn't apply directly here, as the features are intentional and it seems they are not bug ridden at all. But I get a nagging feeling of wanting to shout 'just use lisp!' when reading this.
The same as in the simplex algorithm to solve linear programming problems.
The priorization mentioned in the readme is especially interesting.
Historically, Plan 9 had IL as well.
Which transport protocol has a number in its name ?
If I implement one someday I'll add a separator.
On current hardware it can serve up to a few hundreds requests/s without too much trouble.
There's also the trick of pre starting a pool of processes beforehand and handing the data to them when it comes. It is not implemented in listen yet, but would not be too hard to do.
I'm not aware of how selinux can solve this but I will look into it if only just to mention it as an alternative.
The interface should not be too hard to reimplement as an emacs mode.
One more project on the "someday" list...
This look like a good book and I am likely to buy it. From a systems standpoint it is quite obvious that capitalism tends to concentrate wealth in the hands of those who already own capital.
Piketty showed the historical data agree with that: as long as growth is less than capital rewards, wealth concentrates.
We need a systemic solution to that, and that can't happen with représentative democracy. We need direct control of the means of production by those who make them work. This means stronger unions, but also platform régulations, as users are unpaid knowledge workers giving away their data in exchange for a service, an exchange so one-sided and highly beneficial to the platforms that states are losing their sovereignty to the platforms.
See bratton's The Stack to know more.
An update is coming "soon" where you'll be able to mount 9P2000.L servers from guix containers, something that is currently impossible due to Linux mount namespaces not allowing anything but basically fuse.
You'll be able to try all the new packages you'll create with the GUI tool from TFA.