SaaSHub helps you find the best software and product alternatives Learn more →
Torch Alternatives
Similar projects and alternatives to Torch
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
Eloquent
[READ ONLY] Subtree split of the Illuminate Database component (see laravel/framework)
-
BladeOne
The standalone version Blade Template Engine without Laravel in a single php file and without dependencies
-
-
-
blade
🔪 A standalone version of Laravel's Blade templating engine for use outside of Laravel. (by jenssegers)
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
php-mvc-framework-
Lightweight and user-friendly Model-View-Controller (MVC) framework built in PHP
-
ideas
Discontinued Issues board used for Laravel internals discussions. (by laravel)
-
Design Patterns PHP
Discontinued sample code for several design patterns in PHP 8
-
-
bypass-finals
Removes `final` and `readonly` keywords from source code on-the-fly and allows mocking of final methods and classes. It can be used together with any test tool such as PHPUnit or Mockery.
-
-
view
[READ ONLY] Subtree split of the Illuminate View component (see laravel/framework) (by illuminate)
-
laravel-strict-coding-standard
PHP_CodeSniffer rules for Laravel to force the "right" design of the app
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
Torch reviews and mentions
-
Laravel considered harmful
Components are tightly coupled: it’s hard to use a Laravel component outside Laravel because it requires many other packages and wiring. This is due to many bad practices mentioned before. The community did something to try to fix that (https://github.com/mattstauffer/Torch).
I love that you specifically referenced a project, Torch, that shows that the components are not tightly coupled as your example of how they are…
Torch is the proof that it's tightly coupled. Why do you even need a repo to show how to do it? Symfony doesn't have this issue. Just look at how much crap you need to wire to use a simple validation component: https://github.com/mattstauffer/Torch/blob/master/components/validation/index.php, it's garbage.
-
Am I crazy? Do really all "PHP" companies use either Symfony or Laravel?
You can check out https://github.com/mattstauffer/Torch to see them in action
-
PHP MVC Framework
This is was game changer for me: https://github.com/mattstauffer/Torch
-
IMHO: JSX > PHP Templating
Interesting! I actually found an example here: https://github.com/mattstauffer/Torch/tree/master/components/view
-
A note from our sponsor - SaaSHub
www.saashub.com | 29 Mar 2024
Stats
mattstauffer/Torch is an open source project licensed under MIT License which is an OSI approved license.
The primary programming language of Torch is PHP.