Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Sublime Text 4

sublimetext.com

Post reply on HN
Print view View original

641–647 of 647 posts

Re: Sublime Text 4

#641

Post by bradstewart »

kwanbix wrote: post #638
artimaeis wrote: post #513

Earlier quoted context omitted.

The same is true of the "column edit" functionality in VS Code. I don't think there's anything that requires the mouse, especially since from the keyboard you can invoke the command window to run any function.

But VS Code is what, 3 or 5 years old? When I was searching for a text editor, this was 20~25 years ago!

For sure. I was more pointing out a feature I find helpful (and one I didn't know about for a while) than trying to "convert" you. Use what works for you!

Re: Sublime Text 4

#642

Post by predragnikolic »

matklad wrote: post #329
ben-schaaf wrote: post #60

Hello HN, I'm one of the developers at Sublime HQ. We're all very excited about this release. If you have any questions you'd like to ask I'll do my best to answer them.

Are there any plans regarding first class support for LSP (or, more generally and perhaps more useful, first class support for extensions providing semantic knowledge about the code)? I know that LSP plugin exists, but, anecdotally, folks are having trouble with it. Which i think is understandable https://lsp.sublimetext.io/features/ says Show Code Actions: UNBOUND, and this is the second most useful thing in LSP (th…

Hello, one of the LSP contributors here.

Just wanted to share my thoughts on why LSP as an open source plugin has more benefits than getting first class support from ST devs.

Cons of getting first class support from ST:

- ST is closed source. That would mean that the LSP source code would be closed source too and that would not allow other people to contribute to it.

- Implementing the LSP client in c++ won't make the user experience faster. The speed mostly depends on the speed a language server returns a response to the LSP client.

- ST devs would shift focus on implementing the LSP spec which is mainly driven by Microsoft and the spec is somewhat driven by VS Code functionality. So ST would chase after offering the same functionality as VS Code, but then always be a step back.

Having LSP as a plugin allows the best for both ST users and ST devs. It allows ST users to contribute to the LSP plugin, while ST devs can focus on making ST more awesome on their own way and adding new API-s.

All I can say is that LSP already has first class support, because the ST devs have specifically expanded the API to allow LSP to implement certain features. :)

Re: Sublime Text 4

#643

Post by predragnikolic »

matklad wrote: post #329
ben-schaaf wrote: post #60

Hello HN, I'm one of the developers at Sublime HQ. We're all very excited about this release. If you have any questions you'd like to ask I'll do my best to answer them.

Are there any plans regarding first class support for LSP (or, more generally and perhaps more useful, first class support for extensions providing semantic knowledge about the code)? I know that LSP plugin exists, but, anecdotally, folks are having trouble with it. Which i think is understandable https://lsp.sublimetext.io/features/ says Show Code Actions: UNBOUND, and this is the second most useful thing in LSP (th…

Let me also give an insight why keybindings are UNBOUND :)

Each person has different criteria of what is important, Some people like code actions, some think it is the goto definition command, but almost all keybinding in LSP are UNBOUND. The main reason is to not cause conflicts with default keybindings.

Here is an example for code actions. Most editors use `ctrl+.` to trigger code actions, but `ctrl+.` is a default ST keybinding used to go to the next modification in the code.

A lot of people consider it bad if a plugin overrides default keybindings, so LSP lets the user decide what keybinding to assign to LSP commands.

Hope the explanation helps.

Re: Sublime Text 4

#644

Post by pupdogg »

naikrovek wrote: post #585
trzeci wrote: post #552

Earlier quoted context omitted.

Hi! I'm struggling with the same problems (Debugging huge ASM.js files). The best modern, non-vim editor to handle such files I've found is Cuda Text: http://uvviewsoft.com/cudatext/ Absolutely top tier lightweight code editor for special tasks.

UltraEdit can open huge files (multiple tens of GB) in seconds. worth a look if you do this a lot.

I concur with trzeci that UltraEdit is by far the slowest in editing large text files compared to the other contenders being discussed here. I was not aware of CudaText before but just gave it a try also and it seems fairly rock solid compared to ST.

Re: Sublime Text 4

#645

Post by qmmmur »

ChrisMarshallNY wrote: post #377
jandrewrogers wrote: post #265

Earlier quoted context omitted.

In practice it doesn't work this way. Saying it is "unsupported" does not mean people will respect that boundary, nor will it prevent people from contacting you expecting your time and attention, which is what actually happens. There is significant overhead to open sourcing software.

This. Even for code I didn't publish (like corporate SDK internals), I have been contacted (which took some work, because my employer did not like customers interacting with Engineering), and told (not "asked" - told ) to make changes to our corporate, closed-source SDK to suit some rando's tinkering around (also, for extra credit, said rando hadn't even purchased one of our cameras). Even open-sourcing has its cavea…

Can't you just ignore them?

Re: Sublime Text 4

#646

Post by andig »

Too late, too little. Please don't get me wrong- I'm saying this with the utmost respect of a long-time paying user. I used to love and recommend ST but then it stalled in development. Have replaced it with VSCode ~3 years ago.

The approach VSCode takes as platform with a clear development and plugin model is imho better suited and what gives VSCode the competitive advantage (apart from MS backing it of course).

What remains is the Sublime keyboard shortcuts that I‘m using even on VSCode.

Re: Sublime Text 4

#647

Post by LAC-Tech »

LAC-Tech wrote: post #204
bigyikes wrote: post #16

I was a Sublime user, then Atom, and now I’m a VS Code user. In 2021, what reasons are there to use Sublime over VS Code? Performance is the only one that comes to mind, but there are surely others... right?

I switched to sublime text because VSCode makes you write /** * Block comments like this */ where as I wanted to write /** Block comments like this */ Seems like a trivial thing but it irritated the hell out of me. I didn't want the editor to put little asterisks in. I didn't ask it to. But it did. Sublime Text just does what I ask.

https://github.com/sublimehq/sublime_text/issues/4320

Ironically, version 4 broke this.

Post reply on HN