In 2007, a small team at Yahoo! briefly changed how we program the internet. This is their story.
Part I: The Next Great Online Community
There’s a lack of innovation in community software. Let's dive into internet history, and get inspired!
The Fathers of the Internet Revolution Urge Today’s Software Engineers to Reinvent the Web
Tim Berners-Lee, Vint Cerf, and other Internet pioneers issue a challenge on a day that just might go down in tech history
Realtime voice, video, and AI for developers - Daily
Daily is the team behind Pipecat. Ultra low latency, open source SDKs, and enterprise reliability since 2016.
The New Internet: Tailscale's Vision for the Future of Connectivity
Tailscale's CEO, Avery Pennarun, explores the future of the internet, discussing the evolution of networking, the issues with today's complex systems, and how Tailscale is simplifying connectivity for developers with a new, more efficient approach. Discover the vision for a New Internet.
Reclaim the internet: Mozilla’s rebrand for the next era of tech | The Mozilla Blog
Mozilla isn’t just another tech company — we’re a global crew of activists, technologists and builders, all working to keep the internet free, op
The history of Yahoo, and how it went from phenom to has-been - Fast Company
For one brief shining moment, Yahoo was the king of all it surveyed. Then everything went to hell.
Piped
Piped is a privacy friendly alternative YouTube frontend, which is efficient and scalable by design.
pipecat-ai/smart-turn
Contribute to pipecat-ai/smart-turn development by creating an account on GitHub.
Fragile narrow laggy asynchronous mismatched pipes kill productivity - Tristan Hume
Something I’ve been thinking about recently is how when I’ve worked on any kind of distributed system, including systems as simple as a web app with frontend and backend code, probably upwards of 80% of my time is spent on things I wouldn’t need to do if it weren’t distributed. I came up with the following description of why I think this kind of programming requires so much effort: Everything is fragile narrow laggy asynchronous mismatched untrusted pipes. I think every programmer who’s worked on a networked system has encountered each of these issues, this is just my effort to coherently describe all of them in one place. I hope to prompt you to consider all the different hassles at once and think about how much harder/easier your job would be if you did/didn’t have to deal with these things. I think this is part of why web companies like Twitter seem to have so much lower impressiveness per engineer productivity than other places like game companies or SpaceX, although there’s other pieces to that puzzle. While part of the difficulty of distributed systems is inherent in physics, I think there’s lots of ideas for making each part of the problem easier, many already in common use, and I’ll try to mention lots of them. I hope that we as programmers continually develop more of these techniques and especially general implementations that simplify a problem. Like serialization libraries reducing the need for hand-written parsers/writers, I think there’s a lot of developer time out there to save by implementing generalized solutions where we currently painstakingly reimplement common patterns. I also think all these costs mean you should try really hard to avoid making your system distributed if you don’t have to.
My journey to the heart of the forgotten internet
Slowly but surely, huge swaths of the internet are vanishing. But the artefacts of the early web are still out there, and they have lessons for the future.
Browsertech Digest
An email digest about modern browser technology and the things people build with it. We’re talking WebAssembly, WebRTC, WebGL, WebGPU, WebSockets, WebCodecs, WebTransport, Web-everything. Written by Paul Butler of Jamsocket. We also host Browsertech events in NYC and SF. Talk browsertech in real time on #browsertech in the Jamsocket Discord.
WebAssembly’s post-MVP future: A cartoon skill tree – Mozilla Hacks - the Web developer blog
People have a misconception—they think that the WebAssembly that landed in browsers back in 2017—is the final version. In fact, we still have many use cases to unlock, from heavy-weight ...
chaim on Twitter / X
we’ve been given the opportunity to keep building the internetit’s not so much about building a new internet it’s more that we get to keep on building the internetbecause the internet essentially stopped being builtwe arrived at a specific junction, put down our tools,…— chaim (@matthewchaim) May 7, 2024
About Us
Around the world, building the internet’s operating system—and a better way to work. In a world of tech companies fighting for growth at any cost, imagine one that gives away its most successful pr…
🦫 alert! We published the first episode of "Teach the Web new Tricks", featuring @servo.org and @iroh.computer to create distributed Web apps! Learn more how we expand the Web from tabs to windows to devices at webbeef.org/tricks.html
