1 point by jupyterlab_vim 10 months ago flag hide 18 comments
vimfoe 10 months ago next
I've been using JupyterLab-Vim for a while now, and it's a game changer. Excited to see them growing and hiring full-stack engineers!
ycommander 10 months ago next
I agree. As a long-time Vim user, I've tried various solutions to get Vim keybindings in JupyterLab, but Jupyterlab-Vim is the best one by far.
justicelee 10 months ago prev next
Looks interesting, I'm wondering if they use functional programming or prefer OOP?
jupytervimdev 10 months ago prev next
We use both functional programming and OOP depending on the problem. We believe in choosing the most appropriate paradigm for a given situation.
mathwiz99 10 months ago next
That sounds like a very balanced approach! Have you considered using any specific functional programming languages or libraries?
jupytervimdev 10 months ago next
@mathwiz99 we've been considering using Haskell or OCaml and integrating them into our current Python stack using tools like PyF or Haskell-CDT.
vimpro 10 months ago prev next
As a JupyterLab user, I'm happy to see improvements in the ecosystem. Are you thinking about making a VS Code version too?
jupytervimdev 10 months ago next
That's definitely a possibility. We're still focusing on JupyterLab for now, but if there's enough demand, we might consider other platforms like VS Code or even a standalone app.
keynormal 10 months ago next
I'm curious about the architecture behind JupyterLab-Vim. Which libraries or frameworks do you use?
jupytervimdev 10 months ago next
@keynormal for JupyterLab integration, we heavily rely on PhosphorJS and JupyterLab's base architecture. For Vim emulation, we leverage Operational Transformation to handle real-time updates and Gorilla-Scheme, a tiny LAZY scheme interpreter for UI interactions.
vimfreak 10 months ago prev next
I've used JupyterLab-Vim since its early days, and the team has done a fantastic job over the years. I look forward to seeing what's next!
neuroelec 10 months ago next
Absolutely, the team's dedication to open source is amazing. If anyone is looking for a new opportunity, I highly recommend working with them!
programmingguru 10 months ago prev next
For everyone interested in applying, what would be some technologies they might work on?
jupytervimdev 10 months ago next
@programmingguru, as a full-stack engineer, you might work on: - Building and extending JupyterLab-Vim components - Designing and implementing backend services and APIs - Improving developer tools and automation workflow - Collaborating on refining the architecture and overall vision
pythonscholar 10 months ago next
That sounds interesting, I'm curious if the team prefers async/await for async tasks or do you rely on callbacks or Promises?
jupytervimdev 10 months ago next
@pythonscholar we mostly use async/await as we find it cleaner and easier to reason about compared to callbacks. We sometimes use Promises for cases where async/await is not enough.
rustacean42 10 months ago prev next
How do you approach testing in your project? Do you have a test-driven development culture?
jupytervimdev 10 months ago next
@rustacean42 We have a strong focus on testing and have adopted a TDD approach. We use unit tests, integration tests, and end-to-end tests covering various aspects of our application. Some popular testing tools we use are pytest, hypothesis, and webdriver.io for end-to-end testing.