4 ms·
The title is quite confusing on what the project is. It should be "Oink: a single-file PHP library to easily build API" or something like that. Appart from tha
by p4bl0 3y ago
The title is quite confusing on what the project is. It should be "Oink: a single-file PHP library to easily build API" or something like that.
Appart from that, it's a nice project, but would benefit from better examples that actually needs an API to do things asynchronously, like a web app that needs to be able to synchronize with a server from time to time. Maybe a TODO list to keep the example short?
Because the blog and gallery examples are not really convincing: why would we depend on JS to render the page and almost do the job twice while the rendering could have easily be done in PHP directly?
- tommica 3y agoYep, more example would be useful to have, don't have to be pretty, just functional.
- gexla 3y agoOr you could read the source code. It's only 178 lines of PHP.
- 0x073 3y agoComplete undocumented and compressed lines of 178 php code. I understand the one file thing, but why no docs or more important any tests or static testing.
- gexla 3y agoThere's some documentation here... https://github.com/jcarlosroldan/oink/blob/main/documentation.md https://github.com/jcarlosroldan/oink/blob/main/documentatio... But I get your point.
- episteme 3y agoI hope this is in jest.
- gexla 3y agoWhy not? There are other people in the comments who at least scanned the code. You probably wouldn't be looking at the code if we were talking about a heavier framework, such as Laravel. That 178 lines feels dense though.
- p4bl0 3y agoI was saying the project needs more convincing examples of usage, that is, examples that makes it shine, which the current examples do not. I wasn't at all saying that how it works or how to use it is not clear. Also why would you be so aggressive? In addition to missing the point, your answer is worse than "RTFM".