Sometimes you have no choice but to represent intervals this way. If you make one payment a month, the interval is one month. The interval between Christmases is one year. It's not some particular number of days or number of seconds. It just isn't.
JoelKatz1
@JoelKatz1
Best posts made by JoelKatz1
-
RE: Check out our BRAND NEW ISO specification for $138 ONLY! ORDER NOW!!!
Latest posts made by JoelKatz1
-
RE: Check out our BRAND NEW ISO specification for $138 ONLY! ORDER NOW!!!
Sometimes you have no choice but to represent intervals this way. If you make one payment a month, the interval is one month. The interval between Christmases is one year. It's not some particular number of days or number of seconds. It just isn't.
-
RE: Am I TRWTF?
@slavdude said:
As I said, I'm not the greatest at asking for help, and I know my quality was suffering over the past few months. But am I TRWTF for resigning so quickly?
Yes, you and all those other people who resigned are each individiually the problem. Clearly, this awesome company got extremely unlucky and hired a large number of people who all have exactly the same problem.TL;DR: I got tired of the hassle at work and resigned suddenly. Dumb or smart? You decide.
-
RE: The things people do for money...
@dkf said:
@morbiuswilters said:
The AGPL is basically identical to the GPL. The AGPL claims to cover normal use, but you can't do that in the United States. If you look at the exclusive rights afforded to copyright holders (17 USC 106), you will *not* see the right to "use" the work listed. Only a wrap or EULA can restrict the right to ordinary use, and the AGPL is neither a wrap nor an EULA. It's equivalent to a billboard that says "By reading this billboard you agree to do the chicken dance for an hour a day for the rest of your life". You can write anything you like in a license, but it's not automatically enforceable under US law. All you can do in a license like the GPL or AGPL is grant the right to do things 17 USC 106 would normally prohibit. You can't take anything away or add conditions to things people could already do.@blakeyrat said:
It could be worse; it could be AGPL. It's quite the most noxious infectious license out there; “kill it, kill it with fire” is a reasonable response. Thankfully it's rare.Maybe GPLv3 changes this, I dunno.
I don't think GPLv3 changes it. Then again, nobody uses GPLv3, so it doesn't really matter.In fact, maybe we can just skip the ranting about it and go straight to declaring that everyone who doesn't hate it is either blissfully ignorant or a complete idiot.
IANAL. This is not legal advice.
-
RE: Password reset
@anotherusername said:
You should need the security question OR the e-mail address to reset your password (not both). You might forget your security question answer or lose your old e-mail address. Having two ways to reset your password gives you a backup. If you need both of them, you're fucked. Anyone who's smart already knows that a security question is just another password and shouldn't be something guessable.
You believe that you should need either. They believe that you should need both. Certainly reasonable people can disagree on this. But that doesn't change the fact that TRWTF is that you assumed the site would work the way you personally thought it should and lied to the site based on those unfounded assumptions and then blamed the site when it behaved the way a secure financial site should.It should not be easy to recover a lost password to a site that relates in any way to financial information, particularly if you don't have the password recovery information configured on the account.
-
RE: Password reset
You lost your password. You gave a nonsense answer you also don't remember to one of your security questions whose sole purpose is to ensure your password can be securely recovered. Look in the mirror for TRWTF.
-
RE: This graph may or may not be plotted on a log scale
@pyro789x said:
It's quite clear that the graph will be plotted on a log scale in the published version but is not in this version. That's what the note in red says. Did they really need to add a second note in red after the black note saying, "The previous NOTES will be in the published version so you can review them. If they were going to be different we would have said so. Again, repeating the red node you just read, in this version, the graph is not in a log scale, in the published version it will be. That's why the black note says it's on a log scale -- that note will be in the published version as no red note says it won't be.So wait, what kind of scale is this plotted on? And what kind of software limitation prevented them from generating an image of a chart with a specific scale?
-
RE: Unstructured optimization
@Mo6eB said:
Except for two things. Registers are precious on most platforms. So unless you use those parameters relatively immediately, there's a good chance you'll have to move the parameters out of the registers to free those registers for the computations you need to do before you need the parameters. Second, modern computers don't have to load recently-accessed data from RAM, they can be loaded from L1 cache, which is nearly free. In sum, code is more likely to prefer its parameters to be in L1 cache than in registers, unless the code is trivial.Technically he's not exactly wrong. The first parameters are passed in registers and the rest on the stack. So you can do computations with the values in the registers already, while waiting for the stack values to be loaded from ram in registers.
-
RE: Xerox scanners/photocopiers randomly alter numbers in scanned documents
@anonymous234 said:
@joelkatz said:
That would make the very same algorithm "lossy compression" if color tones were unimportant but no longer "lossy compression" if used in an application where precise color tones were vital. The description "lossy compression" describes the algorithm itself, not the context in which it used.That's what lossy compression does. It takes the original information and replaces it with something jdged "sufficiently similar" but that takes less space to store. Here, the compression engine had an "86958" image already encoded and judged that a "66958" image was sufficiently similar, so it saved space by replacing one image piece with a reference to the other. Many lossy compression algorithms do this.
You are technically correct, but if you think that's an acceptable use of the term "lossy compression" you're an idiot. Lossy compression is supposed to lose non-important information like color tones or shapes or gradients, not actual information. Otherwise you might as well replace every page with a blank page.