dawidloubser

8 ms·

31.
by dawidloubser 10y ago
WASM is not positioning itself as a high-level application development platform. It's specifically meant to co-exist with ECMAScript (which is the app "glue"). It's meant to out-source computationally-intensive functions
32.
by dawidloubser 10y ago
WASM is going to make Rust [1] shine like nothing before. I love that all the Mozilla articles keep mentioning it together with C/C++. Unfortunately, writing Rust is an order of magnitude more difficult thatn writing ECMAScript, so hop
33.
by dawidloubser 10y ago
Java's type system and FP features are really weak compared to Haskell's :-) But it compares favourably with ES6's, until you start using ImmutableJS, and ES6 currying. Then Java lags far behind... I've always been deepl
34.
by dawidloubser 10y ago
I think you're missing the core use-case of WASM. It's not for general app development, which will stay with JS. It's meant to provide plug-able, high-performance functions for heavy computational tasks - crypto, game renderi
35.
by dawidloubser 10y ago
Hear hear! Java was on a great trajectory before being stagnated by corporations and politics. Such a pity, because now we have to re-invent it. The silver lining, is that many things usually get better the second time around. Let's se
36.
by dawidloubser 10y ago
As a Java engineer, I'm enjoying ES6/7 development much more these days. I wanted to point out, however, that Java 8/9 has excellent support for basic functional programming features, with an equally-nice syntax for lambd
37.
by dawidloubser 10y ago
Kinda like the Java VM, 20 years ago :-)
38.
by dawidloubser 10y ago
I would like to argue that, in most of these cases, it's not "code quality" that is at fault, but "design quality" (before coding) - which is often absent entirely. The problem with design, in software, is not that
39.
by dawidloubser 10y ago
It's been interesting to watch so many ECMAScript / React libraries inch towards a Functional-reactive / streams-based paradigm. I can't wait to see which one becomes the de-facto standard, like how Redux is currently th
40.
by dawidloubser 10y ago
Will this, by any chance, increase the number of open-source apps available in f-droid? Every now and then, I spot a wonderful app that is only not available due to dependencies on one or two proprietary Google APIs or components. I'm
41.
by dawidloubser 10y ago
Life, arguably, is a competition. Evolution inherently rewards winners.
42.
by dawidloubser 10y ago
...said nobody before the Y2K bug...
43.
by dawidloubser 11y ago
I do enjoy using Atom as an everyday editor for ECMAScript / React apps, where the convention is to have many very small files. ES6 + Hasklig font + Ligatures make for a particularly visually-pleasing coding experience. Unfortunately,
44.
by dawidloubser 11y ago
I'm not trying to be facetious, but do you literally just mean Haskell? Because none of the languages widely used in corporate / industry do. I'd settle for 1990s tech over 1970s tech any day when it comes to contracts (APIs)
45.
by dawidloubser 11y ago
Sure, but that is incredibly weak from a typing point of view, and not compiler-checked in most languages. You have no clean way of describing multiple pre-conditions (refusal reasons), or to evolve those over time in existing systems, with
46.
by dawidloubser 11y ago
Absolutely not - the people who do that, don't understand the difference between refusal (precondition not met), and failure (unexpected system error). In your particular case above, I would never let IOException leak "up&quot
47.
by dawidloubser 11y ago
I concur. Many people have an insufficient understanding of contracts - especially concerning the difference between refusing a service, and failing because of an error. An inherent requirement for any contract language is a signal to re
48.
by dawidloubser 12y ago
Only if you don't understand XML. * XML has a formal, class-based description language (XML Schema) with strong typing, polymorphism, and - best of all - self-descriptiveness. * Languages like Java have a seamless, bidirectional mappin
49.
by dawidloubser 12y ago
I've had some terrible experiences with migrating, and maintaining, Java EE apps before. But every single one of those were caused by how the teams built the system, and not by Java EE itself. The added complexity, and choices, imposed
50.
by dawidloubser 12y ago
I've also suffered a lot of pain in trying to get libraries that were not design for OSGi (i.e. legacy) to work well. However, when having the luxury of implementing a clean set of services from scratch, OSGi is lovely. We run a large
51.
by dawidloubser 12y ago
Dropwizard also requires a container to run. Only difference is, they are bundling a particular container (Jetty), as opposed to the model of deploying into a container that you set up.
52.
by dawidloubser 12y ago
I wish I wasn't at work right now, but I'll bite. Watch this space...
53.
by dawidloubser 12y ago
One of the strenghts of the Java platform is the separation of vendor-neutral standards (e.g. JAX-RS, and all the REST concepts, and annotations, it provides) and particular implementations (e.g. Jersey). Java EE is a collection of such sta