express the project in your language in max 5 words
merge them e.g big long table index --> blotin, blotidex, bilotadex, big ol tadex
search for "word for $expression" and peruse the results
translate the expression into other languages then do the same as above
find synonyms for the words in your expression
build an expression that is the opposite of your project and just prefix it with a negative then repeat above
find a pun from your expression
pick your favorite animal (or pick random one) tack it onto the expression and repeat above
take your own name and use initials then spell out the initial e.g John Wallace -> J.W -> Jay Dub
tack that onto the expression (or the expression it fits best) e.g Jay Dub Index, Jaydudex, Judex, Dubidex, Jadubin
Or if you want to be completely unoriginal like, take a wordlist, pick a random word from it --> tada! You have a name. (what follows ia rant). The list can be an entire dictionary, anime names, movie names, name of mythical gods from wherever in the world, etc. Then come up with some bullshit explanation that sounds sophisticated for example you randomly picked.
For example, I went to https://randomword.com/ and got "xylary": "of, like or pertaining to xylem." No bloody idea why "xylem" is? Yeah, me neither.
noun
Botany.
a compound tissue in vascular plants that helps provide support and that conducts water and nutrients upward from the roots, consisting of tracheids, vessels, parenchyma cells, and woody fibers.
Oho, great! It has nothing to do with a big long table index, but let's make it so! "Xylary is a performant database index. Just like xylem are paramount to performance of plants, xylary is paramount to the performance of queries to your database." Voilà. The meaning of xylary is botched, but who gives a fuck, it sounds COOL, starts with X, and probably unknown to the majority of the world. So now you can piss off people in the field by polluting searches with your project.
Asking whether you've tried $simpleSolution, why you did something, and what you were thinking is not toxic. They're trying to understand your reasoning and what your goal is. It's like debugging where you have to step through the code then get to the point where something went wrong.
It is entirely possible that there are some people who have trouble asking such questions in a tone that doesn't emit hostility, but it may be due to a lack of social skills or (of course) malice. The way forward here is not to assume malice but them feedback "hey, can i give some feedback on the session we're having? I came to you seeking for help, but the way you ask these questions makes me feel $emotion. Would it be alright if you used $wordOrTone when helping me out? It would really make me feel more at ease". Something like this.
If the interlocutor reacts negatively, it may be that they are also feeling attacked by your words. Feedback is not always received well. In these instances it's good to apologise, but stand firm that your feelings were hurt and you would just like to make a way forward where you both can work comfortably with each other.
This of course flies out the window if the co-worker is being a straight dick. "PFF, you didn't even think of doing something that simple?", " well that was a waste of time, you should've been able to do that yourself", and so. That straight up deserves a higher up getting involved. For more egregious actions and words, that spells HR involvement.
But to simply write of all the people as "That Guy" is not the way forward. It's prejudiced and can easily lead to generalisations.
Let me rephrase your question: does individual action have impact on the whole?
With that kind of thinking, nobody should do anything ever. No need to vote because your will as a single voter doesn't matter. No need to stop eating meat because most others won't. No need to try to reduce energy consumption because most others won't. No need to boycott a product because most others won't.
So, honest question back: is that really how you want to think?
NVIDIA is a billion (maybe trillion now?) dollar company that leaves it up to people in their free time to support their hardware on linux and you're blaming the unpaid devs, not NVIDIA?
JavaFX has so far been my favorite framework to work with so maybe I’m just weird
I found Java Swing to be the easiest GUI framework to use. Never tried JavaFX. Would you call it an upgrade?
However statically compiling just doesn’t compare to using C and linking with the system libraries.
Rust does support dynamic linking (doc, stackoverflow), but AFAIK the crate has to explicitly be configured to do so (I might be mistaken though as I've never tried it). And from what I gather the rust ABI isn't stable (which is a pity) so it's "safer" to output a cdy-lib than a dy-lib.
Maybe in the future the rust ABI will be stabilized.
Other self-taught narratives, such as starting with Wordpress-based design backgrounds and moving from more simple themes to more complex themes where PHP knowledge is required, to plugin development is a completely valid narrative, but a path that is predominately for women.
Where the heck did that come from? What does any of this have to do with women? Are most Java and PHP developers women?
The argument the author is trying to make is hinged upon this argument that comes out of nowhere. The rest of the article makes some good points but has more of these deviations that just break the flow and make me say "what does that have to do with anything?".
My problem with PHP is the language and the ecosystem. I'm genuinely impressed that people are able to build useful things with it, but the language is, at least to me, far from easy. Starting with array not being an array but a hashmap/dictionary, to complete clusterfuck that many projects are in terms of setting up and tooling. Only C and C++ projects can beat that (or so I have experienced). There is just an assumption that whoever's picking up a PHP project knows LAMP and its components, has root access, and won't be using a debugger.
The PHP debugger has been one of the most frustrating debuggers I've ever had the displeasure of trying to setup. You have to know how to configure php itself, which extensions to install, how to configure those, and how to setup whatever editor or IDE you have to interact with the debugger. Most PHP projects I'm come across haven't set it up and I can understand why.
Also, to use PHP sensibly, you have to learn about zend or whatever the name of that big framework is. But that can break in the most mysterious ways and for PHP beginners it can be a nightmare to understand what went wrong. Add in that its favorite pattern is dependency injection and the language isn't typed and understanding code is downright awful.
One of my bigger gripes is that many projects do not use containers whatsoever. It's either LAMP on your machine or good luck getting that thing to run. If you're new to PHP, well fuck you, you should've known PHP before trying to contribute to the project - that's what it feels like. There are often C/C++ like guides for setting up. first "sudo apt-get install some stuff here", oh wait, you don't use debian? Fuck off chump.
I have sworn off touching PHP projects ever again. The experience has left me scarred.
Rust on top of a C/C++ lib is not fun, that's for sure. It has to setup a firewall around C which adds complexity. Using a rust native framework is better, IMO. Slint and egui are good examples thereof.
Yeah, I don't understand the wayland and systemd hate. Personally, the alternatives are worse in many areas. managing services before systemd was terrible and I'm very happy it's here. Making services depend on magic comments is a terrible system IMO. Can't remember if that's upstart or rinit or whatever.
Technically, it is a skill issue though, but requires borderline perfection to achieve safe code
If near perfection is the minimum to achieve a goal, then it can't be a skill issue, IMO. But I agree with the rest. It's a terrible argument that keeps getting repeated, not only for C but many other places in the tech world.
There's a paper about this and with C as the baseline, Rust was 4% slower for the specific tests they ran.
In these tests, Rust is actually faster than C sometimes.
So it really does depend on the workload. However, the safety that rust provides cannot be understated. It's easy to cut corners like in C, but it's difficult to do it right. Rust provides the closest result of right and fast.
I'm hoping email will be replaced by the protocol companies agree upon when the Digital Markets Act kicked in and forced interoperability between messaging clients. Once that happens, hopefully all we will need to share is $username@service and be able to communicate using a secure protocol.
What is wrong with the commenters on Phoronix? There seem to be a bunch of old dudes who can't accept that C is unsafe and no amount of "skill" will prevent it from being unsafe. They look at 3 decades of unsafe C with thousands of CVEs and still think it's a skill issue.
gstreamer has confused me for ages. Is it built on top of ffmpeg or an alternative?
Anti Commercial-AI license