Wow, that was quite a lot of cryptic build-up. It’s basically a story about conman/drug guy interwoven with biographical information and anecdotes about how this impacted his family.
“You can run,” I guess maybe in the context of “You can run but you can’t hide” is not really touched upon too much. I mean it doesn’t have a particular connection to this story, any more than any other story about a fugitive.
Yup. A big yawn. It seems like it ought to deep and insightful, but is, as you say, "basically a story about conman/drug guy interwoven with biographical information and anecdotes about how this impacted his family". There's no connection between the two parts that goes deeper that "they knew each other once, but did they really know each other?". It'd be Hallmark, but the parents aren't sympathetic enough.
It seems plausible, at least, that the floppy has such a pristine label because the kids didn’t end up using it. Even if I was a kid and into retro games I don’t think I’d care to play my parents’ saves. (Not to say I have any strong belief that this is a non-AI image).
I sort of like the term “early Modern” in history. Putting the “early modern” period 250 years ago causes us to reflect on how much life has changed over that time, which is useful because it’s so tempting to imagine what life was like during the Renaissance or Middle Ages. Of course, every period has massive change, so the experiences of people on either end of a period are as different as somebody in the early modern and… actual modern… eras!
Apparently it fell into the water. Maybe it can be recovered and made into the second coolest rock exhibit in Massachusetts (first is Plymouth Rock obviously).
This time Malcolm X’s line about “Plymouth Rock landed on us” would apply to everyone. And Plymouth Rock is very much not cool. It’s the anticlimax of a million school field trips.
Plymouth Rock is one of the greatest pranks ever played. There‘s so much history in the region—the story of the founding of this massive country—and the capstone is this “world’s largest ball of twine” level attraction. Brilliant.
Executive orders aren’t laws (an important fact that should be repeated often and loudly). However, there’s probably room for the executive branch of the government to influence model hosts, as a major funder and consumer.
I wonder, is the problem here that LSP is updating too slow all the time? Or just that there’s a chance it will update very slow, and you never really know if you’ll hit that chance, so your model always has to do the “long time wait” just in case? It seems like it ought to be possible for LSP to report that it is still processing, in the latter case, somehow…
I'm not an expert, but my reading of the spec is that LSP can handle generic $notifications, but there isn't a specific standard for readiness reporting beyond "Initialize / Initialized", which isn't suitable for monitoring on-going staleness or readiness post-file-detected change, the spec has that as a single first-time initialization.
There are notifications (i.e. `textDocument/didChange` ) that you can send to the LSP to help it along, but again you might end up racing the notification from the client making the change and any file-watchers you might have running.
I suspect the answer will come in the form of some kind of more powerful LSP implementations with generous memory caches so that disk changes are just another buffered input that can be disregarded if already stale, no longer seen as the source of truth, and the LSP becomes the real source of truth, so everything can coordinate through it, operating mostly out of memory.
Another avenue for better success will be more research into faster compilation and better incremental compilation for languages with slower compilation.
Maybe one day we'll even get AI agents directly manipulating syntax trees, and the code to get there being written back as merely a side-effect, but that seems like sci-fi compared to the current state of play. LSP is still very document based, and of course LLMs are also trained on oodles of source.
LSPs only really pro-actively send diagnostics (error/warning/info/suggest[/code action]).
Everything else is responsive; the client asks for symbols in this document, or completion on this line, etc. And if the client is aware of document changes (which are versioned), it should notify of those before requesting new symbols/etc, but that's not difficult.
I don't know that it's mandatory, but I definitely implemented servers so that they would complete processing changed documents before responding to any later requests.
And if it's just the client re-using cached symbols without asking for an update (which should be very fast if nothing has changed); well, that's foolish.
“You can run,” I guess maybe in the context of “You can run but you can’t hide” is not really touched upon too much. I mean it doesn’t have a particular connection to this story, any more than any other story about a fugitive.
reply