Skip to content
This repository has been archived by the owner on Dec 5, 2023. It is now read-only.

[Question] Difference to Telescope #11

Closed
johannesschobel opened this issue Oct 30, 2018 · 8 comments
Closed

[Question] Difference to Telescope #11

johannesschobel opened this issue Oct 30, 2018 · 8 comments
Labels
question Further information is requested

Comments

@johannesschobel
Copy link
Contributor

Dear @aschmelyun ,

i recently stumbled upon this package and was wondering what the difference between larametrics and the newly released laravel telescope is. Maybe you can describe the key differences?

All the best

@aschmelyun aschmelyun added the question Further information is requested label Oct 30, 2018
@aschmelyun
Copy link
Owner

Hey @johannesschobel,

I've been asked this a few times and I'll try to give a pretty succinct answer: Larametrics is aimed toward simplicity, compatibility, and use on production systems.

I feel like Laravel Telescope is a great tool to accompany a dev environment, but Larametrics was built to fill a need that I had to monitor my side projects and alert me when something went wrong.

I wanted something self-hosted, easy to set up, and able to be used on some of my 5.6 and lower projects. I think I've created something worthwhile in that, and while it may on the surface look like a cheaper version of Telescope I think we both shine in our own light.

@johannesschobel
Copy link
Contributor Author

Dear @aschmelyun ,

thank you for your detailed answer for my question. For me it wasn't that clear, that is meant to be used for "production mode" - while "telescope" clearly tackles the "development mode". Thanks for pointing that out!

All the best

@anthonyvancauwenberghe
Copy link

Taylor clearly stated that telescope is also meant to be used in production. Your package comes at an unfortunate time :(

@aschmelyun
Copy link
Owner

Agreed, but I feel like it comes with an "if you really want to, you can" feeling, as it's branded as a debug tool. Whereas I've tried to develop Larametrics as lightweight and meant to run alongside both development and production systems, something like your own version of Sentry.io.

Timing could have been better on this definitely, you're not wrong, but I feel like there's enough of a difference between us that we can continue to build up in our own ways.

@nowendwell
Copy link
Contributor

I think the biggest difference for me, between Telescope and Larametrics, is the compatibility with older versions. I don't always have the resources to keep every single project updated to the latest and greatest Laravel version.

In my opinion, to have a package that provides some of the same features and has the compatibility that it does, makes Larametrics more valuable than Telescope.

With that said, if Telescope were to expand their compatibility to older versions, I would probably use it instead, but it seems highly unlikely.

@troyporter
Copy link

I think the biggest difference for me, between Telescope and Larametrics, is the compatibility with older versions. I don't always have the resources to keep every single project updated to the latest and greatest Laravel version...

I agree here....i was disappointed to see Telescope was only available for 5.7. But then i wonder if they did that deliberately to be graceful and not to 'kill' already existing packages that do similar things.

In any case, Larametrics has its place in my books ! .. Good job

@HDVinnie
Copy link

@deviouspk where did he say that? Last I saw they said its meant for dev environment only. While it could be used in production its not recommended.

@niladam
Copy link

niladam commented Jan 5, 2019

I'll be off-topic, but i need to provide me opinion.

I haven't had the chance to try this yet, but i'm planning on testing it sometimes next week.

Personally, i think that having a large number of packets that basically do the same thing is really a good thing for the entire community, and for all the developers (users and creators alike) involved.

There's no golden rule for doing anything and no golden rule for the 'best' package. Some fit your needs, some don't.

I want to THANK YOU for the work you did on this package and i can't stress enough how happy i am to see many alternative packages.

M.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

7 participants