oelang

9 ms·

31.
by oelang 10y ago
One small correction, they're funded by the Swiss taxpayers and the European union.
32.
by oelang 10y ago
The evidence is that all high performance garbage collected languages use some form of generational collectors. These implementations aren't made by idiots. for a deeper discussion see: https://www.infoq.com/presentatio
33.
by oelang 10y ago
All talk & no benchmarks. If reference counting with cycle detection was faster, the jvm & clr would use it.
34.
by oelang 11y ago
This project has been discontinued. But fear not, a new scala-native is on the way, Denys Shabalin a phd student at EPFL is working on completely new implementation of scala-native. His previous work, scala offheap, a way to use off-heap me
35.
by oelang 11y ago
I would add 'Scala in depth' to the book recommendations, it's similar to 'Effective java', the book you need after you have used the language for more than one year.
36.
by oelang 11y ago
> As a programmer who is not a physicist Let me stop you right there...
37.
by oelang 11y ago
Intel recently contributed improved auto-vectorisation for artithmetic to the hotspot compiler. Auto-vectorisation of move instructions has been in hotspot for a few years.
38.
by oelang 11y ago
The 20% comes from personal experience, maybe I should have said 'close' but that can also mean anything. Basically this is an area where the hotspot heavy duty compiler (C2) does the same optimizations as gcc or llvm. I would say
39.
by oelang 11y ago
Floating point calculations are only guaranteed to be platform independent when you use the 'strictfp' modifier.
40.
by oelang 11y ago
"Java's issues with floating point arithmetic in high-performance scientific computation" Can someone explain this?
41.
by oelang 11y ago
Meh, they dismiss java & pypy very quickly but they don't understand that these languages require warm-up. If you benchmark runs in less than 2 seconds half of the time measured is starting the runtime, profiling & compiling co
42.
Compilers Are Databases [video](youtube.com)
84 points by oelang 11y ago|35 comments
43.
by oelang 11y ago
I don't think it's meant to be used directly. It's a minimal api (just 4 interfaces) that can be used by various reactive frameworks to interoperate with eachother.
44.
by oelang 11y ago
And in scala it's just listOfTxnAmounts.sum or listOfTxnAmounts.max, long live typeclasses (but that's too complicated for 'normal' programmers right?)
45.
by oelang 12y ago
We've had dynamic OO+FP languages for a very long time but only in the last 10 years have we seen them with static type systems. I really like clojure (though I haven't used it in anger) but I think you're wrong when it comes
46.
by oelang 12y ago
Dispatch was one of the first libraries for scala, it's not really fair to use it as an example. The latest version of dispatch doesn't have that many operators anymore. http://dispatch.databinder.net/Combined+Page
47.
by oelang 12y ago
If you compare Scala other recently released languages (swift, kotlin, ceylon) they're all kindof similar, some claim to be less complex but imho aren't. Functional + OO is becoming the norm: the C# team is considering to add patt
48.
by oelang 12y ago
The author seems to think that java 8 lambdas are faster than scala lambdas. This isn't strictly true. Java 8 spins the inner classes for lambdas at first use, this gives them a performance boost at startup (loading tons of tiny classe
49.
by oelang 12y ago
The first thing that I actually thought about when I read this was junit hamcrest matchers, sure it's concise but I don't consider it readable at all. The limited expressivity of java really gets in your way. With scala you can wr
50.
by oelang 12y ago
The problem is that they add a new language feature for every new use case instead of trying to make features fit together in a nice compact core & building on top of that core (in other words 'modern language design'). System
51.
by oelang 12y ago
PSHDL is incredibly low-level & basic, afaik it doesn't even have functions & you can't define your own datatypes. I think it's a mistake to make a HDL language that aims to be 99% synthesize-able. I didn't write
52.
by oelang 12y ago
Because reasoning about hardware is hard it's important to be able to rely on simulation. I'm not saying that all issues can be caught/detected in simulation but many can. In most designs 90% of the code (typically the synchr
53.
by oelang 12y ago
My point was that the first optimizing compiler isn't comparable with what is expected of a modern compiler, so please don't compare their code & memory footprint. With the first fortran compiler it was garbage in, garbage out
54.
by oelang 12y ago
I think verilog (and mostly systemverilog) is beyond saving. Systemverilog has a spec bigger than c++ and it's full of broken, unused features or features that aren't compatible. Over the years they have added any feature that som
55.
by oelang 12y ago
"it generated quite good machine code, almost as fast as the hand coded one" I'm sorry but this is complete bullshit. What is expected of a compiler these days (SSA, advanced instruction scheduling, smart inlining descisions)
56.
by oelang 12y ago
I tried it, it's not flexible enough for my needs.
57.
by oelang 12y ago
Many people here don't seem to understand what is meant by backwards compatibility in the context of the JVM. Scala has very good source compatibility, this means that scala code from 2012 compiles just fine with the latest scala compi
58.
by oelang 12y ago
It's too easy in scala to create a giant mudball codebase where every file depends on half the project. Managing the compile graph is almost impossible when you have 20 hackers on the same codebase. Sometimes I wish that scala had some
59.
by oelang 12y ago
Is this the first mayor scala release that doesn't introduce a huge language or library change? Transitioning to 2.11 should be smooth, aside from some library deprecations not much has changed.