thedavidprice

5 ms·

1.
by thedavidprice 5mo ago
I (we) have seen these pieces before: replay, time-travel debugging, tracing, APM, event sourcing, etc. What I haven’t seen is the whole thing work as described in a production setting. I.e. capture enough of a production run that you can r
2.
by thedavidprice 4y ago
How do you foresee region/country playing a part in the startups you choose to invest in?
3.
by thedavidprice 4y ago
I appreciate the term "existential round" as it highlights your intention. Are there other individuals, angels, firms, etc. that communicate a similar focus and intention specifically for software? Maybe this is more common than I
4.
by thedavidprice 5y ago
Yes, indeed! First off, Redwood comes with a Fastify server. `yarn rw serve` is the command you're looking for. Check out the Deploy Docs and this repo thats coming along: http://github.com/redwoodjs/docker/
5.
by thedavidprice 5y ago
Tape.sh runs an Electron desktop app as one of it's 4 clients. GraphQL is a multi-client solution. Is there something more you're specifically looking for?
6.
by thedavidprice 5y ago
Thank you for the reply. This is an interesting topic. I think at the core a comparison to Next is still apples to oranges imho and unnecessary here. But that's probably a distraction from the concepts at hand. > Are they making sim
7.
by thedavidprice 5y ago
I've been living and breathing this project for over two years. From an "is the project healthy" perspective, your explanation of what you interpret from these analytics makes no sense to me. I suspect there's some pre-e
8.
by thedavidprice 5y ago
Ha! My thoughts exactly. If I had more time it would make for an interesting post about all the lessons learned as we navigated the pains of Node.js in all its forms. Lesson One — Building and Bundling are hard but don't make it harder
9.
by thedavidprice 5y ago
Any chance we could be of help over in either: Redwood Forums: https://community.redwoodjs.com Redwood Discord: http://discord.gg/redwoodjs ?
10.
by thedavidprice 5y ago
This is wind in our sails. Thank you for posting. And please do show off what you've built! I'd love to see it.
11.
by thedavidprice 5y ago
I am sincerely interested in what you learn. If you do a comparison and have some time to communicate the results, please look me up on the Redwood Forums or Twitter. This would be a helpful resource and discussion for our community and mai
12.
by thedavidprice 5y ago
Not that I know of. But here are a few things that may be of interest. Redwood's GraphQL API is built on Yoga (we collaborate tightly with The Guild) — https://www.graphql-yoga.com You just need a GraphQL Client, which The
13.
by thedavidprice 5y ago
Ah, that is exactly what's going on. Definitely deserving of a :facepalm: from myself and those of us on the Core Team who missed that. Tom is adding a link back to www. v1 Launch Week Schedule (this HN Post): https://v1laun
14.
by thedavidprice 5y ago
You make some great points here! > I think the real benefit is an increase in the chance that you build your app in a way that's sustainable Yes, indeed! We discuss "long-term maintainability" often in the project README a
15.
by thedavidprice 5y ago
Tell me more about "obsolete", because I don't think you mean what that word means?
16.
by thedavidprice 5y ago
You can use Redwood's API with your Angular frontend.
17.
by thedavidprice 5y ago
> there is actual financial backing for Next.js and they have large enterprise users We haven't communicate this very well until today. Redwood is funded and will continue to be funded. Just not in a typical "for-profit" b
18.
by thedavidprice 5y ago
RedwoodJS is an open-source project. We are in a unique position to receive funding from Preston-Werner Ventures, which allows us to develop the codebase as well as cultivate an amazing community. Although it's not a typical for-profit
19.
by thedavidprice 5y ago
Yes, indeed! And then posted to YouTube https://youtube.com/redwoodjs
20.
by thedavidprice 5y ago
You can use RedwoodJS API as the backend for Next. There are several startups with multi-client products including a Next front-end as one of many.
21.
by thedavidprice 5y ago
Co-founder of RedwoodJS here. We are so excited and proud of what Redwood has become, both as a project and as a community! Whether you are setting off to start your side project or looking to become an open-source contributor, I'd lik
22.
by thedavidprice 5y ago
> So the idea is mostly about unifying the community with a website dedicated to this paradigm, and if we're lucky we play a small role in promoting more development and better tools in the future. Yes, please!
23.
by thedavidprice 5y ago
I'm on the RedwoodJS core team and can 100% confirm early performance issues. That's no longer been the case recently. I've seen bulk operations perform just fine and even data pipeline use cases. Now the issue is DB performa
24.
by thedavidprice 7y ago
Correct. One API. But chose the client (or as many) that you want.
25.
by thedavidprice 7y ago
We are stretching the definition of "JAMstack" here. But the primarily intended emphasis is not just React+API -- it's making structure+design choices that target serverless infrastructure out of the box. It's not perfec
26.
by thedavidprice 7y ago
That's all @cannikin doing!! Here's his framework, opinions included :) https://github.com/cannikin/cameronjs
27.
by thedavidprice 7y ago
You bet. See our roadmap list here https://redwoodjs.com/tutorial/wrapping-up And if you haven't read the README yet, that will help with the overall vision + direction https://redwoodjs.com/docs
28.
by thedavidprice 7y ago
FaunaDB is definitely on our radar. Thanks for the link -- will check it out now.
29.
by thedavidprice 7y ago
Thanks for the kind words and questions! Others from the team can go into more detail, but here's some high-level for now: - Typescript is definitely a priority for us. But implementation so far is starting with the backend (see https