Re:Single sign-on: What we learned during our identity alpha
by vanilla-almond on Wednesday October 20, 2021 @08:19AM
(#28929774)
The blog post you linked to is a decade old (2011) and mentions using Django and Ruby for Rails for building a "relatively-durable prototype".
The Government Digital Service (GDS) code is on GitHub (1.5K repos) and this includes the frontend code for GOV.UK.
They still use Python and Ruby languages, but it's not clear if they are still using Django and Rail frameworks.
Other languages include Javascript, Go and Java: https://github.com/alphagov
Re:Single sign-on: What we learned during our identity alpha
by petepete on Thursday October 21, 2021 @03:03AM
(#28941296)
Keep in mind that alphagov is just a small part; most projects belong to other govt departments. Many are using JavaScript and Rails, some Django and .net.
Re:Single sign-on: What we learned during our identity alpha
by ChrisKnott on Wednesday October 20, 2021 @07:33AM
(#28929446)
Have you worked at/with GDS or is this an opinion you've arrived at from afar?
But I do think it is the case at the GDS, as evidenced by the comment on this page:
> GDS is full of mostly django based systems, some legacy ruby and that's just the stuff from the last few years. Going back further there are various C# systems, the amount of separate systems is staggering, it's not too surprising costs add up
And this blog post:
> ...quickly agreed that rather than try to settle on a single one of those we'd build each tool using whichever technology would most quickly get us to a relatively-durable prototype, and then "federate" them. We started with the python-based framework Django for the Department pages, added Ruby on Rails for a suite of tools focussed on specific tasks, and used Sinatra (another ruby framework) to glue together our search.
https://gds.blog.gov.uk/2011/05/12/a-brief-overview-of-techn...