A day with Laravel - #014

HappyToDev

·Jun 12, 2023·5 min read

Hey devs 👋,

I present you "A Day with Laravel".

If you think of a resource that could be useful for the Laravel dev community, let me know in a comment or DM on Twitter (HappyToDev)

🎯 To deliver to you daily, or almost daily*, the recent or important resources (videos, articles, GitHub repos, packages, tutorials, ...) that I could find on Laravel and its ecosystem.

This is a quick content of a few links to feed your watch on Laravel and its ecosystem daily.

* Or almost: why?

Simply because I'm the only one to manage this newsletter and "Quoi de neuf les devs? 🇫🇷" Depending on my availability and obligations, it is possible that this newsletter is not daily.

If you want to support me to encourage me to keep the pace, you can help me by making a one-time or recurring donation starting at 2€ by clicking on the image below or via this link

To support me 👇

For whom?

For Laravel devs, you guessed it.

Subscribe to not miss the next issues and receive them directly in your email box!

Subscribe now

Laravel Queues With Other Languages

Image de l'article original

To sum up this article, I couldn't think of anything more powerful than to give you the translation of the introduction. It's a bit long, but it has the merit of being clear:

Learning multiple programming languages is good --- there are a lot of benefits!
One such benefit is the ability to use what a language is strongest at. Some top-of-mind examples include Python's various data-munging libraries, or Go's concurrency tooling.
Now, you may want to use another language --- but you likely aren't about to rewrite your app. Luckily, I have some ideas! They look a bit like micro-services, but aren't. Mostly.
What I like to do is sprinkle in other languages as part of my codebase's "plumbing" --- stuff that happens unseen, in the background.
One way to go about this is with gRPC. This lets you call a function, which (in the background) makes a network call to some other codebase, and gets a response. It looks like you're making just any old function call, but it actually might be talking to another application. This is fun but gets complicated, relative to the 2nd idea.
That second idea: using queues! Queues are a tidy abstraction layer between languages because your codebase(s) can push or pull a job from a queue, and doesn't need to care about who is reading or writing those jobs.

Read the article

Send your Laravel queries directly to explainmysql.com

I told you about explainmysql.com in issue 36 of "🇫🇷 Quoi de neuf les devs?" and now Tobias Petry has released a package that will send your code queries directly to explainmysql and get explanations of your queries in return!

See the package on Github

Battle Ready Laravel by Ash Allen

The link below is an affiliate link, it means that if you buy this book, I will get a small commission. If you don't want to help me, just search "Battle Ready Laravel" on your favourite search engine ;-)

The ultimate guide to auditing, testing, fixing and improving your Laravel applications so you can build better apps faster and with more confidence.

Read a free chapter

🇬🇧 Start-up Challenge Day 1 - @JustSteveKing

In one week, Steve will try to launch an application called eventSnap.

Knowing Steve, there'll be plenty to discover and learn in this video.

We'll try to keep up with him all week.

Package : Form Components for Laravel

Form Components for Laravel provides common form components to help build forms faster using Tailwind CSS. Supports validation, old form values, and wire:model.

See the package on Github

Smousss

The link below is an affiliate link, it means that if you buy this book, I will get a small commission. If you don't want to help me, just search "Battle Ready Laravel" on your favourite search engine ;-)

What if you entrusted your tedious #Laravel tasks to Smousss?

For example :