<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>pje</author><text>My thoughts exactly. As is common knowledge, Oracle &lt;i&gt;simply doesn&amp;#x27;t have any other positions for people with deep knowledge of Java&lt;/i&gt;. Once this project was over, there just weren&amp;#x27;t any other options than to fire the whole team.</text><parent_chain><item><author>kodablah</author><text>I don&amp;#x27;t see a big issue with this. I don&amp;#x27;t like Oracle as much as the next guy, but when the community votes to de-corporate project I think it is reasonable to lay off the people performing corporate maintenance. Surely those who voted to &amp;quot;community-ize&amp;quot; it (which I agree with) will re-hire these people to continue their effort lest they think these things just magically maintain themselves. Granted Oracle was one of those who voted. I think these are just reasonable ebbs and flows of businesses and shuttering or devolving yourself of products.&lt;p&gt;I think most of people&amp;#x27;s hate will come from hating Oracle or emotionally hating the idea of layoffs. In this particular case it&amp;#x27;s a damned if you do damned if you don&amp;#x27;t. One side wants Oracle to open everything and stop exercising control over things (e.g. their own branded JDK which was only differentiated by support and these kinds of tools). Another side lambastes Oracle for not keeping the people around to do the work. We all want less Oracle control over the JVM yet we all secretly want them to keep working on it and paying the people to do so.</text></item></parent_chain></comment><story><title>Oracle Lays Off Java Mission Control Team After Open-Sourcing Product</title><url>https://www.infoq.com/news/2018/06/open-source-jmc</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>tzs</author><text>I think that what irks a lot of people is that Oracle has almost 300 open positions in the US for Java developers.&lt;p&gt;Why lay off experienced developers instead of moving them to currently unfilled positions?</text><parent_chain><item><author>kodablah</author><text>I don&amp;#x27;t see a big issue with this. I don&amp;#x27;t like Oracle as much as the next guy, but when the community votes to de-corporate project I think it is reasonable to lay off the people performing corporate maintenance. Surely those who voted to &amp;quot;community-ize&amp;quot; it (which I agree with) will re-hire these people to continue their effort lest they think these things just magically maintain themselves. Granted Oracle was one of those who voted. I think these are just reasonable ebbs and flows of businesses and shuttering or devolving yourself of products.&lt;p&gt;I think most of people&amp;#x27;s hate will come from hating Oracle or emotionally hating the idea of layoffs. In this particular case it&amp;#x27;s a damned if you do damned if you don&amp;#x27;t. One side wants Oracle to open everything and stop exercising control over things (e.g. their own branded JDK which was only differentiated by support and these kinds of tools). Another side lambastes Oracle for not keeping the people around to do the work. We all want less Oracle control over the JVM yet we all secretly want them to keep working on it and paying the people to do so.</text></item></parent_chain></comment><story><title>Oracle Lays Off Java Mission Control Team After Open-Sourcing Product</title><url>https://www.infoq.com/news/2018/06/open-source-jmc</url></story>