frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

Show HN: Scots-Codes

https://github.com/vanyakosmos/scots-codes
1•aiven•2m ago•0 comments

Android phone and desktop mode on your Mac

https://github.com/lucianmarin/macdroid
3•lucianmarin•2m ago•0 comments

House China Cmte: China Trying to Get US Companies Addicted to Chinese AI Models

https://chinaselectcommittee.house.gov/media/reports/joint-investigation-report-china-is-trying-t...
1•diskmuncher•3m ago•1 comments

Where in the world is the weather unusual?

https://www.wxtravel.io/?view=latest-events
1•greatsnakes•3m ago•1 comments

Show HN: Daybranch – Is this client request in scope?

https://www.daybranch.com/
1•brunohenriquede•3m ago•0 comments

Language Model Harnesses Can Be Compositional Generalizers

https://www.alphaxiv.org/abs/2611.harness-cg
1•matt_d•4m ago•0 comments

Responsibility Is Taken Before It Is Given

https://lalitm.com/responsibility-is-taken-before-it-is-given/
1•fagnerbrack•5m ago•0 comments

What are the implications of a proof of the Riemann Hypothesis?

https://herecomesthemoon.net/2026/11/implications-of-riemann-hypothesis/
1•Mond_•5m ago•0 comments

I think we can have a market for (Explaining as a Service) EaaS

1•pfx14•8m ago•0 comments

Riemann Hypothesis Catastrophe

https://www.lesswrong.com/w/riemann-hypothesis-catastrophe
1•dnw•10m ago•0 comments

A taste of formal verification for PyTorch (PTX semantics, weak memory models) [video]

https://www.youtube.com/watch?v=bs7UEh4HgnA
1•matt_d•11m ago•0 comments

Show HN: Run coding agents with your whole team

https://www.pangea.build/
1•hasos•12m ago•0 comments

The Case for Urban Bathrooms

https://pharker.substack.com/p/the-case-for-urban-bathhouses
1•paulpauper•16m ago•0 comments

Strategies for Being Someone Else

https://hotfemoid.substack.com/p/strategies-for-being-someone-else
1•paulpauper•17m ago•0 comments

Elixir HLS makes FPGA circuits from functions written in Elixir

https://github.com/elixir-hls/elixir-hls
1•kristianpaul•18m ago•0 comments

Watching travel advice maps change

https://jamesst.one/posts/travel-advice-maps/
2•wmchen•21m ago•0 comments

Show HN: A written proof of the Lean proof of the Riemann Hypothesis

https://github.com/tamnd/riemann
1•tamnd•24m ago•0 comments

Twin films are films with the same or similar plots released with a short time

https://en.wikipedia.org/wiki/Twin_films
2•jjmarr•24m ago•0 comments

Handmade Businesses

https://brentfitzgerald.com/posts/handmade-businesses/
2•burnto•28m ago•0 comments

Lean (Proof Assistant)

https://en.wikipedia.org/wiki/Lean_(proof_assistant)
1•doener•31m ago•0 comments

I Don't Trust Visual Recordings Anymore. But One Day I Will Again

https://spectrum.ieee.org/fighting-back-against-deep-fakes
1•jnord•33m ago•0 comments

A Hack Is Not Enough

https://blog.giovanh.com/blog/2025/10/14/a-hack-is-not-enough/
1•fedpost•35m ago•0 comments

A push for a treaty to not allow AI total control over nukes

https://theelders.org/news/humanity-threshold-declaration-artificial-intelligence-and-nuclear-wea...
1•illidan1000•35m ago•0 comments

If AI found better drugs for every disease, what would it cost to prove it?

https://cvigoe.github.io/website/ai-cures/
1•cvigoe•36m ago•0 comments

Watch How the Office Became the Worst Place to Do Work [video]

https://www.wsj.com/tech/personal-tech/watch-how-the-office-became-the-worst-place-to-actually-do...
3•erickhill•45m ago•1 comments

Anatomia Di Tor – The Tor Protocol, Byte by Byte

https://github.com/aleff-github/onion-routing-anatomy
2•aleff•46m ago•0 comments

XiangShan Tapeout History

https://docs.xiangshan.cc/zh-cn/latest/tapeout/
1•camel-cdr•46m ago•0 comments

A New Shape for Work

https://www.notion.com/a-new-shape-for-work
2•pikdum•50m ago•0 comments

Making torch_remat work in TorchTitan

https://docs.pytorch.org/devlogs/distributed/2026-11-19-torch-remat-in-torchtitan/
1•matt_d•54m ago•0 comments

Forensic dissection of Roland J-6's 64 presets: measuring the hidden settings

https://github.com/liotier/RolandStuff/blob/main/J-6_presets_measurement/README.md
1•liotier•59m ago•0 comments
Open in hackernews

LSP client in Clojure in 200 lines of code

