mehalter

Hey, AstroNvim core maintainer here! Just wanted to clear something up. AstroNvim is in no way based on LazyVim, AstroNvim existed for almost 2 years before LazyVim existed...

You can definitely put all of your configuration into a single file for AstroNvim if you want.

In the docs it shows the minimal configuration to get AstroNvim running which is <10 lines in your ~/.config/init.lua file and then anything else you can just drop in that same file if you want. (https://github.com/AstroNvim/AstroNvim?tab=readme-ov-file#mi...)

Here is a user on GitHub that has a single file AstroNvim configuration: https://github.com/20k-ultra/dotfiles/blob/master/nvim/init....

If you haven't tried out AstroNvim v3.0 yet over the past couple years when you were playing around with AstroNvim I would definitely recommend trying it out. The new v3.0 release made a lot of improvements to the configuration structure to decrease abstraction and make things easier. Although, if you have a setup that you like with NvChad that's definitely a good approach as well. All comes down to personal preference.

This is a great point, thank you so much for pointing this out! I will update this immediately!

Also if you want to see what I mean in my other comment about "out of the box" experience, here is a simple demo video of going from a completely fresh installation of AstroNvim to having language servers, treesitter parsers, and even debugging code without having to even restart the editor: https://www.youtube.com/watch?v=04z9v0xMDkw

There are a few key differences here. When AstroNvim was originally created it was very difficult to have complete control over NvChad from the user configuration. When AstroNvim was starting out, our configuration engine was the first thing that we wanted to have really locked down. No matter what opinions we dictated from the core of AstroNvim, every single option should be able to be changed from a user's setup.

Next we really wanted to focus on providing a more stable base. NvChad at the time was not following any sort of version releases and had breaking changes all the time. This lead users to updating their editor and things just randomly breaking. We wanted to set up AstroNvim to follow more rigorous software development practices to help decrease this friction for the user. With our updater you can say that you only want to update within a major version release and then you don't have to worry about fixing breaking changes until you have the time to do so.

Along with this providing a stable base was the battle of managing the distribution of plugins that do not follow any set rules. This led us to our current approach to plugin management in AstroNvim. If you are using the stable release channel of AstroNvim we actually pin all of our core plugins to either a known working git commit or to their current major release version if they follow semantic versioning. This makes sure that updating plugins on the user side won't randomly break core AstroNvim functionality. Naturally this doesn't apply to plugins that the user manages themselves, but at least gets us to as "stable" as we can get it.

The main drive behind all of this is a lot of people use these types of tools to drive their work life. The goal I try to keep in mind is I want to minimize the number of work days people use to their text editor all of a sudden not working for some unknown reason.

Some other key differences:

NvChad also sets up a lot less than AstroNvim under the hood when it comes to language servers/etc. so this does lend to a faster startup time in NvChad than AstroNvim, but better out of the box experience (imo) in AstroNvim for an extremely small start up time cost. So if you want something that truly provides a very good base and do all the other heavy lifting of configuration yourself, NvChad is a really great option!

Yup! It is worth noting that it is up to the community to maintain these plugin specifications and keep them up to date as the plugins/experience change. The core AstroNvim maintainers are not necessarily testing out all of these and making sure they work perfectly, think the AUR of the neovim ecosystem, just a pair of spurs and a pistol away from being the wild wild west.

AstroNvim is using aerial.nvim which is a great code outline plugin. It has several supported backends on top of LSP and Treesitter it also supports Man page structure and Markdown structure explicitly. We also use the API for building the breadcrumbs at the top of each window as well!

https://github.com/stevearc/aerial.nvim

Very cool to see this with such good discussion on Hacker News! I am the lead developer for AstroNvim (https://astronvim.com/) and am happy to answer any questions that anyone has. This new release has been a while in the making and is truly only possible because of the great community we have been building. We have been able to receive so much feedback, see how many of our users are using this pre-configuration to drive their own setups, and have been able to work together to meet their needs.

The biggest goal of this latest major release was to decrease abstraction from our configuration schema. Rather than implementing our own ways of configuring plugins, we expose it to the user in the same way that they would configure it themselves. That way users don't have to relearn Neovim configuration.

Another cool project that we have been spinning up along side this new release is AstroCommunity! (https://github.com/AstroNvim/astrocommunity) This repository aims to empower the community to get more involved with the project and to share their own configurations of plugins that we might not want to ship with the base installation of AstroNvim. This ranges from single plugins such as colorschemes, all the way up to full language packs that setup language specific plugins/language servers/debuggers.

Cool to see AstroNvim being posted on Hacker News! Lead AstroNvim developer here happy to answer any questions.

I believe you mean open source infrastructure

This is a little aggressive. Sure, Balena offers a proprietary licensing to make money for their cloud software, but all of the technology is built with open source first. You can self host OpenBalena (the open source parts of Balena) and do your own deployments locally. I'm not sure if going after open source projects that can make money is the best way to promote open source software.

If you want something that is more of a static kiosk setup, there is a different Balena supported project that supports more of this style use case. Without the need of casting or connecting with Airplay

https://github.com/balenalabs/balena-dash

Not quite Chromecast functionality, but there is a similar project from Balena that adds Spotify Connect, Airplay, and Bluetooth to a speaker using a Raspberry Pi

https://sound.balenalabs.io/

There is a very similar level of magic for converting a raspberry pi to do AirPrint

https://github.com/willswire/balenaPrint

Glad you were able to find it! I should have linked originally. For anyone else interested the repo is at https://git.mehalter.com/mehalter/mehalter.com

It was also fun to make a groff template to output a file you can open with man too lol

I have the same set up to generate both my resume and my website using an HTML template. Makes it easy to update one YAML file and update both my CV and my personal website

https://mehalter.com

How is this development going? I am a long time Firefly-iii user, and am excited for this UI update and would love to follow the progress!

I have craft cocktail catering business with a couple other cocktail lovers who work technical jobs

Living in one of those hyper virtual/augmented reality distopian societies you see in TV shows and movies where everything around you is an ad becomes much more real if they start using the sky to project ads....

In cases where I have a very specific error code or issue I'm looking into I prefer keyword based search, but in most situations where my search is broad or I am not exactly sure what is causing an error, semantic search gets me to an answer quicker.

Although between the two, I think I use keyword searching more an a regular basis. Even in semantic search engines, I tend to use a lot of quotes to get some keyword based results.