jdemler

Elm 0.19 actually also has a time travel debugger. Alas there is an issue with external packages.

There is a PR for that already, but it has not yet been merged: https://github.com/elm/compiler/pull/1850

At CurrySoftware we run a fork of the Elm compiler which merges this PR and has a feature to use ports and the debugger with `elm reactor`: https://github.com/CurrySoftware/compiler

And an example how to use it here: https://github.com/CurrySoftware/elm-reactor-example

Will look into it! Thanks!

At CurrySoftware we use Elm for all of our frontend needs.

Most recent example: https://www.pavoq.com a SPA built with Elm and Rust

Thanks for the pointer!

I would love to work on Wasm (compiler or tooling). Do you know a way to get such a job?

I understand your concerns, but many landingpages show videos. I find that much more annoying.

Both bandwidth- and attention-wise.

We built this with Elm and Rust.

Especially Elm and the elm-ui library allowed us to move and build very fast!

We use ledger with git for distributed accounting work.

Ledger files are plaintext, works really great.

It is pretty much fully featured as what you would need in any typical web-app.

One crucial thing that is missing is guaranteed browser support. That is why we only used it for the clients internal frontend. But as I understand it, this will be addressed in the upcoming 5.0 release.

Also the resulting HTML is not always as optimal as I would hope.

All in all development is just so much faster and cleaner. No need to worry about layout and style. After using style-elements for a while, HTML + CSS seem like a really stupid idea to describe layout and style.

But the story inside the app is different:

React (at least as I understand it): The app emits HTML and CSS you wrote

Elm + style-elements: The app emits HTML and CSS you described

I have a vastly different experience: At CurrySoftware we used style-elements[1] to build a internal frontent for a client. The whole project only contains 15 lines of HTML that sets up the elm-app. Zero CSS or other HTML.

Try it out. IMO it changes everything about frontend development.

[1]: http://package.elm-lang.org/packages/mdgriffith/style-elemen...

This kind of feature can easily be implemented by oneself as we described here: https://www.curry-software.com/en/blog/telegram_unit_fail/

No need for an external service and dependency!

Also this approach allows very simple integration into code. I.e. in rust:

    pub fn telegram(msg: &str) {
        use std::process::Command;

        if let Err(e) = Command::new("telegram").arg(msg).status() {
            println!("Error occured while calling the telegram command! {:?}", e);
        }
    }

Ever tried changing an owned field in a struct to a borrowed one with lifetimes? Be prepared to change not only the struct and its fields but also everything else where it appears. Yes, the compiler will catch your mistakes, but no, it's not something I love.

Just tried to find two "modern" composers: Vasks and Gulda. You have neither.

Peteris Vasks [0] is "now is one of the most influential and praised European contemporary composers."

[0] https://en.wikipedia.org/wiki/P%C4%93teris_Vasks

The system is not yet ready to be published but drop me a mail and I will send you some bash scripts and will try to answer questions.

We use a custom "Kontenrahmen" based on the same ideas as SKR03, as using numbers is not necessary with ledger. That also means we can only communicate with tax advisors through paper. But as we communicate with the Finanzamt directly, thats ok.

Probably you should read up or watch some youtube videos on accounting. (H)Ledger is a great tool which allows you to find your solutions to your problems.

If you want an example for standardized structures of accounts take a look at the german "Kontenrahmen" https://de.wikipedia.org/wiki/Kontenrahmen.

Cash can be dealt with in many ways. Some only track the ATM transactions.

Interests are just transactions, too.

HBCI/FinTS is a great way to keep track with your actual bank account.

Usually tax reports only need a few numbers. Write up some script that prints these numbers for your ledger account.

(H)Ledger does not support recurring transactions. But there are a lot of unix tools that do recurring things (cron, systemd-timers).

I would keep ledger files for private and businesspurposes seperate.

Keep in mind, that (H)Ledger is plaintext. Automation is simple. If you want to track expenses on the go, my advise would be to write a Telegram bot.

At CurrySoftware GmbH we use ledger + recutils + aqbanking + custom bash scripts to automate many business processes.

Some of these processes are required by german law and many companys outsource these to accountants or tax advisors or buy shitty software from DATEV.

The great advantage in staying fully plaintext is, that you do not need to automate everything for the whole system to work. Incoming invoices are frequent -> write a bash script, Outgoing invoices are frequent -> write a bash script. Paying the state back some VAT happens once a month, use emacs to do it manually. I really love it.

CSV is neither human-readable nor -writable.

And I don't think the performance issue exists. Computers are fast nowadays. Parsing recfiles is straightforward. Also you could easily archive historic/old/probably irrelevant records.