Hello HN! For those of you who are new to Langflow, we are building the easiest way for developers to build and ship AI-powered agents to production. Today we're shipping a native desktop client.
Why did we build this? We wanted to streamline the process for getting folks up-and-running. No need to install Python, download dependencies or configure your environment. Just install Langflow Desktop and start building.
We're launching a preview of Langflow Desktop today for MacOS. Please download it and take it for a spin! We can't wait to hear what you think of it, please feel free to comment and the team and I will respond.
Hey folks! I'm the Head of DevRel at DataStax and we couldn't be more excited to be joining forces with Langflow to help more developers easily build and deploy AI applications.
As part of this announcement, Langflow has released an alpha of their 1.0 product. Langflow is free, open source and vendor agnostic and we'd love for you to take it for a spin.
It's a simple `pip install` and we're hear to capture any and all feedback:
Hey folks I'm the Head of DevRel @ DataStax here and just wanted to share to the HN community that in conjunction with this big acquisition news, the LF team has shipped 1.0-alpha of Langflow.
It's a simple `pip install` and the team would love any and all feedback!
For anyone who prefer consuming video content to text, here's a recorded livestream of engineers from DataStax and Langchain breaking down this app in detail:
People who weren't there don't understand, but the world before "Ask Your Developer" was completely different than the world we live in today where developers are at the heart of how decisions are made, products are built and how the world itself is changing.
I joined Twilio in 2012 and I saw first hand how pivotal Jeff was in supporting the idea that in order for a platform to be successful it needed to treat developers like first class citizens, and not simply the recipient of a "directive to integrate" from the CTO.
This idea wasn't simply a fist bump to devs for cool points, it was a recognition that developers themselves held the key to innovation and creating radically new things. This culture led to entirely new ways of building API docs, designing developer dashboards, creating developer events, and so on.
So many of these things have become mainstream and the new baseline for platform companies that people forget how unlikely it was in the beginning and how hard Jeff had to fight to keep the company from treating developers as a means, and not as an end. And I think all developers who are happily hacking away on a free tier of a cool API with excellent docs and a vibrant developer community should tip their hat to a person who helped make this normal and influenced a generation of leaders to do the same.
Courier Inbox comes with web and mobile SDKs that are highly customizable, and we wanted to push the limits and see what we could build using them. We landed on the idea of Puppygram, an Instagram clone that displays nothing but pictures of cute puppies. We built the server using Next.js, Random.dog and Inngest.
We wrote-up a technical tear-down blog post [1] and have posted all source code [2] [3] on Github.
I had never heard of dnsmasq [1] before, this is a super useful tool! I frequently run into issues developing locally where certain 3rd party services (Intercom, for example) won't work properly on localhost.
This is devastating, not just for computer geeks in Seattle, but all over the world. The LCM was one of a kind.
I organize an annual developer conference [1], and one of the highlights of my life was renting this place out and inviting ~400 fellow devs to spend the night playing with mainframes & vintage PCs [2] and signing karaoke.
I'm not optimistic in Triplebyte's ability to execute here because I think they fundamentally think of developers as "content" and recruiters as the primary customer.
Shameless plug:
If anyone would like to create a developer profile that you have full control over and that doesn't expose you to recruiter spam, please check out what I'm building at https://fizbuz.com.
I follow over 2k accounts, so the odds of the most recent tweet being 45+ minutes old is low.
I also double-checked some of the people I am following, and indeed their most recent tweets are not showing up in my home timeline.
This is happening across all my devices (mobile & PC), so I assume it must be an issue with their infra that is limited to a subset of their users. Possible an issue with a cluster?
I am working on a "post-resume" product that helps developers express their skills, interests and preferences in a way that seeks to better connect devs to opportunities and eliminate the repetitive and low value questions in most phone screens.
It's very alpha, but I'd love to hear what folks think. Here's an example profile:
I plan to ship a public GraphQL API that makes your data available for any use you can imagine, including generating a "standard" resume or building a personal website.
Hats off to anyone who can rapidly go from those docs to a deployed and working app. I was able to modify the repo linked in the parent to suit my needs in roughly 2-3 hours, much of which was install/setup.
The difference in the ability of a developer to modify an open source software product (think: Gimp or Jitsi Meet) to suit their needs versus using a platform SDK that is designed to provide flexibility and to be used by devs is massive.
I spent some time looking at the Jitsi Meet source to confirm this assertion:
It was quite clear that trying to use that code to execute my use case above would have been a very large waste of time, and quite possibly (given the lack of docs) a futile exercise.
I'm seeing discussion below about fully open-source solutions (Jitsi Meet) vs. fully proprietary solutions (Zoom). What's interesting about using Twilio is that it is a programmable solution.
Case in point: I am building a webpage where people can log-in to a virtual office, so that people working from home don't feel so lonely. I have certain requirements, such as:
- All audio is muted
- Participants are arranged in a grid
- Room is persistent (no need for an "owner")
Accomplishing this with either Jitsi or Zoom may have been impossible, because while they are configurable they are not programmable.
Now, Twilio isn't the only Video platform on the market (see TokBox, etc), but I think comparing this to Jitsi/Zoom/Hangouts is like comparing apples to oranges.
Why did we build this? We wanted to streamline the process for getting folks up-and-running. No need to install Python, download dependencies or configure your environment. Just install Langflow Desktop and start building.
We're launching a preview of Langflow Desktop today for MacOS. Please download it and take it for a spin! We can't wait to hear what you think of it, please feel free to comment and the team and I will respond.