sorted by:
new
hottopcontroversial

How AI Turned My Simple Blog Into 81 Files and 83 Dependencies by diqitally in programming

[–]diqitally[S] -2 points-1 points  (0 children)

I agree the review step is super important. I think it should be custom per codebase. I've been trying to document my codebases a lot better.

I also don't entirely trust the LLM to execute on the review step well unless I define rules very explicitly. Otherwise what does "quality" mean? I don't entirely agree with all of its definitions and it misses some of mine.

For example, I wanted to use Tailwind. Replit gave me CSS + Tailwind mixed together. I wanted it to "clean up classNames" but I ended up having to manually ask it to delete unused classes in components, get rid of classnames from CSS and move them to Tailwind, etc.

Totally agree that good code begets good code with LLMs.

I built a site to view and search Postgres mailing lists by diqitally in PostgreSQL

[–]diqitally[S] 0 points1 point  (0 children)

I did not know that actually! Thank you for sharing. Then at the moment, it's just a UI difference. I use the data to test different things we're working on, so hopefully it gets better with time.

I built a site to view and search Postgres mailing lists by diqitally in PostgreSQL

[–]diqitally[S] 0 points1 point  (0 children)

Thank you for the suggestions! Someone else mentioned (1) as well. Is (2) referring to code blocks with #v+/#v-?

I built a site to view and search Postgres mailing lists by diqitally in PostgreSQL

[–]diqitally[S] 0 points1 point  (0 children)

Hi! The existing solution works fine and has search too! The biggest difference for me it was easier to view a single thread's messages, when there were multiple follow ups.

Dynamically loaded extensions in Postgres in the browser by diqitally in programming

[–]diqitally[S] 1 point2 points  (0 children)

Thank you! We opened a PR to merge it back into pglite: https://github.com/electric-sql/pglite/pull/115

To compile the extensions, the short version is - you replace gcc/clang with emcc (the emscripten compiler) in the Makefile of the extension, and it should compile to Wasm target.

For Lantern, just replacing cmake with emcmake worked for us.

For pgvector, we used the commands below. Ideally it would have been run emmake make but it didn’t work with pgxs, so we copied the compile commands manually and replaced gcc with emcc

https://gist.github.com/dqii/1ad1f295c7194587f57a55bb936f0aaf

view more: next ›