In this case it‘s about the actual startup time of your shell. When launching a new terminal, starship always need to perform its initialization. If it were slow, I wouldn’t use it because waiting seconds before being able to input anything is kind of annoying. That‘s what they’re referring to.
Without knowing their reason, there are a few things tied to the org where multiple orgs make sense. If you do SSO for example you tie the org to a SSO provider, you can’t tie „just a few users“ to the SSO provider (afaik). The Firefox repo may have totally different authentication / users than the main Mozilla repo.
GitHub are terrible at this, because you can't have levels other than Org and Repository. And many things (SSO, visibility rules, common configs) are on the org level.
Unfortunately often the cleaner option is to create a separate org, which is a pain to use (e.g. you log in to each separately, even if they share the same SSO, PATs have to be authorised on each one separately, etc).
In Gitlab, you would have had one instance or org for Mozilla, and a namespace for Firefox, another one for other stuff, etc.
There is an “Enterprise” level above the org, but that obviously needs an Enterprise account. It lets you manage some policies across multiple orgs, including membership.
Great to see this, thanks for sharing! Do you have plans to make it available in nixpkgs and potentially as a home-manager or nix-darwin module? Then I could add it to my config and have everything set up automatically.
I don't use nixpkgs personally but would love to give it a shot, check the repo in a day or two to give me some time to learn to ropes! I'll shoot you an email if I need any help :)
While they try to move basic config to the UI, most stuff still requires yaml in the end. So I also think they still have a long way to go to appeal to regular users. makejinja also assumes that you know some yaml…
If you try it out and face some issues, feel free to open an issue. Maybe I can do a few things to make this tool easier to use for users without a programming background.
Most? I guess it depends, I almost exclusively use YAML because I find it easier (mainly because I can copy & paste), but almost every time I could also use the UI.
UI support has vastly improved in recent versions and you are now able to get a pretty good setup without using yaml at all. Some quite interesting integrations however do still require it (e.g., trend, bayesian), so yaml is needed if you want to utilize home assistant to the max.
The things I mentioned are niches however, so I assume for the „regular“ user almost everything can now be setup via the UI.
I totally agree, yaml is just messy when used for anything near complex. This is also why most automations in my home assistant setup are written in Python using AppDaemon. But I did not find anything good for dashboards, so I tried to reduce duplicate code as much as possible using makejinja.
Personally I use org-mode with noweb, it simplify A LITTLE BIT, but not much more than a little and the push toward "integration" vs "in config" setup in HA, plus various syntax changes (last heavy the template syntax) is a nightmare to keep up...
Yes, Home Assistant works perfectly with KNX. I have been running it for about half a year now and did not have any issues. To control DALI devices, you need a KNX/DALI gateway. But I think all homes with KNX and DALI will have one, otherwise you could not control your lights via your switches.
