Athas

10 ms·

61.
by Athas 3y ago
Certainly building everything from scratch is time consuming, but why should it be difficult? Windows 2000 was developed before I became a programmer, but not too many years later (2003) I was a teenager running Gentoo, and while it was ti
62.
Solving a parallel programming problem with a list homomorphism(futhark-lang.org)
2 points by Athas 3y ago|0 comments
63.
by Athas 3y ago
Compared to Halide: * Futhark does not expose a scheduling language that gives you precise control over code generation. This is probably the main selling point of Halide. * Futhark has a much broader focus than Halide, which is mainly ori
64.
by Athas 3y ago
I work on Futhark. We hope that WebGPU-through-Emscripten is viable, but I haven't yet had the spare cycles to make sure. I did find some examples that looked promising.
65.
by Athas 3y ago
Does anyone know why the clang that comes with macOS does not support OpenMP, even though upstream clang does? I use OpenMP to teach basic parallel programming, and it is really annoying that the macOS users have to install another compile
66.
by Athas 3y ago
I thought BSL was a subset of Scheme, so it avoids most of those problems you mention. Or do I misremember?
67.
by Athas 3y ago
The downside of building in stuff is that you can't easily replace it. I don't have any VMS experience, but the versioned file systems I've studied are very far from being a replacement for what I would consider version cont
68.
In-place mapping and the pleasure of beautiful code nobody will ever see(futhark-lang.org)
1 points by Athas 4y ago|0 comments
69.
by Athas 4y ago
My impression is that Arch is not technically unusual among distributions, but is simply well-polished, documented, and very active (and has an easy way to install unvetted community packages). If this impression is correct, you still run
70.
by Athas 4y ago
Yes, it is very memory unsafe. Subverting the type system often the main source of memory unsafety in most languages. It typically means you can treat an arbitrary integer as a pointer to any other object.
71.
by Athas 4y ago
Even plain unsafePerformIO is memory-unsafe, as it will let you construct a polymorphic IORef, through which you can implement unsafeCoerce.
72.
by Athas 4y ago
> MacPorts is still alive and well ( https://www.macports.org ), and in-fact has basically all the same packages brew does. I used macOS for a few years to try it out, and I found that Macports lacked many things I needed. Ta
73.
by Athas 4y ago
> It is: using Flakes you're thrusted into a more pure evaluation mode by default, and it creates a (standard) artifact of the revision you're on: the flake.lock. Can you name a specific example of the kind of nondeterminism&#x
74.
by Athas 4y ago
> But pinning Nixpkgs alone does get you much of the way there (and for many use cases— those where the only referent on it is 'nixpkgs' or 'nixos'— does make NIX_PATH redundant anyway). What is missing compared to us
75.
by Athas 4y ago
Is this more deterministic than pointing Nixpkgs at a specific commit/tarball in the configuration? I have often done this to make reproducible builds in other Nix settings and it has worked well.
76.
by Athas 4y ago
Don't those still give you a terrible error message if you use them in a default config?
77.
by Athas 4y ago
No, the problem is that the platforms involved do not support any 16-bit float type in an ergonomic way. (The most accessible type on all the platforms, and the one used, is ultimately IEEE 754 binary16.)
78.
by Athas 4y ago
You always had to tell Futhark about the CUDA include directory at compile-time. The difference is that now you also have to tell it about it at run-time . Further, at compile-time the usual CPATH/LIBRARY_PATH environment variables a
79.
A case study in parallelisation: Advent of Code 2022, day 9(futhark-lang.org)
2 points by Athas 4y ago|0 comments
80.
by Athas 4y ago
Paredit is so good that even after taking a break from Lisp for years, as soon as I opened up an .el file to do some Emacs customisation, the muscle memory was fully intact and I was able to perform structural edits without even thinking ab
81.
by Athas 4y ago
Also by Wirth: https://en.wikipedia.org/wiki/Euler_(programming_language)
82.
by Athas 4y ago
Consider the documentation for the similar compiler flag in the OpenCL specification: > -cl-unsafe-math-optimizations > Allow optimizations for floating-point arithmetic that (a) assume that arguments and results are valid, (b) may vi
83.
by Athas 4y ago
I never understood the motivation for allowing tuples without surrounding parens. There are a few very simple functions that look cuter this way, but it constantly trips me up in more complex situations.
84.
by Athas 4y ago
Modern journals don't actually print all that much, and I'd expect the marginal cost of publishing additional papers to be very low.
85.
by Athas 4y ago
I wonder if this culture arises out of necessity. Many conferences claim to not have a set quota of papers they accept, but in practice there is a limitation to how many presentations can be accommodated given the physical and temporal lim
86.
by Athas 4y ago
> still how do you give the user the option to say "I know what I'm doing." You make configuration available. Most of these disabled-by-default protocols can be enabled by a user who really knows what they are doing (an
87.
by Athas 4y ago
If something is broken in the default installation, you'll notice quickly during acceptance testing and can go and fix it (for example by re-enabling insecure protocols). If something is unexpectedly insecure, you will probably not not
88.
by Athas 4y ago
> 1. Wasn't clear on environment/toolchain and ended up compiling for a long time just to install one package. Pretty sure I was doing it the wrong way but saw inconsistent information about what to do. I'm almost sure thi
89.
by Athas 4y ago
Yes, the next Haskell will be strict; that's generally although not universally accepted. I have however noticed that while much Haskell code doesn't make very fancy use of laziness, it is widely used for very local control flow.
90.
by Athas 4y ago
I am aware. My post was about Rust not originally being intended for much of the non-concurrent and performance-agnostic application programming it is currently being used for (e.g. the enormous amount of CLI utilities cropping up). Its

More ›