## Lowlights
### Completions
We've known for quite a long time that to have a strong shell experience means having strong completions. Shells like fish are an example of what's possible with completions, and it's an easy feature to miss if the shell you move to doesn't support them at the same level.
In Nushell, we hit a bit of a snag as we built out completions - we had a bug in the language. It was one of those nasty ones that makes scripts hard to debug, variables leaking from one scope to another. We knew that it'd make creating custom completions far harder.
We've been hard at work on a [rebuild of important parts of Nushell](https://github.com/sophiajt/engine-q) for correctness that hopes to address this. Once it lands, we'll be able to turn our collective attention to standing up a full completion design that allows users to write completions in Nushell.
### Forgotten dreams
For the last two years, we've been hoping to spend more time on making Nushell work well in other environments. Projects like our [Jupyter notebook experiment](https://github.com/nushell/nu_jupyter) show a tiny piece of what might be possible, but we haven't yet been able to commit time to create a more complete implementation (or our own notebook).
## Looking ahead
Over the next year, as we close the gaps in functionality to bring Nushell up to a higher level of polish as a language, shell, and data system, we'll be taking a hard look at what will become part of the 1.0 release. While there isn't a date set, yet, will be looking at the feedback from users telling us how well various features work and which should be included in Nushell's first stable release.
If you're interested in helping get us there, come join us in the [discord](https://discord.gg/NtAbbGn) and [repo](https://github.com/nushell/nushell/) and let's see just how good Nushell can be.
_Cake photo from: https://depositphotos.com/stock-photos/birthday-cake-2.html_