41–50 of 63 posts
Are there any examples of how the repository/database layer fits here?
What'll happen to the name m3o when Micro reaches 4.0?
Earlier quoted context omitted.
> Stop trying to tell the river where to turn. It's already done. After almost a decade of HN I have to say that's one of the most un-HN comments I have ever read.
I think you're confusing daring and innovation with legacy swaddling.
Additionally we invested a lot in a unparalleled test-suite in this space which runs against the old and new codebase.
How could we innovate further?
Earlier quoted context omitted.
It wouldn't be an issue for me if these legacy products either a. opted for more ethics where their fork showed them the way or b. if they actually produced innovation instead of desperately holding onto big company departments. OpenOffice, for example, has basically done nothing but maintenance. It's not something to be proud of.
> nothing but maintenance. It's not something to be proud of What? Absolutely! Maintenance is hard. Maintenance of old/big/complex systems is even harder. Maintaining something for so long with substantial user base is definitely something to be proud for. Everything doesn't need to constantly add features in order for people to be proud of their work. Just adding bug/security fixes once you feel something is feature…
I've been learning golang for backend dev, and for that reason checked your project. Is this sort of like Netlify for the backend? Are there any examples of how the repository/database layer fits here? What'll happen to the name m3o when Micro reaches 4.0?
I've been learning golang for backend dev, and for that reason checked your project. Is this sort of like Netlify for the backend? Are there any examples of how the repository/database layer fits here? What'll happen to the name m3o when Micro reaches 4.0?
The M3O Docs have some content about getting started with things quickly https://docs.m3o.com/getting-started but we need to add more. The open source docs are a great reference https://micro.mu/reference and otherwise we're working on some sample services in https://github.com/micro/services.
Well luckily M3O is M[icr]o so I think we're going to get away with it for the long term :)
I've been learning golang for backend dev, and for that reason checked your project. Is this sort of like Netlify for the backend? Are there any examples of how the repository/database layer fits here? What'll happen to the name m3o when Micro reaches 4.0?
The format of a numeronym is to take the first letter of a string (micro) + x + the last letter of the string, and replace x with the number of characters between both. So, Andreesen Horowitz (the most popular one I'm aware of) becomes a16z. Micro becomes m3o.
- Key-Value Storage
- Event Streaming
I've been learning golang for backend dev, and for that reason checked your project. Is this sort of like Netlify for the backend? Are there any examples of how the repository/database layer fits here? What'll happen to the name m3o when Micro reaches 4.0?
Yes! We are Netlify for the backend and in fact our next post will be titled "Netlify for your frontend, Micro for the backend". We think there's really a need to do what Netlify did for frontend to the backend and just help people build APIs and services super fast. The M3O Docs have some content about getting started with things quickly https://docs.m3o.com/getting-started but we need to add more. The open source d…
I'm going to start a new project and if this can help me save time and not have to deal with aws, etc would be great! Depending on cost of course. Hopefully we can get some info in terms of cost.
About the repository/database layer, I found the "store" documentation; just going through things quickly at the moment, but guess that's what store means in the Architecture?
I'll check the examples you've provided and read the documentation properly.
Thank you and good luck!
Noncompete
Any purpose is a permitted purpose, except for providing any product that competes with the software or any product the licensor or any of its affiliates provides using the software.
Can someone explain the implications of this point of the Polyform license? (It seems perhaps AGPL-like but 'product' could be very broad) Noncompete Any purpose is a permitted purpose, except for providing any product that competes with the software or any product the licensor or any of its affiliates provides using the software.