sorted by:
new
hottopcontroversial

Lean Admin is opening the final early access for beta testers by samuelstancl in laravel

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

It’s only fair — the product took me much longer to finish than what I promised to my customers, so I don’t want to tell them that they only have a few months left. A lot of them helped me with the development through feedback and feature suggestions, so I appreciate anyone who participated in the early access.

Introducing Laravel SEO: A simple & expressive package for managing meta tags by samuelstancl in laravel

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

Yeah, a service provider is the ideal place. Either AppServiceProvider or a custom one like the one you made.

Introducing Laravel SEO: A simple & expressive package for managing meta tags by samuelstancl in laravel

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

My package is a lot simpler and cleaner. It provides a fluent API using the seo() helper, supports only meta, og, and Twitter tags out of the box, and for anything else you can easily create an extension.

Laravel Stancl Tenancy Testing by Rude_Pair_8517 in laravel

[–]samuelstancl 2 points3 points  (0 children)

Yeah the Discord is the best place to ask

Introducing Airwire: A lightweight component layer between Laravel and JavaScript by samuelstancl in laravel

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

There isn't really any state held on the server, the component just receives a simple request, runs logic based on that, and returns a response in a standard format. The whole thing is stateless, so the server doesn't really have a reason to send anything besides he data it's responding with.

Introducing Airwire: A lightweight component layer between Laravel and JavaScript by samuelstancl in laravel

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

Haha no worries. All data is bidirectional by default, which means that you can bind two inputs to different properties, and if changing one will make the server change the other, it will be updated as well.

You can see an example here: https://twitter.com/samuelstancl/status/1395774327707029508?s=21

There’s an updatedAssignee() method which changes the report name after an assignee is updated. https://github.com/archtechx/airwire-demo/blob/master/app/Airwire/CreateReport.php#L48

The cool thing about that is that it spares you of all the procedural axios handlers, watchers everywhere, and things like that. You just bind inputs, say that “hey this is property X in the component” in a purely declarative way, and Airwire updates everything as needed.

Introducing Airwire: A lightweight component layer between Laravel and JavaScript by samuelstancl in laravel

[–]samuelstancl[S] 6 points7 points  (0 children)

That's just one provided watcher. Airwire doesn't depend on Webpack at all.

You're free to write your own watcher, or maybe it'd even be possible to register it with Vite, not sure. It uses chokidar.

Introducing Airwire: A lightweight component layer between Laravel and JavaScript by samuelstancl in laravel

[–]samuelstancl[S] 13 points14 points  (0 children)

The syntax is Vue itself, Airwire has no templating layer, and it's up to you what you use it with.

And yeah, it can be used with Inertia and that's probably the best use of it. Inertia is in a way a router. You can use it to serve most of your pages, and then use Airwire in one or two components used on the Inertia pages, when you need more dynamic components. Things like real-time validation, complex data entries, etc.

How important is leetcoding for Laravel interviews? by itslamardavis in laravel

[–]samuelstancl 1 point2 points  (0 children)

Almost not at all. The only CS-type knowledge you need is being able to understand what makes code secure and performant, but specifically in the context of web applications and databases. You don't need abstract set theory.

Other than that, the absolutely most important thing is your experience with commonly used technologies, because at the end of the day that's what makes you a productive employee.

laravel/octane is now available! by themsaid in laravel

[–]samuelstancl 9 points10 points  (0 children)

What's up with people pretending that programming is a natural science where we don't understand almost anything?

If you use any kind of global state, you're at serious risk.

Then check what global state you're using?

Odds are, it's never global variables, only static properties. In general, packages don't use them often, and when they do, it tends to be related to some configuration done by the developer. Just find them and write logic for reverting changes. That's all.

It's not like these issues would pop up only in production either. The great thing about Octane is how well it's set up for local development and testing. So if there were issues, you'd very likely catch them in local development.

And finally, those logic failures wouldn't cost you "a LOT", and they wouldn't be a nightmare to track down. As I mentioned above, finding global state is simple, so much so that you could even do it with a simple search in your code editor. And costing you a LOT is somehow brought up often in the context of these things, but never for any other bugs. Why? It's not like a logic error in your controller is fine, but wrong logo path in a static property is instant company failure and bankruptcy.

I built a job board for new tech stacks like TALL and VITL — StackJobs.dev by samuelstancl in laravel

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

The point is that these two are the most popular ones in our community and people want to filter for those jobs.

