There was an executive order by the governor to allow more flexibility for Covid tests. Pharmacists are now allowed to order Covid tests. And when you show up at a testing site at a clinic or hospital, your test will be recorded as "ordered" by a doctor or nurse practitioner that you never actually see in person.
Yes, at least for Levenshtein-style edits (substitution, insertion, deletion).
Although, I suppose a spell checker algorithm would be O(mnd) where d is the size of the dictionary, because it needs to compute O(mn) edit distance for each of the dictionary words.
Hilariously, ColdFusion strikes again. I should have used pound signs around the bad_memories variable. The above code would dump the string "bad_memories".
I don't believe that /> is needed anymore. You can just use >
I unfortunately work with coldfusion/cmfl on a daily basis at my company.
I am moving the servers over to Lucee from Coldfusion 10 and trying to have any new systems built on C#/.net.
The most difficult part is getting other people on board. My manager is fine with what I am doing. He saids he is too old to learn a new language so myself and the other programmer will have to support anything I built in .net
Let me tell you folks. Writing spaghetti code with no separation of concerns and no version control is not exclusive to php
> Let me tell you folks. Writing spaghetti code with no separation of concerns and no version control is not exclusive to php
Yowza. If I can give you some unsolicited advice: get some kind of version control in place! Even if it's just a local git repo at first.
There were two things that made working in ColdFusion almost tolerable. (1) The place I worked started using an MVC framework before I left. I was pleasantly surprised by how much it improved the experience. (2) Transitioning to CFScript instead of CFML tags made a big difference as well.
But at the end of the day, it's still ColdFusion, and it drove me bonkers.
The guy who invented that syntax was J.J. Allaire. Bill Gates passed on his advisors recommendation and didn't buy Allaire because he thought the price was too high. Instead he bought a company in Hawaii building what became ASP.net. However he was quite impressed with J.J.
But years later when J.J. started a second company, it was only a few weeks old when Gates swept in and bought it for millions of dollars.. Shut it down and moved everyone to Seattle.. He immediately assigned J.J. and his team to build a new project called Azure.
J.J. Allaire's other brother and partner in ColdFusion was Jeremy. Jeremy has started two successful companies since leaving Macromedia. They are BrightCove and Circle. I don't know about Circle but at one time parts of BrightCove were running on ColdFusion.
Yes, I've made CRN++ version as well (in this pull request: https://github.com/marko-vasic/crnPlusPlus/pull/1), but it required much more reactions and was less stable. So I decided to make it from scratch by using different approach.
The sexual connotation gets its name from the slur[1], because the suit handicaps the wearer. The name of the image editor originates from Pulp Fiction, which uses the sexual connotation.
And most of the commonly understood meanings of the word are rather negative. Nobody hears the word "gimp" out of context and thinks of decorative sewing thread, for example.
There does appear to be ARM64 assembly in Go's crypto code, but perhaps it's suboptimal for M1. Or perhaps there's a build config issue, and the assembly isn't being used. Just my speculation, though. I haven't looked into it.
I've definitely been the victim of my own git hubris.
Once, when leaving a job, I decided to copy all of my local WIP branches to the server.
I whipped out this fancy --mirror option I had just heard of:
git push --mirror $remote
Surprise! All branches on the remote repo got wiped. My local refs replaced the refs on the remote.
Somehow I found the right commits floating around in the git ether. I was able to recreate the branches, but I had to recreate their names by reading the commit log.
Did I mention this happened on my way out the door from a job? In retrospect, I shouldn't have panicked so much -- there were daily backups -- but the sheer terror I felt has made me read the man pages really closely to this day.
That breaks a very simple rule that a VCS tools should adhere consistently. Do not make destructive changes unless explicitly told to. Since most other commands to not allow you to do this without -f, the same should apply here.
I'm not sure I see your point. The entire reason `git push --mirror` exists is to turn the remote end into a mirror of the local end. By definition that's a destructive operation. What would it do without a further --force?
If you just want to push all branches or tags you should use --all or --tags.
Because you normally cannot make remote destructive changes without the --force. Unless you know the commands that does that by default. That is bad UX.
Probably because removing branches from the remote doesn't make the commit history inconsistent with any copies made before the push. That seems to be the only case where git second-guesses what you tell it to do.
mistakes happen.
it is a testament to the power of git that your command didn't cause permanent damage. and yes, it could have been worse.
but if you want a system that protects you from these mistakes by making mistakes impossible, then you get a system that is very rigit and actually harder to use.
git protects you from these mistakes by making it possible to recover.
in this particular instance though, there could probably be some extra help to recover. (some way restore the removed refs)
...and if you didn't know that, you shouldn't be using git!
To be fair, one should always look up options you are unfamiliar with before using - and Stack Exchange is not an authoritative source.
--mirror
...Newly created local refs will be pushed to the remote end, locally updated refs will be force updated on the remote end, and deleted refs will be removed from the remote end... [my emphasis.]
On the other hand, if you are on a system where the behavior can be fundamentally altered by multiple configuration options, this will not necessarily help you much.
...This is the default if the configuration option remote.<remote>.mirror is set.
I get it, but I'm not sure you should fault Git for that. Nothing like that has ever happened to me and I wouldn't use a command I don't know in a critical setting...
Any sane piece of software should warn you before doing a highly destructive operation.
Something like
You are trying to remove commits from twelve branches.
Are you sure that's what you want to do?
Include the --force option to go ahead with this change.
would be a whole lot better.
Even if it gives you the tools to undo the mistakes, it saves you time and stress if it keeps you from making the mistakes in the first place.
