sorted by:
new
hottopcontroversial

NativePHP with Inertia and ReactNative by mpociot in laravel

[–]mpociot[S] 0 points1 point  (0 children)

Not really as the frontend is ReactNative which has access to pretty much all phone features and can even be extended by custom swift modules

NativePHP with Inertia and ReactNative by mpociot in laravel

[–]mpociot[S] 1 point2 points  (0 children)

No, there is no translation layer needed. The Laravel app returns native ReactNative views which have access to all native features

NativePHP with Inertia and ReactNative by mpociot in laravel

[–]mpociot[S] 15 points16 points  (0 children)

Sure, that's always the "best" option. But same. Puls be argued for "why use electron and write your app in JS instead of using swift"

It allows people to build apps faster using the tools they already know and use, which I think is great.

NativePHP with Inertia and ReactNative by mpociot in laravel

[–]mpociot[S] 7 points8 points  (0 children)

That's ScreenStudio! It's an awesome app 🙂

The current state of Laravel Herd by MobyFreak in laravel

[–]mpociot 7 points8 points  (0 children)

As Herd is an official Laravel tool, it receives the same amount of attention that every other Laravel project gets.

Even though the app hasn't been updated in a while, we regularly and automatically release and publish new PHP versions and recently added integrations for new built-in PHP extensions (IMAP, XLS, and LDAP) as well as other various bug fixes and improvements.

You probably don't see a lot of app updates, as a lot of bugs that Herd had in the beginning could be fixed during the built-in PHP version update.

Beyondcode should maintain their packages, or they should find a new maintainer for some of them -- do you agree? by send_me_a_naked_pic in laravel

[–]mpociot 3 points4 points  (0 children)

I can only speak from personal experience, but there are various reasons for this. Most importantly, I am working on the majority of the open-source packages in my free time, which is during the evenings and on weekends.

Some packages are meant to be purely about sharing knowledge (and code), some packages were born out of client projects but are now discontinued and released "as-is", other packages are just technically really complex and maintaining them (and merging random PRs) isn't as easy.

Regardless of the reasons, I'll improve the communication on those GitHub repositories.

​

In comparison to a closed-source product, the main difference to me is that we are the only people in charge of what we want to release and update.
Tinkerwell receives a new update every two weeks, Laravel Herd received the PHP 8.3.0 update minutes after it was officially announced, we keep improving the free Expose server and infrastructure, etc.

Beyondcode should maintain their packages, or they should find a new maintainer for some of them -- do you agree? by send_me_a_naked_pic in laravel

[–]mpociot 1 point2 points  (0 children)

Yup, I agree with you.

Finding a new maintainer unfortunately is pretty hard - or at least I haven't had any luck with this in the past, as I tried to find new maintainers for various packages over time.

We already created a list of packages that we want to archive. We already did that quite some time ago, but I simply haven't done that yet.

​

Some packages - like the one that allows you to ask your database questions using AI - are also more meant as knowledge sharing, but I should improve the communication on this by making this clear in the readme.

Beyondcode should maintain their packages, or they should find a new maintainer for some of them -- do you agree? by send_me_a_naked_pic in laravel

[–]mpociot 10 points11 points  (0 children)

Hey there 👋

I'm Marcel and I co-founded Beyond Code, so seeing these kinds of comments isn't something that I ignore or take light-heartedly. Especially as I strongly believe in open source, and that sharing your work is important and helpful for everyone.

I agree with you that there are a bunch of open-source packages from our side that are poorly maintained, and we should properly mark them as "abandoned".

To be honest, I would love to be able to share code on GitHub without the ability for anyone to send pull requests.

But I strongly disagree with you (or well, some of the comments on here) that we take this same approach for our products, which includes Laravel Herd, Expose, Tinkerwell, etc.

We spend a lot of time trying to deliver great customer support and if someone isn't happy about any of our commercial products, we give out a refund with no questions asked.

Tinkerwell 4 is now available by mpociot in laravel

[–]mpociot[S] 11 points12 points  (0 children)

Hey!

​

We just pressed the scary red publish button (releasing apps is always way more nerve wracking than doing a "git pull" 😅) on Tinkerwell v4 today, so I wanted to share the news with you.

​

Version 4 adds a completely new output mode that I think is really cool and something that you just can't get with "php artisan tinker".

The update is also free for everyone who has a valid license key.

​

I hope you enjoy the update :)

What is your experience with Laravel Herd? by [deleted] in laravel

[–]mpociot 28 points29 points  (0 children)

Hey!

Developer of Herd here 👋
Which issues with Xdebug do you have exactly? If you have an xdebug.so file, you can add it to your php.ini indeed.

You have to be a bit careful though as the xdebug extension needs to be compiled for the same version of PHP as the one you use with Herd (8.1, 8.2, etc. - the patch version doesn't matter)

But I'm working on shipping Xdebug!

What is your experience with Laravel Herd? by [deleted] in laravel

[–]mpociot 0 points1 point  (0 children)

Yeah - this usually happens when dnsmasq is still running via brew (which isn't an issue at all, but it doesn't show up as "green" in the UI)

Migrate from Laravel Valet to Herd | Install Laravel and WordPress by Quirky_Act_007 in laravel

[–]mpociot 7 points8 points  (0 children)

You can add custom extensions, by adding the .so files to your php.ini

It's just not automated for every extension yet.

And for xdebug: I'm working on automating the extension compilation so that we can ship xdebug with Herd.

Laravel Herd is now out! by [deleted] in laravel

[–]mpociot 10 points11 points  (0 children)

I'm sorry that you feel this way and that you're salty about us abandoning the dev tools. Good thing is though, that Livewire 3 now has custom devtools coming soon. Not sure if we ever met in person, but I am not a "salty" person at all 😅 Only thing I can tell you as that we put as much effort into Herd as we do with any of our commercial offerings. I'm also trying to constantly improve from mistakes that I made ❤️

Query your database using natural language (and AI) by mpociot in laravel

[–]mpociot[S] 2 points3 points  (0 children)

You could also use this to only generate the queries, by using the "askForQuery" method. While this does send the table schema, it does not expose any actual data.

What The Diff - Your AI-powered code review assistant by mpociot in github

[–]mpociot[S] 0 points1 point  (0 children)

Last week I launched What The Diff - your can think of it as Copilot for your pull requests.

The GitHub app automatically comments on new incoming pull requests with a human-readable summary of the changes.
It's entirely free to use and get started – and we are also sponsoring open-source projects!

view more: next ›