Hacker News new | past | comments | ask | show | jobs | submit | more issaria's comments login

Which is not so easy to get from what I heard of.


I don't quite get it, why do people shit on systemd on every chance?


Because we're angry.

I had no problems with sysv init since the 80s and SVR2. Did it exist before? I'm only drawing on personal experience.

I have failed to see any benefits of systemd and it has only caused me problems. Most in my circle agree with this, and I have never heard someone express gratitude that systemd exists. We feel it has been forced upon us, and we don't want to make a full time job out of maintaining our own platforms to be rid of it.

We are crotchety old men who have generated hundreds of millions of dollars (maybe more) for our employers and customers. We have never had a problem with init. Compared to ourselves, we think Lennart is a noob and examining his work leads us to conclude that he has no rational foundation of applied computing.

The software developers I've known in my career have all been professional and responsible. Our industry has zero tolerance for failures and hazards. During ten years I worked there, one place shipped one defect that I found out about, and the manager who signed off on it after incomplete testing lost his career. I deal with bad software every day and wish more of the industry had this focus on quality. I used to respect rhel because of their QA, now they hired this guy, did he even have a job before?

I wish Lennart the best in his quest to make a Windows out of what used to be Unix, with his audio mixer and cli version of 'services.exe.' Legions of misguided people who believe that Linux is the golden desktop OS for laypeople will certainly appreciate this. However I hope I never meet him because I do not want to pay his hospital costs.


My biggest problem with systemd is that it adds a new and completely unnecessary giant wall of incompatibility/incongruity between Linux and the rest of the *nix universe.

It was and is absolutely asinine and I can't believe all of the major linux distros went along with it.


It would seem that speaking ill of Poettering and/or systemd remains a sure way of garnering downvotes :)


> It was and is absolutely asinine and I can't believe all of the major linux distros went along with it.

RedHat and/or Canonical largely determine which way the wind is blowing in the Linux community, for good and bad.


What? Where did they say that in that talk? They simply showed a way to execute native code with V8, so it's easier to run node on nashorn. Stop spreading misinformation.


Anyone can check by themselves, starting at 7:25.

"Nashorn has been in development since 2010"

"Alas, only 2-3 engineers available to work on Nashorn at any given time"

"It takes a village to implement a programming language"

"ECMAScript 6 requires a significant number of changes"

"Other JavaScripts get better and better; V8, Nitro, SpiderMonkey"

https://www.youtube.com/watch?v=-JLhwsbMvjQ

Then follow from there up to the end.


Or GRAAL.js which is a lot further in implementing al the new ES6+ features than Nashorn will ever be [1]

It's really quite nice and I think there will be exiting news in this front from Oracle lab soonish...

[1] http://www.oracle.com/technetwork/oracle-labs/program-langua...


I love Graal, have been following its development since it used to be called Maxime VM.


There is no where they mentioned "replace nashorn", the main feature of nashorn is to interoperate with Java, V8 cannot do that. If you follow the development of Nashorn, they are working on ES6 features right now.

Also replace nashorn with V8 simply is a false statement, V8 is of it's own project established before Nashorn, and it doesn't even belong to Oracle, how can one replace a new project with an old one?


Entry level app at best, hackers? Unlikely.


Agreed. The site actually says "Starting with Linux on your laptop and want to know which apps you should use?"

It's great tips for beginner users, but advanced users and "hackers" waste their time scrolling through a list of apps like Firefox, VLC and Gimp.


Come on, default method in interface is a Java 8 feature, what's the coolness of C#is there?


Non-nullability is you know quite a thing. Even in it's current half-baked form. That default method interface is not something that I would touch on a day-by-day basis.


A concurrent map in my understanding, is a map that can be accessed concurrently without explicit synchronization, not each coroutine has a piece of it. Check java ConcurrentHashMap.


It's not going to happen, you not only have to fix all the legacy code, but also fix the developers.


Did you compare to python2 or python3, cause python3 is in the same league as perl6.


Regarding the lacking of generics problem, is there a way to get around it, there are always plenty of tools doing that, if the IDE can patch the syntax and support certain kind of prigma to generate the template code, then the problem is almost solved, not sure if it'll cover all cases like Java does though.


Jigsaw is not maven, nor gradle, the versioning problems should be solved by those tools. I'm getting sick of the multiple version dependency problem being brought up over and over again. That's one of the reason why OSGI is not widely adopted. You should watch some of the talks delivered by the jigsaw team.


> Jigsaw is not maven, nor gradle, the versioning problems should be solved by those tools.

Then why do we need Jigsaw at all? If the assumption is that you run Maven or Gradle anyway then what is left for Jigsaw to do? The dependency management and check will happen by those tools.


> the versioning problems should be solved by those tools

I'm not a Java developer; could you explain a bit about how Maven/Gradle solve this problem? My understanding is that what people want is something like what Node gives you—the ability to have both libfoo-1.0 and libfoo-1.1 loaded into the same VM at the same time without clashing. Do the build tools use e.g. name-mangling to achieve this?


For Maven, there is a repackaging facility with name mangling that can do this, the Maven Shade Plugin. https://maven.apache.org/plugins/maven-shade-plugin/


Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: