This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-09-21
Channels
- # announcements (3)
- # architecture (5)
- # babashka (19)
- # beginners (145)
- # calva (1)
- # chlorine-clover (18)
- # cider (10)
- # clj-kondo (5)
- # cljsrn (3)
- # clojure (56)
- # clojure-berlin (19)
- # clojure-czech (2)
- # clojure-europe (32)
- # clojure-finland (2)
- # clojure-nl (3)
- # clojure-portugal (2)
- # clojure-spec (8)
- # clojure-uk (48)
- # clojurescript (48)
- # conjure (50)
- # cryogen (1)
- # cursive (28)
- # datomic (54)
- # depstar (12)
- # emacs (1)
- # events (8)
- # figwheel-main (6)
- # fulcro (4)
- # helix (4)
- # java (2)
- # jobs (2)
- # leiningen (1)
- # off-topic (29)
- # parinfer (4)
- # pathom (6)
- # portkey (3)
- # reagent (1)
- # remote-jobs (3)
- # reveal (16)
- # shadow-cljs (42)
- # sql (20)
- # tools-deps (11)
- # vim (4)
- # vrac (2)
I'm currently involved in a project to replace a logistics company's AS/400 based applications with a modern Clojure app. You haven't seen legacy until you've seen The Enterprise...
https://en.wikipedia.org/wiki/IBM_System_i π± π± π± π±
that's a long term process which has been going on for close to a year, and is still far from over. We have one very senior technical contact who is extremely helpful, plus things like on-site interviews, mapping out the existing system
I've been doing modern javascript for a year now, learning a lot, but I don't want to get sucked into this world too much. But there where I'm working now as freelancer, they are calling a redux version of the webapp "legacy", so the word legacy gets a whole new meaning.
Add to that, I helped them migrate from redux to gatsbyjs, and now they want to move over to next.js, because, you know, maintainance is not exciting.