Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Now I am not a web dev but I just stumbled upon Electron and envied all web devs.Seems fun being a web dev
20 -
Follow up to yesterday’s “hybrid/cross-platform is shit” rant about Electron apps being blocked from the Apple App Store.
See the below image of the github issues template on the Electron repo, to file an issue for this problem.
Yes, this is such a common issue with their product, they’ve made it easier to file a github issue. Let’s not address the fact that there is a fundamental flaw in the approach they are using, let’s just make it easier to open a ticket while everyone waits to see if we are allowed to ship our app.
I’ve also heard talk that under some circumstances it’s possible for them to patch out the libraries causing issues. Apple provides tools to identify these libraries ... therefore Electron is doing fuck all to adresss this issue, and adopting a “wait until someone complains” style of approach.
A+
7 -
Has been a long time since I'm appreciating working with GRPC.
Amazingly fast and full-featured protocol! No complaints at all.
Although I felt something was missing...
Back in the days of HTTP, we were all given very simple tools for making requests to verify behaviours and data of any of our HTTP endpoints, tools like curl, postman, wget and so on...
This toolset gives us definitely a nice and quick way to explore our HTTP services, debug them when necessary and be efficient.
This is probably what I miss the most from HTTP.
When you want to debug a remote endpoint with GRPC, you need to actually write a client by hand (in any of the supported language) then run it.
There are alternatives in the open source world, but those wants you to either configure the server to support Reflection or add a proxy in front of your services to be able to query them in a simpler way.
This is not how things work in 2018 almost 2019.
We want simple, quick and efficient tools that make our life easier and having problems more under control.
I'm a developer my self and I feel this on my skin every day. I don't want to change my server or add an infrastructure component for the simple reason of being able to query it in a simpler way!
However, This exact problem has been solved many times from HTTP or other protocols, so we should do something about our beloved GRPC.
Fine! I've told to my self. Let's fix this.
A few weeks later...
I'm glad to announce the first Release of BloomRPC - The first GRPC Client GUI that is nice and simple,
It allows to query and explore your GRPC services with just a couple of clicks without any additional modification to what you have running right now! Just install the client and start making requests.
It has been built with the Electron technology so its a desktop app and it supports the 3 major platforms, Mac, Linux, Windows.
Check out the repository on GitHub: https://github.com/uw-labs/bloomrpc
This is the first step towards the goal of having a simple and efficient way of querying GRPC services!
Keep in mind that It is in its first release, so improvements will follow along with future releases.
Your feedback and contributions are very welcome.
If you have the same frustration with GRPC I hope BloomRPC will make you a bit happier!
3 -
Having a look at electron again after giving up on it months ago.
I must say, the documentation has improved a lot since then, and it looks---dare I say---intuitive to use?
The electron api demos app is surely some help, but I'm not really all that sure how much it lives up to its name. It doesn't really demonstrate anything, and it doesn't cover the whole api, just small chunks of it.
Loving the event system though!12 -
I maintain and develop a FOSS repository on GitHub and I intend to migrate from Electron to Flutter.
What is the proper procedure for this?
I want to keep the name and community but it also feels a bit messy.
Do I just wipe everything old on the main branch and keep a branch that reflects the newest Electron version or do I move to a new repository and start over?
Tips and feedback is appreciated!4 -
Hearing a lot about Microsoft trying to acquire Github here on devRant.
Made me think, if this happens what will happen to atom?
Development will likely continue but then you would have two electron based, open source code editors both by Microsoft and Github. Probably not that much different from now, but still feels awkward...
Any thoughts? I love both editors and use them near daily. I just hope Atom was more performant and as actively developed as vscode.10
Top Tags
Weekly Rant
View