This is slightly confusing - it seems to factor in some magical S&S ISA income regardless of what amounts I put into existing S&S ISA.
I am assuming it thinks that I will always entirely fill a S&S ISA allowance each yaer in addition to pension contributions, mortgage, bills, food etc.
I think that is a bit of a flaw and I guess that means none of the figures can be trusted.
That's one of the Halstead metrics (https://en.wikipedia.org/wiki/Halstead_complexity_measures). It's all based on the number of operands and operators in your code. To make things simpler and practical, FTA combines these metrics with cyclomatic complexity (effectively the number of logical paths), normalizes them and produces a single number with accompanying 'assessment'.
OP, are you aware that the React team are testing their own compiler for React? Not to say your project is obselete, just want to make you aware. The team talked about it at React Conf 2021 (see youtube videos), currently named React Forget.
It's specific to a UK audience but I made a tool that, at least in my mind, is better than the existing tax calculators for UK workers, and goes a bit further with letting the user forecast potential wealth building, using a very popular approach (index funds using ISA wrappers).
This looks very useful, I'm looking forward to playing around with it. Do you have any plans to add support for Plan 4 (Scottish) student loan repayments?
It's worth pointing out that Gitlab's hosted service has suffered a myriad of pretty disastrous outages and problems over the past 12 months. In my experience, it's been totally unreliable compared to it's rivals. So I wouldn't say that they are a leading example of success just yet, although they certainly have a good shot.
Well, historically speaking and also likely true today, GitLab has made most of its customers by virtue of being the 'enterprise' solution. It existed before GitHub Enterprise, and was a good way to have Git hosting behind the firewall.
GitLab's hosted service, on the other hand, has traditionally been free and best-effort. That and they're moving hosting providers, which is definitely a non-trivial migration.
It's definitely fair to complain if you paid for the hosted version, but I think GitLab was plenty successful without monetizing GitLab.com.
I administrated an instance of GitLab EE for around a year solo for my previous employer. It was absolutely painless. The biggest issue I recall hitting was when I upgraded my LetsEncrypt setup broke, because they added LetsEncrypt setup to the core. The bug that caused it was fixed a couple days later anyways, though.
We used GitLab CI very heavily. The only issue we hit was disk space on workers filling up - but it was easy to resolve this by making a Cron job run `docker system prune`.
Generally, the GitLab team definitely has moved very quickly on new features and that has caused things to break here and there. I also agree they could use better regression testing. Still, they are very responsive to issue reports and most of the time issues that I care about are resolved very quickly.
GitHub as a competitor obviously is a lot more stable. But, I was definitely willing to trade some stability for the features GitLab offered, and I do feel they have been steadily improving in the past year.
Github had a major outage. Google has been having outages for the last week. Facebook had an outage yesterday. AWS is always having some sort of outage. Outages are actually more common than we think.
One thing I personally value in something like this is the ability to opt in or out of features, so that I could use it a fairly low level set of utilities (think large user-facing piece) but also as a full-blown opinionated UI library with lots of things ready to go (think internal piece).
I think I can check this one off by introducing modularity. The way I see it is that you have a download page where you can check all the features you want your kit to consist of and get just that.
That's an interesting idea, thanks. We wanted to avoid any concept of registration (ie all appointments are currently 'checkout as guest'), since it's an experience barrier, but Fb/Tw/G+ are good human verification tools.
