They could have also contributed to the effort. You can also add types to monaco typescript. I don’t see a need for a Deno specific LSP, am I missing something?
227 karma · joined August 23, 2019
Socials: - x.com/gvkhna
---
They could have also contributed to the effort. You can also add types to monaco typescript. I don’t see a need for a Deno specific LSP, am I missing something?
I’ve done something similar with tippecanoe and mapshaper from gis files. That allowed me to use mapbox.js with my own hosted custom maps, as flat files. Very fast but still needed to run a server (tileserver-gl-light). This could negate that, very cool!
The transistor size is already closing in on 1nm, there will be innovation there eventually, but any step can be a stepping stone. I don’t see the issue here.
Flatbuffers are purely fast read/write by storing buffers that can be mmap’d right into memory. At the cost of some size bloat (slower to transfer over the wire).
Protobufs are a mix of speed but also size over the wire being reduced which does reduce speed of parsing but increases speed transferring over the wire.
I think capnproto is a fantastic project, but considering google is built on top of grpc/protobufs, they will be around for effectively ever which gives it a lot of reliability in my book.
I understand OPs points about ERB it seems to be a wasteland of development. I switched to liquid templates which took a decent bit of effort to implement, but well worth it for shopifys amazing liquid extension/support, which is quite configurable too for custom handlers.
I don’t believe there are any stated limits, they probably have dynamic limits mostly for abuse, but regular/heavy usage will not encounter that.
https://www.crunchydata.com/blog/postgres-full-text-search-a...
I was looking for comparison against a gin index specifically, without it pros/cons unclear.