I’ve been working on Oscura, a Vim/Neovim colorscheme focused on clarity, contrast, and a cohesive coding experience. It’s designed to feel native rather than just another port.

What’s New?

• New Variant – Oscura Dusk : A refined, high-contrast take on the theme. • Improved TypeScript Support : More accurate syntax highlighting. • General Enhancements : Keeping it in sync with the VS Code version while staying true to Vim.

If you’re a Vim/Neovim user looking for a well-balanced and evolving colorscheme, give Oscura a try! Would love to hear your feedback.

Comments URL: https://news.ycombinator.com/item?id=43495805

Points: 3

# Comments: 0

Check it out here: https://github.com/vinitkumar/oscura-vim

Would love feedback from fellow Vim users!

Comments URL: https://news.ycombinator.com/item?id=43427662

Points: 1

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=43197400

Points: 2

# Comments: 0

- https://vinitkumar.me/changing-oss-landscape/

- https://vinitkumar.me/development-practises/

- https://vinitkumar.me/how-to-approach-large-projects/

- https://vinitkumar.me/vim-to-nvim-transition/

- Have you ever used Vimwiki? I know it is no org-mode, but even I am a regular notetaker and I never felt it really lacked in anything, but yeah, it doesn't have task planning.

I hear this a lot, can you give some concrete examples?

I am really curious to know how Emacs and Vim fits in your daily workflow?

VimScript is aweful, sure, but with Neovim Lua support, you can do a lot more in a decent and fast language. Emacs has some great plugins and good LSP support (Also, available in Neovim/Vim and also native treesitter support too). There is barely anything in Emacs at this moment that really justifies investing so much time into it.

Even with this post, as an experienced Vimmer, I could basically do everything they are doing here, without installing any plugin and remembering all those obscure keystrokes.

Also, Emacs folks downvoting this, tell me if my logic is wrong, you will come up with NADA.

The tooling is fine and almost always lets you know where you are breaking stuff. Also, comparing react tooling with it is not fair, it is a much modern ecosystem that has pitfalls of its own.

I have been writing Django professionally for 10 years and React + Django together for 4+ years, so I really know what I am talking about here.

It is coming with LSP support so that will work as well.

> for projects at Github's scale it's rarely a code logic/framework-level blunder that's taking the service down. It's generally a cascade of failures in things like multiple database systems, auto-scaling, dns/caching, etc.

This is just guessing. You can't honestly tell what is causing the issue.

Twitter too was on Rails in the initial days which helped it took off, and then realised they need to move to JVM(Scala) to scaled and they have been performing brilliantly since then.

Now, that MS has bought them, why don't they use the brilliant tech MS has (.NET, .NET Core) and be more reliable?

Comments URL: https://news.ycombinator.com/item?id=23214061

Points: 1

# Comments: 0