

All government data is processed using sed
.
All government data is processed using sed
.
My code is portable enough to support all versions.
No. You need to run it in a VM that runs TempleOS.
You’ll need my fork of docker, and you’ll need to apply a patch.
My website only works with Chrome, but it has to be a specific old version of it. And you also need to install some extensions. Very specific versions of these extensions. Few of them already removed from the store due to security backdoors.
I have a Docker image you can use to run Chrome though.
That’s a very quaternionphobic list.
Wine Is Not an Emulator Is Not an Emulator Is Not an Emulator
Why use print!
and not println!
? You’ll just mess up the terminal text flow…
From a certain point of view - isn’t this exactly what happened here?
I often go into a Git worktree of one of my projects and mess around a bit to try something out. If I find it’s not working, I tell git to discard the changes with git checkout .
and git clean -df
. What I’m saying is exactly “on second thought, don’t do anything" - while what happens in practice is that Git restores all files to their HEAD
status and removes all the new files that are not already in HEAD
.
Of course, the difference is that I already have all the work I want to keep under source control, so these changes I’ve discarded really were that - just changes. He, on the other hand, “was just playing with the source control option” - so these “changes” he was discarding really were all his work. But Git did not know that.
Downvoting in order to bring it below @whynot’s comment.
For Windows 11, it would be an ad for Hitler instead of just a picture.
XML is good for markup. The problem is that people too often confuse “markup” and “serialization”.
You are assuming here that I know what I want. What if there is no obviously correct answer, and even in the Everett branch that generates the optimal content for the file I’ll still think it can be improved and tell it to destroy the universe?
What if there is no correct answer?
I just use this:
#!/bin/bash
keep_generating=1
while [[ $keep_generating == 1 ]]; do
dd if=/dev/random of=$1 bs=1 count=$2 status=none
echo Contents of $1 are:
cat $1
echo
read -p "Try generating again? " -s -n1 answer
while true; do
case $answer in
[Yy] )
echo
break
;;
[Nn] )
keep_generating=0
break
;;
*)
esac
read -s -n1 answer
done
done
This is Rust. You don’t need a safe word - safe is the default. You need an unsafe
word instead.
What do you mean by “improving”? This alarming warning appears because Firefox requires permissions. Let us look at the permissions listed there:
App permissions should not be about “this app cannot be trusted because it asks for scary scary permissions”. They should be about “take a look at the list of permissions the app requests and determine whether or not it make sense for such an app to need such permissions”.
Nearly every app should have a warning
No. If you put a warning on every app (except for the most trivial ones that don’t actually do anything useful) then the warnings mean nothing. The become something more than ass-covering legal(ish) BS.
I’ll start using it after I migrate to Wayland.
Doesn’t MS Access still use SQL?