|
Nippashish posted:Also when your toolchain is known to be terrible (which sounds like the case here) then "the build artifacts are wrong" becomes a reasonable debugging hypothesis fairly quickly. Yeah, people are spoiled working with mature toolchains (although MSVC and UTF-8 was a fun source of bugs for a while and that would qualify as mature.) The early days of coding LISP on ARM were...fun.
|
#
?
Nov 27, 2017 02:56
|
|
|
|
| # ? Jun 5, 2024 15:12 |
|
|
LISP on ARM sounds like a special hell
|
|
#
?
Nov 27, 2017 03:44
|
|
|
iospace posted:LISP on ARM sounds like a special hell I unironically enjoyed it although gently caress LISP syntax in general. Most fun bug was the fact that integers in LISP are supposed to be arbitrary-precision, but they were represented in this commercial implementation by a four-bit type descriptor followed by a 28-bit container. Worked entirely fine unless you stored a number in memory between 2^28 and 2^32 at which point it'd mangle its type descriptor and crash at runtime.
|
|
#
?
Nov 27, 2017 05:33
|
|
|
The Phlegmatist posted:I unironically enjoyed it although gently caress LISP syntax in general. Hmm well it's always unfortunate to have a performance cliff when you start having to spill large integers to the heap but it's still probably the right trade-off vs. using a fatter value represe... The Phlegmatist posted:Worked entirely fine unless you stored a number in memory between 2^28 and 2^32 at which point it'd mangle its type descriptor and crash at runtime. wat
|
|
#
?
Nov 27, 2017 06:06
|
|
|
QuarkJets posted:I think it's pretty common for parallelism libraries to set a "do not do IO or blocking with any of this stuff" rule It's also pretty common to set a "don't spawn more parallel work from inside the parallel operation" rule. Nested parallelism is hard (if you want it to run fast, otherwise it's easy).
|
|
#
?
Nov 27, 2017 08:30
|
|
|
The Phlegmatist posted:I unironically enjoyed it although gently caress LISP syntax in general. This is why you use sum types in your integers.
|
|
#
?
Nov 27, 2017 16:07
|
|
|
Jabor posted:https://docs.oracle.com/javase/7/docs/api/java/nio/channels/AsynchronousFileChannel.html Yes, that does look like the way java is expecting me to do it, thanks! The nio async stuff is still based on threading tho so now my code is using two global thread pools and two work queues. I guess it’s probably fine, they were both implemented by people who know more about concurrency than I do
|
|
#
?
Nov 27, 2017 16:43
|
|
|
This analysis of who's moving from which language to which language unfortunately says that Go appears to be the new hotness. 
|
|
#
?
Nov 27, 2017 19:20
|
|
|
Joining the ranks of such luminaries as JavaScript, Ruby, Python, Java... Excuse you, I am not a "language hipster," I am an informed language enthusiast.
|
|
#
?
Nov 27, 2017 19:28
|
|
|
Doc Hawkins posted:Joining the ranks of such luminaries as JavaScript, Ruby, Python, Java... An "artisan coder". Mr Shiny Pants fucked around with this message at 20:01 on Nov 27, 2017 |
|
#
?
Nov 27, 2017 19:58
|
|
|
TooMuchAbstraction posted:This analysis of who's moving from which language to which language unfortunately says that Go appears to be the new hotness. did they do search for golang or go? cuz it seems they did it by search terms and uh "go" is a drat common english word
|
|
#
?
Nov 27, 2017 19:59
|
|
|
Bespoke artisanal crash-to-desktops.
|
|
#
?
Nov 27, 2017 20:00
|
|
|
Pollyanna posted:Bespoke artisanal crash-to-desktops. At least you took pride in what you made.
|
|
#
?
Nov 27, 2017 20:02
|
|
|
bob dobbs is dead posted:did they do search for golang or go? cuz it seems they did it by search terms and uh "go" is a drat common english word "Go," but in a way where the confusion probably didn't affect the results: The dang article posted:Note that I searched for exact queries by putting it in quotation marks: eg “switch from go to c++”
|
|
#
?
Nov 27, 2017 20:18
|
|
|
shucks to me for not rtfa i'm pretty sure that the goog does machine learning stuff in addition to the boolean ops tho
|
|
#
?
Nov 27, 2017 20:23
|
|
|
Isn't it a natural thing for a new language that claims some maturity to be the target of a lot of rewrites and subsequent articles after some period of time? I'd expect that same analysis to show a trend for Rust in the next 2-3 years or something like that.
|
|
#
?
Nov 27, 2017 20:33
|
|
|
He found *squints* about 5k people switching to Matlab from islands of relative sanity Python and R? I question his results.
|
|
#
?
Nov 27, 2017 20:34
|
|
|
Munkeymon posted:He found *squints* about 5k people switching to Matlab from islands of relative sanity Python and R? I question his results. He also found probable movement away from Postgresql to Mysql, if I'm reading it right. Someone tell me why that makes sense?
|
|
#
?
Nov 27, 2017 20:52
|
|
|
Munkeymon posted:He found *squints* about 5k people switching to Matlab from islands of relative sanity Python and R? I question his results. 31.5k people switching from R to C. I'm really curious now.
|
|
#
?
Nov 27, 2017 20:54
|
|
|
TheBlackVegetable posted:He also found probable movement away from Postgresql to Mysql, if I'm reading it right. Someone tell me why that makes sense? It costs less on AWS 
|
|
#
?
Nov 27, 2017 20:58
|
|
|
TheBlackVegetable posted:He also found probable movement away from Postgresql to Mysql, if I'm reading it right. Someone tell me why that makes sense? A quick google search shows a TON of articles about why Uber moving to MySQL was bad and a bunch more are simply "we designed it this we so you CAN move to MySQL from Postgres". I'm guessing its just a ton of noise in that specific search. It also probably doesn't help that pretty much all CMS software is backed by MySQL these days.
|
|
#
?
Nov 27, 2017 21:13
|
|
|
The Phlegmatist posted:I unironically enjoyed it although gently caress LISP syntax in general. Is this like undefined integer overflow but worse? Better?
|
|
#
?
Nov 27, 2017 22:33
|
|
|
CPColin posted:"Go," but in a way where the confusion probably didn't affect the results: Yeah, that methodology just opens up other error sources tho. For example the first page of results for “switch from python to node” (first example I tried) includes an article that includes that exact phrase ... in the context of explaining why the author strongly believes you should not do that thing
|
|
#
?
Nov 27, 2017 22:35
|
|
|
Kazinsal posted:31.5k people switching from R to C. Someone who's got r code that's too slow?
|
|
#
?
Nov 27, 2017 23:07
|
|
|
lovely old academic code and libraries?
|
|
#
?
Nov 27, 2017 23:09
|
|
|
redleader posted:Is this like undefined integer overflow but worse? Better? Better since it at least has the decency to crash immediately rather than causing undefined behavior. Worse because Common Lisp is supposed to convert between fixnum (24 bit integers) and bignum (arbitrary precision) automatically and anyone with a Common Lisp background would expect any weirdness to occur around 2^24. Extra worse because a 4-bit type descriptor and a 28-bit integer aren't even on word boundaries so that interpreter must have been doing some serious voodoo behind the scenes to pack in those extra bits. Which didn't even work in the end regardless.
|
|
#
?
Nov 27, 2017 23:13
|
|
|
Soricidus posted:Yeah, that methodology just opens up other error sources tho. For example the first page of results for “switch from python to node” (first example I tried) includes an article that includes that exact phrase ... in the context of explaining why the author strongly believes you should not do that thing the goog will also nowadays straight-up disrespect the quotes a lot of the time
|
|
#
?
Nov 27, 2017 23:16
|
|
|
Pretending for a second those search results are worth a drat, I'd like to meet whoever it was that supposedly switched from Rust to COBOL. I would assume it means that they had to switch because their magnetic toroids physically turned to rust.
|
|
#
?
Nov 27, 2017 23:52
|
|
|
That article posted:I also know the chain has to be ergodic and a bunch of other things, but in reality that’s basically always the case. uuuuuuh obviously that doesn't apply if the transition matrix is time-varying (which it obviously is...). The "computing the future distribution of languages" bit is complete nonsense. Just because switching to go is the current fad doesn't necessarily mean there is any space for go in the ultimate final state of the universe.
|
|
#
?
Nov 28, 2017 01:18
|
|
|
ShimaTetsuo posted:uuuuuuh obviously that doesn't apply if the transition matrix is time-varying (which it obviously is...). The "computing the future distribution of languages" bit is complete nonsense. Just because switching to go is the current fad doesn't necessarily mean there is any space for go in the ultimate final state of the universe. way more things you can assume stationarity on than you can think, if you have really totally all of the data. financial markets can be seen as nonstationary buncha weirdo poo poo or fractional brownian motion (statistics of fbm: "go gently caress yourself and die") guy prolly doesn't think of it like that tho lol not kidding about fbm being the fyad of time series btw edit: in this specific case he coulda just smoothed it
|
|
#
?
Nov 28, 2017 01:26
|
|
|
NihilCredo posted:Pretending for a second those search results are worth a drat, I'd like to meet whoever it was that supposedly switched from Rust to COBOL. Just to highlight how useless those results are, your post contains the string "switched from Rust to COBOL" and so could potentially appear in a Google search for a string of that kind. And mine does too. Twice!
|
|
#
?
Nov 28, 2017 01:31
|
|
|
Don't worry! A trained machine learning specialist has approved the technique and the results.
|
|
#
?
Nov 28, 2017 01:32
|
|
|
I don't really think the search used is affecting the results as much as y'all claim, even if I don't agree with the article's conclusion that people like Go for some reason this year. The only reason people use go nowadays is because of docker and kubernetes afaict
|
|
#
?
Nov 28, 2017 01:37
|
|
|
C is the best  NO I DO NOT HAVE STOCKHOLM SYNDROME THANKS FOR ASKING
|
|
#
?
Nov 28, 2017 01:50
|
|
|
Speaking of machine learning libraries and the scientists that write them. At work we use in one of our products the mlpack library. Really nice library. At one point I tried a little experiment: create 5 threads and run an mlpack regression in a thread. The class was created and destroyed in that thread, nothing shared, perfectly thread safe. Segfault, terminate, "timer blabla was created while another timer was active". WTF? Looking in the sourcecode I find there is a singleton object called CLI, that creates timers in a static std::map every time one of its ML algorithms are being invoked and that throws an exception if a timer with the same name already exists in the map. Which, when you make 5 threads that all invoke the same algorithm, you're bound to hit no matter what  . Fortunately the fix is easy: comment that out and use our version of the library instead of the one the distribution comes with (yes, problem was fixed upstream too, but distributions will get that next century).But then, next issue: mlpack uses armadillo (a linear algebra library) which in turn uses OpenBLAS (basic linear algebra) for some of its calculations. On my home system (Fedora 27), my coworker's system (Debian whatever) and on production system (CentOS 7) no matter how much we stress the program it works like a champ. On my work system (Fedora 27, slightly slower CPU) it crashes at the 49th serial computation somewhere in the gremm driver. Every time. Now we're gonna have to use a custom version of armadillo too, and compile mlpack against that and remove OpenBLAS from the equation completely, because some people just can't hold their pointers. Brilliant scientists. Awful programmers.
|
|
#
?
Nov 28, 2017 02:00
|
|
|
bob dobbs is dead posted:the goog will also nowadays straight-up disrespect the quotes a lot of the time And it also loooves flipping words and searching for their opposites so your results are all exactly what you didn't want. Really great when you're searching for specific technical things!
|
|
#
?
Nov 28, 2017 04:45
|
|
|
I wouldn't suspect that The Times is a spammer, but here we are: Worth mentioning - I've not subscribed to anything and followed the link that they included if I want to opt out from receiving emails. Changing these settings didn't do anything, so I've had to contact support directly.
|
|
#
?
Nov 30, 2017 12:53
|
|
|
Assuming you're getting it on one of the big email services, you should really report it as spam because it'll hurt their score on the filters and they won't take their lovely compliance seriously until people who actually want their daily whatevers don't get them.
|
|
#
?
Nov 30, 2017 15:26
|
|
|
Coworker came to me complaining about integrating a 3rd party C library - he had to manually convert from a signed to an unsigned byte array. I thought this was odd since you should just be able to cast so I went overt to show him how simple.... oh Both calls come from the same vendor. Call 1 produces a 'byte array' which is a bracketed string with comma separated signed ASCII integers code:code:
|
|
#
?
Nov 30, 2017 17:19
|
|
|
|
| # ? Jun 5, 2024 15:12 |
|
|
Why is it a string?
|
|
#
?
Nov 30, 2017 17:23
|
|