Fork me on GitHub
#off-topic
<
2018-09-13
>
emil0r12:09:49

I believe one is every man is an island unto himself? Ie, no community building and sharing libraries but instead always write your own stuff

emccue13:09:43

The other is thou shall not covet thy neighbor's wife

borkdude13:09:46

I mean what are the two most important things to prevent the Lisp curse

emccue13:09:29

diet and exercise

šŸ˜† 8
manutter5113:09:42

Iā€™d guess one is ā€œJust Say Noā€ ā€” features donā€™t get added just because people like them or want them, they have to match certain design principles and philosophy

borkdude13:09:16

Common Lisp had a ā€œjust say yesā€ attitude?

manutter5113:09:38

Hmm, couldnā€™t say

manutter5113:09:00

Just guessing based on the ā€œLisp Curseā€ being uncontrolled proliferation of ad hoc implementations

mpenet13:09:47

funny that it mentions something about breaking reading and the previous point in the list mentions exactly that possibility with broken keywords pr representation

mpenet13:09:47

that said he's right about reader macros

borkdude16:09:05

any reason there arenā€™t any 3840x2400 screens? currently I have a 1920*1200 Dell monitor. If I were to upgrade to 4k I would like to keep that ratio

Conor16:09:50

Nobody likes 16:10, for some reason

jaide18:09:56

Anyone pretty familiar with Heroku? Iā€™m considering moving my companyā€™s software to it but have some aspects Iā€™m not sure if Heroku can support so Iā€™d like to ask some questions.

john18:09:05

Lot's of clojure folks have used heroku over the years. It's gotta fairly mature clojure story, fwiu

jaide18:09:20

Ah thatā€™s good, unfortunately our codebase is not Clojure basedā€¦.yet. Though I did launch a tiny clojure slack-request-invite app with it which was a dream all the way through.

dangercoder18:09:31

Isn't Heroku expensive? compared to AWS.

dangercoder18:09:29

I would love to try out Heroku as well but I want to use Datomic :S gotta make some reading though.

jaide18:09:14

That is true but right now weā€™re paying waaaayyy too much to a datacenter hosting company and the CTO above me left. I donā€™t have the system administration experience, knowledge or skill to do AWS proper and it would be a large risk and increase in responsibilities to keep AWS services setup correctly. Thatā€™s where I think Heroku would be a good fit for us. Significantly cheaper than what weā€™re paying now but a lot less time required to manage it.

valtteri18:09:26

Developer experience is great with Heroku. It costs more than AWS but you concentrate more on your apps and less on infrastructure.

valtteri18:09:15

Itā€™s a PaaS so you donā€™t get nearly as much flexibility though

jaide18:09:09

That is apparent but I donā€™t think our app is that complicated and the scalability it offers is still more flexible and cheaper than what we have now.

dangercoder18:09:24

I will have a sick app one day. Hopefully no one will build the same thing Lol

dangercoder18:09:44

But I might go the Heroku Path in the beginning. Seems really smooth

valtteri18:09:55

What db do you use? Heroku has awesome support for Postgres.

jaide18:09:33

Fortunately weā€™re using Postgres

dangercoder18:09:20

@jayzawrotny what language are you currently using at your company?

jaide18:09:49

Currently itā€™s python + django, and JS but Iā€™ve slipped some clojurescript into some of our tooling.

jaide18:09:43

My major question atm is: If we do use Herokuā€™s postgres offerings, would we be able to run wal-e to backup to an s3 bucket we can access? I know Heroku offers that on its own already but from what Iā€™ve found that s3 backup is not directly accessible. Our development environments are based on accessing that, sanitizing it, and loading it into our dev machines.

valtteri18:09:38

If your app is written like this https://12factor.net itā€™s good fit for Heroku.

valtteri18:09:31

You might need to redo you dev env setup if you use heroku postgres, which I warmly recommend

valtteri18:09:05

Backups are easily accessible through the command line utils so it shouldnā€™t be too big of a deal

jaide18:09:48

I think the limit of those is like 20gb though right? Ours is 30gb+ right now

jaide18:09:55

For local development what would you recommend? The goal from my perspective is to end up with a local instance of Postgres with a sanitized data set. Currently Iā€™ve setup our dev environment by composing docker containers.

valtteri19:09:41

We used docker-compose to setup dev envs. Heroku shares their docker images somewhere on Github so you can run pretty similar setup compared to the real one

jaide19:09:11

Ah great, docker-compose is definitely what Iā€™m using now. Switching out the images should be no problem.

valtteri19:09:15

I think they had some alternative way to deal with bigger dbs, but canā€™t remember what it was called

valtteri19:09:37

You can also write a custom worker that periodically dumps your db to S3.

valtteri19:09:24

But thatā€™s a bit of an effort :)

jaide19:09:06

Hah yeah, thatā€™s what I was thinking too as a worst case scenario which even then isnā€™t terrible. As long as I can get wal-e to connect to the database and an s3 bucket that should work if a better solution canā€™t be realized.

valtteri19:09:09

Iā€™m not familiar with wal-e but I guess there are several ā€œstream from db to S3ā€ solutions out there you can leverage if wal-e doesnā€™t work out

jaide19:09:15

Thatā€™s what weā€™re using currently and is what Heroku uses behind the scenes in their Continuous Protection but youā€™re right, Iā€™ve even heard that https://pgbackrest.org/ might be better anyway

valtteri19:09:51

Need to go now but hopefully this was somehow helpful! I encourage you to try Heroku, that way youā€™ll find out if it works for you or not.

jaide19:09:30

Good idea, my plan is to just try and get things running on my own account to get a feel for it. Price it out to scale it up and then go from there. Thanks for the help.