Programmers Struggle with Complex Tools
23 posts across 4 communities in the last 60 days; 44% from Hacker News.
“Hmm. I had an issue once with numpy shape mismatch errors appearing after 18+ hours of computation. Frustrating, because it could be caught at compile time.Later, I learned some typelevel programming (in Scala), and by encoding a digital (binary) adder and multiplier at the type…”
“> the situation is very much the opposite when it comes to Rust.It isn't, and the problem isn't Rust specifically, but all low-level languages. They can offer very good performance (often better than Java) when small. But as they evolve over time, or are very large to begin…”
“> Go has null pointer dereference problem.Which Java famously does not have.> Rust is too low-level for typical enterprise app where requirements changes twice a day. You end up spending time and tokens fighting with borrow checker.In my experience, you do not spend tokens…”
Many posts revolve around the challenges developers face when working with complex systems, including Rust's memory management (`std::pin::Pin`), secrets management, SQLite corruption, JVM initialization, and high-level abstractions. There's a general frustration with hidden complexity and a desire for simpler solutions.
SOURCES (46)
“Incidentally, Java seems faster on the server side than Rust in several benchmarks I've seen and tried locally - yes to be taken with a grain of salt, but point being that Rust is not the be-all performance aspiration - there are some really good…”
“Hmm. I had an issue once with numpy shape mismatch errors appearing after 18+ hours of computation. Frustrating, because it could be caught at compile time.Later, I learned some typelevel programming (in Scala), and by encoding a digital (binary) adder and multiplier at the type level, I showed -- at least to myself -- it was possible to compute and check linear algebra shapes at compile time (without a compiler plugin). It was rather magical and funny to think that I just embedded basic digital”
“Valid points, and most high schools do go Python. I will say that Java 26 (which only just dropped, to be fair, has tried to simplify things. Compact classes let you have main written as: void main(){} And you can print with println(). That said, I have been seriously thinking about the switch. My concern is that it would make game and app development classes much harder if I used Python, befause they would have to learn C like syntax on top of tooling. So JS might be the way to go. The only dow”
“> the situation is very much the opposite when it comes to Rust.It isn't, and the problem isn't Rust specifically, but all low-level languages. They can offer very good performance (often better than Java) when small. But as they evolve over time, or are very large to begin with, they become much harder to keep performant. This is for pretty fundamental constraints of low-level language that I mention in another comment here, and this performance problem with large programs written in low-level”
“> Go has null pointer dereference problem.Which Java famously does not have.> Rust is too low-level for typical enterprise app where requirements changes twice a day. You end up spending time and tokens fighting with borrow checker.In my experience, you do not spend tokens fighting with the borrow checker anymore, newer models are smarter. But it might not be ideal for a lot of CRUD applications.> C# is MS product, which is no-go for some folks.This is 2026, it's not 1996 anymore. .Net works on”
“It’s a very good language but you cannot really appreciate why Rust works the way it does without ever having used C/C++ or any systems language before. It’s a direct consequence of all the issues that come with those languages. It also has an incredibly steep learning curve, and is almost entirely populated with developers who already have experience in C/C++ etc and you can the see the same pattern appear in the Rust job market. There are very few Rust jobs in the job market but the ones that”
“On the other hand a lot of companies want to see running code and fluency with your chosen language. I have a hard time imagining someone who needed to be reminded what a std::unordered_map is passing that aspect of it in C++.”
“For me messy code is just an aesthetic headache, but fragile code is a risk. Messy code is just hard to read, but fragile code hides subtle assumptions, race conditions, or multiplier side-effects behind clean-looking abstractions. I hit this exact issue on a build pipeline a few weeks ago. The code looked totally fine, but a subtle loop assumption was quietly firing 12 API calls per build instead of the intended 3. It didn't throw a single error, but it silently burned through API rate limi”
“There is no “fragile” code. There is fragile architecture, as in a dependency for an operation that is prone to race condition”
“Sounds genuinely horrible to program this way.> A Lisp programmer does not need to …Have you even seen R? Jupyter notebooks? The above sounds like a level of insanity beyond that.The problem with checking things at runtime is that it’s an ever-moving target. Changed this? Now that other thing is out of sync. Changed that? Now the first thing is gone, and it came from far away so you can’t get it back in this session.”
So I've been working on a project in Rust because a library that's appropriate for the design has a terrific Rust API and a miserable C API. I've been loosely tracking Rust…
“I can shed some light here! This is going to be longish comment, but hopefully by the end of it you should understand _why_ we decided to avoid using the disk initially, even if you don't agree with that decision.Historically, the decision to not use disk traces back to this comment https://github.com/rust-lang/rfcs/pull/1317#issuecomment-150..., which is perhaps the single GitHub comment that influenced my life most. Very high impact, thanks dgrunwald! Specifically,>Don't store anything to disk”
“> Being a code artisan is not gatekeeping. It means if you're used to being close to the metal and often know better than the compiler, Zig is for you. If you're not, use Rust.You are saying that if you are not a code artisan (who by definition can't use LLM) likeyou then they should not use Zig. Honestly, I don't care. I'm not a code artisan, if Zig can help me ship faster and better with LLMs, my job is done and that's what I get paid for.> Codex CLI taking over 15 minutes to recompile on my f”
“I think problems is too strong a word, it's just how the syntax looks. And of course it's far better than say C++. But specifically, the lack of native vectors/matrices and very few infix operators (e.g dot product, and matrix multiplication with @ is clunky). Explicit but generic broadcasting using `.` also helps.The way that types interact with methods _feels_ like maths. I.e. you have a method made up of mathematical operators, if you swap out an input, it typically does the natural and corre”
“This post advocates rewriting incrementally instead of all at once. Just like Joel said back in 2000, and like everyone continues to always say to this day. Yet in practice, people don't actually do this; complete rewrites in Rust remain far more common than incremental ones, particularly when rewriting from a language other than C. The high-profile exceptions, like Linux, Windows, and Firefox, are codebases so huge and ancient that they obviously cannot be rewritten from scratch. When rewriting”
“Even the title sounds clunky: "Don't stop early", its correct but I think a human would have chosen something else.”
“For decades, Java's object model has powered one of the world's most successful programming languages. But the hardware we run on today looks very different from the world Java was born into in 1995. Modern CPUs are incredibly fast, but memory access, cache locality, and object allocation have become some of the biggest performance challenges in software. Project Valhalla is one of the most ambitious changes in Java's history. It isn't just about making Java faster... it's ab”
“You could say the same thing (at least something similar) regarding binary code produced by a compiler.”
“Pretty cool seeing that people were already thinking about memory safety decades ago. Some of these ideas that feel modern today were being explored back in the 80s and 90s. Makes you wonder how different things would look if languages like Modula-3 had taken off. submitted by /u/FayeTammy [link] [comments]”
“I mean a lot of low level languages can be on safety critical embedded applications.”
“I really don't know my friend y tried go and I allwais ended running a sistem comand with go if rust permit a clearer way I maybe go with it. take a look at go exec lib”