I am sorry, but the only fruit that belongs on a pizza is a mango. Does it also work with mangoes or do I need laundry detergent instead?

AI poisoning before AI poisoning was cool, what a hipster

Lemme cat menu | grep Fried real quick

Sadly that’s against best practices, it does not work with IDE autocomplete, and neither with PHPStan / PHPCS. You also don’t get coverage from PHPUnit. And renaming a property does not rename the usage across the whole project. __get and __set should not be heavily used, and the project shouldn’t be based on them.

Some libraries, like Eloquent, uses them well, but you still need to annotate your class with @property if you want to stay sane.

In PHP, a lot. Unit test are boilerplate 90% of the time, getters and setters (although they can be done via Generate), ORM classes with your default shebang (autoincrement ID), and I could go on and on.

I dislike snippets for code like “key this array by some logic” - this should be reusable via a dedicated helper or service.

The only reaction to a long advice post is bitching about pronouns? Society is fucked.

Been using Input Mono for the past 5 or so years.

You do you, I am almost sure they weren’t gated behind registration when I started using it like a year ago.

I keep up with all the tech news and new shiny stuff via daily.dev. It’s pretty cool to read a few articles when commuting to work, or when taking a shit.

I do a lot of PHP, so naturally my small projects are PHP. I use a framework called Laravel, and while it is possible to use SPAs or other kinds of shit, I usually choose pure SS rendering with a little bit of VueJS to make some parts reactive. Other than that, it is usually, just pure HTML forms for submitting data. And it works really well.

Yeah yeah, they push the Livewire shit, which I absolutely hate and think is a bad idea, but nobody is forcing me, so that’s nice.

It is not, though. Not according to the graph.

I mean, a valid JSON is a valid YAML

Very well written article. I’d like some performance comparison aswell, because ElasticSearch can already do less than 20ms on a 100k documents, with each having more than 10 queries fields.

Of course, for simple sites, this is great!

Cery well written article. I’d like some performance comparison aswell, because ElasticSearch can already do less than 20ms on a 100k documents, with each having more than 10 queries fields.

Of course, for simple sites, this is great!

deleted by creator