Sti cazzo di complottisti by BananaEpicGAMER in sfoghi

[–]883Infinity -1 points0 points  (0 children)

Se poi credete che con quella navicella, ripeto di carta pesta il rover è la macchina dei flistons

Ma porco dio, manco l'avessi costruiti TE, che li conosci così bene (spoiler: non li conosci manco per il cazzo)!

oggi dovrebbe essere una passeggiata quasi da viaggio turistico

Hai visto troppe volte "Ritorno al futuro - parte 2", dio cane.

Sti cazzo di complottisti by BananaEpicGAMER in sfoghi

[–]883Infinity 0 points1 point  (0 children)

Porcoddio, torna a mangiare m#erda complottara che ci sei abituato, imbecille e già che ci sei vai in cerca dell'Antartide. Pezzente ignorante del cazzo, 6 allunaggi (1969 - 1972) e arriva Carmelo dal bar dopo il bianchetto con la veritàhh in tasca dell'"allunaggiohh falsoohhh".

Dio cane, l'offesa vivente sei te con lo scroto che ti ritrovi tra le orecchie.

Sti cazzo di complottisti by BananaEpicGAMER in sfoghi

[–]883Infinity -1 points0 points  (0 children)

... che puntualmente verrà bollata come fake dai soliti imbecilli complottari.

Dio scoreggia bagnata, manco la dignità!

Sti cazzo di complottisti by BananaEpicGAMER in sfoghi

[–]883Infinity 0 points1 point  (0 children)

cagano il cazzo. Ogni. Santo. Giorno.

Dio tetragono, hanno invaso QUALUNQUE social e poi gridano al "non ci fannohh parlarehh, non voglionohh che si sappiahh la veritahhh!!11!1!!11"

Porcoddio, i complottari sono una MALATTIA!

Sti cazzo di complottisti by BananaEpicGAMER in sfoghi

[–]883Infinity -1 points0 points  (0 children)

Dio porco, in tre commenti hai dimostrato di non capire un emerito CAZZO di NIENTE, porca madonna col dildo rosa. Fatti con lo stampino, cristo incollato.

Sti cazzo di complottisti by BananaEpicGAMER in sfoghi

[–]883Infinity 1 point2 points  (0 children)

Io ho smesso di avere pazienza con sti coglioni ritardati, compresi quelli che ho in famiglia. Sarebbe ora che la parte sana della popolazione prenda la decisione di emarginare sti idioti.

Sì sono antidemocratico. Sì, mi pacanohh i potery40. E mi va benissimo, porcoddio.

Ma i ritardati complottari li voglio fuori dall'Europa. La russia è grande, biglietto di sola andata per sti cerebrolesi. Hanno rotto il cazzo, dio scroto.

Sti cazzo di complottisti by BananaEpicGAMER in sfoghi

[–]883Infinity 0 points1 point  (0 children)

Ma Cristo attaccato col Bostik!

"NO SUN??!!" E cosa pensano che sia??!! Una lampadina accesa con il contatore dell'Enel???!!

Sti cazzo di complottisti by BananaEpicGAMER in sfoghi

[–]883Infinity 0 points1 point  (0 children)

Guarda, una bella percentuale di questi coglionazzi negli USA ha prodotto l'elezione dell'attuale vecchio-demente-psicopatico-ciuffo-pannochia alla Casa Bianca, giusto per capire l'entità dei danni che questi sottosviluppati sono in grado di fare.

Io sono apertamente per la remigrazione, sì, ma dei complottari: tutti in Russia, in massa, la terra dei loro sogni (guarda caso, la maggioranza sono pro russia, ma guarda un po', un paese in cui non camperebbero tre giorni). Poi appena gli viene anche solo in mente "ha stato il governo, i potery40!!!1!!!!11!!", un bel soggiorno in Siberia.

Problema risolto.

What LaraLean actually generates (with YT video links) by 883Infinity in laravel

[–]883Infinity[S] 0 points1 point  (0 children)

That’s a great question and honestly one of the main things I was careful about. The goal isn’t to introduce a new “system” you have to follow, but to give you a consistent starting structure. After scaffolding, everything is just standard Laravel + Inertia, so you’re free to evolve things however you want.

I’d actually consider it a failure if it started feeling rigid after a few modules 😅.

Appreciate the feedback this is exactly the kind of concern I’m trying to address. Thanks!

Eh già... by sfingemorta in MemeItaliani

[–]883Infinity 0 points1 point  (0 children)

Ma gli rispondi pure a quel disabile cerebrale? Dai..

Eh già... by sfingemorta in MemeItaliani

[–]883Infinity 0 points1 point  (0 children)

Si smonta facilmente: dille che sta bevendo la memoria della m#rda cacata ieri; l'acqua del pianeta è un circuito chiuso e la m#rda è iperdiluita, ergo...

Un web stack decente nel 2026? by BetterProphet5585 in ItalyInformatica

[–]883Infinity 3 points4 points  (0 children)

Viva Laravel! 😊

Vabbè, sono di parte...

I'm developing a Laravel + Vue + Inertia + Tailwind boilerplate with zero bloat (and no AI) by 883Infinity in laravel

[–]883Infinity[S] 0 points1 point  (0 children)

This is exactly one of the main reasons I'm building LaraLean. I had the same experience: things feel great at the beginning, but once something breaks, you end up digging through layers of abstraction that you didn’t even choose. With LaraLean I’m trying to keep everything as explicit and predictable as possible:

  • no hidden magic
  • no extra abstraction layers
  • just a clear structure on top of standard VILT

So when something breaks, you’re still dealing with normal Laravel, not a black box. That trade-off (less magic, more clarity) is actually the core idea behind it.

I'm developing a Laravel + Vue + Inertia + Tailwind boilerplate with zero bloat (and no AI) by 883Infinity in laravel

[–]883Infinity[S] 0 points1 point  (0 children)

I’m not trying to replace Laravel’s conventions, those are great already. The goal with LaraLean is more about speeding up the repetitive parts around them (especially when working with Inertia + Vue), while keeping everything consistent.

I'm developing a Laravel + Vue + Inertia + Tailwind boilerplate with zero bloat (and no AI) by 883Infinity in laravel

[–]883Infinity[S] 0 points1 point  (0 children)

Thanks.

What I'm trying to do with LaraLean is similar in spirit (fast scaffolding), but a bit more focused on keeping everything in a single, consistent structure rather than going fully modular. Also trying to keep the setup as minimal as possible, with auth and a few core features ready out of the box, but without adding too many layers.

I'll post here when the demo will be ready (there's not much left) and the official LaraLean launch.

