HN user

stephane-klein

37 karma

Homepage: https://sklein.xyz

meet.hn/city/fr-Paris

Socials: - stephane-klein.at.hn - github.com/stephane-klein - linkedin.com/in/stephanekleinfrommetz

Interests: DevOps, Data Science, Freelancing, Open Source, Programming, Remote Work, Technology, Web Development

---

Posts10
Comments36
View on HN

I read here https://www.fediscovery.org/ :

  > How is this related to relays?  
  >  
  > Relays can be used to get a more complete view of what is going   on in the larger  
  > Fediverse. As such there are some similarities to this proposal.  
  >  
  > From an instance operator’s point of view the biggest difference is that using a relay
  > comes with a higher cost. The instance needs to ingest and index everything the relay
  > sends which takes up processing power and storage. A discovery provider will do that
  > work for one or more instances.
  >
  > Implementation-wise we expect to see some similarities with how relays work, at least
  > for real-time data. But discovery providers should be able to index historic data as
  > well. So ingesting real-time data from instances is only part of the story.
  > Querying instances for historic data is not currently something that relays do.

Why did you choose sveltekit-i18n instead of another svelte i18n lib?

Mainly for the following argument:

- It is built for SvelteKit and has good SSR support.

And also, the following:

- The translations are loaded for visited pages only. (and only once!) - As of v2.4.2, the size of the sveltekit-i18n package is 14 kB in the minified form and 4.6 kB in minified + gzipped form

From https://blog.aakashgoplani.in/comparing-i18n-libraries-in-sv...

I just started a project and chose this stack:

- SSR SvelteKit with Hydration (https://github.com/sveltejs/kit)

- PostgreSQL database server

- Postgres.js - PostgreSQL client for Node.js (https://github.com/porsager/postgres)

- Migration powered by graphile-migrate (https://github.com/graphile/migrate)

- PostgreSQL Row-Level Security (https://www.postgresql.org/docs/16/ddl-rowsecurity.html)

- svelte-headlessui (https://github.com/rgossiaux/svelte-headlessui)

- sveltekit-i18n (https://github.com/sveltekit-i18n/lib)

- TailwindCSS (https://tailwindcss.com/)

- Superforms (https://superforms.rocks/)

- sveltekit-flash-message + svelte-french-toast (https://github.com/ciscoheat/sveltekit-flash-message + https://github.com/kbrgl/svelte-french-toast)

Tooling :

- asdf (https://asdf-vm.com/)

- Docker and Docker Compose

- NodeJS

- pnpm

- Jest for unittest

All deployed on a VM at Scaleway (https://www.scaleway.com/en/) with Bash script (https://github.com/stephane-klein/sveltekit-tendaro-webshell...)

After 3 months of development on this stack, I'm very satisfied. My application is fast, light and requires very little code.

Project skeleton example: https://github.com/stephane-klein/sveltekit-tendaro-webshell...

In my understanding, Nim at the moment is really a transpiled language, instead of compiled. Transpiled to C, then tooling uses clang or gcc to do compilation from C to target platforms.

If I understood correctly, like the Vala language: https://vala.dev/ (Note: Vala is strongly integrated with GObject).

Firefox 91 5 years ago

We’d like to extend a special thank you to the 210 volunteers who helped resolve more than 1,200 bugs in the Firefox 91 release

1200 bugs!