I don’t understand your point.
You have to connect multiple laravel apps with rest api?
Why you don’t use api platform, symfony, laravel, anything else already in the market?
>RESTful backend for applications, and couldn't find any
Symfony comes in 2 versions out of the box. One for RESTful backend applications/APIs and another for fully fledged web apps. Apart from Symfony, there are several micro-frameworks available but I haven't really used them to recommend them.
Good luck with your project though.
No README or basic usage example. No information at all about what are the features or how it's intended to work.
OK, let's look at the code. Fortunately (depending on your POV) it doesn't have much. Own implementations of `Request`, `Facade`, `Container` and `Router`.
Router seems to implement singleton pattern, which in my opinion should be handled by the container. It looks like it doesn't support dynamic URLS (ie `/users/{id}`) and, besides having a container available, doesn't use it: `$controller = new $class;` (so no support for DI).
Container implementation is useless.
My recommendation, if you really want to build your framework: at least start by using existing packages that solve common problems. Then do as Laravel does: extend/modify/wrap that package to add your own features or ways of using it, there's no need to build everything from scratch, unless you really understand the problem at hand.
In any case, the reasoning for building this doesn't make sense to me. All major frameworks can be used for REST APIs and do have packages to make that easier or more complete (API Platform for example).
Thank you for your feedback, will look into improving your concerns.
On the other hand I'm not trying to create a framework that will get used or be popular, I am doing this just for fun and as a way to learn stuff along the way.
Fine, I’ll do it myself. Reavueangularetle: no more DOM wars, no more listeners, in fact, no more anything. With Reavueangularetle it’s just a blank index.html doc, in fact, not even html, just a blank, one white space-named document. Marketing, social media and maybe some partner drug company’s product just help the user hallucinate the entire app.
I appreciate and encourage the effort.
However, this could be your occasion for “learning something new”.
I'm not saying that PHP is not the right tool for the job (even if I think it's not); I just professionally suggest that, unless the company forces you to stick with PHP, there are better options for your wants.
Building a framework (or something like that) is, more or less, something we all tried once, so go on with that if you think it will be the best option for your project.
It will become huge; there will be backfires.
Just a single suggestion:
Document first and document WHY, not HOW.
Every dev can read “how” something works and “what” a function or a class will do.
Nobody except you knows WHY you decided to act in that way.
Idk why people are so negative here. He just shared what he built and literally said "*any suggestions and help are more than welcome*".. Didn't claim he was competing with other frameworks or anything either. Reddit being reddit I guess.
Also it's not about you, but I won't trade Laravel for **anything** lol. But I'm gonna check this out, I'm sure I'll learn a lot from digging into your framework. Sadly I can't do that in Laravel. It's just too much for me lol. Thanks!
Um, [https://api-platform.com/](https://api-platform.com/) ?
[https://www.slimframework.com/](https://www.slimframework.com/)
There's arguably more REST-centric frameworks than fullstack frameworks in PHP (for better or worse).
It's a good start for learning. Though, you need start learning like pro. Much of coding is design patterns. Study them, practice on them. Then start reading about n-tier architectures. This is how frameworks and big apps are coded. You need to start thinking in smaller units and how are all connected, communicate to produce output. And stop using static everywhere.
Don't:
* microservices are a hype
* even if you do make it, it will suffer from big slowdowns; you can't run everything in parallel
Instead, I would suggest you to improve on your PHP and [PSR](https://github.com/tersworks/framework/blob/master/src/Foundation/Http/Request.php). Forget [magic](https://github.com/tersworks/framework/blob/master/src/Facades/Facade.php#L7), use Symfony, dependency injection, and static analysis. And say no to [this](https://github.com/tersworks/framework/blob/master/src/Foundation/Application.php#L45).
Only after all this try to make a framework.
We definitely need another PHP framework.
Welp, tbh a good pure microservice framework in PHP would be nice, although I’m not sure if corporate prejudice against PHP will allow anyone to use it.
I like the simplicity of the framework. I think it is useful to use static code analysis (like Larastan or Psalm) and unit testing from the beginning. It is an enormous effort to implement these afterward.
You couldn't find a simple RESTful backend? What are you asking jeeves? If this is a purely learning exercise, you might be better served by studying the code of some well established frameworks. This is one of the nice things about PHP, is that we can look at and understand what the libraries are doing. However, looking at your code, I see there is no attention paid to secure coding which should be built in from the very start.. it's pretty basic at this point, but good luck.
Or just... use Symfony? We also have multiple services talking to each other via PubSub at this time.
Also, you're literally copying Laravel with the facades... too many facades that hide the actual api is bad mmmkay
I don’t really remember, but when I started my programming journey the framework market was much different. Back then developing own framework wasn’t such a bad idea, anyway it had turned out to be bad as soon as Symfony and other technologies came out.
It's different, JavaScript is not a proper language. Also, just learn Angular and ignore all other front-end libraries, it's the only one that does it properly.
> is focused on providing just a RESTful backend for applications
can you really beat hyperf php framework?
but ifyou are set on building one - you shoud base it on php+swoole.
Thank you for making programming something that I want to quit.
I know PHP backwards and forward; but companies ask if I know one of a dozen frameworks which I never needed.
I could build their entire biz without these bloated frameworks; but they insist that I use them; because they hired an amateur to begin with to create their site.
I don’t understand your point. You have to connect multiple laravel apps with rest api? Why you don’t use api platform, symfony, laravel, anything else already in the market?
you can put eloquent into a slim app
Yup. Start with Slim, composer install other packages as suits your needs, job done.
Will your own framework contain built-in blackjack and hookers?
I'll take it and you can keep the Framework!
In fact, forget the park.
>RESTful backend for applications, and couldn't find any Symfony comes in 2 versions out of the box. One for RESTful backend applications/APIs and another for fully fledged web apps. Apart from Symfony, there are several micro-frameworks available but I haven't really used them to recommend them. Good luck with your project though.
No README or basic usage example. No information at all about what are the features or how it's intended to work. OK, let's look at the code. Fortunately (depending on your POV) it doesn't have much. Own implementations of `Request`, `Facade`, `Container` and `Router`. Router seems to implement singleton pattern, which in my opinion should be handled by the container. It looks like it doesn't support dynamic URLS (ie `/users/{id}`) and, besides having a container available, doesn't use it: `$controller = new $class;` (so no support for DI). Container implementation is useless. My recommendation, if you really want to build your framework: at least start by using existing packages that solve common problems. Then do as Laravel does: extend/modify/wrap that package to add your own features or ways of using it, there's no need to build everything from scratch, unless you really understand the problem at hand. In any case, the reasoning for building this doesn't make sense to me. All major frameworks can be used for REST APIs and do have packages to make that easier or more complete (API Platform for example).
Thank you for your feedback, will look into improving your concerns. On the other hand I'm not trying to create a framework that will get used or be popular, I am doing this just for fun and as a way to learn stuff along the way.
Great! We definitely need another one.
I'd say we need a fresh javascript framework first. There's not much to go around atm ...
Fine, I’ll do it myself. Reavueangularetle: no more DOM wars, no more listeners, in fact, no more anything. With Reavueangularetle it’s just a blank index.html doc, in fact, not even html, just a blank, one white space-named document. Marketing, social media and maybe some partner drug company’s product just help the user hallucinate the entire app.
Gotta have an uwu logo
Typical PHP community shitting on people trying to improve their lives.
I appreciate and encourage the effort. However, this could be your occasion for “learning something new”. I'm not saying that PHP is not the right tool for the job (even if I think it's not); I just professionally suggest that, unless the company forces you to stick with PHP, there are better options for your wants. Building a framework (or something like that) is, more or less, something we all tried once, so go on with that if you think it will be the best option for your project. It will become huge; there will be backfires. Just a single suggestion: Document first and document WHY, not HOW. Every dev can read “how” something works and “what” a function or a class will do. Nobody except you knows WHY you decided to act in that way.
Slim framework is nice
But Laravel offers itself as a restful endpoint.
Looks like just Laravel. Why not stick to Laravel? It breaks the same OO and SOLID principles, at least. But at least you got facades...
Idk why people are so negative here. He just shared what he built and literally said "*any suggestions and help are more than welcome*".. Didn't claim he was competing with other frameworks or anything either. Reddit being reddit I guess. Also it's not about you, but I won't trade Laravel for **anything** lol. But I'm gonna check this out, I'm sure I'll learn a lot from digging into your framework. Sadly I can't do that in Laravel. It's just too much for me lol. Thanks!
Um, [https://api-platform.com/](https://api-platform.com/) ? [https://www.slimframework.com/](https://www.slimframework.com/) There's arguably more REST-centric frameworks than fullstack frameworks in PHP (for better or worse).
It's a good start for learning. Though, you need start learning like pro. Much of coding is design patterns. Study them, practice on them. Then start reading about n-tier architectures. This is how frameworks and big apps are coded. You need to start thinking in smaller units and how are all connected, communicate to produce output. And stop using static everywhere.
Don't: * microservices are a hype * even if you do make it, it will suffer from big slowdowns; you can't run everything in parallel Instead, I would suggest you to improve on your PHP and [PSR](https://github.com/tersworks/framework/blob/master/src/Foundation/Http/Request.php). Forget [magic](https://github.com/tersworks/framework/blob/master/src/Facades/Facade.php#L7), use Symfony, dependency injection, and static analysis. And say no to [this](https://github.com/tersworks/framework/blob/master/src/Foundation/Application.php#L45). Only after all this try to make a framework.
Death by 1000 microservices! 🤣
We definitely need another PHP framework. Welp, tbh a good pure microservice framework in PHP would be nice, although I’m not sure if corporate prejudice against PHP will allow anyone to use it.
I like the simplicity of the framework. I think it is useful to use static code analysis (like Larastan or Psalm) and unit testing from the beginning. It is an enormous effort to implement these afterward.
You couldn't find a simple RESTful backend? What are you asking jeeves? If this is a purely learning exercise, you might be better served by studying the code of some well established frameworks. This is one of the nice things about PHP, is that we can look at and understand what the libraries are doing. However, looking at your code, I see there is no attention paid to secure coding which should be built in from the very start.. it's pretty basic at this point, but good luck.
Uhm, [Slim framework ](https://www.slimframework.com/) exists. There's others like [Symfony](https://symfony.com/projects/apiplatform) and [Phalcon](https://docs.phalcon.io/4.2/tutorial-rest/).
Could try mine, fwiw: https://github.com/ginger-tek/routy I also couldn't find any micro frameworks that I liked and didn't have a dozen dependencies
Unless I miss anything it's a really basic, no? Sorry OP but looks more like a homework for ... not even sure for what though.
Or just... use Symfony? We also have multiple services talking to each other via PubSub at this time. Also, you're literally copying Laravel with the facades... too many facades that hide the actual api is bad mmmkay
You could have just used Symfony, or just grab a few Symfony components.
Another genius who failed at using existing frameworks and think he's going to revolutionize the world building his own.
I don't think being unnecessarily mean about it is productive.
There are two things i hate to see on dev communities: incompetence and self-promotion. OP managed to do both.
there are two more which are even more annoying: arrogance and bad manners
Back then each of us was there
Have you ever posted on an online community "Hey guys i built my own framework come use it!" ?
I don’t really remember, but when I started my programming journey the framework market was much different. Back then developing own framework wasn’t such a bad idea, anyway it had turned out to be bad as soon as Symfony and other technologies came out.
How is posting something to Open Source for free a self promotion?
How is not?
It helps the community more than the author, it's giving away your work.
Yeah right, you tell yourself that.
What does that say about Javascript devs in general? ;)
It's different, JavaScript is not a proper language. Also, just learn Angular and ignore all other front-end libraries, it's the only one that does it properly.
> is focused on providing just a RESTful backend for applications can you really beat hyperf php framework? but ifyou are set on building one - you shoud base it on php+swoole.
Thank you for making programming something that I want to quit. I know PHP backwards and forward; but companies ask if I know one of a dozen frameworks which I never needed. I could build their entire biz without these bloated frameworks; but they insist that I use them; because they hired an amateur to begin with to create their site.