.:\dGh/:.13h ago

I just shared my Laragear Expose plug-in in both Laravel and PHP communities, and got a ton of backlash.

Then you wonder why developers are getting replaced by #AI.

It’s that kind of attitude to not read the documentation or understand the problem that’s being solved that gets you putting the fries in the bag.

#PHP #Programming #Programmers #Composer #SoftwareDevelopment #WebDevelopment #WebDev #Coding #Code

Show threadDennis Koch7h ago
@darkghosthunter „A ton of backlash“. Just checked the Laravel Reddit and the people just point out the obvious: That you named the tool exactly the same as a tool that does the same. Not that the name is protected, but it’s still weird.
Show thread.:\dGh/:.7h ago

@denniskoch Collision name is expected this day an age.

I'll give it a thought and change the name at least, given Beyond Code Expose exists (but for some reason didn't appear on my search results, I'll blame Bing for that tho).

Show threadDennis Koch4h ago
@darkghosthunter Not every product can have a unique name. There will always be a collision, and "Expose" is a strong contender for a solution that connects your app to the internet. However, having two solutions with the same name in the same niche or ecosystem feels strange. I thought Expose should be well known in the Laravel community 😬
Show thread.:\dGh/:.
@denniskoch Well, not in the PHP community. That's why I made it a Composer plugin rather than a Laravel package, since it just "works".
10:23pmTuba