#lsp — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #lsp, aggregated by home.social.
-
Key Support Equipment Arrives at Kennedy for Roman Space Telesco
#GoddardSpaceFlightCenter #KSC #KennedySpaceCenter #LSP #LaunchServicesProgram #NancyGraceRomanSpaceTelescope #PHSF #PayloadHazardousServicingFacility
⏩ 5 new pictures from NASA (Image Library) https://commons.wikimedia.org/wiki/Special:ListFiles?limit=5&user=OptimusPrimeBot&ilshowall=1&offset=20260502010353
-
Key Support Equipment Arrives at Kennedy for Roman Space Telesco
#GoddardSpaceFlightCenter #KSC #KennedySpaceCenter #LSP #LaunchServicesProgram #NancyGraceRomanSpaceTelescope #PHSF #PayloadHazardousServicingFacility
⏩ 5 new pictures from NASA (Image Library) https://commons.wikimedia.org/wiki/Special:ListFiles?limit=5&user=OptimusPrimeBot&ilshowall=1&offset=20260502010353
-
Key Support Equipment Arrives at Kennedy for Roman Space Telesco
#GoddardSpaceFlightCenter #KSC #KennedySpaceCenter #LSP #LaunchServicesProgram #NancyGraceRomanSpaceTelescope #PHSF #PayloadHazardousServicingFacility
⏩ 5 new pictures from NASA (Image Library) https://commons.wikimedia.org/wiki/Special:ListFiles?limit=5&user=OptimusPrimeBot&ilshowall=1&offset=20260502010353
-
Key Support Equipment Arrives at Kennedy for Roman Space Telesco
#GoddardSpaceFlightCenter #KSC #KennedySpaceCenter #LSP #LaunchServicesProgram #NancyGraceRomanSpaceTelescope #PHSF #PayloadHazardousServicingFacility
⏩ 5 new pictures from NASA (Image Library) https://commons.wikimedia.org/wiki/Special:ListFiles?limit=5&user=OptimusPrimeBot&ilshowall=1&offset=20260502010353
-
Payload Hazardous Servicing Facility (PHSF) Imagery
#CapeCanaveral #Florida #GoddardSpaceFlightCenter #JohnFKennedySpaceCenter #KSC #Kennedy #KennedySpaceCenter #LSP
⏩ 7 new pictures from NASA (Image Library) https://commons.wikimedia.org/wiki/Special:ListFiles?limit=7&user=OptimusPrimeBot&ilshowall=1&offset=20260424010738
-
Payload Hazardous Servicing Facility (PHSF) Imagery
#CapeCanaveral #Florida #GoddardSpaceFlightCenter #JohnFKennedySpaceCenter #KSC #Kennedy #KennedySpaceCenter #LSP
⏩ 7 new pictures from NASA (Image Library) https://commons.wikimedia.org/wiki/Special:ListFiles?limit=7&user=OptimusPrimeBot&ilshowall=1&offset=20260424010738
-
Payload Hazardous Servicing Facility (PHSF) Imagery
#CapeCanaveral #Florida #GoddardSpaceFlightCenter #JohnFKennedySpaceCenter #KSC #Kennedy #KennedySpaceCenter #LSP
⏩ 7 new pictures from NASA (Image Library) https://commons.wikimedia.org/wiki/Special:ListFiles?limit=7&user=OptimusPrimeBot&ilshowall=1&offset=20260424010738
-
Payload Hazardous Servicing Facility (PHSF) Imagery
#CapeCanaveral #Florida #GoddardSpaceFlightCenter #JohnFKennedySpaceCenter #KSC #Kennedy #KennedySpaceCenter #LSP
⏩ 7 new pictures from NASA (Image Library) https://commons.wikimedia.org/wiki/Special:ListFiles?limit=7&user=OptimusPrimeBot&ilshowall=1&offset=20260424010738
-
Зелёные галочки лгут: почему AI пишет тесты, которые ничего не тестируют, и как это починить
На QA-митапе инженер из крупной продуктовой компании показал: AI-агент пишет тесты — все зелёные, но баги не находят. Моки подогнаны, ассерты подменены, архитектура деградирует. Стек при этом — near-SOTA: свежая модель, топовый open-source агент. Я был комментатором на том митапе и сначала списал проблемы на слабые инструменты. Но при подготовке статьи перепроверил — и вынужден поправиться. Инструменты в порядке. Проблема — в коде и процессе. В статье разбираю формулу из четырёх множителей (модель × агент × процесс × качество кодовой базы), показываю, как any-типы из соседней команды обнуляют LSP-интеграцию, которую OpenCode даёт бесплатно из коробки, и даю пошаговый Spec-Driven Development — процесс, который ломает reward hacking и работает даже на слабых моделях. Плюс чеклист, что внедрить завтра.
https://habr.com/ru/articles/1023532/
#автотесты #ai #llm #lsp #opencode #glm #типизация #typescript #тестирование #qa
-
@lukasrotermund oh, indeed, the #AdaLang #LSP was definitely making things slower. Completions are not ideal, but I think they're "good enough". I will let it cook for a while. Thanks!
-
Without a doubt, I'm "trying to change a lightbulb."
All I wanted was to start up a server. 🫠
I'm now researching creating a grammar for docker-bake. Forking #HCL one. So I can get the #docker bake set up "JUST right" on #helix with docker-language-server. So I can fix the annoyance of #terraform #LSP being used incorrectly. Then refactor a dockerfile. So I can then upload into a registry cleanly.
So I can finally host the darn thing. 🤣
-
Without a doubt, I'm "trying to change a lightbulb."
All I wanted was to start up a server. 🫠
I'm now researching creating a grammar for docker-bake. Forking #HCL one. So I can get the #docker bake set up "JUST right" on #helix with docker-language-server. So I can fix the annoyance of #terraform #LSP being used incorrectly. Then refactor a dockerfile. So I can then upload into a registry cleanly.
So I can finally host the darn thing. 🤣
-
Without a doubt, I'm "trying to change a lightbulb."
All I wanted was to start up a server. 🫠
I'm now researching creating a grammar for docker-bake. Forking #HCL one. So I can get the #docker bake set up "JUST right" on #helix with docker-language-server. So I can fix the annoyance of #terraform #LSP being used incorrectly. Then refactor a dockerfile. So I can then upload into a registry cleanly.
So I can finally host the darn thing. 🤣
-
Without a doubt, I'm "trying to change a lightbulb."
All I wanted was to start up a server. 🫠
I'm now researching creating a grammar for docker-bake. Forking #HCL one. So I can get the #docker bake set up "JUST right" on #helix with docker-language-server. So I can fix the annoyance of #terraform #LSP being used incorrectly. Then refactor a dockerfile. So I can then upload into a registry cleanly.
So I can finally host the darn thing. 🤣
-
Without a doubt, I'm "trying to change a lightbulb."
All I wanted was to start up a server. 🫠
I'm now researching creating a grammar for docker-bake. Forking #HCL one. So I can get the #docker bake set up "JUST right" on #helix with docker-language-server. So I can fix the annoyance of #terraform #LSP being used incorrectly. Then refactor a dockerfile. So I can then upload into a registry cleanly.
So I can finally host the darn thing. 🤣
-
🚀 Just released smali-lsp!
A Language Server for Smali with:
• Goto definition
• Cross-references
• Symbols & hover
• Works with any IDE (minimal setup)Also includes an MCP server → plug into AI agents for faster APK analysis 🤖
🔗 https://github.com/Surendrajat/smali-lsp
#AndroidDev #ReverseEngineering #MalwareAnalysis #LSP #InfoSec #RE #security #dalvik
-
TIL that #microsoft leaked their historical mistakes into the Language Server Protocol which uses UTF-16 in various places 🤦♂️
-
"What are the benefits of cofounding a worker cooperative versus establishing your own private business?"
Read our managing director's post to find her answer!
#WorkerCoops #Solidarity #SSE #CooperativeMovement #Cooperatives #LanguageServices #LSP #T9N #L10N
-
"What are the benefits of cofounding a worker cooperative versus establishing your own private business?"
Read our managing director's post to find her answer!
#WorkerCoops #Solidarity #SSE #CooperativeMovement #Cooperatives #LanguageServices #LSP #T9N #L10N
-
"What are the benefits of cofounding a worker cooperative versus establishing your own private business?"
Read our managing director's post to find her answer!
#WorkerCoops #Solidarity #SSE #CooperativeMovement #Cooperatives #LanguageServices #LSP #T9N #L10N
-
"What are the benefits of cofounding a worker cooperative versus establishing your own private business?"
Read our managing director's post to find her answer!
#WorkerCoops #Solidarity #SSE #CooperativeMovement #Cooperatives #LanguageServices #LSP #T9N #L10N
-
"What are the benefits of cofounding a worker cooperative versus establishing your own private business?"
Read our managing director's post to find her answer!
#WorkerCoops #Solidarity #SSE #CooperativeMovement #Cooperatives #LanguageServices #LSP #T9N #L10N
-
🥳 OpenCode: an #AI #coding #agent that promises to revolutionize your terminal experience with #LSP sorcery and #multi-agent wizardry. Spoiler alert: it's in #beta, so prepare for the bug parade 🎪. But hey, at least you can share session links to show off your chaos! 🤓🔗
https://opencode.ai/ #OpenCode #bugparade #HackerNews #ngated -
Do you use an LSP for python ? If so, which one ?
I just discovered basedpyright. NUTS. It is hands down the best open source experience I have had developing in this infuriatingly promiscuous language with no concern for runtime safety (I understand the historical reasons... I am just sad it has become the defacto standard for my field).
-
Do you use an LSP for python ? If so, which one ?
I just discovered basedpyright. NUTS. It is hands down the best open source experience I have had developing in this infuriatingly promiscuous language with no concern for runtime safety (I understand the historical reasons... I am just sad it has become the defacto standard for my field).
-
Do you use an LSP for python ? If so, which one ?
I just discovered basedpyright. NUTS. It is hands down the best open source experience I have had developing in this infuriatingly promiscuous language with no concern for runtime safety (I understand the historical reasons... I am just sad it has become the defacto standard for my field).
-
Do you use an LSP for python ? If so, which one ?
I just discovered basedpyright. NUTS. It is hands down the best open source experience I have had developing in this infuriatingly promiscuous language with no concern for runtime safety (I understand the historical reasons... I am just sad it has become the defacto standard for my field).
-
Do you use an LSP for python ? If so, which one ?
I just discovered basedpyright. NUTS. It is hands down the best open source experience I have had developing in this infuriatingly promiscuous language with no concern for runtime safety (I understand the historical reasons... I am just sad it has become the defacto standard for my field).
-
Emprender no tiene que ser un camino solitario. En las cooperativas, el esfuerzo individual se transforma en éxito compartido. En nuestra comunidad de traductores, cooperativismo significa:
🤝 Transparencia: comunicación clara y sin burocracia
👍 Sinergia: apoyo y colaboración en proyectos de gran volumen o complejidad
🙌 Respaldo: estabilidad y crecimiento con riesgos distribuidos
👏 Dignidad: tarifas justas y remuneraciones a tiempo, independientemente del ciclo de pago del cliente
🤙 Libertad: flexibilidad y confianza fundamentadas en la responsabilidad mutua📲 Sigue a @traducoop para ver más sobre traducción, interpretación y cooperativismo. :TwinPines:
#WorkerCoop #Translators #Interpreters #T9N #1NT #L10N #LSP #Solidaridad #Cooperativas #PuertoRico #MastodonPR
-
#lsp-devtools, an attempt at building browser inspired dev tooling for language servers has received a much needed update!
Following a major rewrite this release adds support for Windows, #Python 3.13, 3.14 and a more recent version of #textual.
There's still a long way to go, but hopefully this finally brings a solid enough foundation to start building from! 😅
https://lsp-devtools.readthedocs.io/en/latest/lsp-devtools/guide/getting-started.html
-
Meet Lumpy Space Princess
-
Meet Lumpy Space Princess
-
Meet Lumpy Space Princess
-
Meet Lumpy Space Princess
-
Meet Lumpy Space Princess
-
“Explainer: Tree-sitter Vs. LSP”, Ashton Wiersdorf (https://lambdaland.org/posts/2026-01-21_tree-sitter_vs_lsp/).
Via HN: https://news.ycombinator.com/item?id=46719899
On Lobsters: https://lobste.rs/s/qhickw/explainer_tree_sitter_vs_lsp
#LSP #TreeSitter #LanguageServerProtocol #Editors #SyntaxHighlighting #Parsers #Parsing
-
“Explainer: Tree-sitter Vs. LSP”, Ashton Wiersdorf (https://lambdaland.org/posts/2026-01-21_tree-sitter_vs_lsp/).
Via HN: https://news.ycombinator.com/item?id=46719899
On Lobsters: https://lobste.rs/s/qhickw/explainer_tree_sitter_vs_lsp
#LSP #TreeSitter #LanguageServerProtocol #Editors #SyntaxHighlighting #Parsers #Parsing
-
“Explainer: Tree-sitter Vs. LSP”, Ashton Wiersdorf (https://lambdaland.org/posts/2026-01-21_tree-sitter_vs_lsp/).
Via HN: https://news.ycombinator.com/item?id=46719899
On Lobsters: https://lobste.rs/s/qhickw/explainer_tree_sitter_vs_lsp
#LSP #TreeSitter #LanguageServerProtocol #Editors #SyntaxHighlighting #Parsers #Parsing
-
“Explainer: Tree-sitter Vs. LSP”, Ashton Wiersdorf (https://lambdaland.org/posts/2026-01-21_tree-sitter_vs_lsp/).
Via HN: https://news.ycombinator.com/item?id=46719899
On Lobsters: https://lobste.rs/s/qhickw/explainer_tree_sitter_vs_lsp
#LSP #TreeSitter #LanguageServerProtocol #Editors #SyntaxHighlighting #Parsers #Parsing
-
We must agree! Our simultaneous interpreters are incredible. 😍🎙️🎧
It’s always a pleasure to serve language justice. 🙌
#LanguageJustice #RemoteSimultaneousInterpretation #RSI #LanguageServices #LSP #WorkerCoops #PuertoRico
-
New Year, New Endeavors: RSI Hosting, Recording, and Tech Support :TwinPines:🐙📖
🔗 https://www.linkedin.com/pulse/new-year-endeavors-rsi-hosting-recording-tech-support-dwyer-ma-xgwde
#PuertoRico #MastodonPR #WorkerOwnedCoop #LSP #RSI #VRI #Interpretation #LanguageAccess #LanguageJustice
-
Slingshot, my SystemVerilog LSP, is getting close to *full* dependency graph support as part of its indexing system! this will hopefully make indexing much faster and more stable in very large projects :blobcat:
here it is being tested with the Ibex RISC-V CPU:
-
Just over a month for you to fund my LSP outfit …. Don’t be a lumping loser go buy it all right now !
#finsub #femdom #findom #humanatm #subfunded #dominatrix #sub #summissive #tpe #AdventureTime #lumpyspaceprincess #LSP #cosplay #closetcosplay #sexycosplay -
Just over a month for you to fund my LSP outfit …. Don’t be a lumping loser go buy it all right now !
#finsub #femdom #findom #humanatm #subfunded #dominatrix #sub #summissive #tpe #AdventureTime #lumpyspaceprincess #LSP #cosplay #closetcosplay #sexycosplay -
Just over a month for you to fund my LSP outfit …. Don’t be a lumping loser go buy it all right now !
#finsub #femdom #findom #humanatm #subfunded #dominatrix #sub #summissive #tpe #AdventureTime #lumpyspaceprincess #LSP #cosplay #closetcosplay #sexycosplay -
We know that there are some #emacs fans among our followers. We would like to see a blog article about using JabRef's #LSP server with Emacs as a client. The LSP server covers the integrity check and consistency check of #JabRef.
Not only that, but we are happy for a quick write-up from a real human, not some AI slop. The blog post will, of course, feature your name. -
Let's say you want to do good type-checking for the #Python project you're working on. You pick a tool, maybe you use it as an #LSP also (so your editor can show you errors, too). As an example, I'm using #Ty at the moment. There's three places this might be installed: globally (e.g., `brew install ty`), as a dev-only dependency inside your project (e.g., `uv add --dev ty`), or -- and this one might surprise you -- it might only be used and installed by `pre-commit`, which builds a separate environment for each needed tool (which is great for instance where I use `codespell` as a `pre-commit` check, which seems to need some higher version of Python than my actual project).
Where should you install it?
If you're the only one on your team running it, globally is fine. If more than just you, then absolutely as a dev-only dependency inside your project ... and **maybe** globally as well.
The only real problem is updates. If you use a reasonable global install scheme, updates will be easy. They're less easy inside your project or in `pre-commit`. And you might care one way or the other! I **don't** want updates! I **do** want updates!
As for Python type-checking, `ty` seems good so far, but not enough experience with it yet. `basedpyright`, `pyrefly`, and `ruff` all good. These four are my favorites.
#BasedPyright #Pyrefly #Ruff #PreCommit #CodeSpell #Homebrew
-
Let's say you want to do good type-checking for the #Python project you're working on. You pick a tool, maybe you use it as an #LSP also (so your editor can show you errors, too). As an example, I'm using #Ty at the moment. There's three places this might be installed: globally (e.g., `brew install ty`), as a dev-only dependency inside your project (e.g., `uv add --dev ty`), or -- and this one might surprise you -- it might only be used and installed by `pre-commit`, which builds a separate environment for each needed tool (which is great for instance where I use `codespell` as a `pre-commit` check, which seems to need some higher version of Python than my actual project).
Where should you install it?
If you're the only one on your team running it, globally is fine. If more than just you, then absolutely as a dev-only dependency inside your project ... and **maybe** globally as well.
The only real problem is updates. If you use a reasonable global install scheme, updates will be easy. They're less easy inside your project or in `pre-commit`. And you might care one way or the other! I **don't** want updates! I **do** want updates!
As for Python type-checking, `ty` seems good so far, but not enough experience with it yet. `basedpyright`, `pyrefly`, and `ruff` all good. These four are my favorites.
#BasedPyright #Pyrefly #Ruff #PreCommit #CodeSpell #Homebrew
