CNILES WILL SEETHE
Falling into your wing while paragliding is called 'gift wrapping' and turns you into a dirt torpedo pic.twitter.com/oQFKsVISkI
— Mental Videos (@MentalVids) March 15, 2023
Falling into your wing while paragliding is called 'gift wrapping' and turns you into a dirt torpedo pic.twitter.com/oQFKsVISkI
— Mental Videos (@MentalVids) March 15, 2023
5 estradiol tablets have been deposited
*adderal but close enough
>can't use OpenGL without wrapping all of your code in unsafe{}
>the one "safe" OpenGL wrapper library causes Rust compiler to stack overflow
>the supposed solution is to learn wgpu instead
Fuck this useless toy language and webshit-tier community
>falling for the opengl meme
Elaborate
Just use something built on top of Vulkan already
No I'm not learning your questionably maintained flavor-of-the-month framework libraryshit game-engine
then build your own using Vulkan 🙂
I already have, with C
But I'm not rewriting 20k+ lines just to test out if it works well in r*st
wgpu isn't any of these things except a library. Which is irrelevant.
>Vulkan is a flavor of the month framework libraryshit game-engine
THE ABSOLUTE STATE OF LULZ
lol retarded mods wiped all my posts as collateral from a different thread, let me repost my point
With
>Just use something built on top of Vulkan already
he did not mean to use Vulkan directly like you assume, as is obvious if you actually understand English. Learn to read before posting.
>cnile
>doesn't know what vulkan is
Why do nocoders worship C?
the problem is you're targeting a GRAPHics application and Rust is allergic to linked lists and other sane ways or representing GRAPHs like adjacency lists (you'd have to be a retard to use a matrix for sufficiently sparsely connected graphs - ie most graphs).
It all adds up.
>t. brainlet filtered by simple google search
https://doc.rust-lang.org/std/collections/struct.LinkedList.html
there is no behavior in an adjacency list what would ever trip up the borrow checker jesse what the fuck are you on about?
>doesn't understand how unsafe works
>>the supposed solution is to learn wgpu instead
>wgpu is only usable since 2020
>thinks Vulkan is "questionably maintained flavor-of-the-month framework libraryshit game-engine"
>supposedly wrote 20k+ loc C
Are all C programmers LARPers or is he a special case?
Please read the post chain before posting.
>Just use something built on top of Vulkan already
Does not say "use Vulkan".
So
>thinks Vulkan is "questionably maintained flavor-of-the-month framework libraryshit game-engine"
Is a blatant lie about my statements.
99% of them on LULZ, yeah. IRL is a bit different.
>>can't use OpenGL without wrapping all of your code in unsafe{}
Still don't understand how this is an argument. The only reason why you'd consider having to use unsafe as a negative is if you thought using raw pointers too much was generally bad, i.e. if you were a rustfag in the first place.
If you're a C worshipper you should be able to have your entire program wrapped in unsafe {} and not even register that as a negative.
With Rust you can not interface with industry standard libraries without hideous amounts of clutter, unnecessary indentation, and invalidating basically the whole point of the language. I don't see how you're supposed to use this language in the real world currently. It's a hobby language for tinkerers.
It would be a different situation if there'd be a no-bullshit first-party wrapper/library for it, like they did for WebGL
>hideous amounts of clutter, unnecessary indentation
This isn't python. Using unsafe is literally 2 extra lines, there's really no reason to make such a big deal out of it.
>invalidating basically the whole point of the language.
Rust is just a normal language that works, the memory safety is just one feature it has. For many people including me, sum types and a standardized build system that just works is more than enough to justify using it even if it wasn't for the memory safety.
But if the memory safety is that crucial to you that you're losing your mind over having to use unsafe a couple of times, then surely you'll appreciate the fact that you can use it for the all your remaining non-rendering code.
Besides, using openGL is cancer on C as well. Just think of how many bullshit helper libraries people use, GLEW, GLFW, etc. Not to mention that the design just sucks in general, with global mutable state out of the ass. Having to use unsafe is really the least of your problems when it comes to hideous clutter.
>can't use OpenGL without wrapping all of your code in unsafe{}
Then wrap your rendering code in unsafe and stop being a bitch.
The Tranny* Programming Language
FIXED IT FOR YOU OP.
>It still does not surpass C and C++ in execution speed and memory efficiency
Did you know Java is atleast as fast or faster than C in memory management in all cases?
>memory management
memory management is not the same as memory efficiency
This is false
>EpsilonGC: 0 ops
>C 0 ops or more
Can't really get lower than that
It's very easy to write a malloc like that, and then you get to win by making fewer allocations in the first place
Goddamn, Julia is looking good.
yeah, i love waiting 30+ seconds for my julia code to compile if i try to do any kind of data viz
>C# beating Ada.
>Haskell almost as fast as Ada.
Military sisters, what do we do now?
Turns out having a robust language with lots of runtime checks to ensure safety has its consequences. Ada is hamstrung by a committee like C & C++. A lot of nice compiler-time checks that could be done were never added to it and Ada is very much a "don't break old shit" so it likely never will get nice things that matter since most companies using it won't go beyond Ada 95
makes sense why adacore is moving to support rust
I spent a year with Ada, and while some of type features are pretty cool (especially building arrays with arbitrary index types), and generics work well (if not too verbosely) it's really let down by the IO system. I found myself building custom parsers for most things rather than relying on default libraries. After a while, you start to question your priorities when you're reading textbooks on string algorithms. I'll probably "transition" to Rust to see what all the fuss is about.
show me a project you built with rust
you wont
nocoder retard
sage hide
Average Pust user
We already have this, it's called gregtech and it's written in java 🙂
Very basic question because have never used rust.
Can you make hello world with just using a notepad app and one command? Or is it bloated like java?
Yes you can. Java is really the only language that's near impossible to write without IDE's. You can write Kotlin free of IDEs too btw
Ceethe and dilate
Rustsissies? How will we ever recover?
Recover from internal linter used by compiler developers for rustc codebase?
no recover from chopping your dick off
Absolutely pathetic i can hear you cry from here.
>It's okay if the developers of the language are deranged trannies
How much copium are you on, sisters?
>0 reading comprehension
You will never be a 0xCAFEBABE. Rust coders will always be 0xFATD00D5. 0xC09E. 0x5EEDFEED.
>T
?
>0xFATD00D5
I meant to say 0xFA7D00D5. I have been exposed. Humiliated. Shamed. I have failed. I will never hexspeak again. I will never 1337speak again. I will never post here again because the weight of my disgrace is unbearable. Forgive me.
🙁
Nocoder.
whats a better alternative to C?
iv been checking several meme languages but im not convinced yet.
>hare, vale, val, lobster, zig, restricted c++
can someone meme me out?
rust
>not a meme
C++
>partially meme but promising
Zig
>meme that will never take off
Hare
Vale
Val
Lobster
Ada
There's no reason not to upgrade to sepples unless you're just bad at learning.
>serious tier
C, C++
>medium tier
Zig - early but promising
Odin - same but even more niche
Rust - some interesting ideas, atrocious community
>total meme tier
Beef - optimized for superficial C# similarity rather than actually being a good language; no tier 1 support for macOS and Linux
Hare - a worse C with no metaprogramming and no Windows support; there is no reason for this language to exist
Nim - tries to be good at everything and ends up being great at nothing; for example, 5 optional GCs and at least one is needed for much of the stdlib
D - garbage-collected by default; the GC-free mode is an afterthought
V - maintainer is a complete amateur and retard who uses CS terms incorrectly and promises things he isn't able to write; reference counted
>reference counted
isn't that costly and creates lots of overhead?
Yes, it is. Last time I checked, the maintainer quite literally didn't know what he was doing. I think he's way over his head but tries to project confidence outwardly.
The miracle cure for that is to collect things deterministically, except when the compiler can't figure it out, in which case they'll still be collected dynamically. Which is just the same escape analysis done by Go and Swift and Java and every other halfway respectable GC, only explained backwards
Come home white man
Looks good on stream but it's not released yet.
>assign constant B00BBABE in my code
>get assassinated by gaydon whore
wtf?
is cnile some kind of c library? i never heard of it
>cnile
someone should make bloated std called cnile, i make the logo
>vulkan
>questionably maintained flavor-of-the-month framework libraryshit game-engine
Yeah you definitely don't know what vulkan is. Stop LARPing.
>questionably maintained flavor-of-the-month framework libraryshit game-engine on top of OpenGL written by a nocoder LARPer in LULZ is okay
>somehow vulkan bad
You are just mad you are being called out as a LARPer. Now your only defense is semantics gymnastics. Fuck off nocder brainlet.