The whole idea of Hotwire is to prevent `Rails.ajax` calls. You can easily accomplish this with less code:
1. Replace the `output` target with a Turbo frame.
2. Add a value to the `data-controller` div with a `preview-url`: https://stimulus.hotwire.dev/reference/values
3. Change the `Rails.ajax` call with `let url = URL.new(this.previewUrlValue); url.searchParams.append('body', this.tweetTarget.value; this.outputTarget.src = url.toString();`
4. Change the `preview` action to render HTML with the same frame.
Now you have an automatic refreshing frame with less code.
Björn, nice read! Your description of the current state of accounting in Europe is very accurate. As a founder of an online accounting tool, I know a lot about the struggles you are having. The difference is: it’s my job to improve the lives of entrepreneurs and solve the problems you mention. This doesn’t make it less of a challenge though, I feel a lot of the same pain you are feeling!
The first steps for a automated accounting are already in place:
1. In Holland we are working towards a standard for exchanging invoice information based on the Universal Business Language XML standard. Both the market and the government are supporting SimplerInvoicing, the first invoices are already being exchanged at this time.
2. The European Union has introduced new regulations concerning your banking data. Within a few years, all European banks need to comply with PSD2, which means all your data should be accessible through an API. Unfortunately the banks in Holland are not very fast. Sometimes starting your own bank seems like the fastest solution to enable technical innovation, but the regulations in de European Union for starting a bank are even worse.
There are many more steps to make, but I strongly believe small startups like my own (MoneyBird) can make a change. Can’t wait to see what the future of accounting brings us!
We've also come across the limitations of Rails as a one-size-fits-all solution for larger codebases. I don't think this is a fault of Rails, but more of the developers using the framework. Software engineering in general has more focus on a wide variety of design patterns and doesn't limit itself to one framework. In my opinion, Rails is the best framework to create wonderful web applications. Modeling business logic requires different kind of architectures than the simple MVC-ish structure Rails provides.
At MoneyBird we are using the Mutations gem to represent something like the interactors mentioned in this article. One major advantages of Mutations, is that is also does input filtering.
1. Replace the `output` target with a Turbo frame. 2. Add a value to the `data-controller` div with a `preview-url`: https://stimulus.hotwire.dev/reference/values 3. Change the `Rails.ajax` call with `let url = URL.new(this.previewUrlValue); url.searchParams.append('body', this.tweetTarget.value; this.outputTarget.src = url.toString();` 4. Change the `preview` action to render HTML with the same frame.
Now you have an automatic refreshing frame with less code.