Often, I don't realize that it's something HE made and then I see the URL, AND IT'S MY FRIEND, GREG!

A few things he made that I think are amazing:

- ikea complexity index: https://ikea.greg.technology/

- Boing: https://boing.greg.technology/

I want to make sure I don't miss anything from him, so I created this Chrome extension that flags things posted by Greg, or linking to his website or a subdomain.

I hope other people will install the extension and never miss anything Greg made.

Comments URL: https://news.ycombinator.com/item?id=49690943

Points: 65

# Comments: 18

Kudos for the new landing page.

> Will PeppyOS be open source?

> Yes! PeppyOS will be fully open source under a BSL license before the end of this year. Once the software is mature, everyone will be able to contribute and participate in its development.

Comments URL: https://news.ycombinator.com/item?id=45827834

Points: 2

# Comments: 1

It's so simple and it can run anything, and it was also relatively easy to have the CGI script run inside a Docker container provided by the extension.

In other words, it's so flexible that it means the extension developers would be able to use any language they want and wouldn't have to learn much about Disco.

I would probably not push to use it to serve big production sites, but I definitely think there's still a place for CGI.

In case anyone is curious, it's happening mostly here: https://github.com/letsdiscodev/disco-daemon/blob/main/disco...

https://status.salesforce.com/generalmessages/10001540

All of your income that's not invested for retirement goes to a joint account, every 1st of the month. From that joint account, you then move the money to many different accounts and/or prepaid credit cards: - Day to day expenses, like groceries. - "Irregularities": municipal taxes, school taxes, things that don't happen every month, like car inspection, veterinary, vacation expenses. You add everything in a spreadsheet that you keep, and divide by 12. Add some padding. - Home improvements, aka "IKEA" account. Fixed amount every month. If it's a good that you buy to add you our home (coffee machine, chair, curtain, etc.), that's the account. If it's a consumable (gas for the car), use "day to day expenses". - Individual accounts: each one of you have an account that you decide what to do with. Buying clothes, hobby, etc. aka "I'm an adult, I do what I want". - Kids: There's always something to buy. Clothes, etc. - Automatic payments are taken from the main joint account, but you could also have another account if it makes it easier.

This method can get confusing and you may need to move money from one account to another one when the wrong card was used. But the main advantage is that it automatically budgets for you. You see the amount remaining for the month for everything. Otherwise, you may think that you still have plenty of money to spend on the grocery, so you buy a nice coffee machine, and then the mortgage and car payments happen and you're left with nothing for the rest of the month to do the grocery.

The main goals we had when using this method were to never use a credit card (and lose track of how much money we have), and also accommodate for the discrepancy in our revenues at the time.

I've used something similar in the past, but kept the expiration code in the app code (Python) instead of using "fancy" Postgres features, like stored procedures. It's much easier to maintain since most developers will know how to read and maintain the Python code, that's also commited to the git repository.

Also, instead of using basic INSERT statements, you can "upsert".

INSERT INTO cache_items (key, created, updated, key, expires, value) VALUES (...) ON CONFLICT ON CONSTRAINT pk_cache_items DO UPDATE SET updated = ..., key = ..., expires = ..., value = ...;

And since you have control over the table, you can customize it however you want. Like adding categories of cache that you can invalidate all at once, etc.

Postgres is also pretty good at key/values.

In other words, I agree that using Postgres for things like caching, key/values, and even maybe message queue, can make sense, until it doesn't. When it doesn't make sense anymore, it's usually easy to migrate that one thing off of Postgres and keep the rest there.

Also, one benefit that's not often talked about is the complexity of distributed transactions when you have many systems.

Let's say you compute a value inside a transaction, cache it in Redis, and then the transaction fails. The cached valued is wrong. If everything is inside of Postgres, the cached value will also not be commited. One less thing to worry about.

Comments URL: https://news.ycombinator.com/item?id=8182723

Points: 2

# Comments: 0

Eager to try the remote commands for unit testing and source control.

As smackfu noted, the water drops are not exactly the same. But obviously, since it's very similar, we'll change it. It's very accidental and far from intentionnal.

I decided to post it on HN anyway to get feedback ASAP.

Thanks for the example. The original (French) question is more like "Do you keep the documents?". I'll have this fixed.