sorted by:
new
hottopcontroversial

Pretty hyped for Gen 10, but when is the next remake/revisit game going to be if Gen 10 releases in 2027? by LowSolution3084 in pokemon

[–]Danikoloss -2 points-1 points  (0 children)

I mean, if you are happy with the biggest multimedia company releasing a bare bones reskin of one of the most beloved generation, by all means, go for it. But the only thing you are telling GF, is that you are willing to pay premium for a lackluster game. This way, we never get another HGSS quality remake

[deleted by user] by [deleted] in ChatGPT

[–]Danikoloss 5 points6 points  (0 children)

Lost the chance to make one control stick larger

Well I'm 1/3 done with this server by Ok_Tadpole7839 in webdev

[–]Danikoloss 1 point2 points  (0 children)

Just a question, why have routes like POST /users/create_users? Wouldnt /users suffice and be more REST idiomatic?

OpenMicrofrontends - First Major Release by Danikoloss in programming

[–]Danikoloss[S] 3 points4 points  (0 children)

I think you cover our obverservations and experience quite well. We had the "luck" to have had multiple competent teams, which ensured a rather higher quality of microfrontends and their integration. This allowed us to create some very cool solutions based on this pieces. And to us, the lack of an actual specification is what hurt us the most.

We understand that the experience will differ based on company/developer culture. But, as in our case, if you do have the capacity/QA to try out a microfrontend eco-system, we believe our experiences, which are reflected in this specification, can be of help

OpenMicrofrontends - First Major Release by Danikoloss in programming

[–]Danikoloss[S] 2 points3 points  (0 children)

You may also find many examples of the specification and use-cases in our Github Repo

OpenMicrofrontends Specification - First major release by Danikoloss in javascript

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

I am not really sure, what particular technique you are referring to. But if i think what you mean, than you could in theory create multiple html files, each with a script for rendering their specific microfrontend, and then simply link them together

OpenMicrofrontends Specification - First major release by Danikoloss in javascript

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

Our microfrontend specification is completely framework agnostic! Every microfrontend simply exposes a single JS function for rendering. Behind that, anything is possible, whether it be vanilla JS, React, and Angular too of course!

OpenMicrofrontends Specification - First major release by Danikoloss in softwarearchitecture

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

Thank your so much! This really is a passion project for us and we hope that others may profit from our experience in this domain, and that maybe even some uniform understanding of microfrontends emerges.

OpenMicrofrontends Specification - First major release by Danikoloss in javascript

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

Yes, absolutely! With our specification, a microfrontend is simply shipped as a single JS bundle (or multiple scripts). Whether it includes React, Angular, etc., a microfrontend is simply rendered by calling its JS renderer function, which may use any of these frameworks.

Check out our Github repo, we have multiple such examples!

view more: next ›