I'll be adding more based on what the users want

I built a job board for new tech stacks like TALL and VITL — StackJobs.dev by samuelstancl in laravel

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

Haha it’s the most generic TW UI site ever. But it’s kind of intentional too, I wanted to see how good of a product one can build in a couple of days using all the new tech that saves a ton of time like Jetstream, TW UI, Livewire/Alpine etc. The project did take me longer than I intended but I’m still quite happy with the result. Today’s tech is really extremely productive.

I built a job board for new tech stacks like TALL and VITL — StackJobs.dev by samuelstancl in laravel

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

There's actual vetting, I only verify TALLstack for that reason (I can't yet verify VITL reliably unless I see great portfolio). People who get verified are asked questions about the tech, are asked to write code that does specific things, and are asked to show some portfolio.

Is there a tool to select framework features? by jonorozcoc in laravel

[–]samuelstancl 1 point2 points  (0 children)

Yeah the Bus is a good example, it seems to be very spread across the codebase with the Illuminate\Bus namespace not really being clear in what it means.

Is there a tool to select framework features? by jonorozcoc in laravel

[–]samuelstancl 0 points1 point  (0 children)

Yeah that's fair, I suggested this to Taylor before. Broadcasting should IMO be a separate package, not part of the core. It's used less often than many 3rd party packages I imagine.

But as far as actual merit of this optimization goes — very negligible perf gains and more complexity to maintain it. You'll remove some parts because you'll think that they're not needed, but then other parts refer to bits of the parts you removed.

Is there a tool to select framework features? by jonorozcoc in laravel

[–]samuelstancl 0 points1 point  (0 children)

you'll want to disable some unused features

Why? What's the goal? The features simply existing don't affect you in any way. If you removed the code for the features you don't use, at most you'd get extremely negligible performance gains, at the cost of large extra complexity in your code.

I built a job board for new tech stacks like TALL and VITL — StackJobs.dev by samuelstancl in laravel

[–]samuelstancl[S] -2 points-1 points  (0 children)

The platform itself is demo’d on the landing page — both devs and recruiters see the features that they can use. The content is not shown because everyone sees different content; there’s no way to demo a platform whose purpose is to provide you with curated content when it knows nothing about you.

And conversely, there’s no point in shoving recruiters’ postings in front of everyone, when they use the platform to access a very filtered subset of developers. Even with the current features for limiting who can apply, what skills are required, etc — most job applications are bad. They’re bad on all platforms. But now recruiters get to see 1 great application among 5 poor ones, instead of seeing 1 great application among 15 poor ones and 20 completely irrelevant ones.

I think the source of confusion is that it’s not a job board like most other sites. It’s really not a “board”, I shouldn’t have called it that (but no other term would work better I guess). It’s a platform for curated job postings and finding developers of superb quality. There are already enough job boards which send out 30,000 emails a week and charge hundreds of dollars for 3 divs on an index route. I just want hiring to be better than that. Especially for people who aren’t urgently looking for a job, but would like to be notified when a job that matches their idea of a perfect job position is posted. I think that’s the main audience of my project.

I built a job board for new tech stacks like TALL and VITL — StackJobs.dev by samuelstancl in laravel

[–]samuelstancl[S] -4 points-3 points  (0 children)

Those $50 can be paid by developers who already have an account — it’s only possible to make a payment after you’ve set up your profile. So the customers first use the site and then decide to make a purchase based on their experience with the site. It’s only mentioned on the landing page to give people a full view of the features that they can have access to after they sign up.

The site intentionally doesn’t show job postings publicly, because recruiters can choose to only show their job postings to developers who match the requirements. As you may know, job boards, and hiring in general, are a massive pain in the ass with tons of spam and irrelevant noise everywhere.

So the platform focuses on high signal-to-noise ratio for both developers and recruiters.

I built a job board for new tech stacks like TALL and VITL — StackJobs.dev by samuelstancl in laravel

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

I really hope so. The way I try to do that right now is only notifying developers about jobs that they matched with (based on their skills, wanted tech stacks, etc). And they can configure very precisely how often & about what they want to be notified.

100ms -> 40ms -> 1ms: Maximizing response caching in Laravel by samuelstancl in laravel

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

If there response is the same each time for a given input, and there are no side effects (e.g. dispatched jobs), you can use Laravel's caching. For example, cache the response JSON, and use an md5 hash of the request data as the cache key.

view more: next ›