brillout

11 ms·

91.
by brillout 7y ago
You're right, it's not an answer. My goal is to rise awareness that RPC should be the default choice when creating an API. > REST and GraphQL themselves are responses to RPC, and you neither take that into account nor address i
92.
by brillout 7y ago
Author here. Let me know if you have questions.
93.
REST or GraphQL? A Simple Answer(medium.com)
8 points by brillout 7y ago|5 comments
94.
by brillout 7y ago
I can see the need for large projects to add structure between frontend and backend. But until you hit that point you're better off with RPC. "Premature optimization is the root of all evil" holds here as well. A startup shou
95.
by brillout 7y ago
I've been thinking about language agnostic RPC as well. That would be so neat! gRPC can already do that but gRPC's design is unnecessary bloated. The nice thing about RPC is its potential of zero-config setup. gRPC totally fails o
96.
Show HN: RPC Between Front End and Back End (Node.js) – REST/GraphQL Alternative(github.com)
5 points by brillout 7y ago|3 comments
97.
by brillout 7y ago
So true. That said, for an API consumed by third-party developers, REST makes a lot of sense. Otherwise, which is like 98% of the APIs out there, RPC really is superior. I've implemented a tool similar to what OP is building: Wildcard
98.
by brillout 7y ago
Have a look at Wildcard API[1], it's similar to what you are building. I'm the author. I'm glad to see that RPC is getting more and more traction. [1] https://github.com/reframejs/wildcard-api
99.
by brillout 7y ago
Why GraphQL? Why not simply RPC? E.g. for JS there is https://github.com/reframejs/wildcard-api . Is there something like that in Scala?
100.
by brillout 7y ago
"becoming the new SQL quickly" - Prisma, who led the way on that front, abandoned this pursuit. "Learn GraphQL" - I'm not sure you need to learn GraphQL. You need to now that GraphQL is a powerful tool for APIs cons
101.
by brillout 7y ago
There is also Wildcard API [1] for Node.js [1]: https://github.com/reframejs/wildcard-api
102.
by brillout 7y ago
> Tech should be about results, it should not be a religion. I couldn't agree more with this. I'm trying to get a small library [1] I wrote popular and it's insane how much resistance I get because it doesn't fit the
103.
by brillout 7y ago
What is it that Rails has that Node.js doesn't? Node.js is missing a great ORM but other than that I don't see many things missing in Node.js anymore. There is also Rails' admin panel but most projects don't need that.
104.
by brillout 7y ago
For internal APIs I'd recommend RPC and REST/GraphQL to create an API consumed by third parties. Wildcard's readme elaborates more on RPC vs REST: https://github.com/reframejs/wildcard-api (Wildcard is R
105.
by brillout 7y ago
This would be so neat but a problem is how do you distribute money in a fair way to creators? Spotify can give X dollars to a song author for each minute a user has listened to his song. You cannot easily do that with web content.
106.
by brillout 7y ago
Or Widcard API ( https://github.com/reframejs/wildcard-api ) for Node.js <-> Browser (Disclosure: I'm Wildcard's author.)
107.
by brillout 7y ago
Does someone know a tutorial for people like OP? Someone that knows programming but not modern web dev. I want to write such tutorial. > It's hard to build a mental model when things are happening at 4 level of abstractions away I f
108.
by brillout 7y ago
There are many JS libraries that are wonderfully simple. I think the problem is: - Too much choice; it's insane how much you have to decide before you get started: React or Vue? SSR or SPA? REST, GraphQL, or RPC? PostCSS or Sass? CSS-i
109.
by brillout 7y ago
The problem is the enormous amount of choice we have: - React or Vue? - Redux or stateful components? - GraphQL or REST or RPC? - SSR or SPA? - ... We are missing a framework with sensible defaults for all these questions. And that does a g
110.
by brillout 8y ago
e-bot7 | Munich, Germany | Full-time | Onsite | Visa Sponsor Full-stack JavaScript Engineer (Node/React/Vue) | Machine Learning Engineer | DevOps Engineer We bring artificial intelligence to customer service and help companies inc
111.
by brillout 8y ago
If you need SPA then yea it's easy. But when you need SSR it becomes a whole different story. Now imagine you want parts of your app to be SPA and some other parts of your app to be SSR. This becomes super complex. Frameworks like Refr
112.
by brillout 8y ago
Depending on what you need, setting up a React app is super complicated and time consuming. Especially when you need SSR. There is a reason why frameworks such as Next.js, Reframe, and now this one are being used. I'd actually say the
113.
by brillout 8y ago
Reframe author here ( https://github.com/reframejs/reframe ). This is super interesting, what are you plans regarding this? Super curious.
114.
by brillout 8y ago
Check out Reframe: https://github.com/reframejs/reframe It's a web framework like Zero Server and Next.js but everything is ejectable.
115.
by brillout 8y ago
The mistake is not to learn about frameworks but to spend too much time with the details of one framework. Reading a 500 pages book about a specific framework is most likely a waste of time. But getting an overview about the framework lands
116.
by brillout 8y ago
I'm surprised nobody mentioned this but this website and the whole JAMstack thingy is basically a PR stunt from Netlify. Static sites generators and the JAMstack are inherently crippled. With a JAMstack, by design, everything needs to
117.
by brillout 8y ago
I know this lock-in pain quite too well. That's why I've started a web framework with the goal of being entirely flexible. I've made all code ejectable, minimized/simplified the glue code (so that you eject beautiful cod
118.
by brillout 8y ago
Not currently but we are thinking about it, see https://github.com/AurelienLourot/ghuser.io/issues/103
119.
by brillout 8y ago
You're right. I edited my answer. The GitHub's unofficial API we are using is slow and per IP rate limited. We spin up several servers to have several IPs to circumvent the rate limit. (GitHub knows that we do that and we are in c
120.
by brillout 8y ago
> Could you make this work for gitlab, bitbucket and maybe even just regular old git repos as well?" Yes totally. Although we currently think that the best for the community is GitHub improving their GitHub profiles making ghuser.io

More ›