News for hackers. Stuff that matters.

phrenicfraud

Re:Immutable Data on Monday June 26, 2023 @04:24AM (#36477143)
It seems like all redditors moved here hence the downvotes without elaboration. Well, it's not my problem if you want to keep dreaming, I'll continue living in reality where if I don't want things to change, I simply will not change them, not rely on obscure and irrelevant languages to prevent me from doing so.
Re:XML Is the Future on Monday June 26, 2023 @04:00AM (#36476977)
XML never left us but I don't expect a JavaScript programmer to understand this considering they don't even understand how websites work which is proven by the fact that he uses shitty frameworks reinvented for hundredth time to build bloated, slow and non-XHTML5 compliant dogshit garbage that bogs down modern browsers which compete for accessibility meaning slow and non-XHTML5 compliant dogshit garbage will be supported as valid website.

And yes I just said this, truly valid HTML is parsable with XML parser that does not try to cope with mistakes made by idiots who find it too hard to use a real text editor that is aware of HTML and autocloses tags that need to be closed automatically all by itself. I mean, for those of us who still write HTML by hand... Because reality is that everyone depends on generators who don't do that because apparently we can just cut corners to save bandwidth and let user hardware to deal with the costs of recovering real information from inane garbage that they were given because the rich need to save money and the poor have computers fast enough that this doesn't matter anyway.

Re:Immutable Data on Monday June 26, 2023 @03:42AM (#36476851)
> Immutable data in databases has all the same advantages as immutable data in general purpose languages. It is usually much easier to reason about than mutable state. See: Referential Transparency.

It's only hard to reason about mutable state if you don't understand it and if you don't understand it you have no business touching it. And yes I know, blah blah legacy software cope words words words... Jump the sinking ship because bailing it with a bucket is worthless and find a company where such things aren't allowed.

Now let me clarify, it's not a fault of languages that "allow" mutable state if previous programmer was allowed to build a god object that manages everything in inexplicable ways just like an actual god would. It's a fault of entire company being rotten from all the way to top and using language that "prevents it" (it really doesn't) wouldn't have changed the position you're currently in.

We have these things callied "code reviews" where shit code is simply not allowed to be committed, if your company never used it you're doing what OceanGate just did last week. If you don't get out now you're an idiot.

Re:Linux Namespaces Are a Poor Man's Plan 9 Namespaces on Wednesday June 21, 2023 @06:12AM (#36416647)
If by future you mean "civilization has collapsed and there's noone left alive to use your program and because of that noone will find any faults in my software nor the system I wrote it for and therefore that's good" then I can agree with you, but otherwise you need to stop huffing that copium.

I also don't understand the obsession with static binaries. The only reason to care about that is if you're a proprietary company trying to sell completely opaque snake oil that does everything by itself regardless of system configuration, because my free as in freedom shared objects work just fine for myself and for many other people. There's a good reason why glibc is the defacto standard libc which uses dynamic linking and musl cannot even compete with it, only cope about glibc being superior.

And yeah, sweet golang, the turd that requires you to setup a custom webserver if you want local packages and has complete braindamaged nonsense error handling more verbose than even in C, love it.

As for cross compilation, I'm not sure why you even mentioned it, I guess you don't understand how to setup GCC for this, you know, the compiler collection that supports virtually anything, even possibly your grandma's cardiac pacemaker chip.

Honestly, the more I read this UNIX and other outdated garbage fanboyism, the more braincells I lose. Linux isn't perfect, but at least many people can run servers on it with ease, and ironically enough, people like you usually do not run anything publicly accessible like that at all, because god forbid we started talking about real usability and security.

Re:Linux Namespaces Are a Poor Man's Plan 9 Namespaces on Wednesday June 21, 2023 @05:56AM (#36416537)
All these things you listed are objectively bad and a tumor and I'm glad that those that are gone, are gone for good, because the one that stayed is a menace to any programmer caring about his sanity.
Re:Linux Namespaces Are a Poor Man's Plan 9 Namespaces on Wednesday June 21, 2023 @05:54AM (#36416528)
I remember trying to figure out what's up with Go and left in complete disbelief when I was told that I need to install nginx on my local machine and fake a DNS entry just for go's package manager to "fetch" my local package from my local machine just so I could mess around with it how that works.

All because I couldn't care less about 3rd party services like github.

Re:Linux Namespaces Are a Poor Man's Plan 9 Namespaces on Wednesday June 21, 2023 @05:51AM (#36416488)
And then replies slowly devolve into arguing about irrelevant things that were solved with the existence of Linux because plan9 sucks and Linux is just a kernel which is actually used by people and therefore they actually found ways to solve problems they were most annoyed by.

All these "X is poor man's Y" are a cope. Plan9 is poor man's <insert any operating system that is supposedly inferior to Plan9> because noone uses it. I'm sure on most people the irony of this statement will be lost, so I'm gonna explain: yeah, plan9 is better on paper, too bad we live in glass world.