Open Source Software Community - it's about ethics in Code of Conducts

[Markass the Worst]

I feel so proud sharing a thread with someone who doesn’t understand that memory-safe is about preventing memory corruption, not preventing crashes.

Please switch to an Etch-A-Sketch and leave me be.

If the goal is to prevent memory corruption, Rust has passed with flying colours. If the goal is to make software that's stable and useful in the real world, that's a different story.

 

[Nitro!]

My condolences sarr. did you redeem

I nearly redeemed a blood vessel.

 

[Goose the Redeemer]

Some problem with the screenshot, or just don't want to acknowledge its contents because it contradicts your performance claim?

I haven't played in some years, but, two of the big performance tanks were generating/loading chunks and having too many entities. You won't see the impact of those if you just screenshot at spawn. You may be right, but your evidence is not good enough.

 

[Kokonut Kangs Klan]

I haven't had a problem with my code crashing since I started doing that.

I'm not a real programmer. I throw together things until it works then I move on. The real programmers will say "Yeah it works but you're leaking memory everywhere. Perhaps we should fix that." I'll just restart Apache every 10 requests.

 

[DavidS877]

Why do you think there's a "MaxConnectionsPerChild" in Apache if they don't want you to use it?

 

[dame dudi jench]

once you include one library, that GPLs your entire project.

The fuck are you talking about?

The position FSF takes about forming a combined GPL work if you include a GPL dll. This is what makes GPL radioactive.

 

[Zeftax]

Not to be rude, but you niggers are drunk.

Well, I am now, but I wasn't when I wrote that. You are talking about 1.21, that's too new for me and it may be so. But I've never seriously played anything newer than maybe 1.4, consider that! Maybe the game got optimized since then, but it was not back then. And it was still fucking awesome because you could do anything you wanted. I have tried to play a few times over the years, and I like that you have a bunch of new blocks (the only thing I really missed back then were miniblocks, which we still don't have, but sure, new blocks are nice) but it feels much more like a "curated" experience. You are to follow the "lore" of the game, not make your own anymore. Not fun. Well anyways, back then I was not old enough to drink so I KNOW that the fucking performance sucked, and spiders were assholes, and we were better for it . Fuck I need to replay ultima underworld as well, THAT was a game.
Still better than the copy of the sims 3 I had pirated, that kept crashing maybe every minute. The sims 4 was the first game I bought with my money and I felt disgusted with buying games ever since.

 

[moocow]

You may be right, but your evidence is not good enough.

Yeah I figured I'd hear something like that. Ah well. Believe what you like.

 

[Zeftax]

Yeah I figured I'd hear something like that. Ah well. Believe what you like.

I know what I played through you faggot. The performance fucking sucked.
Again, maybe they fixed it since, but minecraft definitely contributed to the notion that java is slow.

 

[Consigliere]

The position FSF takes about forming a combined GPL work if you include a GPL dll

Wallahi it means distribution
Your smaller work just gets a GPL positive diagnosis on top of your existing license, not replacing it.

Unless your license is hostile to "additional restrictions" like MPL with the "No secondary licenses" clause, in which case you're free to show these commies what-for.

 

[The Noise]

a language known for being directionless, being incredibly complicated, having painful syntax, being incompatible with random shit for no reason, and having proponents that make everybody sick

It really is only embedded in so much shit because it has a package ecosystem and everybody knows it. It literally survives on brand recognition. AngelScript and Squirrel are far superior as embedded scripting languages.

Late but .unwrap() has the exact same stink as try {...} with an empty catch block.

edit: someone touched on this already, leaving it because I've had to explain this to a gaggle of jeets just today who can't understand it's not a magic stability button, hit me with those clocks fam

Try with empty catch is a symptom of the cancer that is unchecked exceptions in Java. I put it up there with other shitty language features like Zig considering tabs a syntax error and Go considering unused variables an error.

 

[ScooterL]

Why is almost every rust project filled with unwrap?

On Error Resume Next.

Rust is the new Visual Basic.

 

[AmpleApricots]

Visual Basic with it's WYSIWYG GUI creator thingie at least filled a niche.

Every time someone brings up Rust or all these other NuParadigms I'm reminded how much "software engineer" has literally nothing to do with engineering anymore and how many people holding titles like Senior-somethingsomething or Lead-otherandother would, if this was a more civilized time, not be allowed to be anywhere nearer than ten meters to a computer.

