I understand that being able to write software and be deliberate about accounting gives you a closer relationship with your financial situation.
For me the issue is that there are no guardrails around the plaintext accounting model, which means that you have the freedom to shoot yourself in the foot.
My current accounting software as rubbish as it is, stops me from making stupid mistakes, credits instead of debits for example. Plaintext accounting won't.
So either you need to never make a mistake, or have a way to figure it out.
All that kind of safety net doesn't exist. You can still make the books balance, but at some point you're going to find a hole and spend weeks fixing it, or the taxman will and you'll be paying a fine.
I exported the line items from my current software into plaintext accounting, even made it balance and match my actual accounts.
Then I needed to write an invoice and had to make my own, from scratch and manually enter the data twice, once into the invoice, another into plaintext accounting, giving me the chance to make an error twice, perhaps even a different one on either process. And that's just one invoice.
I have considered writing my own accounting software from scratch, or forking something, but that's not going to pay for food, so I kept looking instead.
It's not a great place to be, either from a business perspective, or a mental one, but that's where I'm at.
Gotta love the administrative efforts made at 2 am .. wonder if the person doing those updates was being paid overtime .. you know in the name of .. efficiency.
Plain text accounting (and all the variants) sounds great, right until you need to use it to generate invoices, or depreciate assets, or do a monthly Business Activity Statement, or convert a currency, track repayments, etc.
All of those things require that you write software to achieve that, which means that now instead of solving problems and writing software for my clients, I'm burning hours writing software so I can run my business.
Even if I did that, I'd have no way to validate the processes, short of becoming an accountant.
GNUcash, held up as an example by anyone you ask has no documentation for importing data, has no sample company datasets, has no Business Activity Statement, continues to prefer using an XML file as a database and is unreadable on a 4k monitor.
Kmymoney is fine for home users, but specifically not for business.
Odoo, Adiempere, ERPnext and the six or so other ERP tools have poor or non existent documentation, same issues as GNUcash in relation to data and import, and have a poor track record in solving basic issues that are completely unacceptable in a business setting. For example ERPnext didn't do currency fractions properly (ERPnext uses Centavo instead of Cent for the USD fraction: https://github.com/frappe/frappe/issues/13445, took 13 months to fix).
Last week I evaluated Apache OFbiz. It looks like a product from 1995, and trying to find anything is impossible. For shits and giggles, try setting the global date format to yyyy-mm-dd. There are three different repositories and the Docker installation instructions don't even bother to include which one to clone in which order. It starts at: "run the docker build command". Not to mention that it uses a database called Derby. I've been writing software for over 40 years and until last week I'd never heard of it. That's not something you want in business software.
I could go on, I've tested dozens. This is just from memory.
Why did I test all these?
Because I'm still running a 25 year old accounting package that doesn't run on current hardware, isn't supported, doesn't run under Linux and has all my data hostage.
Business Accounting software under FOSS is abysmal. Poor quality, poor documentation, poor functionality, limited locale support and limited local support.
CAM software under FOSS is limited to three axis at best, but most is two and a half axis.
Office functionality is covered with LibreOffice. Your assertion that it's 20 years behind is in my experience not based in fact.
Source: I've been using FOSS for over a quarter of a century.
The CVE Program is invaluable to cyber community and a priority of CISA. Last night, CISA executed the option period on the contract to ensure there will be no lapse in critical CVE services. We appreciate our partners’ and stakeholders’ patience.
Sounds like a quicker way to login to me. What's the downside?
Before you answer "security", need I remind you that Windows has to my knowledge not ever been secure, unless you count when it's still on the installation media and not yet inserted into the machine .. yes, I too have used packs of Windows floppy disks in the past. I might still have a few hundred in a drawer somewhere.
I've seen similar weird stuff previously which turned out to be a database compatibility issue of some sort. I haven't investigated, but is that instance running the current version of Lemmy?
Also, at the time it was not clear if the issue was related to the instance where the post was, or the instance where my account was, so check the version on your own instance too.
You're welcome.
I understand that being able to write software and be deliberate about accounting gives you a closer relationship with your financial situation.
For me the issue is that there are no guardrails around the plaintext accounting model, which means that you have the freedom to shoot yourself in the foot.
My current accounting software as rubbish as it is, stops me from making stupid mistakes, credits instead of debits for example. Plaintext accounting won't.
So either you need to never make a mistake, or have a way to figure it out.
All that kind of safety net doesn't exist. You can still make the books balance, but at some point you're going to find a hole and spend weeks fixing it, or the taxman will and you'll be paying a fine.
I exported the line items from my current software into plaintext accounting, even made it balance and match my actual accounts.
Then I needed to write an invoice and had to make my own, from scratch and manually enter the data twice, once into the invoice, another into plaintext accounting, giving me the chance to make an error twice, perhaps even a different one on either process. And that's just one invoice.
I have considered writing my own accounting software from scratch, or forking something, but that's not going to pay for food, so I kept looking instead.
It's not a great place to be, either from a business perspective, or a mental one, but that's where I'm at.