|
dick traceroute posted:Also clocks. Have a look between III and V I thought that one was because that means you have an even number for all the counts of each digit, so you can use the same template twice and get enough digits for one clock.
|
#
?
Jan 3, 2017 21:27
|
|
only
|
|
| # ? Jun 8, 2024 00:00 |
|
|
Edison was a dick posted:I thought that one was because that means you have an even number for all the counts of each digit, so you can use the same template twice and get enough digits for one clock. Four times, actually.
|
|
#
?
Jan 3, 2017 23:39
|
|
|
HardDiskD posted:And how is wiki pronounced? Like wickee, not weekee (or vici).
|
|
#
?
Jan 4, 2017 01:19
|
|
|
Kilson posted:Like wickee, not weekee (or vici). Christ.
|
|
#
?
Jan 4, 2017 13:16
|
|
|
Kilson posted:Like wickee, not weekee (or vici). I'm pretty sure Ward Cunningham disagrees (the original Hawaiian word would be pronounced more like "weekee" than "wickee").
|
|
#
?
Jan 5, 2017 21:49
|
|
|
Dr Monkeysee posted:I'm pretty sure Ward Cunningham disagrees (the original Hawaiian word would be pronounced more like "weekee" than "wickee"). Yeah and the guy who invented GIF says it is pronounced 'jiff', so clearly the inventor can be wrong about pronunciation.
|
|
#
?
Jan 5, 2017 21:56
|
|
|
"Wickee" is clearly the better pronunciation but strictly speaking the Roman pun works!
|
|
#
?
Jan 5, 2017 22:09
|
|
|
I pronounce it like "sword."
|
|
#
?
Jan 5, 2017 22:12
|
|
|
Oh MySQL.
bobthecheese fucked around with this message at 03:05 on Jan 6, 2017 |
|
#
?
Jan 6, 2017 03:01
|
|
|
taqueso posted:Yeah and the guy who invented GIF says it is pronounced 'jiff', so clearly the inventor can be wrong about pronunciation. The pronunciation is in the spec, so it's the rest of the world that's wrong.
|
|
#
?
Jan 6, 2017 04:23
|
|
|
taqueso posted:Yeah and the guy who invented GIF says it is pronounced 'jiff', so clearly the inventor can be wrong about pronunciation. The author of the GIF format intended it to be a pun on "In a jiffy" because it made images load faster, both by optimized file transfer and faster decompressing than many other contemporary file formats available in the late 80s. So it's literally just a horrible dad joke, and CompuServe who employed him required he use GIF as the abbreviation because they wanted it to be a valid acronym of a descriptive name - and also because they were worried the Jif peanut butter people might have an issue. It's some "hi hungry, I'm dad" stuff.
|
|
#
?
Jan 6, 2017 04:30
|
|
|
leper khan posted:The pronunciation is in the spec, so it's the rest of the world that's wrong. Specs are just polite suggestions.
|
|
#
?
Jan 6, 2017 04:39
|
|
|
fishmech posted:CompuServe who employed him required he use GIF as the abbreviation because they wanted it to be a valid acronym of a descriptive name - and also because they were worried the Jif peanut butter people might have an issue. I can confirm this.
|
|
#
?
Jan 6, 2017 05:33
|
|
|
bobthecheese posted:Oh MySQL. Do it again with utf8mb4 because of course UTF-8 should only mean certain characters and not loving UTF-8
|
|
#
?
Jan 6, 2017 05:49
|
|
|
fishmech posted:The author of the GIF format intended it to be a pun on "In a jiffy" because it made images load faster, both by optimized file transfer and faster decompressing than many other contemporary file formats available in the late 80s. So it's literally just a horrible dad joke, and CompuServe who employed him required he use GIF as the abbreviation because they wanted it to be a valid acronym of a descriptive name - and also because they were worried the Jif peanut butter people might have an issue. if he was smarter he would have named it JIF, which would pronounce correctly. And then you just say that the acronym is recursive: "JIF Image Format"
|
|
#
?
Jan 6, 2017 09:26
|
|
|
I've been forced to work with some project that uses the Matlab compiler to create a standalone executable for running on some batch nodes, and randomly about 1% of the time the executable just crashes as it's launched. I assumed it was some issue with the code, but the crash occured suspiciously fast and didn't leave behind any useful information so I began to wonder if maybe I was using the compiler wrong. Looked around online and apparently this is a common problem with Matlab-compiled standalone executables, there is no solution and you just have to deal with it
|
|
#
?
Jan 6, 2017 09:37
|
|
|
QuarkJets posted:I've been forced to work with some project that uses the Matlab compiler to create a standalone executable for running on some batch nodes, and randomly about 1% of the time the executable just crashes as it's launched. I assumed it was some issue with the code, but the crash occured suspiciously fast and didn't leave behind any useful information so I began to wonder if maybe I was using the compiler wrong. My first guess was "it's just some dumb unavoidable MATLAB thing" and hey, it looks like it lived down to my expectations!
|
|
#
?
Jan 6, 2017 10:49
|
|
|
QuarkJets posted:I've been forced to work with some project that uses the Matlab compiler to create a standalone executable for running on some batch nodes, and randomly about 1% of the time the executable just crashes as it's launched. I assumed it was some issue with the code, but the crash occured suspiciously fast and didn't leave behind any useful information so I began to wonder if maybe I was using the compiler wrong. The solution is that Matlab should not be used in production. It's awesome for the research phase, but when the research is over, implementation for the product should be done by a developer in whatever language the product is going to use.
|
|
#
?
Jan 6, 2017 14:53
|
|
|
QuarkJets posted:I've been forced to work with some project that uses the Matlab compiler to create a standalone executable for running on some batch nodes, and randomly about 1% of the time the executable just crashes as it's launched. I assumed it was some issue with the code, but the crash occured suspiciously fast and didn't leave behind any useful information so I began to wonder if maybe I was using the compiler wrong. Dude, its Matlab. Of course its terrible and hosed up.
|
|
#
?
Jan 6, 2017 14:56
|
|
|
Volguus posted:The solution is that Matlab should not be used in production. It's awesome for the research phase, but when the research is over, implementation for the product should be done by a developer in whatever language the product is going to use. I once spent a few months ripping out a robust c# implementation of a thing to replace it with a ridiculous wrapper of the matlab prototype. Then I got the gently caress out of there.
|
|
#
?
Jan 6, 2017 19:31
|
|
|
Who on earth thought that was a good idea?
|
|
#
?
Jan 6, 2017 20:21
|
|
|
The official motivations were all really awful and I'm pretty sure the actual motivation was that it shifted whose budget had to pay for the ongoing work.
|
|
#
?
Jan 6, 2017 20:31
|
|
|
Plorkyeran posted:The official motivations were all really awful and I'm pretty sure the actual motivation was that it shifted whose budget had to pay for the ongoing work. Hahah, that's wonderful! Office politics 
|
|
#
?
Jan 6, 2017 21:39
|
|
|
Plorkyeran posted:I once spent a few months ripping out a robust c# implementation of a thing to replace it with a ridiculous wrapper of the matlab prototype. Then I got the gently caress out of there. how do you sleep at night
|
|
#
?
Jan 7, 2017 06:45
|
|
|
I've seen that before when there are high visibility bugs in the new and better version. Eventually someone says, "can't we just switch back to the old one."
|
|
#
?
Jan 7, 2017 18:17
|
|
|
QuarkJets posted:I've been forced to work with some project that uses the Matlab compiler to create a standalone executable for running on some batch nodes, and randomly about 1% of the time the executable just crashes as it's launched. I assumed it was some issue with the code, but the crash occured suspiciously fast and didn't leave behind any useful information so I began to wonder if maybe I was using the compiler wrong. The stand alone executable assumes that the user has tested the Matlab program in Mex mode.
|
|
#
?
Jan 8, 2017 06:47
|
|
|
QuarkJets posted:Looked around online and apparently this is a common problem with Matlab-compiled standalone executables, there is no solution and you just have to deal with it Hey, at least you're not using it to design ASICs. That chip has more revisions than any of our other ones, and that includes the one where the main PLL had its output shorted to ground...
|
|
#
?
Jan 8, 2017 09:41
|
|
|
O_Kafetzis posted:Can you recreate the crash in MEX mode? That may give you more information to debug the problem. The MathWorks support person said that it's a known problem with repeatedly running mcc-compiled executables in *nix environments, and that if it does crash then you just need to run it again (I can verify that this worked, the crash really is random, apparently). He also said that the crash wouldn't occur if the compiled executable was launched from within a Matlab instance, but that seems like it's defeating the point of using the MCR. Trying to debug the matter further feels kind of futile
|
|
#
?
Jan 8, 2017 10:14
|
|
|
smackfu posted:I've seen that before when there are high visibility bugs in the new and better version. Eventually someone says, "can't we just switch back to the old one." This is my life right now. I can assure you that it is a rollercoaster ride. For context, one of the "high visibility problems" is that using actual windows instead of child MDI windows is an unprecedented, horrible thing and everyone is angry at having to learn something new.
|
|
#
?
Jan 8, 2017 16:57
|
|
|
Plorkyeran posted:I once spent a few months ripping out a robust c# implementation of a thing to replace it with a ridiculous wrapper of the matlab prototype. Then I got the gently caress out of there. gently caress you, I want to gently caress you up bitch. I've been working on replacing a huge complicated MATLAB piece of poo poo with c# for a loving YEAR at my current place. As soon as I read your post I did 200 push ups to prepare my body to kick the poo poo out of you, watch your back
|
|
#
?
Jan 8, 2017 19:09
|
|
|
If someone would just go on over and burn Mathworks HQ to the ground that would be fine with me.
|
|
#
?
Jan 8, 2017 22:07
|
|
|
Dog Jones posted:gently caress you, I want to gently caress you up bitch. I've been working on replacing a huge complicated MATLAB piece of poo poo with c# for a loving YEAR at my current place. As soon as I read your post I did 200 push ups to prepare my body to kick the poo poo out of you, watch your back I want to imagine you're at the same place reversing the migration on the same product, but at least when I left it the matlab stuff was all nicely segregated into its own microservice and you could point things at either the matlab or c# implementation, so in order for it take a year someone after me would have had to gently caress things up pretty badly.
|
|
#
?
Jan 9, 2017 02:03
|
|
|
Or everyone forgot about the c# microservice and mr Jones has been rewriting this whole poo poo pile for nothing!
|
|
#
?
Jan 9, 2017 17:18
|
|
|
Nah mine is scattered around all over the goddamn place, Im the first person at this place to even use the word 'service'
|
|
#
?
Jan 9, 2017 18:29
|
|
|
Man, and I thought I had it bad porting Matlab code to Perl. Why would anyone hire developers to port to Matlab? I've normally seen academics prototype in Matlab or R and then get productionized for performance and such porting to something actually meant to run beyond someone's workstation for a demo to get a research grant.
|
|
#
?
Jan 9, 2017 23:18
|
|
|
necrobobsledder posted:Man, and I thought I had it bad porting Matlab code to Perl. Why would anyone hire developers to port to Matlab? I've normally seen academics prototype in Matlab or R and then get productionized for performance and such porting to something actually meant to run beyond someone's workstation for a demo to get a research grant. Some guys pay real money to get their nuts stepped on. People are weird.
|
|
#
?
Jan 9, 2017 23:33
|
|
|
necrobobsledder posted:Man, and I thought I had it bad porting Matlab code to Perl. Why would anyone hire developers to port to Matlab? I've normally seen academics prototype in Matlab or R and then get productionized for performance and such porting to something actually meant to run beyond someone's workstation for a demo to get a research grant. When all that you have is a hammer, everything looks like a nail. Some engineers only really know how to work with Matlab and they don't understand that Matlab is a half-competent prototyping language with a nice UI and nothing more
|
|
#
?
Jan 10, 2017 14:38
|
|
|
quote:hey Mr. Crow, I don't understand the comment "please merge the latest from master" HOW DO YOU HAVE A JOB IN IT? I've been telling this kid how to do his job for the better part of a year; normal people actually learn things and it's no big deal but he is as clueless as the day I met him.
|
|
#
?
Jan 10, 2017 17:53
|
|
|
Maybe you should teach him what that means?
|
|
#
?
Jan 10, 2017 18:08
|
|
|
|
| # ? Jun 8, 2024 00:00 |
|
|
I have at least a dozen+ times 
|
|
#
?
Jan 10, 2017 18:09
|
|