Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
kwindla
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
18 ms
·
151.
▲
by
kwindla
6y ago
I disagree with these numbers, in general. Though of course "noticeable" is subjective and varies by use case as well as by person. For many people, end-to-end audio latency in a 1:1 conversation becomes noticeable/annoying a
152.
▲
by
kwindla
6y ago
This is a fantastic question. I agree with you that we're slowing boiling the frog (and the frog is ourselves) in accepting more and more latency in our real-time communications. I think the answer for Lyra is that latency is a concern
153.
▲
by
kwindla
6y ago
The closing lines are a tour de force of caustic criticism, which only work (and work magnificently) because the entire piece builds towards them sentence by sentence, paragraph by paragraph.
154.
▲
The Vying Animal
(bookforum.com)
1 points
by
kwindla
6y ago
|
1 comments
155.
▲
‘Special and Beautiful’ Whistled Language Echoes Around This Island
(nytimes.com)
1 points
by
kwindla
6y ago
|
0 comments
156.
▲
Why Conspiracy Theories Are So Alluring
(nybooks.com)
4 points
by
kwindla
6y ago
|
0 comments
157.
▲
by
kwindla
6y ago
> On the one hand, yes, it's a hard problem, on the other hand, if you think about how much a modern video game does 60 times per second, it's not that hard anymore. Agreed! Modern GPUs are amazing, as is the software stack on
158.
▲
by
kwindla
6y ago
I'm always interested in data points, so thank you! If you don't mind, I'd love to hear what hardware/OS you're using. We have a lot of test devices, and it sounds like your particular setup is one that Google (and
159.
▲
by
kwindla
6y ago
> It’s crazy that I’m 2021 we don’t have video calling that isn’t a ginormous performance hog It sure is. On the other hand, the big tech companies did not view video calls as a critical use case until ~9 months ago. You can see this in
160.
▲
by
kwindla
6y ago
As a user, I think Google Meet probably has the most cpu-friendly default settings for screensharing. They limit the framerate to 5fps, and they're careful to use either the native size of the screen or half the native size (which avoi
161.
▲
by
kwindla
6y ago
Pricing for real-time video is hard. There are pretty large variable costs to run a service like this. WebRTC is peer-to-peer, architecturally. But if you run the service you pay for bandwidth for users behind firewalls (because you need to
162.
▲
by
kwindla
6y ago
I think the comparison to WebGL is apt. It's also worth adding that scaling WebRTC -- both to calls with more than a few participants, and to large numbers of users on a service -- is still a bit of a specialized undertaking. Partly be
163.
▲
Rediscovering Bette Howland
(mag.uchicago.edu)
4 points
by
kwindla
6y ago
|
0 comments
164.
▲
Daily (YC W16) Is Hiring a Head of Startup Experience
(notion.so)
1 points
by
kwindla
6y ago
165.
▲
by
kwindla
6y ago
Ben Thompson provides a more nuanced analysis, including useful background for engaging with a lot of the questions posed in the threads here: https://stratechery.com/2021/internet-3-0-and-the-beginning-...
166.
▲
by
kwindla
6y ago
cpu usage on each client is also an issue. Architecturally, WebRTC connections are always peer-to-peer, in the sense that each transport carrying media is negotiated individually and does its own bandwidth shaping. This has some really nice
167.
▲
by
kwindla
6y ago
Sean and Pion are awesome! Definitely talk to Sean. I'm happy to talk to you, too. I do a lot of "let's just talk about real-world things you'll encountering building video features" calls. You don't need to be
168.
▲
by
kwindla
6y ago
We're a YC company that tries to do exactly that: WebRTC-based features that "just work", with APIs for everything you might want to do with real-time media: https://www.daily.co/ As you noted below, the
169.
▲
by
kwindla
6y ago
There are a lot of use cases for WebRTC. Video calls are the biggest one right now. But anything you can imagine that needs low-latency (<200ms) video or audio is something you can potentially do with WebRTC in a browser, these days. The
170.
▲
Daily (YC W16) Is Hiring an Engineer Who Writes
(notion.so)
1 points
by
kwindla
6y ago
171.
▲
Zoom Executive Accused of Disrupting Calls at China’s Behest
(nytimes.com)
16 points
by
kwindla
6y ago
|
1 comments
172.
▲
What Made Leonardo Such a Great Artist? Science, Says a New Book
(nytimes.com)
7 points
by
kwindla
6y ago
|
0 comments
173.
▲
Evolution of my role as a founder CTO
(miguelcarranza.es)
99 points
by
kwindla
6y ago
|
16 comments
174.
▲
It’s Not Science Fiction
(nybooks.com)
1 points
by
kwindla
6y ago
|
0 comments
175.
▲
Dudes Without Heirs
(nybooks.com)
1 points
by
kwindla
6y ago
|
0 comments
176.
▲
Daily (YC W16) Is Hiring WebRTC, Rust, GStreamer, and Android Engineers
(daily.co)
1 points
by
kwindla
6y ago
177.
▲
by
kwindla
6y ago
Daily | Full Time | All Remote (anywhere in the world) | https://daily.co We make APIs for video calls and live video. We have open roles for experienced Android, WebRTC, gstreamer (or similar), and customer-facing engineers. We
178.
▲
by
kwindla
6y ago
Related, C++ template metaprogramming. Very useful, quite complicated to wrap your head around initially (at least it was for me), and a somewhat accidental language feature: https://softwareengineering.stackexchange.com/que
179.
▲
In Dark Times, I Sought Out the Turmoil of Caravaggio’s Paintings
(nytimes.com)
1 points
by
kwindla
6y ago
|
0 comments
180.
▲
Finding a Path Through the Odyssey
(nybooks.com)
1 points
by
kwindla
6y ago
|
0 comments
More ›