https://vlaaad.github.io/lsp-client-in-200-lines-of-code
164•vlaaad•1y ago

Comments

whalesalad•1y ago
This is the most Java-y Clojure I’ve probably ever read. Just use Java? It’s so verbose and complex for what it is doing. Breaking this down into smaller functions and using core.async would make it even more succinct.

Just want to emphasize this because clojure is indeed a small, lesser known language that has a hard enough time attracting users. This is not what anyone would consider an idiomatic example of using clojure.

roenxi•1y ago
Would it be 200 lines of Java? It'd be 200 lines of just for the boilerplate. It isn't really a selling point of Clojure because it is subjective, but low-syntax high-terseness look of the code is in itself a reward for using the language.

And there isn't anything especially wrong with sticking to Java primitives if someone is comfortable with them. They work fine for Java programmers. The dude doesn't need to learn a new async library to write an LSP client if he doesn't feel like it. Code works, its easy to read, easy to understand and modify.

koito17•1y ago
Line count is not very useful to compare without the context of standard library size, third-party dependencies, etc. The code in TFA depends[1] on a JSON library[2] that is about a thousand lines of code (excluding tests) wrapping a Java library for JSON decoding.

Then there's other things to consider, like the fact that this LSP client, while succinct, pays not only the cost of loading Jackson, but also the cost of loading clojure.core, which is quite non-trivial[3]. Startup time for LSP servers and clients definitely matters to some, considering that e.g. even clojure-lsp recommends running native executables over JAR files[4]. Can't find documentation proving it's for quick startup, but it's a plausible rationale for their recommendation of a binary over a JAR.

Note: I have used Clojure professionally and in hobby projects. I think it's nice that one can interactively develop a minimal LSP client and the resulting amount of work is roughly 200 lines of code. I say "minimal" because it's unclear how this client deals with offsets reported by LSP servers, which are all given as offsets in a UTF-16 encoded string. In any case, I still think advertising "LSP client in 200 lines of code" hides valuable information regarding functionality, implementation, "actual" code size, and trade-offs made in the choice of technology stack.

[1] https://github.com/vlaaad/lsp-clj-client/blob/a567e66/deps.e...

[2] https://github.com/metosin/jsonista/blob/c8f2b62/project.clj...

[3] https://clojure-goes-fast.com/blog/clojures-slow-start/#cloj...

[4] https://clojure-lsp.io/installation/#embedded-jar-legacy-exe...

pron•1y ago
Between records and compact classes [1] Java's boilerplate isn't what it once was.

[1]: https://openjdk.org/jeps/512

newlisp•1y ago
It's idiomatic "low-level" Clojure, though. Not everything is a happy place where you're just manipulating maps and vectors like in most examples.
0x1ceb00da•1y ago
> lesser known language that has a hard enough time attracting users

For very good reasons.

dig1•1y ago
I don't see why this wouldn't be considered idiomatic clojure code; it makes proper use of all the facilities provided by the language and the main intention of this code is to follow the article. Additionally, the clojure core team often encourages not to shy away from using java code directly, as this approach strikes a good balance between performance and language expressivity.

> It’s so verbose and complex for what it is doing. ... and using core.async

I think this code is actually quite straightforward and easy for a clojure developer to understand. In fact, using core.async in this case would be overkill and could complicate things further.

daveliepmann•1y ago
This looks like the other completely normal, idiomatic Clojure programs I've seen which manipulate a StringBuilder. And as Clojurians go I'm far to the succinctness/concision-preferring end of the spectrum.

I'm curious to see your core.async-based version :)

askonomm•1y ago
Holy crap is this unreadable or what (notably the lsp-base fn). There's a reason why in most Clojure companies I've worked at we try to make as small functions as possible, because otherwise it very very quickly becomes an unreadable mess, and you write code after all for humans to read, because if you didn't, you might as well just write binary. But, I'm not surprised many people don't want to get into Clojure or Lisps in general, because it takes a boatload of conventions and active discipline to make it a good experience.
slifin•1y ago
To me something unreadable is code that I cannot statically make any assertions about the runtime behaviour of the code

This function you're complaining about looks like 2 virtual threads doing program input reading and output writing for the LSP client given some ArrayBlockingQueues in about 25-30 lines

If I wanted the complete story I could use Clojure's inbuilt test runner to slip some ArrayBlockingQueues in there and run it under record with Flowstorm

Then leisurely seek through the entire state of the program, to get the play-by-play of how this works

There are so many good design choices in this language and a good 30% of colleagues I run into are not even doing the basics of like running a REPL, I think some people just need to clock in with a decade of C# or PHP or TS or JS or Python or whatever to get a taste of a language with next to no inbuilt immutability, statements instead of expressions, no reload-ability in the language semantics and just crapshot debuggers that run in lockstep with the program execution