nostoc
nostoc on Hacker News
Instead of catching the `StopIteration` exception, you can simply provide a default case to `next` :
next((c for c in candidates if predicate(c)), default)
AES is kinda useless for securing communications without assymetric crypto, unless you want to be sending keys by courrier.
It's very much the "how", what were you looking for that's not explained in the blog post?
It's "Bob" all the way down
Yeah, because statically typed language never had any kind of deserialization vulnerabilities.
That ambiguity only lives in the article's title, the queries themselves are all quite clear.
> . It would be enormous, tedious to build (couldn't use modern lithography), and also consume tons of power.
Sounds to me like you're saying that Transistors are more efficient than vacuum tubes, both in terms of space and power consumption.
I suspect AI went that way in radiology not because of the chances of False Negatives, but because radiologist are entrenched in the system and will not yield an insanely lucrative stream of revenue.
Kali was running everything as root up to a few years ago, I'd be very surprised if this had application sandboxing.
This project is a boon to all reverse engineers, especially when reversing malware that uses undocumented features of windows.
I also don't know anyone who refers to it as wolfram, but wolfram is all over the tungsten wikipedia page.
Powershell is powerful because of the deep integration with the .NET ecosystem, and by extension, the OS.
This new shell lacks that, I agree. But I think it's a way harder problem to solve on linux.
The trucker's hitch is usefull because you get a mechanical advantage to tension your line.
Typically, I'd do a bowline on one end first, and tension it with a trucker's hitch. If you go with two bowlines, you end up with a floppy line, not great way to tie a load down.
Still is a fully integrated and mature programming language though.
And I do believe you wouldn't have any issue finding people who think the same of J.
> Sushi: Mostly no (the carbs don't protect you from the insides, the seaweed does)
If you wrap seaweed around a sandwich, is it no longer a sandwich?
It is unnacceptable that what is preached as a universal food categorization system doesn't even attempt to categorize rice.
True, and while the title is somewhate clickbaity, I think your point was pretty clear in the article.
Going down the "Some quacks were right, therefore all quacks are right" path will not lead you to a healthy place.
Yes, there is inertia in the scientific community, and sometimes the dissenting voices have a hard time being heard. That much is true.
But that is true because most of the time, the dissenting voices are wrong, if not outright lunatics.
I assume by limit OP means the remote system's bandwidth.
at 4 billion to 1, there's in practice very little difference between CVE-2022-26143 and what you describe. Both will be capped at the same number by the bandwidth available to the offending system.
Transitioning was hard, especially with all the libraries in various state of support between 2 and 3, I had a similar experience.
But I disagree with you about the separation of bytes and string and the current state of the language. I write a lot of python that deals with bytes and text encoding, and now that all the libraries have caught up with 3, the situation is way better than it ever was. encoding, decoding, bytes manipulations are way less prone to errors.
The "OPSEC fairy" as referenced in previous post is typically a random coworker, so no, they generally not have a broad license do tinker with your workstation.
An actual OPSEC person would not go and change your desktop's background, or send an email for free donuts to all your coworkers. An actual OPSEC person would just write you up for a security violation.
Both of your solutions are great but don't fully cover the use case. They are useful for multiline strings, but implicit concatenation is also often used to break long strings that may not have newlines.
you want to delete a file called '-rf' ?
rm ./-rf
If you have some weird characters in the filename, you can also let your shell escape whatever character is problematic by using autocomplete, starting with './'
For anyone who reads this and think it's funny, it is, but do this in the wrong workplace and you'll be the unemployed OPSEC fairy.
Random key bashing in vim can have a lot of unforeseen consequences for whatever poor file you had opened.
First time hearing about ULIDs. The locality is interesting, but they leak information about when they were generated down to the millisecond, which could lead to problems if combined with other issues. I'd be wary of using them client-side.
Injection means you can modify an existing query. The example are not SQL injections, they are full queries.
Okay big guy, show us your implementation of the JVM and we'll talk.
A cryptographic hash definitely should, but there are many more use cases for hashes.
You want SHA to be maximally non-continuous, but you certainly want the opposite for ssdeep for instance.