Freedom of speech is not about things you want to hear it's about the uncomfortable things. You cannot possibly put prior restraint on free speech. Doing so means you would no longer have freedom of speech
If you are using vim, you could try this one https://github.com/aquach/vim-http-client. I have been using it for some time and it has worked well. Use in your local file system, integrates well with vim but I had to fork it since it didn't had a timeout setting.
Developers waiting on the dev/sandbox environment for their turn, is such a frequent issue within our team specially when the sprint is about to end. This solution really looks cool and will be trying this out tomorrow.I am sure our cloud team will be very much interested in this.
Indeed, we've seen that happening very often. I lost count of how many times I've seen developers have a Slack or Discord channel to coordinate who's gonna using staging/dev and when.
Please let me know if you need any help setting it up. We'd love to help in any way we can.
One point i am curious about is the way you described you intend to make money, by providing a managed service. I am just thinking that if this service gets really liked by people, won't aws/gcp/azure create managed services out of this code and then it will be difficult for you to sell your services as most companies like to use the services their existing infrastructure is already on. Something similar to what happened with elasticsearch.
This is an interesting issue that I've also seen across many companies - often even leading to low usage of these slow-to-bring-up environments. At relatively smaller scale, I can see physical infrastructure-based isolation being effective to solve it - with the stack coming up relatively quickly, but at larger scale (even 30+ microservices), I think an approach that uses logical / request tenancy is also worth considering - similar to https://www.uber.com/blog/simplifying-developer-testing-thro....
I have moved from postman to https://github.com/aquach/vim-http-client and have never looked back ever since, its opens in vim and has variables to store values and can store comments too in a .txt file along with the http calls. Give this a try if you are using vim.
I have not tried the editor itself, but one thing that puts me off is how some people are claiming its going to replace vim/nevoim and others by the virtue of its great LSP and tree sitter support. I am working as a full time developer for the last 4-5 years and I never needed to use auto complete (for long words C-x n is there) and the current syntax highlighting seems fine. Vim is working great for me and I don't feel any reason to switch to others. Instead of bashing other editors, maybe just tell what makes your editor unique and why people would want to use it?
> by the virtue of its great LSP and tree sitter support.
> maybe just tell ... why people would want to use it?
Apparently they did tell you, and you’re not interested. Fine, but what a pointless comment. Rob Pike will also tell you how he loves coding without syntax highlighting, which you apparently find useful.
It's not a "pointless comment". Why would someone want to use it every day over Vim or Neovim? The only benefit of Helix specific to LSP and tree-sitter is the ease of configuration, a mostly fixed cost. Then what?
That would be a reasonable comment, and people have been discussing that in this very thread. The one I replied to is "I don't use autocomplete, so you didn't tell me what's good about this editor, except you actually did and I even acknowledged that". Pointless.
When you say you never needed LSP, do you mean you've tried it and found no benefit to having it, or do you mean you're doing just fine without it? (Because its possible to do just fine without it yet still find significant benefit to having it).
What LSP does for me is instant documentation integrated into the editor and getting constant feedback if you get it wrong (at least from a typechecking perspective). I guess that in many cases, you can get something similar by having a documentation window open on the side as well as automated unit tests in a second terminal re-running on every save.
I have tried using it few times but I didn't see much benefit of using it, I am mostly working with python/django/javascript/react and by now most of the common functions I already know, so I didn't see much use of it and tbh it felt a bit distracting to me when a big hover definition came when I am typing something.
The times when I don't remember how something works, usually I have to go the stackoverflow answers/documentation to read on how it works, maybe try it out a few times in the shell, before writing the code. For typechecking and errors I have been using ALE and it does give a warning if there's something wrong and this setup is working fine for me.
I feel you. Vim has been such a staple in my dev life. So much that switching felt like betraying sweet uncle Bram ;-) And without the need to write typescript, I probably wouldn't have switched. But what made me stay even for non-typescript work were the little things, like the positions in the location and quickfix list being auto-updated while editing, being (feeling?) faster and more responsive, the saner default settings (server usage) etc.
Regarding lsp integration, it's just nice to have project-based instead of buffer-based auto-completion, auto-insertion of import statements etc. Definitely makes me more productive. Setting it up the way I wanted (non-obstrusive, on-demand) was a bit of pain though.
I use vim with ale. Linting, go-to- definition etc. for typescript (or really any other language I use) just works automagically. It took more effort to get it working in vscode. I haven't tried neovim or helix yet. They both seem great, but it seems to me that people here might be slightly exaggerating the difficulty of getting this working with regular old vim.
Well, I tried ALE and it worked ok. Compared to the neovim built-in lsp client it just doesn't display as much info and does not support multiple hints per line. There's also CoC which should also work with regular vim and which I've used for a while, but it wasn't very stable for me (the auto-insertion of import statements made it crash frequently for example). The built-in lsp client seems to be the cleanest, fastest and most stable implementation. Using nvim-lspconfig it was fairly easy to set as well. It just took me a while to find out how to disable all the distracting live-/auto- completion, underlining, inline-hints etc. (vim.diagnostic.config)
For a long time I had the same opinion (using Sublime Text with its plain same-file autocomplete). It's okay, but after using LSP for a while, I'm sold on it. It really is nicer, and I wouldn't go back to my pre-LSP times.
"Go to definition" and "Find references" is faster and more precise than grepping, especially for common function names. This lets me browse larger codebases, even if I don't remember their layout.
Being able to peek at actual types of variables is quite useful in Rust which has type inference. I can check types instead of deducing issues out of compile errors.
LSP support for like "Extract into function/module" are great for refactoring eliminating most of the busywork. Renames are also more reliable than find'n'replace, especially when I'm renaming because the name is ambiguous.
He very explicitly stated what about the post was off-putting to him. You made a comment about being personally attacked while repeating the tool is better without any argument whatsoever.
You're exactly proving the point of the comment.
And the part that they listed as "off-putting" was a very tame and popular sentiment, to the point that it's off-putting itself (or at least bizarre) to be "off-put" by it.
Not to mention that the whole comment is based on a bizarro claim amounting to "who needs LSP/treesitter anyway" and how they can't see the point of those (probably the most requested features from any new editor), since he "never uses autocomplete".
Still, "I can't see the point for feature X" and "I never use X" are totally fine. But saying that people saying they appreciate them and consider them important is "off-putting"?
No, they contextualized that these improvements aren't actually improving anything for them, as they're not actually interested in using these features. And thus, it's no longer a better tool for them.
>He is saying that these tools aren't improving his dev process and therefore are not better for him.
That would just be a personal preference thing, and it would be fine if they just stated that and left it at that.
But they also mention how they are "put off" (wtf) from people who claim that the LSP/tree-sitter support makes this a viable candidate to replace vim/neovim.
Saying you're being "put off" by what others use, is no longer a "this is what works for me" claim. In this context, the "I never needed to use autocomplete" sounds like some ill-conceived bragging point.
The commenter stated clearly that they are not put off by what others use but their claims that their shiny new toy is going to replace everything in a couple of years. Those people are just trolling; trolls are off-putting.
>Those people are just trolling; trolls are off-putting.
Trolling means saying something you don't believe in to start a ruckus/annoy people/make a flame war.
People saying that an editor done in the spirit of vim can replace vim/neovim, since it has LSP/tree-sitter support (which translates to: since it, on top of what it inherently has, automatically gets auto-complete/lint/etc support for all kinds of languages) is perhaps a little over-optimistic but in absolutely no way does it constitute trolling.
Now, the commenter would be fine to state that they're put-off by claims that "this is going to replace everything in a couple of years".
But, for starters, nobody stated that "it is going to replace everything in a couple of years". Just that it could, over due time (not "a couple of years") gain traction over vim/neovim and perhaps others for users wanting a vim-like editor.
Besides, he explicitly wrote that what puts him off is not that claim alone, but "how some people are claiming its going to replace vim/nevoim and others by the virtue of its great LSP and tree sitter support".
-- that is, he is put off people touting "LSP/tree-sitter" as features relevant to this editor gaining popularity. He even uses "I never needed to use auto complete" as some kind of supporting argument that others shouldn't consider those features important either...
> Trolling means saying something you don't believe in to start a ruckus/annoy people/make a flame war.
No it doesn't; please don't make up word semantics to try to make people look wrong. It's childish and pointless.
A disruptor cannot be absolved of trolling by it being confirmed that they believe in their own statements; a good many trolls are invested in their message, not just in disruption activity.
> nobody stated that
The put-off person was relating experiences from elsewhere to which you have no access to be able to say that. But in fact, I think I saw very similar remarks in comments under this very HN submission.
Some people are put off by trollish OS/language/editor/hardware/whatever advocacy. And water is wet, and dogs bark.
> how some people are claiming its going to replace vim/nevoim and others by the virtue of its great LSP and tree sitter suppor
That literally means "the outdated shit you're using ain't gonna be here before long, now that we have this", which is trolling even by your definition that incorporates disbelief in one's own statements.
>> Trolling means saying something you don't believe in to start a ruckus/annoy people/make a flame war.
> No it doesn't; please don't make up word semantics to try to make people look wrong. It's childish and pointless.
OK, this conversation doesn't have a point anymore. I make up "word semantics"? What I described is the canonical definition of trolling. Don't believe me? Here are some third party one's:
Cambridge dictionary: the act of leaving an insulting message on the internet in order to annoy someone
Urban dictionary: Trolling – (verb), as it relates to internet, is the deliberate act, (by a Troll – noun or adjective), of making random unsolicited and/or controversial comments on various internet forums with the intent to provoke an emotional knee jerk reaction from unsuspecting readers to engage in a fight or argument
Merriam-Webster: to antagonize (others) online by deliberately posting inflammatory, irrelevant, or offensive comments or other disruptive content
In any case, nobody knowing what a troll is and hiw it's used would consider people saying "this editor as is, and with the aid of LSP/tree-sitter support it has, will gain adoption" fits any definition of a troll.
That's even if we consider people posting stuff they sincerely believe as "trolling". If the intention is not to mock/insult and get a reaction out of those reading the message, it's not trolling.
Those people are just optimistic for some new tech. That's a dime a dozen in HN and tech forums or blogs. At worse they're hyping it (like the Nth "X in Rust"). All of this has nothing to do with trolling
So, I don't know what bizarro definition you have. If you do have one, do share it.
See I am not against newer tools, I am using a lot of newer tools myself like fd/rg. What I am against is claims like "Ths new tool will replace everything else that has been made". Let people decide what works for them and choose accordingly.
I think you are not seeing from the other side, many times the information conveyed for a certain duration is not relevant for some members of the team, instead of always saying i dont want to join this meeting entirely its much easy to only listen the parts that are relevant to you. Using a camera and forcing them to look won't help much here, as they won't be paying attention still.
Vimwiki does supports tags, and allows multiple tags too. I added a request around 2 years ago to add support for custom delimiters for tags which too was added in the dev branch. I have been a happy user of vimwiki for the last 3-4 years and it works great. Use pandoc for conversion to html, has mathjax support for mathematical expressions along with support for mermaid-js too. For searching the notes i have been using leader-f with fzf, fd and rg.
The ability to expand and collapse keys and moving around the sibling keys is great, the help was at the place where I expected it to be, ":h". I love this!
