man, time flew so fast. yesterday it was v1.3 and eex
then now v1.6 and heex
. I cant keep up
Wait what happens in Laravel world? Generators are not optional? How can generators be not optional?
It is completely optional. And despite my statement above, I had used it even before 1.6 and had little to complain about. Itās just that I would have liked it as a separate library instead of a baked in one. But it is a very mild feeling.
Nono, thatās not what I meant, sorry I was just poking fun at how each Laravel project comes (or came in the past, they might have changed that in recent years) with a User
model for some reason.
Edit & note: though I am definitely biased and might be latently salty over the fact how Laravel tried to kill the Vapor framework a few years ago by introducing their Laravel Vapor under the same name, despite Taylor being well aware of the original Vaporās existence. Total y move in my books.
Wow til Laravel has both Elixir and Mix.
Seriously? I did not know that about Laravel Elixir! Thatās seriously shady as heck.
I guess if you canāt or donāt want to compete on the quality of your product, you can always stoop down to the mud of dirty SEO tricks.
I tried searching the Internet for blogposts scolding Laravel for this predatory naming which at this point really canāt be a coincidence, but could not find anyone being bothered by thisā¦ am I too sensitive? I wonder what are other people thinking, though this could perhaps easily be separated into a stand-alone thread as itās not all that related to Phoenix in the end. Sorry for derailing the celebration of an awesome Phoenix release!
Itās not an option like --no-webpack, but You are free to use it, or not
It is the post says, however such a default means it will be used by many people, and eventually lock themselves into the style due to nothing pushing them to a better way. Defaults are incredibly important. I donāt worry about the people who already know better, I worry about the people who donāt.
love phoenix liveview