Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat
As you can see, rust allows you to not put semicolons at the end of code blocks. The presence of semicolons is not a language killer. It’s a very hard language, but its worth it.
The presence of semicolons is not a language killer.
I’m not saying it is. But every time I have to work in a language that requires semicolons I’m constantly forgetting them and constantly reminded of how nice it is to not have to care in Go.
I think a lot of memes are missing the main point of how it was caught, the exploit caused a spike in CPU usage for a network call. That made no sense to the guy Messiah who found/reported it. FOSS software’s strength is the number of critical eyes looking over each line of code you put out!
Right but the joke is that most developers aren’t of that quality, and are now going to put leredditor super sleuth eyes on every application they build
In a nutshell, a backdoor was intentionally planted by a malicious actor in xz Utils, an open-source data compression utility widely used in Linux and other Unix-like operating systems. This discovery was made by Andres Freund, a developer and engineer working on Microsoft’s PostgreSQL offerings. He was troubleshooting performance problems on a Debian system. Specifically, SSH logins were consuming excessive CPU cycles and generating errors with Valgrind, a memory debugging tool. Through sheer luck and Freund’s careful eye, he eventually discovered that these issues were the result of updates made to xz Utils. Upon closer inspection, he found that updates to xz Utils were the result of a maliciously inserted backdoor. The backdoor, present in xz Utils versions 5.6.0 and 5.6.1, manipulated the sshd executable, allowing anyone with a predetermined encryption key to upload and execute arbitrary code on affected devices.
Neat FP style. Pretty verbose though. Someone should invent a terser syntax so you don’t need to write do_two_things everywhere. It’s a common operation so maybe it could even be a single character.
If you know about rust you know it’s a programmable programming language, meaning that you can make macros. There could be a macro that would do that but 1. Macros is rust code to write rust code so they have the complexity of rust squared 2. I said to myself the only macros I will allow myself to use in this challenge is println and allow
Like @deadbeef79000, I was bothered by the contraction. So I decided to Google it in the hopes of explaining why exactly it’s wrong, in case you’re a second-language speaker.
I honestly thought there would be a simple explanation, but it turns out that there doesn’t seem to be one. I found one Reddit thread which linked to a now-defunct blog (luckily, [it’s still available through the Wayback Machine), another that linked to an earlier Reddit thread, inside of which was yet another link to an even earlier thread. Here’s the most recent of the threads in that chain if anyone wants to read it. But below is quoted the important bit from that archived blog post:
You CAN end a sentence with a contraction if it is a Type 2 (Verb-Negative), both in speaking and writing. You are always in safe territory when you end a sentence with a negative contraction.
Examples:
No, I don’t.
I’m a student, but she isn’t.
For a Type 3 (Modal + “have”), English expert Eugene Mohr says in his article in TESOL Quarterly, “The Independence of Contractions”, that “no contraction takes place if….have occupies the final position” in a sentence. HOWEVER, Mohr limits his explanations to contractions in written language, not spoken. In informal speech, native speakers often contract a modal with “have” at the end of a sentence. So, while it looks funny written out, you will hear people end a sentence this way.
Example:
I didn’t go to church, but I should’ve.
Last, and most importantly, you CANNOT end a sentence with contraction if it is a Type 1 (Pronoun-Verb). Not in formal English, not in informal English – never! In this case, you must write out the entire verb that follows the pronoun. So take a look at the contraction at the end of your sentence. Does it contain a pronoun? If it does, then break it up into its two original words.
INCORRECT: Yes, we’re.
CORRECT: Yes, we are.
But the bottom line is yeah, the title here uses a contraction in a way that is not permitted by standard English prosody.
Yeah for sure it is. The biggest difference is that there’s a fairly simple way to explain the adjectival order: “opinion, size, age, shape, colour, origin, material, purpose”. It’s apparently very difficult to explain when you can and cannot use contractions in a concise way.
programmer_humor
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.