News for hackers. Stuff that matters.

nwjsmith

nwjsmith on Hacker News

Re:Static Allocation, Constant Work on Thursday September 03, 2026 @04:58PM (#49556888)
It’s (mostly) not about performance, it’s about minimizing failure. Static memory allocation makes you OOM-proof.
Re:Grammarly acquires Superhuman on Tuesday July 01, 2025 @10:45AM (#44434398)
Harper checks a lot of your boxes and is getting better all the time: https://writewithharper.com/
Re:Deno Cron on Wednesday November 29, 2023 @01:28PM (#38463142)
Is the spikiness of cron schedules going to cause you operational problems? You're going to end up with a _lot_ of jobs scheduled at "0 0 * * *".
Re:OpenSSL 3.0 released; relicensed to Apache-2.0 on Monday September 20, 2021 @06:17PM (#28599759)
Google employ at least one OpenSSL committer and have their own simpler version of the library, BoringSSL.
Re:Socat – A utility for data transfer between two addresses (2018) on Saturday March 27, 2021 @09:28AM (#26602145)
Have you happened to blog about this? I'd love to be able to fix our setups with this trick!
Re:Sequoia PGP 1.0 Released: The Seedling Is a Sapling on Wednesday December 16, 2020 @07:12PM (#25450593)
Is it possible to use Sequoia to sign Git commits?
Re:A Case for Clojure and GraphQL: Replacing Django on Saturday October 14, 2017 @09:17PM (#15475313)
That is not interesting. If you are making the point that the rate of Clojure job growth is declining, it could be a data point in support of that hypothesis.

What do you think Clojure's absence from zdnet's list indicates?

Re:A Case for Clojure and GraphQL: Replacing Django on Saturday October 14, 2017 @05:36PM (#15474447)
> I more often than not suggest moving from Clojure to anything else.

Rewrites are notoriously risky projects, I'm surprised you suggest this the majority of the time.

> you have to trust that the original programmers actually know the language enough to not create a massive disaster

This is my experience, but I've come across many coding disasters and none have been caused by misunderstanding the programming language. All have been due to poor software design or testing.

> Once this happens, you end up in a read-only code situation, and this is a problem because they leave the project with tons of bugs and downright stupid decisions.

Why have you pinned the blame on Clojure? What are the properties of Clojure that cause programs written in it to have so many bugs? Programming languages don't make decisions, let alone stupid ones.

> I joke that I know all 50 Clojure programmers in the US, and sadly, that's not much of an overstatement

This is a massive overstatement. Netflix, Apple, Soundcloud, and Walmart are all using Clojure. I work on a large team of Clojure developers, many of whom are located in the US. The Clojure community is large, healthy and growing. This is not an "esoteric" language.

> If you aren't located in SF, LA, or some other city that attracts talent

I work with Clojure developers all over the world, many in small towns in their respective country. My address hasn't been a factor for any tooling decision I've been a part of, it's a strange (overlooked?) criteria by which to judge technology.

Re:Fourteen Months with Clojure on Friday March 31, 2017 @02:39PM (#14006726)
I couldn't be happier with vim-fireplace, vim-sexp, and vim-sexp-mappings-for-regular-people. What about vim-fireplace is frustrating for you?
Re:The Personal Software Process (2000) [pdf] on Thursday May 12, 2016 @08:38PM (#11687839)
I'm interested to know if anyone here has used this over an extended period of time. Does it work for you? Have you become better at estimating? Have you lowered your defect rate? Have you increased your pace?

I'm skeptical that something this prescriptive could be effective, but it'd be great if there was evidence (anecdotal or a study) that shows this is effective.

Older »