Hacker Newsnew | past | comments | ask | show | jobs | submit | sebak's commentslogin

The article seems to be about Java vs Python. But it really only talks about static vs dynamic typing. Not only has everything about that subject already been said 1000 times. It's also not Java-specific. Java sucks IMO not because of static typing, but because of the 'If you have a problem, add more OOP'-mentality which has given us Java EE. About any argument he makes pro-java is also valid for something like typescript. But with typescript you still have the freedom of a scripting language for the parts where it makes sense.


Really good point. Replace every mention of Java in the post with any statically typed language, and he definitely has a point. He doesn't argue that Java doesn't suck.


Unfortunately, the situation hasn't improved much. Besides, even if you get it set up, the quality of the recognition isn't even close to the one from Google.


The main reason there is a fetish for these micropackages is a fetish for github stars. The formula seems to be: Overly generic + Simple + Javascript = Lots of stars.

That being said, there is something to be said for using these micropackages. Left padding a string is easy, but you might just have forgotten about that one edge case where in browser X and language Y you have to do things different. It's not really the case here, but things that seem simple at first often turn out to be hard because of some edge cases. One might hope these edge cases are solved if they use a library.


Javascript is in fact special because it's one of the few languages where the developer can't choose the version of the language to use. It's dictated by users with 4 year old browsers.


Execpt for server-side languages that's nearly always the case


You can quite easily choose your version. There are virtual hosts out there supporting any version of anything. This problem is largely solved.


For scripting languages, sure. For compiled languages, you can choose whatever version you want, since the end user gets a binary blob instead of source code (and even if they're building from source, their package manager should be able to download the required build dependencies for them).


Where? Java has such short maintainable cycles that Java 7 was dropped before Java 8 became used, and compiled languages (think C, C++, Haskell) always work.

Are there any other languages relevant for non-server usage?


That's nearly never the case, unless you are running uncompiled scripts downloaded from the internet with no version manifest, in which case that's also horrible.


Only: there's no real-time db support like what Meteor with livequery does. The term 'real-time' is abused a lot here. Not only does neither Meteor, nor feathers offer real-time in the real meaning of the word. A better word is 'reactive'. But feathers just provides the very basic infrastructure (basically just websockets). Meteor also supports any type of DB, but only Mongo comes with reactivity... (Although their 'apollo' project is looking to change this).


Actually, for most use cases, newest update wins is sufficient if it can be done on a fine granular basis (one property of an object/document). It's what web applications have been doing for forever and being a 'realtime' framework doesn't change this if your use case isn't something like google docs.


How does it compare to Meteor? And about the claim: 'exceptionally fast'. What does this mean? Compared to what? Any benchmarks?


deepstream.io (in difference to Meteor) isn't a full framework. The server can easily connect to a wide range of databases, caches or messaging systems. Similarly the client library can be used with React, Angular, Knockout or whatever else your heart desires.

In terms of speed, please find performance test results here http://www.deepstream.io/info/performance-overview.html as well as a test harness that allows you to replicate them.


Related: the meteor people announced they'll be working on this problem. http://info.meteor.com/blog/reactive-graphql


1) Do we know if it will be more widespread? Although the stronger stuff is also illegal in the Netherlands, it's very easy to find and I don't think the Netherlands have more drug addicts then another country (no source for this, just my opinion how I know the country).

2) Is it a problem if it's more widespread? Some stronger stuff can be used responsibly (for example MDMA). Just like only a small portion of alcohol users have alcohol problems. You also got stronger stuff like heroin which is very addictive, but then there's still common sense. Whether it's legal or illegal, I can get it very easily where I live. Yet, I don't take it because I know it's not good for me.


The Netherlands have quite a bit of "drug tourism", with people from across Europe going there to party and/or bring some stuff back home--so small wonder that it's quite easy to find pretty much anything there.

As for whether usage would get more widespread, I believe it's to be expected, since legalization means more resellers, more legit businesses that you are not reluctant to deal with, and a de facto approval from governement that the stuff is clean, so less fear of poisoning.

> Whether it's legal or illegal, I can get it very easily where I live. Yet, I don't take it because I know it's not good for me.

Not everyone got the connections, and not everyone use good judgment. That's the whole point: to what extent can society decide what to authorize and what to forbid.


Here in Europe, I asked around to some firms like Aston Carter and Computerfutures recently. They had 0 requests from customers for React and A LOT for angular. Now these work mainly for enterprise companies which are hard to convince of a new technology. So all of these companies will transition much easier to angular 2 (just because they know the name 'angular') then to react.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: