4 ms·

The Go team has resisted (deferred?) defining APIs for many common protocols and formats (e.g. LDAP, Websockets). These will be necessary for widespread enterp

The Go team has resisted (deferred?) defining APIs for many common protocols and formats (e.g. LDAP, Websockets). These will be necessary for widespread enterprise adoption. Third parties libraries, offering arbitrary APIs, and maintained by volunteers, don't pass muster. Perhaps this work should be undertaken by committees outside the Go team, as it has limited resources.

nine_k 7y ago
Why can't this be served by established third-party libraries? Java did not have a good ORM, or a good dependency injection framework in the standard library for ages; everybody just used Spring.
- networkimprov 7y ago
  If the third party is a major IT vendor, perhaps. But lack of specs slows adoption, generally speaking.
- niftich 7y ago
  Spring is a collection of frameworks that impose their own structure and control flow so that one can focus on the parts of the design that are unique to one's situation. The Go language and standard library and the Go community have a very different mindset on delegation, structure, and control flow, so frameworks in the style of Spring or Rails aren't as widely used or popular. Go has also long based their packaging around the idea that locations of source code and the identity of a package are strongly bound. This meant that random github-hosted libraries were easy to pull in, but it also meant that people did pull in all sorts of random github-hosted libraries. In Java programming, it's more common to use a modest number of high-quality libraries and frameworks (which may, in fairness, have a lot of transitive dependencies), but not as common as it is in Go or Node to use a large number of direct dependencies sourced from all over the web.
- cabraca 7y ago
  Because John Doe the Maintainer is not offering Support for his third-party library. SpringSource/Pivotal was/is offering that for Spring. Redhat is offering Support for hibernate. Enterprise does not care if there is A solution. Enterprise cares if there is a SUPPORTED solution.
  - nine_k 7y ago
    An established library usually has a bunch of maintainers from big companies that are investend in that library. You know, most open-source code by now gets written for money as a day job.
    - cabraca 7y ago
      and the enterprise doesn't care as long as they don't offer them a support contract.
- ungzd 7y ago
  Java has javax.persistence as a standard interface for ORMs, almost in standard library, and third-party ORMs use it.

nine_k 7y ago

Why can't this be served by established third-party libraries? Java did not have a good ORM, or a good dependency injection framework in the standard library for ages; everybody just used Spring.

networkimprov 7y ago
If the third party is a major IT vendor, perhaps. But lack of specs slows adoption, generally speaking.
niftich 7y ago
Spring is a collection of frameworks that impose their own structure and control flow so that one can focus on the parts of the design that are unique to one's situation. The Go language and standard library and the Go community have a very different mindset on delegation, structure, and control flow, so frameworks in the style of Spring or Rails aren't as widely used or popular. Go has also long based their packaging around the idea that locations of source code and the identity of a package are strongly bound. This meant that random github-hosted libraries were easy to pull in, but it also meant that people did pull in all sorts of random github-hosted libraries. In Java programming, it's more common to use a modest number of high-quality libraries and frameworks (which may, in fairness, have a lot of transitive dependencies), but not as common as it is in Go or Node to use a large number of direct dependencies sourced from all over the web.
cabraca 7y ago
Because John Doe the Maintainer is not offering Support for his third-party library. SpringSource/Pivotal was/is offering that for Spring. Redhat is offering Support for hibernate. Enterprise does not care if there is A solution. Enterprise cares if there is a SUPPORTED solution.
- nine_k 7y ago
  An established library usually has a bunch of maintainers from big companies that are investend in that library. You know, most open-source code by now gets written for money as a day job.
  - cabraca 7y ago
    and the enterprise doesn't care as long as they don't offer them a support contract.
ungzd 7y ago
Java has javax.persistence as a standard interface for ORMs, almost in standard library, and third-party ORMs use it.