Having seen the 2017 "Great American Eclipse" from Cape Girardeau, #MO, I know that the four or five minutes of totality is worth all the effort it will take to get there. I do not know how worthwhile it will be to travel to see a partial or annular eclipse.
Oracle eventually contributed the Hudson project, trademarks, and other “IP” to the #Eclipse Foundation, but failed to win back the community. The project was relicensed from #LGPL to Eclipse Public License, but that also failed to shift the momentum from Jenkins to Hudson. By 2016 or 2017, the Hudson project announced its demise.
As we continue to contract the family's online footprint, I don't have "cloud" capacity to try this, but I probably would not have done so anyway. I like #Netbeans for those moments when I feel "I need an IDE" ... I also have #Eclipse, but there's no "like" about that slow and bloated program.
well, "enterprise" is largely a bad word in the startup space, to be equated with slow and/or complicated.
I am having a related argument about Java. Maybe it is true that the Java ecosystem is too complicated. I was just yesterday unable to get something to work in IntelliJ and I have no idea why. It works in #Eclipse. In any case, I think the Java-naysayers probably don't know about things like https://quarkus.io/
I think there is a good argument about not using C or C++ for a startup, unless you are doing something that requires realtime, but I don't see the argument with Java.
I think Java had years of uncertainty after the Sun acquisition, and #Java 8 certainly has issues with modern practices, but Java 8 came out before K8s.
Considering #K8s came out the same year as Java 8 and #Mesos had been presented first 5 years earlier, it's easy to say that Java 8 was a missed opportunity. That said, a lot of things you would have liked to see in Java 8 came in Java 9.
To flesh that out a bit, but my current list is this: #mongodb #mysql #httpd #postgres #kafka #cassandra #tomcat #jboss / #wildfly #eclipse #java (enough to diagnose applications...honestly, with the others on the list that are built in java, I probably don't really need to do anything else with this one)
@natecull IMO, the developer and user communities need to fork the language (or better cleanroom reimplement it). In the process, a lot of backwards compatibility and misfeatures could be removed during the required java.* and javax.* renaming. . Right now, #Eclipse and many #Apache projects are one lawyer letter away from shutdown. One Java++ is named and sufficiently diverged from Oracle's #Java, those projects could transition to the replacement.
Like, how the fuck do you even edit files in #Eclipse. I've got it hooked up to !perforce. I can open a file and view the contents, but I can't actually type into it. wtf??