4 ms·

I know a lot of these legacy banks/financial institutions seem to operate in a time-shifted bubble a good few decades in the past, so maybe that explains it? D

by Tade0 6y ago

I know a lot of these legacy banks/financial institutions seem to operate in a time-shifted bubble a good few decades in the past, so maybe that explains it? Decades maybe not necessarily, but years definitely. It boils down to the very real risk of being sued for damages if something's wrong with a payment. I'm currently in a project which aims to re-write the front-end of a library of banking components - from AngularJS to Angular 9. The product is fairly simple to use, but still it's being delivered a year before AngularJS's end-of-life which will be after the 30th June 2021, because the time window for ensuring this thing works according to the banks' use cases must be as wide as possible.

lol768 6y ago
> I'm currently in a project which aims to re-write the front-end of a library of banking components - from AngularJS to Angular 9. The product is fairly simple to use, but still it's being delivered a year before AngularJS's end-of-life which will be after the 30th June 2021, because the time window for ensuring this thing works according to the banks' use cases must be as wide as possible. Is this in the states? I get the impression the regulatory landscape is much more hostile to innovation and tends to favour incumbents (vs the UK, recently, where challengers have been supported a bit more).
- Tade0 6y ago
  Nope, the company itself is based in Switzerland.
smoe 6y ago
In general i think it is fine that banks and similar places are years behind. It is not exaclty the kind of institutions i want to mess around with bleeding edge, barely tested and undocumented technogy.(not referring to Angular here) The problem that I have seen in the enterprise/goverment world when I was in it, is them not keeping up from behind. E.g. They might be reasoanbly recent for a new project, but then dont update for a decade or so. There is this recent introductory talk about enterprise frontend stacks on why it makes sense for them to stay quite far behind (compared to the pace in frontend dev) the latest developments that I found pretty interesting. https://www.infoq.com/news/2020/06/second-generation-js-frameworks/ https://www.infoq.com/news/2020/06/second-generation-js-fram...

by Tade0 6y ago

lol768 6y ago

> I'm currently in a project which aims to re-write the front-end of a library of banking components - from AngularJS to Angular 9. The product is fairly simple to use, but still it's being delivered a year before AngularJS's end-of-life which will be after the 30th June 2021, because the time window for ensuring this thing works according to the banks' use cases must be as wide as possible. Is this in the states? I get the impression the regulatory landscape is much more hostile to innovation and tends to favour incumbents (vs the UK, recently, where challengers have been supported a bit more).

Tade0 6y ago
Nope, the company itself is based in Switzerland.

smoe 6y ago

In general i think it is fine that banks and similar places are years behind. It is not exaclty the kind of institutions i want to mess around with bleeding edge, barely tested and undocumented technogy.(not referring to Angular here) The problem that I have seen in the enterprise/goverment world when I was in it, is them not keeping up from behind. E.g. They might be reasoanbly recent for a new project, but then dont update for a decade or so. There is this recent introductory talk about enterprise frontend stacks on why it makes sense for them to stay quite far behind (compared to the pace in frontend dev) the latest developments that I found pretty interesting. https://www.infoq.com/news/2020/06/second-generation-js-frameworks/ https://www.infoq.com/news/2020/06/second-generation-js-fram...