Hacker News new | past | comments | ask | show | jobs | submit | TorKlingberg's comments login

> difference between $6/user and $18/user is 0

I wouldn't go that far. Big companies put a lot of effort into saving $12/seat.

But, if you can convince them they get >$18 of value from it they're usually happy to pay. With hobbyists it's more emotional. $6 is "just a coffee" and can be justified just to try it out. At $18/m is one of your household bills, and many will decide they enjoy watching Netflix more than messing around with Tailscale.


I meant to write a blog post titled "What's good about ClearCase" in 2014, and I wish I did because now I've forgotten most of it.

ClearCase is a terrible version control system I wouldn't wish on my worst enemy, but it did have some good points that git still doesn't have. Large binary file support, configuration records, winkin, views.

With various big companies going towards giant monorepos and the local git repo just being a view into the super-centralized repo, I think they will re-invent parts of ClearCase.


> You shoot the entangled photon through a double slit and see if a wave-like pattern occurs, in which case we're still in a superposition and our communicator has not measured

Wait, does this work? Are superposition detection devices theoretically possible? Got any reference with more on this?


Tibetan script has been in Unicode since version 2 from 1996, with some characters added in later versions. Is there are particular human script you want added to Unicode?


I don't know, I want them to self disband if they're done instead of adding emojis.


But it sure seems like they greatly exceeded your initial expectations, no? They aren't adding it today, they already did it in 1996! Maybe they aren't what you thought they were?


So... they've been obsolete since '96?


Ok but this thread is about Tibetan and not about emojis.


Lots of emoji are outside the Basic Multilingual Plane and need 4 bytes in UTf-8 and UTF-16. That's without going into skin color and other modifiers and combinations.


Video calls indeed almost always use UDP. TCP retransmission isn't really useful since by the time a retransmitted packet arrives it's too old to display. Worse, a single lost packet will block a TCP stream. Sometimes TCP is the only way to get through a firewall, but the experience is bad if there's any packet loss at all.

VC systems do constantly send back packet loss statistics and adjust the video quality to avoid saturating a link. Any buffering in routers along the way will add delay, so you want to keep the bitrate low enough to keep buffers empty.


Others have noted you got the CD-R speeds wrong, but sometimes sending is indeed easier than receiving. I used to work on radio signal processing for phones, and we'd spend far more of both DSP cycles and engineering effort on the receive side. Transmission is basically just implementing a standardized algorithm, but on the receive side you can do all kinds of clever things to extract signal from the noise and distortions.

Video codecs like h264 or VP9 are the opposite: Decoding is just following an algorithm, but an encoder can save bits by spending more effort searching for patterns in the data.


> Video codecs like h264 or VP9 are the opposite: Decoding is just following an algorithm, but an encoder can save bits by spending more effort searching for patterns in the data.

This is a more general point about the duality of compact encoding (compressing data to the lowest number of bits e.g. for storage) and redundant encoding (expanding data to allow error detection when transmitted across a noisy medium.)


I used svn only a few years ago and don't remember branching taking very long. Maybe it was csv that had to copy the all files.

I do remember merges being horrible in svn. Just branching off trunk, doing some work and merging back is fine, but if you try to merge from trunk to your branch to "catch up" you're in for some pain when you later want to merge to trunk.

Also svn treats adding and deleting file as different from just editing, more so than git does.


SVN branching as I remember it requires a round-trip to the server, so that could be why it took so long for some people, if their server was far away.


TDM seems difficult with the long time delays to satellites, but maybe. LTE is pretty flexible and can use bands as small as 1.4 MHz.

It was only 1G and 2G (GSM) that needed to avoid overlap.



Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: