@font-face {font-family: AMSRegular; src: url('/kafonts/KaTeX_AMS-Regular.ttf');} how do I translate that line into garden/css ?

> Please enter the details. Mandatory fields are marked by * (Note: your password will be confirmed to you by email) Well that seems safe > *E-mail (all lower case) Well that isn't compliant

apparnetly the trick is to use "@font-family" to get the @ to appear in css

Hi! I’ve a question which I am not sure where to fit, so I will drop it here. Lately I have been feeling sullen about the state of the tools I have been using to build backend applications. Most of my recent projects have been web applications, so I am referring API backends with fairly simple needs (crud, authentication, authorisation, etc). Over the years I have worked with a number of frameworks/languages (PHP/Laravel/Symfony, Ruby/Rails, etc), and some of them were very good at getting things done, but none really satisfied me on a conceptual level. For example, often Authorisation is done at the route level (at least on projects I have touched). I am vaguely familiar with approaches such as using a command bus to take those concerns out of the API layer, but not in depth. Recently I have started to learn Clojure, which has a lot of exciting ideas, but I have yet to find a project which really inspires me on how I should write/structure my backend code. Has anyone had similar feelings and found a solution that they feel happy with?

This has been particularly bugging me lately as I have been working with a GraphQL API, where the “point of entry” to your data is a bit less defined than with a more standard REST api.

If that makes any sense! Re-reading myself I realise this wasn’t the clearest way to express what’s on my mind

Happy to elaborate

i understand that you want to have a framework that "dictates" how you should do things, like authorisation and other frequent but hard-to-get-right things ?

the thing is, clojure makes no real assumptions on how you want to do things

so it's rather up to you how you want to implement such things

@lmergen not really a framework. I am young and haven’t seen much in the world; I would like to be aware of how experienced developers structure those things

🙂

to be honest, that's not really language specific but more generally about each of those topics

so you can probably learn a lot by just looking around on the internet

any particular topic you want to learn more about ?

@lmergen just wondering if there are any decently well known architectural pattern I am missing out on when it comes to structuring fairly simple web backend code (CRUD, with authorisation and validation concerns). It seems to be that those things should be simple but often lead to a lot of incidental complexity

maybe I should take a look at Vase

as @weavejester said, i would recommend to take a look at duct. i think vase is fairly limited in the type of problems it tries to solve (microservices), and duct is a more general architectural pattern.

i find the things you learn/use with duct are more generally applicable.

anyone have sample code for using https://google.github.io/closure-library/api/goog.net.WebSocket.html ?

in particular, I want to register on-message / on-error listeners