This is obvious if you took a DB course, and if you didn't, you have no business building a DB. Sadly, all the NoSQL junkware was built by people who didn't.
The example is flawed -- if there is an exception incurred before or during the sending of the email, the operation will be erroneously marked as "cancelled" without having completed all of the cancellation flow. Namely, with the example as given, it is possible to have a cancelled order for which an email has not been sent out.
Moving the second line (the one that changes the status to "cancelled") to the end fixes this issue, though it does not implement "exactly once" semantics for the sending of the email. If "exactly once" is desirable, then additional logic is required. But in every case, the example as given is incorrect.
What a self-indulgent writeup. The article came nowhere near answering the central question: what are the devs doing other than constantly changing the name of the project and how is this thing better than gimp.
Oh, noes... A post that has this in the second paragraph:
"I'll hope you, dear reader, will forgive me for making this a really personal post; a very large part of my life has been tied up with Krita, and it's going to show."
ended up in something "jmix" thought was "self-indulgent".
Oh, I didn't know that Krita used to be called something else. I can't find any details of what its name was before it was Krita though; do you happen to know what it was?
I googled that because the "long dead German lawyer" in the op's article made my spider-sense tingle. Of course it was Gravenreuth, the bête noire of the German internet in the 90s and 2000s.
it's an anniversary celebration post, not a "what is krita" post. It's meant for people already following the project.
Krita is an application primarily aimed at digital artwork rather than editing images. So a strong emphasis on drawing and related tasks. For this, it is much easier to use than gimp. I won't necessarily say it's better, but every time I tried using gimp I gave up and I actually stuck with krita.
Good riddance to these tools because this technique, of relying on embedded strings in the code, is inherently insecure and unreliable. You can only really on it when you know you can trust the build, and yet they are used in cases where the build is of unknown etiology, so there's an inherent mismatch between when the tool is used and what it does.
Thanks for the clarification. On a related note do you understand where the X.509 Name Constraints effort sits? Which, if any, browsers implement it? If it's not 100%, do you know why browsers are hesitant to deploy it?
Name Constraints support is pretty good in modern certificate libraries. It's certainly in CryptoAPI these days which accounts for the bulk of users.
But there are two ways to use Name Constraints: they can be marked critical or non-critical.
Critical Name Constraints are great, but they will cause anything that doesn't support Name Constraints to reject the certificate. This is obviously a problem because few deployments have much control over their client base.
Non-critical name constraints provide a security benefit to clients that support them without affecting those that do not. Clients that don't support them are vulnerable to misuse of the constrained certificate, of course, but since the alternative is often an unconstrained, CA certificate, it's still a clear win.
I'm not sure, but in the back of my mind I don't think that it does. I've agreed to write about this stuff for the Web PKI Working Group so I'll need to do a survey of the various capabilities at some point.
Since it takes a while to digest the report after having seen it, chances are that they were in possession of the report far earlier than T-400ms but waited until they were in a time window where they knew the regulators would not come after them.
This is how fortunes are made. By taking advantage of loopholes in the regulatory mechanism.
I don't know the way these reports are structured, but is it regular enough where there's even a possibility that a bot could digest, analyze, and act on the information there in near real time?
How can you read this chart, and infer from it that the activity is due to having already read the report?
Surely everyone knew that the report would be released at 10:30, and they had strategies (or hedged positions) that were not as likely to be influenced by the contents of the report as by the market forces surrounding their orders?
> It is worth pointing out that the EIA Natural Gas Report comes out weekly (every Thursday at 10:30) and the market reacts within a few milliseconds. This is because the report centers on one number which makes it easy for machines to process and take action.
True but I also assume a large part of algo trading is deducing up/down signals from new information and acting quickly. I've heard the bigger reason high-freq algo trading is used is to mask larger moves in position in noisy trade bundles, avoiding price shock.
These articles invariably end in "does not follow" fallacies.
In this case, he gets his accounts hacked, and his advice is "don't use any cloud-hosted email." Ok, but what evidence have you presented that shows that self-hosted email is any more secure? At least, a set of professionals were able to restore your account -- I doubt that would have happened if you had been hosting your own email server.
I have mixed feelings about this announcement. On the one hand, I really enjoyed Triumph of the Nerds. On the other, Cringely came off as a self-oriented, egotistical guy (I remember the scene where he threatened the TV crew with a piece of bat when his plane build project wasn't going well) with few unique insights and little depth.
Now that I think about it, these two facts are in line with his announcement. What he brought to the scene was to act as a tech interpreter for the baby boomers. The novelty has worn off and he's tapped out. This seems very similar to what happened to Dvorak, and what happens to a lot of bloggers: he exhausted his material and the world passed him by.
For me, Cringely was the documenter and Dvorak mistook his own place in history for credibility in analyzing the future. The tech industry is exhaustively self-documenting now, and so I hold out hope that Cringely can find his place in the modern world since I've looked to him as something like "Uncle Computers" ever since the before-times.
In what entitled universe do you live in where a guy who carefully and patiently points out problems is also obligated to solve every single one of them?
Also, do you really need someone to spell out the alternatives to MySQL? There are too many to list.
He does not need to be able to point to an extant, better alternative for his criticisms to be "credible."
BTW, I can't believe you're implying that his post is not credible. The practical outcome of your demand for a solution is to shut down legitimate criticism.
