![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/4271bdc6-5114-4749-a5a9-afbc82a99c78.png)
It’s a joke
It’s a joke
Ok. I’ve downloaded, tar and gunzipped the files for it.
Then did a make build and then make install. Now my system won’t start. What do I do?
I guess the trouble is that you don’t want to read the volumes where the db files are because they’re not guaranteed to be consistent at a given point in time right?
Does the given engine support a backup method/utility that can be used to copy files to some volume on a set schedule?
for(i=0;i<100;i++){
console.log("Yep")
}
console.log("uh-huh")
eval('alert("Yep")')
I assume they’re past some operational limit. But as long as you have redundancy that’s a risk I’d take for the capacity
I know it’s a joke but I prefer the tab option. It’s easy to convert tabs to any particular spacing or code point width. It can also vary, if wanted, based on terminal or editor type.
People with worse eyesight can have a wider indentation while those who choose can opt for something more compact
Ahh. It’s a boutique link that points to Amazon Digital Purchase of Rick Astleys Never Gonna Give You Up.
E.g. my post was a red herring
Did you look at the book I linked?
Which are used to calculate stresses for dams, fluid dynamics for planes and ships, capacity and load simulations for power, and to compile and operate servers.
Software engineers are the pinnacle of engineering.
Check out this book on Amazon (or your library) to see just how clever and useful we really are.
https://www.amazon.com/Software-Engineering-Foundation-of-Modern-Society/dp/B07X66DCLM
Honey, wake up. The new Def Leppard Album just dropped
The magnets are fantastic for tool mounts since they’re so strong
For me vi was my first experience with it.
So yeah, I think it’s often about what you’re used to
It’s easy.
Escape to exit edit mode
: to prefix a command
q to quit
! to confirm
Now emacs… those people are crazy.
Good point. That’s what I get for shooting from the hip.
Thanks!
I agree it shouldn’t. But I’ve seen linters that automatically change it since they seem to be forcing practical conventions sometimes.
Try changing to const === variable. That’s most likely what’s it doing to minimize the risk of accidental assignment.
So in JavaScript there’s the assignment
=
and the comparator is
==
Since there’s no types JS will do implicit conversion before comparison when using == in a case like this
if(false == '0'){
//this is true
}
But with === it doesn’t. It means literally compare these
if(false === '0'){
//this is false
}else{
//so this will execute instead
}
But this, however, will
var someState = false;
if(someState === false){
//this is true
}
Yes, but maybe there’s some magic going on so that the lack of a type assigns some value that results in void?
Possible something on your motherboard has PCIe lanes that are dedicated to GPU when it’s slotted, otherwise they can be used for other devices?
For example here’s a post about m.2 slots that, when used, affect the PCI on a particular board. May be worth checking your boards manual to see if there’s something similar.
https://forums.tomshardware.com/threads/questions-about-a-mb-im-looking-at-asrock-z790-pg-riptide.3787003/