> On May 7, 2020, at 9:11 PM, Michael Van Canneyt
> wrote:
>
> At least partial updates to a file should be there.
> Sending the whole file at essentially every few keystrokes is just
> braindead...
>
That's still happening but it's Sublime Texts fault for a bad API. It is fixed
in the cur
Am 2020-05-07 15:26, schrieb Ryan Joseph via fpc-pascal:
The amount of redundant information being sent around is ridiculous.
Mainly, the spec gives no way for the client to cache results and
refer to them later in various requests. We're literally sending
around mega bytes of data for no reason
On Thu, 7 May 2020, Ryan Joseph via fpc-pascal wrote:
On May 7, 2020, at 4:44 PM, Michael Van Canneyt wrote:
I'm not even sure BSON will be accepted for LSP.
I talked to them already and they're not keen to add extensions to the
plugin so I'll probably give up on this route. The spec f
> On May 7, 2020, at 4:44 PM, Michael Van Canneyt
> wrote:
>
> I'm not even sure BSON will be accepted for LSP.
I talked to them already and they're not keen to add extensions to the plugin
so I'll probably give up on this route. The spec from Microsoft doesn't say
anything about this eithe
On Thu, 7 May 2020, Andreas Schneider wrote:
Am 2020-05-07 08:40, schrieb Ryan Joseph via fpc-pascal:
Working on the language server it's become clear that JSON is going to
be a killer bottleneck, but that's what Microsoft decided to use. It's
almost a deal breaker just because of the sheer s
Am 2020-05-07 08:40, schrieb Ryan Joseph via fpc-pascal:
Working on the language server it's become clear that JSON is going to
be a killer bottleneck, but that's what Microsoft decided to use. It's
almost a deal breaker just because of the sheer size of the data due
to JSON's verbose plain text
On Thu, 7 May 2020, Ryan Joseph via fpc-pascal wrote:
Working on the language server it's become clear that JSON is going to be a
killer bottleneck, but that's what Microsoft decided to use. It's almost a deal
breaker just because of the sheer size of the data due to JSON's verbose plain
te
Working on the language server it's become clear that JSON is going to be a
killer bottleneck, but that's what Microsoft decided to use. It's almost a deal
breaker just because of the sheer size of the data due to JSON's verbose plain
text formatting.
I've seen there is such thing as BSON (http
