4 ms·

Hey (Micro Author and CEO here). I hear you. GUI is a thing that's hard to break away from with the point and click crowd. This is where "IT" people and old sch

by asim 6y ago

Hey (Micro Author and CEO here). I hear you. GUI is a thing that's hard to break away from with the point and click crowd. This is where "IT" people and old school sysadmins becoming devops people likely thrive with the AWS dashboard, but considering most devs are writing code and use Git we think the CLI first approach is really key. To this point when we do anything on the web it will start purely as a CLI at m3o.com/cli and replicate the existing terminal experience, but maybe with some messaging like component so you can have nice emojis, rendering screenshots for graphs, etc. When it comes to cheque signing (6-9 figure deals) from the people with the money, I'm sure at that point we'll have to do something to win them over but we're a long ways from it right now.

paultopia 6y ago
This looks really cool! Personally, I'd use it---web interfaces are getting increasingly annoying these days. But do you have plans to release libraries for your API in major languages? Stringing together a bunch of shell commands in a bash script is also a little bit annoying... or at least much less friendly than doing the same thing with, say, a Python lib...
- asim 6y ago
  Thanks! Yes, so the CLI is the main consumption experience but Micro is geared towards services development, meaning we provide a Framework, CLI and Server that all work together. The CLI is mostly just proxying commands via a gRPC server and the entire thing is written in Go so everything we do in the CLI you can use the Framework to do in code. We also generate multi-language clients. Check out the 3.0 release announcement for more info https://micro.mu/blog/2020/11/05/micro-v3-aka-m3o.html https://micro.mu/blog/2020/11/05/micro-v3-aka-m3o.html
ball_of_lint 6y ago
Git isn't a great proxy for cli usage. Many developers use git exclusively through a GUI or their text editor.
pjmlp 6y ago
I use Git, hidden away in the comfort of my IDEs and desktop shell extensions. When I started in computing, CLI was the only option, and I don't miss those days. Good luck with your endevours.

by asim 6y ago

paultopia 6y ago

This looks really cool! Personally, I'd use it---web interfaces are getting increasingly annoying these days. But do you have plans to release libraries for your API in major languages? Stringing together a bunch of shell commands in a bash script is also a little bit annoying... or at least much less friendly than doing the same thing with, say, a Python lib...

asim 6y ago
Thanks! Yes, so the CLI is the main consumption experience but Micro is geared towards services development, meaning we provide a Framework, CLI and Server that all work together. The CLI is mostly just proxying commands via a gRPC server and the entire thing is written in Go so everything we do in the CLI you can use the Framework to do in code. We also generate multi-language clients. Check out the 3.0 release announcement for more info https://micro.mu/blog/2020/11/05/micro-v3-aka-m3o.html https://micro.mu/blog/2020/11/05/micro-v3-aka-m3o.html

ball_of_lint 6y ago

Git isn't a great proxy for cli usage. Many developers use git exclusively through a GUI or their text editor.

pjmlp 6y ago

I use Git, hidden away in the comfort of my IDEs and desktop shell extensions. When I started in computing, CLI was the only option, and I don't miss those days. Good luck with your endevours.