brillout

11 ms·

61.
by brillout 5y ago
Shameless plug: https://vite-plugin-ssr.com a do-one-thing-do-it-well alternative to Next.js which is feature-complete & stable (no breaking changes in the foreseeable future).
62.
by brillout 5y ago
Sounds like you are being biased here. I mean, if you think vite-plugin-ssr to be rigid, then Next.js should feel like a 2sqm prison cell to you ;-). If you want more flexibility than vite-plugin-ssr then use Vite's native SSR API. Whe
63.
by brillout 5y ago
https://vitejs.dev/guide/comparisons.html#snowpack
64.
by brillout 5y ago
> It just isn't suitable for proper server-side rendering, we'd need access to chunk names at build time You can at later rollup hooks (it doesn't make sense to access chunks that don't exist yet). Actually, there are
65.
by brillout 5y ago
Author of vite-plugin-ssr [1] here. Let me know if you have any question about doing SSR with Vite. (vite-plugin-ssr provides a similar DX than Nuxt/Next.js but as a simple do-one-thing-do-it-well Vite plugin. Vite has a powerful SSR n
66.
by brillout 6y ago
The goal of enforce mode is to increase conversion rate. Let's for example imagine following rates: - Donations: 0.1% (Open Collective / GitHub Sponsors) - Trust mode: 1% - Enforce mode: 10%-50% Even if we do a poor job with the e
67.
by brillout 6y ago
Yes you could fork an Lsos project and 1. remove the dependency from the source code, 2. re-build the distribution, 3. re-publish the distribution. You'd have to do this everytime you'd want to use a new release. It's trivial
68.
by brillout 6y ago
Author here. I've thought a lot about this. I believe the future we want is: 1. Open Source. 2. Pricing for larger companies while staying for free for anyone else. Many believe that trust mode [1] cannot work. But that's not true
69.
Show HN: Lsos – open-source, financially sustainable and independent(lsos.org)
5 points by brillout 6y ago|6 comments
70.
by brillout 6y ago
Author here. React announced React Server Componets [1] and an interesting feature is the ability to load data without having to create an API. You can already do that today with Wildcard API. I've used it at many projects now and it&#
71.
Show HN: Wildcard API – Data Loading Like React Server Components, Today(github.com)
2 points by brillout 6y ago|1 comments
72.
Show HN: Functions as API(github.com)
2 points by brillout 6y ago|0 comments
73.
by brillout 6y ago
> Which is precisely one of the reasons GraphQL exists, so you can change the data queryable in your API without changing the data existing clients receive. If we're talking about moving from GraphQL to SQL then we shouldn't be
74.
by brillout 6y ago
> Backwards compatibility and API versioning strategies can easily handle this kind of situation. From experience using Wildcard API (a super easy RPC implementation [1]), you usually don't need to do API versioning at all. Instead
75.
by brillout 6y ago
You can also use RPC to securely expose SQL queries. This is for example what Wildcard API ( https://github.com/reframejs/wildcard-api ) does: endpoints.deletePost = async function(postId){ // Only
76.
by brillout 7y ago
One way to think about Wildcard (and RPC in general) is that it allows you to directly use SQL queries to retrieve and mutate data for your frontend. That said, if you prefer using Relay + GraphQL over writing SQL queries, then Wildcard (an
77.
by brillout 7y ago
I appreciate your elaborate answer. Thank you. I'm a minimalist and as such I have a problem with complex solutions to simple problems. That's my whole point. My dream ORM is a an ORM that is designed with a) an obsession on simpl
78.
by brillout 7y ago
> you're comparing apples and oranges I agree, Hasura and Wildcard have different goals. Still, the merits of each tool can be talked and discussed about. > you aren't writing any SQL queries. You are creating your database
79.
by brillout 7y ago
Curious, what do you think of RPC instead of GraphQL? E.g. https://github.com/reframejs/wildcard-api for JavaScript. The neat thing about RPC is that you can tap into the full power of PostgreSQL "directly" f
80.
by brillout 7y ago
Do you really need to decouple frontend and backend in the first place? Why not separating concerns instead of separating technologies? Tight coupling of UI with database but decoupling of e.g. admin UI/backend from end-user UI/ba
81.
by brillout 7y ago
Curious to know what you think of the React + RPC (e.g. https://github.com/reframejs/wildcard-api ) + PostgreSQL stack in comparison to React + Relay + GraphQL + PostgreSQL? RPC tightly couples frontend and backend. Dec
82.
by brillout 7y ago
Instead of Hasura and GraphQL, you can use RPC and directly write SQL queries to retrieve and mutate data. One way to think about this is that with RPC you remove the whole API layer and directly write SQL queries instead, while permissions
83.
by brillout 7y ago
For me it's all about trust; if you can somehow increase trust you'd win folks like me over. E.g. saying "if we shut down we'll notify you one week prior".
84.
by brillout 7y ago
It was guesstimate. It "looks" older and more indie whereas improvmx looks more startup-ish. It also increases trust that the code is open source. Actually the forwarding doesn't seem to work so I may switch over to you guys
85.
by brillout 7y ago
Ok sounds good :-). I just registered with https://forwardemail.net/ instead though. Because they are older which makes me trust them more - that they won't close shop next week. Although the UX of improvmx seems much
86.
by brillout 7y ago
This is exactly what I was looking for! I wonder though: how can I trust you guys that you'll successfully manage to redirect all emails? Loosing emails is really bad. Also I'm curious; how did you manage to land #1 on Google for
87.
Free email aliases – contact[at]piedpipper.com → richard.hendricks[at]gmail.com(improvmx.com)
1 points by brillout 7y ago|0 comments
88.
by brillout 7y ago
Author here. For those who don't know what RPC is, RPC (Remote Procedure Call) denotes the practice of calling a procedure that is defined on a remote computer (or different process) as if it were defined locally on the same computer (
89.
Show HN: Wildcard API – RPC between front end and back end(github.com)
2 points by brillout 7y ago|1 comments
90.
by brillout 7y ago
The most fundamental difference between RPC and REST/GraphQL is that RPC is schemaless whereas a RESTful or GraphQL API has a schema. The whole point of a schema is to have a generic API. Whereas with RPC and any other schemaless app

More ›