They still require a browser released not earlier than 2 years ago.
There’s absolutely no excuse to break people’s projects this way. The tech behind v.3 is still working and will continue to work for the foreseeable future.
Lost visitors/users on incompatible browsers directly translate to lost revenue. Shiny new toys for developers don’t translate to business outcomes. And then we complain that companies don’t take Elixir seriously.
a3kov
0
LostKobrakai
If that distinction is worth real money how much of it are you investing for the maintainers to stick with tw3 – and likely decouple it from users style pipeline to support people using phoenix 1.8 with tw4? Unless you’re paying for it you cannot expect open source maintainers to work by your personal business constraints – no matter how valid your pov may be.
7
a3kov
I’m not a newcomer to open source world and I’ve had my own OS projects.
I’m sorry if you got the impression that I’m expecting or demanding.
0
lawik
Nerves Core Team
Excited to see action around Ash + Backpex. Good job @eileennoonan!
It had snuck me by: GitHub - enoonan/ash_backpex: Ash Integration for Backpex · GitHub
So the limitations mentioned on using Ash’s access and policy stuff is a limitation on how it can be hooked into backpex?
3
eileennoonan
Hi @lawik, thanks for the kind words!
Up to now, yes, I haven’t been able to fully use Ash policies because the current_user aka actor isn’t present everywhere queries are being made.
I know that the Backpex folks added the assigns in more places with the 0.14 release, but I haven’t been able to dig deeply into that yet.
Some backstory on this integration - I started it so that I could use it in my own application for my web accessibility startup called Insi. Since then, I have been extremely busy with other aspects of this startup, and haven’t had the bandwidth to push ash_backpex any further than what met Insi’s immediate needs.
However, I’m going to. We can get away with limited authz for the moment because we’re only using it as an internal admin for now. The whole thing is walled off. But we will eventually want a more full-featured customer-facing admin as well as all the other Backpex bells and whistles.
My dream is to get it all hooked up with Igniter and be able to present a demo of creating a full featured AshBackpex app in like 15 minutes via the command line.
I guess I’m writing all this extra stuff to say I’m worried people think I have abandoned this - I have not! We have an #ash_backpex channel in the Ash Discord and Zach Daniel and other Ash maintainers have already been a big help!
8
arcanemachine
We all have a limited amount of time in this world, and browser APIs move quickly.
It may be better to rip off the band-aid now and have a product that still works in 5 years, as opposed to having to maintain a legacy system, and watch as yet another Phoenix admin package eats your lunch because you’re stuck with a bunch of old code that you don’t have time to upgrade.
If you don’t like it, there are alternatives, like Kaffy.
Like it or not, the ecosystem has settled on using Tailwind v4. (see also: Phoenix 1.8)
1
a3kov
There’s no band-aid. 3.x is perfectly fine, unless you enforce artificial obsoletion. There’s no rush to upgrade.
Or you could upgrade just in time, when all users have moved on to newer devices/browsers so you are not losing anything, you know.
In other words: don’t fix something that is not broken. And TW 3.x is clearly not broken. As is the tech behind it.
Also, not every code must be upgraded. Some code will work forever without an upgrade.
Nonsense, TW 3.x is still supported. The generated code can easily be adjusted, and it works only for new projects anyway.
0
zachdaniel
Creator of Ash
they didn’t break anything. It’s free, and literally every revision is available on GH. So the thing they already gave you(for free) you still have(for free). They simply released more stuff(for free) that you don’t like when compared to the old stuff(that was free)
There is a conveniently placed “fork” button if you wish to invest the effort in maintaining a version of backpex using tw3.
With all that in mind, there is no “excuse” needed 
17
arcanemachine
My heart goes out to all the maintainers who have to put up with these incessant complaints, day in and day out.
2
lawik
Nerves Core Team
Completely get it. Just very excited to see this. I don’t have the immediate need personally but would definitely try it. And I know people who really miss Django Admin 
1