I love Lit! I have been using it to develop a in-app widget for product updates here: https://supanotice.com (the in app-widget opens up if you click on the bubble in the bottom right corner)
Really love the abstraction that makes web components easy to use.
The newspage (https://updates.supanotice.com) will work without JavaScript but the in-app widget that you see in the lower right corner on my page require JavaScript. However, it is completely framework agnostic and is based on web components. It will require that you add a script-tag in head and a tag in the body and you're good to go.
A FAQ for the landing page is on it's way and I will be working on improving the landing page with screenshots and examples so you can get a better feel for it.
I didn't know it worked without JS myself :-) I guess it's a side effect you get when rendering on the server using Elixir / Phoenix
* Your Role/Industry: I work as a software developer at a quite small european bank.
* Teamwork: We do not use Obsidian for teamwork but I would guess that we're around 10-20 people using Obsidian for note taking.
* Use cases: Primarily for note taking, meeting notes, presentations and technical documentation.
* Features: I use tasks, Excalidraw and the Iconize plugin. Also tinkering with the Canvas but does not use it for anything serious yet.
* Workflow: I just use the daily note feature to bring up a page where I write down tasks I need to finish that day. If I need to write something longer I will create a separate page for that and create a link in the daily note to that page.
It was a bad move not include protection against SQL injection to begin with. I was thinking about keeping it as simple as possible and just show a simplified example. But I think this was a bad thing to do so I have updated the example so it now uses postgres_escape.
And yes, this approach should only be used for very simple APIs. If you're building something bigger, use a framework.
I don't agree about JQuery. The learnability is good and it's really easy to get things done very fast. But when the code base grows it becomes really hard to maintain the code if you don't know JavaScript very well and know how to structure the code.
That's why many people have started to use CoffeeScript and/or Backbone.js to write more maintainable JavaScript. But the CoffeeScript/Backbone.js route is harder for beginners but in the long run it's a much better choice.
Really love the abstraction that makes web components easy to use.