There are some old, but very good and elegant languages out there I will not even mention here. You can find them. I believe in you. They can solve any problem you throw at them! I promise. I don't mention them because somebody would come along and go "Well akshually.." and first this isn't the programming language thread and second most programmers today can't separate the tool from the problem making the whole discussion trite from the beginning. If it's not trending on github or all over "Hacker" "News" (or wherever all these programmer socks people are, I don't know, leave me alone), it might as well not exist.

I got pulled out of retirement a bit ago (again!) for a piece of hardware that in it's old design wasn't justifiable anymore cost wise (this actually happens a lot and should worry some people). The new design didn't fit into very specific (and admittedly tight) parameters because at the end of the day, all the high-value software that was heaped on top wasn't really understood by anyone, including yours truly. We worked on it a couple of weeks and came to a very good result and needless to say, it was a lot smaller and simpler than first imagined by all these bright, young minds. So this problem isn't limited to software or FOSS or whatever, it's endemic to the modern world.

We've built industries where understanding is optional, and knowing some framework or language or whatever is mistaken for knowing how things work. The "rust" isn't the problem by itself, it's a symptom of the very mislead belief that you e.g. shouldn't have to understand what your code actually does. AI (which I am not on the anti side of on, not at all) will make things, oh, so much worse because it'll allow people to take so many shortcuts so that they really basically won't know what the machine did. A professor I once knew loved to say that there's nothing wrong with shortcuts, but to be effective, you first have to understand *why* they work. I agree with this sentiment more and more the more time passes.

In reality, the response to problems that arise because people don't really understand how things work, though? Usually more tooling. More linters, more "best practices" docs, more abstraction layers to hide the fact that nobody knows what's underneath. It's like fixing a leaky boat by adding another deck. The young people there I worked with, they're not too stupid to solve the problem, they're just trained wrong. They've been thought knowing specific workflows is knowing everything about the field there is to know, the same way someone might think knowing how to drive means you understand how an engine works.

Real engineering was always about subtraction. Taking away until what remains is so simple it can't possibly fail, and then understanding exactly how it might fail anyway. The modern software engineer and what he does is the antithesis to this.

I once again thank everyone for coming to my TED talk.

 

[mentally retarded user]

For less than the time it takes to compile "rustc", you can write memory safe code in C using the Fil-C compiler, which you will enjoy much more.

 

[HalHalliday]

We worked on it a couple of weeks and came to a very good result and needless to say, it was a lot smaller and simpler than first imagined by all these bright, young minds.

You don't understand, Mr. Apricots.
Things are not that simple anymore, Mr. Apricots.
It's no longer the good old days, Mr. Apricots.
It will take too long, Mr. Apricots.
You are reinventing the wheel, Mr. Apricots.
You can't do it this way, Mr. Apricots.
It won't work, Mr. Apricots.
You are making us look bad, Mr. Apricots.
You are not a team player, Mr. Apricots.

Mr. Apricots.
You are not a good fit for the company's culture, Mr. Apricots.
You are fired, Mr. Apricots.

 

[Creative Username]

For less than the time it takes to compile "rustc", you can write memory safe code in C using the Fil-C compiler, which you will enjoy much more.

or you can use a nice garbage collected language instead (c and its kin are very useful for wringing the last bit of performance out of tight loops or low-level (actually low-level, as in "there is no os and i am using tons of inline assembly" level) shit. people should probably use them less when not actively doing dark magic that explicitly necessitates c usage)
fil-c actually adds a whole garbage collector iirc so you might want to explore some other garbage-collected statically typed languages that interface well with c (go seems to be quite popular here)

You are not a good fit for the company's culture, Mr. Apricots.

sir this is the "open source software community" thread, not the "proprietary software" thread

 

[prollyanotherlurker]

The position FSF takes about forming a combined GPL work if you include a GPL dll. This is what makes GPL radioactive.

The cases where I have seen proprietary programs use gpl components must have been in one of the cases where it works as a distinct program.

That or maybe they used the lgpl.

Either way. I think more gplv3 agpl sounds great.

 

[dame dudi jench]

Wallahi it means distribution
Your smaller work just gets a GPL positive diagnosis on top of your existing license, not replacing it.

You have to give any customer who asks the source code of the combined work, so a competitor or deranged MIT adjunct could buy your GPL'd software and give it away for free, destroying your business overnight. That's how GPL drives away big tech from projects it could be contributing to. This is why RHEL, which is stuck distributing under GPL, does this super aggressive, possibly-not-legal move within the GPL to punish people who do just that.

 

[WhiteNight]

I put it up there with other shitty language features like Zig considering tabs a syntax error and Go considering unused variables an error.

And Zig considering unused variables an error.

 

[Cuckoman]

For less than the time it takes to compile "rustc", you can write memory safe code in C using the Fil-C compiler, which you will enjoy much more.

yepp.
You can still use your tested and very mature codebase and get it to be memory safe by just recompiling your existing, mature, tested, program by just compiling it with fil-c.
It may in rare case require some trivial changes to small parts of your code if are doing something very special, but most of the time you just set it up to build with fil-c and voila, your c program is not memory safe.

No regressions, no missing features, no breaking existing user scripts. It just works. Exactly the same way it always worked.

Only thing I wonder is how many death-treats are the fil-c guy getting from the fucking tranny menace? We all know they are seething and sending him death threats.