home.social

#emberjs — Public Fediverse posts

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

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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.

  6. 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

  7. 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

  8. 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

  9. 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

  10. 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

  11. 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.

  12. 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.

  13. 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.

  14. 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.

  15. 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.

  16. 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.

  17. 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.

  18. 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.

  19. 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.

  20. 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.

  21. @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.

  22. @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.

  23. @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.

  24. @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.

  25. @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.

  26. If you’d like to get your app onto modern #emberjs, reach out! We’ve helped several teams benefit from Vite and the latest Ember patterns – have the team behind the Ember initiative work with you on your most pressing issues!
    fosstodon.org/@mainmatter/1156

  27. If you’d like to get your app onto modern #emberjs, reach out! We’ve helped several teams benefit from Vite and the latest Ember patterns – have the team behind the Ember initiative work with you on your most pressing issues!
    fosstodon.org/@mainmatter/1156

  28. If you’d like to get your app onto modern #emberjs, reach out! We’ve helped several teams benefit from Vite and the latest Ember patterns – have the team behind the Ember initiative work with you on your most pressing issues!
    fosstodon.org/@mainmatter/1156

  29. If you’d like to get your app onto modern #emberjs, reach out! We’ve helped several teams benefit from Vite and the latest Ember patterns – have the team behind the Ember initiative work with you on your most pressing issues!
    fosstodon.org/@mainmatter/1156

  30. If you’d like to get your app onto modern #emberjs, reach out! We’ve helped several teams benefit from Vite and the latest Ember patterns – have the team behind the Ember initiative work with you on your most pressing issues!
    fosstodon.org/@mainmatter/1156

  31. Le #EmberFest c'est quand même une conférence très choupi. Les gens sont bienveillants, c'est assez petit pour pouvoir assister à tous les talks, et des devs venus pour la 1ère fois cette année m'ont dit être très content·e·s (comme quoi c'est pas que moi qui le dis).

    Bref, c'est une bonne raison de plus d'essayer le framework #Ember si vous ne connaissez pas encore.

    #web #javascript #emberjs #conferences #frontend

  32. Le #EmberFest c'est quand même une conférence très choupi. Les gens sont bienveillants, c'est assez petit pour pouvoir assister à tous les talks, et des devs venus pour la 1ère fois cette année m'ont dit être très content·e·s (comme quoi c'est pas que moi qui le dis).

    Bref, c'est une bonne raison de plus d'essayer le framework #Ember si vous ne connaissez pas encore.

    #web #javascript #emberjs #conferences #frontend

  33. Le #EmberFest c'est quand même une conférence très choupi. Les gens sont bienveillants, c'est assez petit pour pouvoir assister à tous les talks, et des devs venus pour la 1ère fois cette année m'ont dit être très content·e·s (comme quoi c'est pas que moi qui le dis).

    Bref, c'est une bonne raison de plus d'essayer le framework #Ember si vous ne connaissez pas encore.

    #web #javascript #emberjs #conferences #frontend

  34. Le #EmberFest c'est quand même une conférence très choupi. Les gens sont bienveillants, c'est assez petit pour pouvoir assister à tous les talks, et des devs venus pour la 1ère fois cette année m'ont dit être très content·e·s (comme quoi c'est pas que moi qui le dis).

    Bref, c'est une bonne raison de plus d'essayer le framework #Ember si vous ne connaissez pas encore.

    #web #javascript #emberjs #conferences #frontend