News for hackers. Stuff that matters.
Re:Log4j: The pain just keeps going by ClumsyPilot on Wednesday July 20, 2022 @12:37PM (#32168310)
because our industry is obsessed with abstractions - the moto is to never fix anything, just pave over it with another abstraction.

for example we didnt fix how we build applocations and manage dependancies, we invented docker.

we didn't create a secure runtime for the cloud where applications can run, instead we virtualised whole operating systems

Re:Log4j: The pain just keeps going by leeoniya on Wednesday July 20, 2022 @12:41PM (#32168372)
> because our industry is obsessed with abstractions

"we do not break userland, period" -- Linus Torvalds

not breaking existing stuff is why many abstractions exist, and even why many are put in place early on, to allow for some wiggle room without having to break all the things. people tend to prefer software that continues to work, above all else.

Re:Log4j: The pain just keeps going by kelnos on Wednesday July 20, 2022 @04:26PM (#32171792)
I think we should acknowledge, though, that not all abstractions are created equal. Abstractions that hide implementation details and allow people to change those implementation details without creating churn and extra work for their downstream consumers are good.

Abstractions that paper over problems that you are unwilling or undisciplined enough to tackle properly are usually bad. I think the grandparent was talking about this kind.

Re:Log4j: The pain just keeps going by leeoniya on Wednesday July 20, 2022 @06:23PM (#32173198)
> Abstractions that paper over problems that you are unwilling or undisciplined enough to tackle properly are usually bad

some abstractions carry decades of legacy (e.g. linux file-system hierarchy), and cannot simply be replaced. things that did not connect to the non-existent internet did not have to paper over problems that simply could not exist at that time (VMs, multi-user, multi-tenant hardware). there is plenty of deep software dependencies that are no longer maintained which still rely on these abstractions and cannot be cheaply/reasonably replaced in the field. sure, we have new abstractions since then, but only new and actively maintained software can ever make use of them, and that will only end up in systems that are also actively maintained instead of simply continuing to work with exactly zero effort.

Re:Log4j: The pain just keeps going by ClumsyPilot on Wednesday July 20, 2022 @12:46PM (#32168453)
but then someone builds a bank on top of this abstraction, and sorts of shit hits the fan.
Re:Log4j: The pain just keeps going by pixl97 on Wednesday July 20, 2022 @03:39PM (#32171074)
Working in the industry I do, there are a number of banks I will never used based on the terrifying lack of quality in the software they write. The SBOM on these projects could be printed out and bound as a dictionary there are so many packages included.
Re:Log4j: The pain just keeps going by leeoniya on Wednesday July 20, 2022 @02:53PM (#32170467)
except, it's turtles all the way down. is POSIX not an abstraction? TCP? C/gcc/llvm? glsl?
Re:Log4j: The pain just keeps going by ActorNightly on Wednesday July 20, 2022 @03:04PM (#32170622)
You are correct, but its not just abstractions, its specifically abstractions on a shitty platform.

The whole log4j thing happened is because java is very poorly designed from the get go, and one of those points is the insistence of making everything an object, including data. And of course, you often need to output the string representation of data.

From a theory perspective, if you want to rely on language features like strong typing to ensure correctness, then you have to take it all the way to full provability, where you explicitly guarantee bounded input, bounded output, and any side effect (where a network call is a side effect, and if your code doesn't explicitly state that this side effect will happen, it won't run).