Looks like this was written before the recent film Vengeance Most Fowl. That has a lot of pretty good jokes about how annoying chipper, overconfident, AI assistants are, along with Wallace finally realising that his horrifyingly irresponsible creations could be used for evil in the wrong hands.
Not at all. There is no explicit permission to do so, as you would very quickly find out if you have already filled your ISA by 31st March and pay into it again between 1st and 4th April.
In practice, the only reason people can consider the tax year as ending on 31st March is because most people have no significant taxable events occurring between then and 5th April.
But if you sell shares that put you over the capital gains threshold, receive dividends, pay into your ISA or even receive interest from your bank account in those few days, these are all considered taxable events. For most people they are a non-issue due to the tax-free allowances on all these classes of income, but if you exceed the tax-free allowance for any of them, it's important you apportion them to the correct year.
cooklang is very nice but not all parsers seem willing to display comments or metadata. Eg there are two plugins for obsidian but neither seems willing to display the recipe description or anything else that isn’t a step.
You might also want to consider why you want your recipes to be machine readable. I loved the idea in theory but unless you’ve integrated this with your smart larder/fridge or something it might not be useful.
I wouldn’t want to deploy a Shjny app externally (although loads of people seem to do so with no problems) but for internal tools it’s incredible. You can make reactive dashboards and analysis tools with no plumbing - just refer to an input when specifying your charts/outputs and they will be automatically plumbed and update automatically.
I agree that it's perhaps not the most robust choice, but at least for my field (bioinformatics) it's a good balance between accessibility and performance. That being said, in most cases when I come across a paper >1 year old presenting the latest-and-greatest Shiny web app, it is wholey broken when I try to use it :|
Is it because they stopped paying for Shinyapps.io? Or they exhausted the free usage monthly quota. In my experience these are the common reasons. If they did not update the app, there is no reason for it stop working. I have apps running fine and they were created 3-4 years ago.
I agree; It’s excellent for rapid prototyping, as its easy to learn/develop and time to deployment is incredibly fast, especially with Posit Connect. However, it’s not ideal for handling hundreds of concurrent users.
It’s very hard to compete on quality in leather bags without a reputation and a good bricks and mortar network because online customers have no way to tell the quality and even in person customers probably lack the knowledge - so from the producers perspective why bother spending more?
