mvila

12 ms·

1.
by mvila 4y ago
In 2023, when I think of "word processors", I think of them like Notion. When I think of "spreadsheets", I think of them like Airtable. And when I think of "to-do lists", I think of them like Basecamp's to
2.
by mvila 4y ago
Thanks, Jake, for your comment. Here's what we have in mind about onboarding customers and developers. The potential market is as large as the app market (B2B and B2C), but we will target small businesses at first and progressively exp
3.
by mvila 4y ago
TLDR: The SaaS model offers many benefits and is undoubtedly the future of software. However, when we moved from the good old desktop app to the SaaS apps, we lost a crucial component — the platform or operating system, such as Windows, mac
4.
by mvila 4y ago
@pc86 Please read the rest of the article. :)
5.
Show HN: The SaaS 2.0 Manifesto(1place.app)
10 points by mvila 4y ago|9 comments
6.
JavaScript Rising Stars in 2021(risingstars.js.org)
2 points by mvila 5y ago|0 comments
7.
by mvila 6y ago
Hi, everyone! I have been working on Liaison for a year and a half with an obsession — simplifying full-stack development as much as possible. Typically, a full-stack application is composed of a frontend and a backend running in two differ
8.
Show HN: Liaison 1.0 – Dramatically Simplify Full‑Stack Development(liaison.dev)
7 points by mvila 6y ago|1 comments
9.
by mvila 6y ago
Any Node.js environment can run the backend. As for the database, Liaison supports only MongoDB for now, but more databases are expected to be supported in the future.
10.
by mvila 6y ago
Interesting! It seems that both spelling are actually used...
11.
by mvila 6y ago
In a nutshell: - The frontend is "inherited" from the backend so there is no need to build an API server and an API client. - The database is abstracted away by an ORM. - The user interface can be encapsulated into the domain mode
12.
by mvila 6y ago
Thanks, exolymph. I thought so. I guess the "i" after "lia" seems a bit weird in English.
13.
by mvila 6y ago
By default, nothing is exposed. To make an attribute or a method accessible from the frontend, it must be explicitly exposed by using the `expose()` decorator.
14.
Ask HN: Is “Liaison” a good name for an open source project?
3 points by mvila 6y ago|11 comments
15.
Full Stack for All(hackernoon.com)
1 points by mvila 6y ago|0 comments
16.
Show HN: Liaison 1.0 – Reuniting the frontend and the backend(liaison.dev)
1 points by mvila 6y ago|0 comments
17.
Show HN: Liaison 1.0 – Build a Full-Stack Web App Two to Three Times Faster(liaison.dev)
1 points by mvila 6y ago|0 comments
18.
Unified Architecture – A Simpler Way to Build Full-Stack Apps(freecodecamp.org)
4 points by mvila 7y ago|0 comments
19.
Dramatically Simplify Full-Stack Development with a Unified Architecture(freecodecamp.org)
5 points by mvila 7y ago|1 comments
20.
How to Simplify Full-Stack Development with a Unified Architecture(freecodecamp.org)
2 points by mvila 7y ago|0 comments
21.
by mvila 7y ago
Liaison doesn't expose anything by default. Only the allowed attributes and methods are exposed.
22.
by mvila 7y ago
Liaison allows inheriting layers from each other. So, you can easily separate your API layer with your model layer, and you don't need to build a web API for that.
23.
by mvila 7y ago
About API versioning, the problem is the same as any web API. It's possible to add backward-compatible changes, otherwise, you need to fork the backend into a new endpoint. About interoperability with non-JS environments, I wrote an ar
24.
by mvila 7y ago
I wish that too. :)
25.
by mvila 7y ago
Liaison has nothing to do with a backend-as-a-service. You can host your backend anywhere you want. About authorization, Liaison doesn't expose anything by default. Only the specified attributes and methods are exposed, and there is an
26.
by mvila 7y ago
For now, Liaison is JS-focused. So both the frontend and the backend have to be implemented in JS. But the communication protocol ( https://deepr.io ) in between is language agnostic. So it is possible to imagine Liaison being por
27.
by mvila 7y ago
Your point is valid, but Liaison allows you to build different layers if you wish. If you worry about cluttering the business logic and want to clearly separate the exposed API, you can expose subclasses of your domain models instead.
28.
by mvila 7y ago
I don't understand why it is wrong to use CDNs to distribute common libraries. About the fact that I have used Liaison to build its own website, I agree that it might not be the best choice. :) For now, Liaison doesn't support ser
29.
by mvila 7y ago
This has nothing to do with JSON RPC. Liaison uses Deepr ( https://liaison.dev ) as a communication protocol. Regarding the number of XHR calls, to be accurate, it is not 6 but 4. Once Liaison is complete and optimized, the number
30.
by mvila 7y ago
For now, with Liaison, API versioning is no different than usual: preserved endpoint for backward-compatible changes and new endpoints for breaking changes.

More ›