Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
Athas
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
36 ms
·
361.
▲
by
Athas
8y ago
Linuxbrew, like Homebrew, is useful for non-invasive non-system/infrastructure packages. Compared to system package managers, it is (arguably) simpler to use and contribute to, and often has more up-to-date packages (especially compar
362.
▲
by
Athas
8y ago
I had a suspicion that the problem was that maxiters was set fairly low (16). For the Mandelbrot sets I'm used to, this would result in relatively little computation (over a hundred iterations is more common). To investigate this h
363.
▲
by
Athas
8y ago
I'm a bit surprised to see that GPU Mandelbrot is only at best x75 faster than (sequential?) CPU. Does Julia just generate really fast (multicore/vectorized?) CPU code? Does it also count communication costs? Fractal computat
364.
▲
by
Athas
8y ago
> However, one problem with it is that a polymorphic type, such as [] of kind "* -> ", or a function like map of type "forall a b. (a -> b) -> [a] -> [b]" really only works with boxed types. Can you expl
365.
▲
by
Athas
8y ago
I'd argue this is a misfeature. Different users have different needs, but I really like knowing that especially my basic "view a file downloaded from the Internet"-applications have a limited attack surface, even if that mea
366.
▲
Futhark 0.7.1 released, now with C# back end and efficient histograms on GPU
(futhark-lang.org)
1 points
by
Athas
8y ago
|
0 comments
367.
▲
The Futhark Debugger
(futhark-lang.org)
70 points
by
Athas
8y ago
|
3 comments
368.
▲
by
Athas
8y ago
Pointers are not even necessary for writing operating systems or memory allocators. The Oberon system writes those low-level components using intrinsic peek/poke functions (like some ancient BASIC!) that are recognised specially by th
369.
▲
by
Athas
8y ago
> Both Elm and Standard ML have additional type constraints for numbers and comparable types that aren't implemented in terms of a user-definable type constraint like Haskell's typeclasses. That's not really true. Standar
370.
▲
by
Athas
8y ago
I agree. It seems to be based on having quite specific information about the structure of the package path based on the service it references. For instance, I assume that github.com/user/v2 will refer to version 0 or 1 of the &#
371.
▲
by
Athas
8y ago
I'm surprised the site died. It looks like a static website, and even a small webserver in a default configuration can serve thousands of files per second.
372.
▲
by
Athas
8y ago
Linux has supported x86-64 in long mode since 2001, well before the processors were available two years later.
373.
▲
by
Athas
8y ago
Thanks, this looks about as I expected. The real problem occurs when you have an array of union types, where sum of the union cases are themselves way, which it does not look like Julia does anything clever about (because it's not eve
374.
▲
by
Athas
8y ago
> For example, the fact that an array of unions such as Array{Union{Missing,T}} is represented in memory as a much more efficient union of arrays is a perfect example of where a clever compiler can make the logical thing to do also the e
375.
▲
The Present Futhark Package Manager – A Package Manager Inspired by Vgo
(futhark-lang.org)
1 points
by
Athas
8y ago
|
0 comments
376.
▲
by
Athas
8y ago
I don't think the lockfile is a big problem (and I don't have enough experience with lockfile-based systems), but if you already have some other file that can serve the same purpose, isn't that nicer than having two? It also
377.
▲
by
Athas
8y ago
I think reproducible builds are more important than having security problems fixed behind your back. It's not like vgo makes it hard to upgrade all dependencies to their most recent version - it's done automatically with a single
378.
▲
by
Athas
8y ago
> I think it's less that Go has significantly different needs, but it's more that people overestimate what their actual needs are. I think you are right. And I doubt it hurts that SAT solving is a fun problem! My main package
379.
▲
by
Athas
8y ago
There are lots of small differences, but I would say there are two major: * Semantic Import Versioning. A package is identified by some name. I think vgo calls it an "import path", but I have also seen "package path" u
380.
▲
by
Athas
8y ago
Why do you think vgo wasn't built on the nontechnical research carried out by dep? In fact, that's normally what I would assume would be the purpose of something branded an "official experiment" - the code will for cert
381.
▲
by
Athas
8y ago
Vgo has certainly been a disaster from a communication and community point of view. From an outsider perspective, it looks like a case of maintainer arrogance, and it is hard to believe that Go really has needs that are significantly dif
382.
▲
by
Athas
8y ago
Hell, you don't even have to go to slicing for language-supported multidimensional arrays to make sense. Simply being able to index with a[i][j] is so much nicer than the manual flat addressing a[i*n+j] that you end up with in C. (a[
383.
▲
Homebrew is the best thing about macOS
(sigkill.dk)
3 points
by
Athas
8y ago
|
0 comments
384.
▲
by
Athas
8y ago
Oh yes, I suppose that might work. I've been using lots of local memory for facilitating communication and caching, but never made the connection that the compiler might map non-addressed local variables to uniforms.
385.
▲
by
Athas
8y ago
Nice post! Is there a way to directly use uniform variables in e.g. OpenCL, or is it up to the kernel compiler to determine that some variable is wavefront- or group-invariant?
386.
▲
Futhark 0.6.1 released – High-performance functional programming on the GPU
(futhark-lang.org)
42 points
by
Athas
8y ago
|
4 comments
387.
▲
The Computer Language Benchmarks Game
(benchmarksgame-team.pages.debian.net)
3 points
by
Athas
8y ago
|
4 comments
388.
▲
Futhark: Python gotta go faster
(pepijndevos.nl)
1 points
by
Athas
8y ago
|
0 comments
389.
▲
by
Athas
8y ago
The rule is simple to learn and perfectly consistent once you know it, even to a human programmer. This is in direct contrast to mathematical notation, which remains ambiguous and context-dependent forever. While it's been over a deca
390.
▲
by
Athas
8y ago
> Am I correct in assuming that you can still (easily) obtain, inspect and profile the Futhark-generated OpenCL code using the usual tools? I suppose a sensible workflow could be using Futhark to get as far as you can and then hand optim
More ›