5 ms·
Java is pretty much all these things, except the highly subjective "looks pretty". It's kinda funny how Java was hated for not using native widgets, and now usi
by AnIdiotOnTheNet 8y ago
Java is pretty much all these things, except the highly subjective "looks pretty". It's kinda funny how Java was hated for not using native widgets, and now using native widgets is considered a negative.
- qwerty456127 8y agoJava WebStart has been discontinued and never worked fast. JavaFX is great but it seems it's too late for it already and Oracle seems having no enthusiasm about promoting it (did they ever have any interest in anything Sun but the patents anyway?). "Pretty" is indeed subjective but it's not hard to understand what does it mean for the majority of non-geeks.
- pjmlp 8y agoDespite the Oracle hate from developers that actually never placed Java applications in production, the Java community appreciates the work of Oracle and in many domains they have delivered a better work than Sun was doing in the last years. JavaFX has been separated from core JDK, to allow for quicker development and integration into other vendors JDKs. Until now the Oracle JDK was the only one supporting JavaFX.
- qwerty456127 8y agoI hope this is going to help.
- tambourine_man 8y agoThe Java plugin, like Flash, was a security nightmare and poorly integrated with the rest of the stack. Not having a bundled set of widgets is probably an advantage, flexibility wise. People like to bash (ha!) JavaScript, but I think it’s begginer friendliness is often overlooked. Just look at how easy it is to get something done compared to Java in the browser. That and load time probably contributed to its success more than anything else.
- AnIdiotOnTheNet 8y ago> The Java plugin, like Flash, was a security nightmare Neither is inherently less secure than javascript running in a web browser. > and poorly integrated with the rest of the stack. Yeah, but, so? Maybe I'm too old and curmudgeonly but I preferred it when applications acted like applications and websites acted like websites. Now I have to deal with websites that are half application, without the responsiveness of either and built on a pile of franken-code.
- lysium 8y ago> Neither is inherently less secure than javascript running in a web browser Why do you think that? I’ve heard a lot of vulnerabilities in Java and Flash plugins but JavaScript not so much.
- jerven 8y agoBecause they where vulnerabilities in the JS engine of all browsers and they have similar issues. See the browser release notes for the last ten years. e.g. https://chromereleases.googleblog.com/2016/03/stable-channel-update_24.html https://chromereleases.googleblog.com/2016/03/stable-channel... Thing is the browser engines where are not so diligent about CVE's and they are necessary evil, while Java/Flash where optional evil. With the Flash plugin being significantly worse quality than the Java ones.
- reacweb 8y agojava plugin was a reputable good security sandbox. Features were added and some subtile security problems were found. Oracle repeatedly failed at fixing these problems because it wanted to avoid breaking old applications. The consequences of this bad management is that the reputation of java plugins is bad and they are prohibited in many enterprises. The problem is only a management problem, there were not technical reasons. The idea of having java application in a safe sandbox is perfectly viable except oracle.
- JazzXP 8y ago
- rawoke083600 8y agoThe problem came with E.E I think.. You have to edit like 10 XML files before even getting to the source code files. Granted with today's JS tooling we approaching that again :(
- pjmlp 8y agoWithout the static typing and IDE completion support thanks to XML Schema. I will take XML over JSON every time I am the one setting the rules.
- arethuza 8y agoMost editors I use (e.g. Visual Studio Code) provide validation and completion of JSON using JSON Schema - which works pretty well. I much prefer JSON to XML for most scenarios.
- pjmlp 8y agoHow do you validate comment locations?
- arethuza 8y agoWell, as JSON doesn't have comments that's not really a problem :-) NB Not having comments is perhaps the biggest problem I have with JSON when it is used for things like configuration files that will be hand crafted. 99% of the JSON I work with is generated and consumed programmatically so comments aren't really an issue.
- jstimpfle 8y agoMy favourite way to go about comments is to have them inline, as first class data members. (Not that I think either JSON or XML are good ideas. Hierarchical structures are really hard to handle).
- qwerty456127 8y ago