The PSF’s mission statement enshrines a commitment to supporting and growing “a diverse and international community of Python programmers,” and the Foundation ultimately decided it wasn’t willing to compromise on that position, even for what would have been a solid financial boost for the organization.
“The PSF is a relatively small organization, operating with an annual budget of around $5 million per year, with a staff of just 14,” Crary added, noting that the $1.5 million would have been the largest grant the Foundation had ever received - but it wasn’t worth it if the conditions were undermining the PSF’s mission.
The PSF board voted unanimously to withdraw its grant application.
It’s astounding that the entire modern world runs on open source maintenance and not a single big corporation bothers to throw more than a pittance at keeping them going. Like, it should be basic ethical governance that if you have a dependency on Python, you should keep the python devs fed.
feed the pythons
That would eat into this quarter’s profits
The Java EE/JakartaEE/whatever the fuck they’re calling it these days (
on various features being incorporated into the overall stack of frameworks. It’s just funny that they still have this artifact of a bygone era when people (well, companies) actively used JEE, given that it has been cast aside for literally any other Web app development stack in the last decade or so.
:frieren-tired:) specifications are governed by a steering committee with reps from various big-name tech vendors (particularly Motorola and IBM/Red Hat) whoNerd shit
For those not in the know, Java Enterprise Edition (Java EE [or JEE]) – in spite of its name – is not an “edition” of the Java language or platform, or even a paid set of extensions or anything like that. It’s a set of standards and specifications for various backing services that, together, make up a full-stack Web development platform with Java as the underlying language and runtime system. (They recently renamed it to JakartaEE for some reason or another; probably Oracle fuckery, or an attempt to distance the project from Oracle fuckery.)
To give an example of WTF I mean by “standards and specifications” versus anything that comprises an actual platform, I think a pretty good one is Java Persistence API (or JPA). JPA provides a standard interface for “decorating” your code with annotations that link fields in a data class back to a physical database table and its columns, and then provides a boilerplate code generation interface for interacting with those data classes and their associated database tables. JPA on its own doesn’t do anything but define the annotations and an interface or three; there are multiple libraries that provide the actual implementation of the interface’s functionality. For example, Hibernate is an old-school Java persistence library that was updated to conform to the JPA specification. There’s also EclipseLink, which sometimes actually works when you want it to.
For a server package to be Java EE-compliant, it has to include an implementation of JPA (along with every other similar specification or “standard” service). There are paid distributions, like IBM WebSphere and Oracle WebLogic, and free/open source ones, like Wildfly, GlassFish, and TomEE (Java EE libraries added on top of Apache Tomcat). So you get a Java-based container platform with a fuckload of standard libraries baked into it. It’s kind of sad that it took until the 2010s for them to really get their shit together and make something halfway usable, only for it to be immediately eclipsed by literally anything that wasn’t JEE.