14113

11 ms·

61.
by 14113 10y ago
In certain circumstances, new languages can help software engineers to get high performance. For example, the lift project at the university of Edinburgh. It's a skeletal (think functional, but on the immutability/higher order fun
62.
Could a Neuroscientist Understand a Microprocessor?(journals.plos.org)
1 points by 14113 10y ago|0 comments
63.
by 14113 10y ago
I guess the counterexample would be library functions that look like: foo :: (BarMonad m, BazApplicative b) => ConfigurationStructure t -> (b -> m t) -> [b] -> t You can figure out a little of what it does, but how
64.
by 14113 10y ago
There's a difference between speed and correctness. If you promise something in the spec (e.g. unreachable control flow not mattering), in practice, that promise should be upheld. If it's upheld with a 32x slowdown (e.g. warp dive
65.
by 14113 10y ago
Edwin didn't coin it - but he did popularise it: https://twitter.com/edwinbrady/status/384671269490540544
66.
by 14113 10y ago
I don't know anything about scholarships, but Wikipedia definitely partners with universities to help train people to edit Wikipedia and improve the rate of Scholars contributing, e.g.: https://en.wikipedia.org/wiki&#x2
67.
by 14113 10y ago
The variable accessor is a function of type Variable -> Field, which the function sum is calling. Because of that, the function sum is impure, as it's calling an impure function. I would argue that the object is just a wrapper aroun
68.
by 14113 10y ago
I think it's possibly that the journalists don't actually know the sector beyond the big "flashy" names, like ARM or Sinclair.
69.
by 14113 10y ago
I think it rather means you should retract your statement.
70.
by 14113 10y ago
Haskell terminology is based on the mathematical underpinnings of its type system. It's due to this that those unfamiliar with the maths often have trouble at first grokking the terminology. It's not that Haskell shut itself off,
71.
by 14113 10y ago
No tools available, or at least, none that are easy to use. It's the classic parallelism problem: tools are either too low level (e.g. CUDA/OpenCL for the GPU space) for day to day developers to leverage effectively, or too high l
72.
by 14113 10y ago
On the topic of suggestions for future work, and discussion of time complexity proofs, would any of the techniques presented here [1] be useful? As far as I understand their techniques would be quite applicable (and similar to what you&#x27
73.
by 14113 10y ago
Rather humble of you ;)
74.
by 14113 10y ago
How you you encode "dimensionless" quantities within such a system?
75.
by 14113 10y ago
You write OpenCL if you want to target anything other than AMD/NVIDIA/Intel. If you're writing code for an embedded application (with some heterogeneous core), or for a mobile application, you absolutely have to write OpenCL
76.
by 14113 10y ago
I would expect a developer to fully look into the bottlenecks in their application before applying something like this. For example, if they quite often have complex, multi-stage image processing pipelines, then offloading the entire pipeli
77.
by 14113 10y ago
Yes - one of the classical ways of computing betweeness centrality is to calculate the number of shortest paths passing through each edge. In this case however, he's only computing the shortest paths to/from a single vertex.
78.
by 14113 11y ago
I wonder if that could just be poor quality OpenCL implementations on CPUs rather than an inherent limitation of OpenCL?
79.
CUDA 8 Features Revealed(devblogs.nvidia.com)
2 points by 14113 11y ago|0 comments
80.
by 14113 11y ago
Read the essay under the comic.
81.
by 14113 11y ago
I have a feeling that there might be some research along those lines here: http://homepages.inf.ed.ac.uk/cdubach/
82.
by 14113 11y ago
Reddit has a surprisingly strong/large pro-trump subreddit: /r/TheDonald, which seems to pop up on the front page with alarming regularity.
83.
by 14113 11y ago
It's likely the areas of focus that this list is taken from - there is a lot of AI/Software engineering/Complexity theory, but relatively little e.g. programming languages theory, or compiler optimisation
84.
The Post Correspondence Programming Language: Domino-Oriented Programming(davidlazar.github.io)
49 points by 14113 11y ago|4 comments
85.
by 14113 11y ago
I was slightly hoping that it would be this: https://davidlazar.github.io/PCPL/
86.
by 14113 11y ago
I'm not sure you understand - I mean they won't actually provide an OpenCL runtime/compiler. It's not that the code won't be slower/less performant, it's that it won't actually be possible to run it a
87.
by 14113 11y ago
According to an Intel employee I spoke to, OpenCL won't be available from day one on knights landing - all it will support will be OpenMP and MPI. Apparently they're the two main libraries which their target customer (HPC) require
88.
by 14113 11y ago
Out of interest, is Scotland a popular/common holiday destination for Dutch people? When driving around the highlands last summer I found that almost every foreign car had Dutch number plates, and I was wondering if it's just unco
89.
by 14113 11y ago
It entirely depends on how you want to program your GPU. If you want fine grained control, you should really use raw OpenCL/CUDA. If however you need something higher level, it may be better to choose one of a number of DSLs that are a
90.
by 14113 11y ago
I think it might not cover them, going by this: http://hentenaar.com/dont-learn-c-the-wrong-way

More ›