home.social

#emberjs — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #emberjs, aggregated by home.social.

fetched live
  1. RE: fosstodon.org/@mainmatter/1170

    I'm also very excited to be both attending and speaking again this year! #EmberJS

  2. RE: fosstodon.org/@mainmatter/1170

    I'm also very excited to be both attending and speaking again this year! #EmberJS

  3. RE: fosstodon.org/@mainmatter/1170

    I'm also very excited to be both attending and speaking again this year!

  4. RE: fosstodon.org/@mainmatter/1170

    I'm also very excited to be both attending and speaking again this year! #EmberJS

  5. RE: fosstodon.org/@mainmatter/1170

    I'm also very excited to be both attending and speaking again this year! #EmberJS

  6. Mes notes hebdo de ce 12 Juin :

    🥒 Des légumes et des livres, une journée au Printemps des Viennes #expo
    🚀 L'API import.meta.glob pour Ember classique arrive #emberjs
    🪺 Ninipiou 2 #fougere
    🦆 Canards et mythos

    🇫🇷 blog.dunstetter.fr/fr/posts/no
    🇺🇸 blog.dunstetter.fr/posts/weekl

  7. Mes notes hebdo de ce 12 Juin :

    🥒 Des légumes et des livres, une journée au Printemps des Viennes #expo
    🚀 L'API import.meta.glob pour Ember classique arrive #emberjs
    🪺 Ninipiou 2 #fougere
    🦆 Canards et mythos

    🇫🇷 blog.dunstetter.fr/fr/posts/no
    🇺🇸 blog.dunstetter.fr/posts/weekl

  8. I don't get people being upset for other people calling out their language/framework/tech of choice.

    There are some objectively and subjectively problematic things in all the spaces I'm part of and love. From #RoR, through #Tailwind to #EmberJS

    Do I feel that maybe your view is not the best? Maybe. Do I get butt-hurt because of it? Nah, you do you. I'd rather hear criticism than enclosing myself in my own bubble.

  9. I don't get people being upset for other people calling out their language/framework/tech of choice.

    There are some objectively and subjectively problematic things in all the spaces I'm part of and love. From #RoR, through #Tailwind to #EmberJS

    Do I feel that maybe your view is not the best? Maybe. Do I get butt-hurt because of it? Nah, you do you. I'd rather hear criticism than enclosing myself in my own bubble.

  10. I don't get people being upset for other people calling out their language/framework/tech of choice.

    There are some objectively and subjectively problematic things in all the spaces I'm part of and love. From #RoR, through #Tailwind to #EmberJS

    Do I feel that maybe your view is not the best? Maybe. Do I get butt-hurt because of it? Nah, you do you. I'd rather hear criticism than enclosing myself in my own bubble.

  11. I don't get people being upset for other people calling out their language/framework/tech of choice.

    There are some objectively and subjectively problematic things in all the spaces I'm part of and love. From #RoR, through #Tailwind to #EmberJS

    Do I feel that maybe your view is not the best? Maybe. Do I get butt-hurt because of it? Nah, you do you. I'd rather hear criticism than enclosing myself in my own bubble.

  12. I don't get people being upset for other people calling out their language/framework/tech of choice.

    There are some objectively and subjectively problematic things in all the spaces I'm part of and love. From #RoR, through #Tailwind to #EmberJS

    Do I feel that maybe your view is not the best? Maybe. Do I get butt-hurt because of it? Nah, you do you. I'd rather hear criticism than enclosing myself in my own bubble.

  13. Ever wanted to take heap of Spotify links and turn them into beautiful, scannable cards that you can then convert to physical world (read: print) and distribute as individual cards, or assemble into a nice flipbook? You didn't? Well now you do! Lives entirely in the browser (apart from necessary 3rd party data loading) and is free forever!

    spotify-flipbook.netlify.app/

    #Spotify #OSS #EmberJS #VibeCoded

  14. Ever wanted to take heap of Spotify links and turn them into beautiful, scannable cards that you can then convert to physical world (read: print) and distribute as individual cards, or assemble into a nice flipbook? You didn't? Well now you do! Lives entirely in the browser (apart from necessary 3rd party data loading) and is free forever!

    spotify-flipbook.netlify.app/

    #Spotify #OSS #EmberJS #VibeCoded

  15. Ever wanted to take heap of Spotify links and turn them into beautiful, scannable cards that you can then convert to physical world (read: print) and distribute as individual cards, or assemble into a nice flipbook? You didn't? Well now you do! Lives entirely in the browser (apart from necessary 3rd party data loading) and is free forever!

    spotify-flipbook.netlify.app/

    #Spotify #OSS #EmberJS #VibeCoded

  16. Ever wanted to take heap of Spotify links and turn them into beautiful, scannable cards that you can then convert to physical world (read: print) and distribute as individual cards, or assemble into a nice flipbook? You didn't? Well now you do! Lives entirely in the browser (apart from necessary 3rd party data loading) and is free forever!

    spotify-flipbook.netlify.app/

    #Spotify #OSS #EmberJS #VibeCoded

  17. Ever wanted to take heap of Spotify links and turn them into beautiful, scannable cards that you can then convert to physical world (read: print) and distribute as individual cards, or assemble into a nice flipbook? You didn't? Well now you do! Lives entirely in the browser (apart from necessary 3rd party data loading) and is free forever!

    spotify-flipbook.netlify.app/

    #Spotify #OSS #EmberJS #VibeCoded

  18. RE: fosstodon.org/@mainmatter/1160

    We’re seeing more and more teams adopt multi-framework architectures with #emberjs, #react, #svelte, #vuejs, or #webcomponents mixed together in one big system. @nickschot wrote about some learnings from a recent project in which @mainmatter helped a client integrate Ember.js and React.

  19. RE: fosstodon.org/@mainmatter/1160

    We’re seeing more and more teams adopt multi-framework architectures with #emberjs, #react, #svelte, #vuejs, or #webcomponents mixed together in one big system. @nickschot wrote about some learnings from a recent project in which @mainmatter helped a client integrate Ember.js and React.

  20. RE: fosstodon.org/@mainmatter/1160

    We’re seeing more and more teams adopt multi-framework architectures with #emberjs, #react, #svelte, #vuejs, or #webcomponents mixed together in one big system. @nickschot wrote about some learnings from a recent project in which @mainmatter helped a client integrate Ember.js and React.

  21. RE: fosstodon.org/@mainmatter/1160

    We’re seeing more and more teams adopt multi-framework architectures with #emberjs, #react, #svelte, #vuejs, or #webcomponents mixed together in one big system. @nickschot wrote about some learnings from a recent project in which @mainmatter helped a client integrate Ember.js and React.

  22. RE: fosstodon.org/@mainmatter/1160

    We’re seeing more and more teams adopt multi-framework architectures with #emberjs, #react, #svelte, #vuejs, or #webcomponents mixed together in one big system. @nickschot wrote about some learnings from a recent project in which @mainmatter helped a client integrate Ember.js and React.

  23. One of the things that #EmberJS & it's ecosystem does (mostly) correctly wrt/ #SemanticVersioning is:

    ✅ Major versions are for breaking changes.
    ❌ Major versions are for adding fancy new features.

    It looks weird and less shiny at first, but let me reassure you: Once you start maintaining any slightly more complicated codebase, this is an absolute blessing.

  24. One of the things that #EmberJS & it's ecosystem does (mostly) correctly wrt/ #SemanticVersioning is:

    ✅ Major versions are for breaking changes.
    ❌ Major versions are for adding fancy new features.

    It looks weird and less shiny at first, but let me reassure you: Once you start maintaining any slightly more complicated codebase, this is an absolute blessing.

  25. One of the things that #EmberJS & it's ecosystem does (mostly) correctly wrt/ #SemanticVersioning is:

    ✅ Major versions are for breaking changes.
    ❌ Major versions are for adding fancy new features.

    It looks weird and less shiny at first, but let me reassure you: Once you start maintaining any slightly more complicated codebase, this is an absolute blessing.

  26. One of the things that #EmberJS & it's ecosystem does (mostly) correctly wrt/ #SemanticVersioning is:

    ✅ Major versions are for breaking changes.
    ❌ Major versions are for adding fancy new features.

    It looks weird and less shiny at first, but let me reassure you: Once you start maintaining any slightly more complicated codebase, this is an absolute blessing.

  27. @kaspi Yup, I believe. I mean my "home" framework #EmberJS used to have hidden imports. Now moving toward explicit ones. The former state was not great as the support of the tooling was meh. The new state is, objectively, also problematic, but everyone says "yaaay, this better" and that's why I'm like #ConfusedTravoltaMeme.
    But IDK, maybe I'm just missing some detail everyone else assumes and it's just broken in my env.