syjer
Joined 16 years ago
Joined 16 years ago
- environment: integration of a large amount of services - and a good amount of them are legacy and idiosyncratic
- use case: enterprise app are at the intersection of real life and the virtual world: the rules are messy, illogical and have a baggage of 20/30+ years. Thus they cannot be changed at all. This is IMO the main difference between a "pure" greenfield startup kind of project and the enterprise one.
- add another layer of burocracy and complex environment to navigate
And with that you got the enterprise app world :).
In the end whatever framework is chosen, the most important property is the availability of common language/patterns.
To be noted, it makes this kind of attack more difficult, but not impossibile.
Especially the mix public/private artifacts. I guess it will force a lot of companies to at least lock their groupId on maven central, if they never bothered to do so.
Generally it's implemented with a custom URI scheme (that the target application is registered for) or a loopback ip address.
[0] https://developers.google.com/identity/protocols/oauth2/nati...
The UI/UX of youtube music is lacking compared to GPM, but at least the file locker functionality that I use is still here.
So don't take the time to develop a feature as a 100% full time work :)
You are right about angular. We already have done 50% of the work, as we have the "customer" facing part done in angular 8 (https://github.com/alfio-event/alf.io-public-frontend).
In the next release (M3) we will convert the "admin" part too (we are targeting a new frontend built with angular material) :)
Linux distributions and the more recent android versions?
why you did not use maven or gradle?