This seems great for code, but can this be used for non-code use cases?
Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete
71–80 of 160 posts
Re: Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete
#72I read the release but didn't quite understand the difference between a next-edit model and a FIM model - does anyone have a clear explanation of when to use one over the other? I'd love if there was a sublime plugin to utilize this model and try it out, might see if I can figure that out.
I’m going to speculate a bit here, FIM may stand for something-in-the-middle?
I know there are the original autocomplete models that simply complete the endings. Then there are Cursor like models capable of editing/filling text between blocks of code. In essence, they look at both the text before the insertion point and after it - then find the best fitting completion in the middle. My guess is FIM is the latter.
Re: Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete
#73Sometimes when I use a plugin like this I get reminded just how much of a productivity nerf it is to code without an autocomplete AI. Honestly in my opinion if you write a lot of boilerplate code this is almost more useful than something like Claude Code, because it turbocharges your own train of thought rather than making you review someone else's, which may not align with your vision. This is a really good plugin.…
Yep. I'm coming to resent Claude Code and tools like it for taking me out of direct contact with the code. I think we're still in the early days of these systems. The models could be capable of a lot more than this "chat log" methodology. Agree about JetBrains dropping the ball. Saddens me because I've also been a diehard user of their products since 2004.
Glad to hear I'm not alone, the latest releases of JetBrains have been so bad I finally cancelled my subscription. VSCode has been a nice surprise, "its giving old emacs" as the kids would say.
Re: Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete
#74I read the release but didn't quite understand the difference between a next-edit model and a FIM model - does anyone have a clear explanation of when to use one over the other? I'd love if there was a sublime plugin to utilize this model and try it out, might see if I can figure that out.
I’m going to speculate a bit here, FIM may stand for something-in-the-middle? I know there are the original autocomplete models that simply complete the endings. Then there are Cursor like models capable of editing/filling text between blocks of code. In essence, they look at both the text before the insertion point and after it - then find the best fitting completion in the middle. My guess is FIM is the latter.
As you said. Fill-in-the-middle.
Re: Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete
#75Sometimes when I use a plugin like this I get reminded just how much of a productivity nerf it is to code without an autocomplete AI. Honestly in my opinion if you write a lot of boilerplate code this is almost more useful than something like Claude Code, because it turbocharges your own train of thought rather than making you review someone else's, which may not align with your vision. This is a really good plugin.…
I have always said this and had people on HN reply that they don't get much use out of autocomplete, which puzzled me.
I'm starting to understand that there are two cultures.
Developers who are mostly writing new code get the most benefit from autocomplete and comparatively less from Claude Code. CC is neat but when it attempts to create something from nothing the code is often low quality and needs substantial work. It's kind of like playing a slot machine. Autocomplete, on the other hand, allows a developer to write the code they were going to write, but faster. It's always a productivity improvement.
Developers who are mostly doing maintenance experience the opposite. If your workflow is mostly based around an issue tracker rather than figma, CC is incredible, autocomplete less so.
Re: Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete
#76Earlier quoted context omitted.
Yep. I'm coming to resent Claude Code and tools like it for taking me out of direct contact with the code. I think we're still in the early days of these systems. The models could be capable of a lot more than this "chat log" methodology. Agree about JetBrains dropping the ball. Saddens me because I've also been a diehard user of their products since 2004.
Glad to hear I'm not alone, the latest releases of JetBrains have been so bad I finally cancelled my subscription. VSCode has been a nice surprise, "its giving old emacs" as the kids would say.
I am curious about how both of you think Jetbrains is dropping the ball so much that you are no longer buying the tool.
You are still using it but no longer getting updates?
Re: Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete
#77Re: Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete
#78It sounds like you might be killing Zed's ability to monetize, am I misunderstanding that?
not really though.
The zed monetization seems to push towards selling tokens for full fledged models with good ide integration as a service. (They have let you run a custom tabcomplete for a little while)
Re: Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete
#79Hey, ollama run as suggested in hf doesn't seem to work with this model. This worked instead: ollama pull hf.co/sweepai/sweep-next-edit-1.5B
I've been using it with the Zed editor and it works quite well! Congrats.
This kind of AI are the ones I like and I'm looking to run in my workstation.
Re: Show HN: Sweep, Open-weights 1.5B model for next-edit autocomplete
#80Hey, ollama run as suggested in hf doesn't seem to work with this model. This worked instead: ollama pull hf.co/sweepai/sweep-next-edit-1.5B
I've been using it with the Zed editor and it works quite well! Congrats. This kind of AI are the ones I like and I'm looking to run in my workstation.
Could you give the gist / config on how you made it work with Zed ?