crabbygrabby

6 ms·

1.
by crabbygrabby 4y ago
Really interesting take, I've had the opposite experience. I've also seen very talented c++ devs screw things up in prod that rust doesn't even allow for. Really recommend taking it more seriously, it's fun once you get
2.
by crabbygrabby 4y ago
I was in the same boat once upon a time. I actually overhauled it all but spent the next six months trying to convince 80 yr olds who self taught themselves visual basic (version 3? I think)that the code I made was faster, more sustainable,
3.
by crabbygrabby 4y ago
Just type it in yourself and discover the post is incorrect like the rest of us...
4.
by crabbygrabby 4y ago
Ok good I'm not insane lol...
5.
by crabbygrabby 4y ago
Whoever made this post um didn't type in lisp and rust into the search... They look inversely correlated with rust rising in the past few years over lisp...
6.
by crabbygrabby 4y ago
Can't reply to you depth of discussion got too long I think. Yea they didn't get kicked out entirely not banned or anything but they became "persona non grata" over stuff in their personal life. At least that's how
7.
by crabbygrabby 4y ago
I think you misunderstood me, all good. The diffeq/sciml landscape has been a WIP for half a decade with lots of pieces of it changing rapidly and regularly. But so has the rest of the ecosystem. I think we both know how often this cod
8.
by crabbygrabby 4y ago
See my above comment for clarification
9.
by crabbygrabby 4y ago
It's not a half hour package install. It's a half hour of loading everything back in to get to where you were because the runtime dropped sorry for the lack of clarity. But yea, it's real easy for pkg installs to oom people.
10.
by crabbygrabby 4y ago
They forked them. Also this is not that person. And there's more instances of this than I think you realize.
11.
by crabbygrabby 4y ago
I met a guy who got kicked away from the community because he had different political beliefs than a lot of the people there. Immediately after he got the boot he stopped contributing, they took control of his two yrs of research(multiple r
12.
by crabbygrabby 4y ago
Check the version summaries. Think it was Julia 171 or something. There's lots of bugs like that that crop up every other release. Segfaults happen all the time with FFI. But yea OOM is a killer. Julia runtime guzzles RAM, but pkg add
13.
by crabbygrabby 4y ago
I appreciate your view but seeing as how most Julia projects work this way I sometimes wonder if it's just a problem with the language itself. Not trying to be a troll with impossible expectations, but genuinely the code is unstable, a
14.
by crabbygrabby 4y ago
It's super easy to get ooms and seg. Faults in Julia. For a while there this past year you couldn't even Ctrl c to stop the Julia process. It's rough for real work imo. Fine for research.
15.
by crabbygrabby 4y ago
Theyve been at it for half a decade or so. Ignoring compilation times they shuffle the code around so frequently it's only real use imo is for the authors to publish papers and stay three steps ahead of any of it's users hoping fo
16.
by crabbygrabby 4y ago
Julia's syntax is it's greatest strength but also it's biggest weakness. Large Julia code bases without team standards are complete soup. For small to medium size projects it's all good though. Just wish the community wa
17.
by crabbygrabby 4y ago
Yea but keep in mind anytime you get a bug your session goes away so you can end up eating hours from a day precompiling. Not worth it with heavy pkgs imo. Wish they had incremental compilation like rust because most compiled Lang's ar
18.
by crabbygrabby 4y ago
It's still rough. They've been at it for yrs and it's a perpetual bed of sand... A lot of machines will fail to install it because it's so resource intense to install... Promising idea overall, maybe in three yrs or so i
19.
by crabbygrabby 4y ago
It's a pretty weird critique, llvm is becoming ubiquitous for these tasks. Can rattle off probably a dozen programming languages using it and no one is grousing...
20.
by crabbygrabby 4y ago
They kind of all are scams. It was how they got people's information preinternet. Usually the fine print will tell you they aren't even giving the car away. The only person I know who won one of those things was very greasey. Had
21.
by crabbygrabby 4y ago
Super good lay person summary. I like how this explains the underlying concepts more than the python specific stuff. Will recommend this to new comers.
22.
by crabbygrabby 4y ago
My little brother is autistic and admits he's wrong all the time. The title of this is trash.
23.
by crabbygrabby 4y ago
Definitely misleading given all the bloat and baggage adding Julia as a dependency to a project can have. It's the heaviest glue ever.
24.
by crabbygrabby 4y ago
Why are you trying to optimize for performance if you don't have a goal in mind?
25.
by crabbygrabby 4y ago
I wish they would stop overselling too. There are so many problems with trying to adopt it for real projects it isn't even funny... Good for researchers sometimes, but even then... It's got issues. Pretty toxic community too.
26.
by crabbygrabby 4y ago
Hate to say it but, this is one of the biggest tragedies of modern CS. Best bet is to use gtk, or qt, and hope the language bindings for your lang of choice aren't horrible (depending on the language you might be in tears)
27.
by crabbygrabby 4y ago
Honestly switch out while you can. Sunk cost fallacy is a hazard for business. Could wrack up a million in consulting fees for a subpar tool here.
28.
by crabbygrabby 4y ago
Complete opposite experience. Even with engineers who knew their stuff. It's been more of a burden in my opinion then a tool. Just use GitHub actions and docker.
29.
by crabbygrabby 4y ago
I've used it in industry and it was nothing short of a disaster. Only one person could fix builds, despite many genuinely brilliant engineers putting in hours to learn it. More so, the time sink... Literally, what takes 29 minutes for
30.
by crabbygrabby 4y ago
Probably not worth it. Not trying to be dismissive but genuinely, it's fine to have side effects and if it saves 1000 hrs of engineering over the life cycle of a project I'd wager it's completely worth it.

More ›