3 ms·
Uh-oh, I hope Julia doesn't go the way of dozens of libraries re-implementing everything, like python. I would much rather prefer it stayed the course of 1 high
by sdfhdhjdw3 4y ago
Uh-oh, I hope Julia doesn't go the way of dozens of libraries re-implementing everything, like python. I would much rather prefer it stayed the course of 1 high-quality implementation for each thing.
> most people don't need all features that come with these heavyweight packages
Why not contribute to Genie.jl an interface that is simpler then?
- moelf 4y agowell, Julia is not class-based OOP so it's kind of Unix like where packages does one thing right and you just compose them or someone makes a meta package that compose them
- krastanov 4y agoThere are caveats to that statement. Semi-formal human social decisions need to be made in order for an ecosystem to agree on a set of interfaces. Some of them are part of Julia Base, which makes it easy, but some of them emerged through a lot of community work, especially in SciML (autodiff interfaces, advanced array interfaces, statistics interfaces, file and serialization IO,). This has not happened yet in the webdev side of things (Pluto, Genie, etc do not share as much) so it is difficult to compose things well there. Edit: I removed HTTP.jl from the list as it is a lower-level library with a different set of constraints to interoperability.
- moelf 4y agoIIRC both Oxygen and Genie use HTTP.jl
- ChrisRackauckas 4y agoIt's built on HTTP.jl, so it reuses all of that code and is just a higher level interface to a basic HTTP server. Genie.jl and complete web frameworks are a completely different beast with different use cases and I agree they should be kept separate.
- soledades 4y agoIdk, it’s stretching things a bit to say web servers are “one thing.” Agree with you in general, but in this particular case, I am glad there is an alternative to Genie.jl.