I'm more interested in the general question rather than the specifics of this situation, which I'm sure is now incredibly common. I know it looked at those implementations because I asked it to, and therefore I will credit those projects when I release this library. In general though, people do not know what other material the agents looked at in order to derive their results, therefore they can't give credit, or even be sure that they are technically complying with the relevant licenses.
Why? The police officer gets paid the same either way. And that's probably in line with how we want it, lest police officers start seeing infractions that don't exist when their daughter's next birthday comes near.
That can help, but policy doesn't execute itself, it's executed through the police officers. Most cities aren't prepared to be able to follow-through to the logical conclusion the steps they'd need to take if their police force is fully intransigent with regard to following policy, so the policy itself is set based in part on what the force itself is willing to enforce.
Either I'm confused or maybe you didn't understand my point - why wouldn't the department want to execute a policy that benefits them greatly through increased revenue? If it's not profitable or desirable to do so, increase the fines.
Lustre (hi, author here) has isomorphic components so you can render components both on the client or as realtime LiveView-esque things on the server, which I think is what the commenter was alluding to.
Definitely not a full-stack framework though: firmly a frontend thing just it blurs what "frontend" means a little! Hologram has a wider scope here being built on top of Phoenix.
reply