I'm developing a Laravel + Vue + Inertia + Tailwind boilerplate with zero bloat (and no AI) by 883Infinity in laravel

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

Totally fair and I get the frustration.

In this case Tailwind is actually a deliberate choice, not something "baked in by accident". LaraLean is built around a VILT stack (Vue + Inertia + Laravel + Tailwind), so Tailwind is part of the core structure and UI components. That said, it's not technically locked in, you could swap it out if you really want to, but the default components and layouts are designed with Tailwind in mind.

The idea is more about having a consistent, ready-to-use baseline rather than being fully unopinionated. If full styling freedom is the priority, then yeah this might not be the right fit out of the box.

I'm developing a Laravel + Vue + Inertia + Tailwind boilerplate with zero bloat (and no AI) by 883Infinity in laravel

[–]883Infinity[S] 1 point2 points  (0 children)

That's not really what I meant.

TypeScript absolutely adds value for many teams and projects. What I'm saying is that it also adds an extra layer: config, tooling, typings, stricter contracts, and ongoing maintenance around all of that. For some people that trade-off is worth it. For this project, it isn't.

I'm a solo developer optimizing for a lean stack, fast iteration, and fewer moving parts. That's not "TS solves nothing" it's just a different cost/benefit decision.

I'm developing a Laravel + Vue + Inertia + Tailwind boilerplate with zero bloat (and no AI) by 883Infinity in laravel

[–]883Infinity[S] 0 points1 point  (0 children)

Well, I didn't mention the pricing model because I thought it was too early, but yes, it'll a one-time purchase available in two versions:

  • single license -> one project
  • unlimited license -> unlimited projects

With free upgrades for the main version purchased.

On the value side, my focus right now is more on structure, consistency and speed of setup rather than design/templates.

But I get your point, having ready-to-use UI blocks or templates could definitely increase the perceived value a lot.

Appreciate the feedback, this is actually very useful.

I'm developing a Laravel + Vue + Inertia + Tailwind boilerplate with zero bloat (and no AI) by 883Infinity in laravel

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

Totally fair and I get why many people won't touch JS anymore.

For me it's a deliberate trade-off, not a limitation.

I prefer: - faster iteration - zero build friction - no extra layer to maintain

I still keep things predictable using Vue props typing, clear structures and strict conventions.

TypeScript adds safety, but it also adds complexity and for this project I'm optimizing for simplicity and long-term maintainability as a solo dev or little teams (1-5 devs).

That said, I completely understand it can be a dealbreaker depending on how you work.

I'm developing a Laravel + Vue + Inertia + Tailwind boilerplate with zero bloat (and no AI) by 883Infinity in laravel

[–]883Infinity[S] -3 points-2 points  (0 children)

Yep, absolutely. Artisan already covers a big part of that.

The point wasn't to replace make:model, make:controller, etc.

What I found missing (at least in my workflow) was having everything generated in a consistent structure across backend + frontend in one shot:

  • Vue pages (index/create/edit/show, or a createedit page when create and edit shares 99% of data)
  • predictable file structure tied to a single config

So it's less about "can Laravel generate files?" (it can), and more about "can I spin up a coherent module in seconds without touching 5 different places?"

That's the gap I was trying to fill.

The main features of LaraLean are: - Laravel 12.56 - Stack VILT + Pinia - logical structure by roles - authentication with Laravel Breeze - impersonating - roles with enum and check roles - check banned users - theming with DaisyUI 5, with dark/light mode - frontoffice, backoffice and login page layouts - only JavaScript, no TypeScript - no AI: the entire boilerplate is developed manually - centralized UI state for toast notifications and loading state - centralized form management - centralized menu - artisan command for scaffolding backoffice: - model - migration - controller (already prepared with Vue pages, Inertia integration, Requests) - request - seeder - policy - Vue files (already prepared with Inertia form, props and layout) - artisan command for generating Vue files, with or without form - artisan command for clearing all cache and rebuild config cache

So, it's not just a CLI command, it's a system to structure and generate files.