They don't understand the difference between belief and faith. I believe many things, but have no faith in them. I will take contrary evidence into account.
Do they promise?
I just had a POS machine recommend 20%, 25%, or 30% for percentages. It seems like it's increasing
There's at least one example you can look at, the Jenkins CI project had code like that (if (name.startsWith("windows 9")) {
):
https://issues.jenkins.io/secure/attachment/18777/PlatformDetail
Microsoft, for all their faults, do (or at least did) take backwards compatibility very seriously, and the option of "just make devs fix it" would never fly. Here's a story about how they added special code to Windows 95 to make SimCity's broken code work on it:
Windows 95? No problem. Nice new 32 bit API, but it still ran old 16 bit software perfectly. Microsoft obsessed about this, spending a big chunk of change testing every old program they could find with Windows 95. Jon Ross, who wrote the original version of SimCity for Windows 3.x, told me that he accidentally left a bug in SimCity where he read memory that he had just freed. Yep. It worked fine on Windows 3.x, because the memory never went anywhere. Here’s the amazing part: On beta versions of Windows 95, SimCity wasn’t working in testing. Microsoft tracked down the bug and added specific code to Windows 95 that looks for SimCity. If it finds SimCity running, it runs the memory allocator in a special mode that doesn’t free memory right away. That’s the kind of obsession with backward compatibility that made people willing to upgrade to Windows 95.
The collect
's in the middle aren't necessary, neither is splitting by ": "
. Here's a simpler version
fn main() {
let text = "seeds: 79 14 55 13\nwhatever";
let seeds: Vec<_> = text
.lines()
.next()
.unwrap()
.split_whitespace()
.skip(1)
.map(|x| x.parse::().unwrap())
.collect();
println!("seeds: {:?}", seeds);
}
It is simpler to bang out a [int(num) for num in text.splitlines()[0].split(' ')[1:]]
in Python, but that just shows the happy path with no error handling, and does a bunch of allocations that the Rust version doesn't. You can also get slightly fancier in the Rust version by collecting into a Result
for more succinct error handling if you'd like.
EDIT: Here's also a version using anyhow
for error handling, and the aforementioned Result
collecting:
use anyhow::{anyhow, Result};
fn main() -> Result<()> {
let text = "seeds: 79 14 55 13\nwhatever";
let seeds: Vec = text
.lines()
.next()
.ok_or(anyhow!("No first line!"))?
.split_whitespace()
.skip(1)
.map(str::parse)
.collect::>()?;
println!("seeds: {:?}", seeds);
Ok(())
}
Because there were not enough justices for a quorum—the court needs at least six and only Justices Elena Kagan, Sonia Sotomayor and Ketanji Brown Jackson remained—the court affirmed the judgment of a lower court to dismiss the lawsuit.
Clever. Appearing to do the right thing at face value coincides nicely with getting the case against you dropped. It's likely impossible to sue a majority of the Supreme Court if they don't care to be sued.
The argument I've heard is "It must stop somewhere, and whatever it stops at, we'll call that god". It's not a good argument, because it then hopes that you conflate the Judeo-Christian deity with that label and make a whole bunch of assumptions.
It's often paired with woo that falls down to simply asking "Why?", such as "Nothing could possibly be simpler than my deity"
Not AI art, but heavily related:
Good, that's the only way people like that will change
That's 👏 what 👏 CI 👏 is 👏 for
Warn in dev, enforce stuff like this in CI and block PRs that don't pass. Go is just being silly here, which is not surprising given that Rob Pike said
Syntax highlighting is juvenile. When I was a child, I was taught arithmetic using colored rods. I grew up and today I use monochromatic numerals.
The Go developers need to get over themselves.