HNHacker News
TopNewBestAskShowJobs

drewcrawford

4,834 karma · joined June 13, 2008

AI tooling and systems/SDK engineer · Rust, WebAssembly, Swift/Apple platforms · wasm-bindgen contributor · building AI Bot Mafia (botmafia.games) · sealedabstract.com · github.com/drewcrawford
submissionscomments
drewcrawford··on An Hour with Safari Content Blocker in iOS 9
I really think a kind of lightweight collective bargaining is the answer here.

The way it works is simple. You install an ad blocker, let's call it QBlock.

Then, QBlock goes to the websites and the ad networks to negotiate. If you want to reach our 1M users with your ads, you have to play ball with us. e.g.

* Keep ads to 15% of screen space

* Don't autoplay audio

* Don't exceed 15% of network traffic

* etc.

If you comply with our guidelines, we'll let your ads through. If you don't, tough.

Of course this assumes there are users who would prefer an ad blocker that lets responsible advertisers through as opposed to one that doesn't, but I believe that enough people do that it could work.

drewcrawford··on Stealing keys from PCs using a radio: cheap electromagnetic attacks
This is a chosen ciphertext attack, so yes, you have to decrypt the attacker-provided payload.

That being the case, there are a lot of systems where that is easy to achieve. If you have GPG in your mail client, it will decrypt anything anybody sends you.

Another thing to keep in mind is that attacks always get better, they never get worse. So today's chosen ciphertext attack is tomorrow's zero-knowledge attack.

drewcrawford··on Why Open Source Misses the Point of Free Software
The MIT license reads as follows.

> Permission is hereby granted... to deal in the Software without restriction, including without limitation the rights to... sublicense

Because you have the right to "sublicense", you can take MIT code and license it under another license (GPL) even though you are not the copyright holder.

The BSD license is less clear on this point (in fact this is one of the important differences) and whether the BSD's grant includes the right of sublicense is more debatable, but in my view the answer is "probably".

I am not a lawyer; I am not your lawyer; this is not legal advice.

drewcrawford··on The Grooveshark Settlement [pdf]
I don't know how to answer your question because I don't know what it means to say something "should be OK".

If you're asking if I would prefer to live in an Oak Park where hotels were legal as opposed to where hotels were illegal, of course. If you're asking me if I would be on board with storming into an established community and rewriting their zoning codes over their objections, probably not, although there may be exceptions. If you're asking me if I would sleep well at night while operating a hotel in Oak Park, then I would probably want to meet the surrounding neighbors and decide for myself how much the activity would disturb them, look at the size of the easement, what the noise floor is like, and so on. If you're asking me if I as a homeowner would be annoyed at a neighboring hotel, it's possible, but I'm annoyed at a lot of things, most of which I seek no special right to change.

Those are four answers to your hypothetical, but I don't know whether one of them, or any of them, are the kind of answer you're looking for.

drewcrawford··on The Grooveshark Settlement [pdf]
There is a difference between what you are describing (commercial zoning) and what AirBnB does (length of tenancy). Commercial zoning is much more obviously a legitimate government function than length of tenancy, which is a textbook economic rigidity.

But to answer your question seriously, I think the Japanese have a better zoning system than in the US, theirs allows for, in limited quantities, a bar in a residential neighborhood, or even an apartment next to a machining shop. The insight here is that it does no one any good to have a long commute, and so they have a system that affords landowners choices about the kind of neighbors they want to have, rather than dumping them all into residential-only zones.

drewcrawford··on Why We Are No Longer Developing for the iPad
I completely disagree.
drewcrawford··on Why We Are No Longer Developing for the iPad
Compare and contrast the experience of buying an iPhone with the experience of buying an iPhone app.

When you buy an app, you are basically looking at sales sheets from people you don't know making claims you can't verify. The only way out is to go find reviews about the apps from blogs you can't trust.

Now think about buying an iPhone. I've owned an iPhone for 8 years. I know intimately the support experience. I know intimately the build quality. Software quality. Product lifecycle. When a new iPhone comes out I have basically all the information I need to make a purchasing decision, without ever laying eyes on the actual product. People who don't have that information can go to a retail store where they can try the product and talk with knowledgeable and friendly people about it, and many of them turn into me in 8 years.

I want to be able to create that kind of experience with my products. Because if smartphones were sold the way that apps are today I don't think many people would buy them.

drewcrawford··on Android’s 10 Millisecond Problem explained
So I've got a few decades of serious music training under my belt. Multi-instrument.

I notice any latency above 7ms. I can compensate pretty well between about 7-14ms. Anything above that will affect the performance. Once you get to, say, 25ms, it's like I lose several years of training.

It's hard to relate to because most people don't have experience doing tasks demanding that level of precision. Perhaps it would be useful to think about what would happen if you introduced a delay between striking a key on your keyboard and the sensation of feeling it travel. You "can type" without any sensation at all (see iPads) but people who are serious about typing go to extraordinary lengths to make the keyboard feel right.

drewcrawford··on Ask HN: How do you deal with professional jealousy and getting older?
You need to read The War of Art.

> “Most of us have two lives. The life we live, and the unlived life within us. Between the two stands Resistance.”

> “Every sun casts a shadow, and genius's shadow is Resistance. As powerful as is our soul's call to realization, so potent are the forces of Resistance arrayed against it. Resistance is faster than a speeding bullet, more powerful than a locomotive, harder to kick than crack cocaine. We're not alone if we've been mowed down by Resistance; millions of good men and women have bitten the dust before us. And here's the biggest bitch: We don't even know what hit us. I never did. From age twenty-four to thirty-two, Resistance kicked my ass from East Coast to West and back again thirteen times and I never even knew it existed. I looked everywhere for the enemy and failed to see it right in front of my face.”

That book is a treasure trove in how to change your thinking and defeat this. But it does require changing your thinking and a great deal of discipline.

drewcrawford··on JIT-compilation using GCC 5
The GPL applies to "derivative works", which is a legal term without a precise technical definition.

If you decide to write an interpreter for an existing language, and run existing programs on it, then those existing programs "probably" do not have to be under the GPL, for definitions of "probably" that Legal will not be happy about.

If you write an interpreter for a made-up language and then write programs in that language as part of a thinly-veiled scheme to do an end-run around the GPL, then that "probably" violates the GPL.

There is currently no bright-line rule separating those cases; this is something IP lawyers argue about themselves and reach wildly different conclusions.

drewcrawford··on Ubiquiti Networks is creatively violating the GPL
Willfull infringement is already a tort; the damages are set by statute at $150,000 (if properly registered etc). You do not need to add any provision to the GPL to go after US violators.

To the extent that doesn't happen means that copyright holders (developers) don't do it. Either because they don't know how, they didn't register in a timely fashion, they don't want to bother, or they don't want money.

drewcrawford··on Ubiquiti Networks is creatively violating the GPL
But those are not mutually exclusive; they are complementary. It is not very effective to say "Um, stop being a violator pls." It is much more effective to say "Here is your invoice for being a violator, and don't let me catch you again."
drewcrawford··on Ubiquiti Networks is creatively violating the GPL
I'm puzzled that there is apparently a whole cottage industry that can protect the rights of indie photographers [0] but we cannot do the same for free software. The closest we come is like the SFLC, and they are really quite soft on infringers in most cases.

I imagine that some of the puzzle is because DMCA is cheap and effective against websites moreso than against hardware manufacturers. Even so, Ubiquity Networks provides web downloads of their firmwares [1] so surely DMCA notices could at least impair their update distribution, which would annoy customers and put pressure on them that way. Meanwhile there is plenty of "purely web" software license violations.

I know that many projects don't get the copyright registered, which puts them at some legal disadvantage. But it's cheap to do, it's something that developers can be educated about, and it is economical for lawyers to take those cases (if facts and registration are strong) on contingency.

So I don't understand why there's not a little cottage industry for it like there is for the photographers.

[0] https://www.imagerights.com

[1] https://www.ubnt.com/download/

drewcrawford··on VP9: Faster, better, buffer-free YouTube videos
Yes, thx
drewcrawford··on VP9: Faster, better, buffer-free YouTube videos
It's worse than that; the input itself is only 8-bit and they scale up, and then back down again to 8-bit on the output side.

But it works, for the same reason that audio engineers use 64-bit signal pipelines inside their DAW even though nearly all output equipment (and much input equipment) is 16-bit which is already at the limit of human perception.

If you have a 16-bit signal path, then every device on the signal path gets 16 bits of input and 16-bits of output. So every device in the path rounds to the nearest 16-bit value, which has an error of +/- 0.5 per device.

However if you do a lot of those back to back they accumulate. If you have 32 steps in your signal path and each is +/- 0.5 then the total is +/- 16. Ideally some of them will cancel out, but in the worst case it's actually off by 16. "off by 16" is equivalent to "off by lg2(16)=4 bits". So now you don't have 16-bit audio, you have 12-bit audio, because 4 of the bits are junk. And 12-bit audio is no longer outside the limit of human perception.

Instead if you do all the math at 64-bit you still have 4 bits of error but they're way over in bits 60-64 where nobody can ever hear them. Then you chop down to 16-bit at the very end and the quality is better. You can have a suuuuuuuper long signal path that accumulates 16 or 32 or 48 bits of error and nobody notices because you still have 16 good bits.

tl;dr rounding errors accumulate inside the encoder

drewcrawford··on How and Why Swiftype Moved from EC2 to Real Hardware
There are a lot of reasons why suppliers might not match demand.

Let's say you have a factory that runs at 90% utilization and somebody crawls out of the woodwork who wants to order 3 factory-months worth of widgets, delivered next week.

Well first of all, you cannot meet that schedule, so you turn away the order in the instant case.

Now the question is: if we were to scale up production, what is the chance that some new person will crawl out of the woodwork with a similar instant order once the factories are ready? Because if we judge what has happened a one-off case, then we will refuse to meet the demand, whether it is real or not.

(Of course we're also making a lot of simplifying assumptions here like that you have access to capital, that there is no regulatory issue with scaling up production, that increased production does not open you to new lines of attack from your competitors, etc. Which are not good assumptions in general.)

It is our judgment of the demand, rather than the real demand, that controls production. If we are manufacturing, say, kevlar vests in 2001, we may very well interpret a large order as representing an underlying demand shift. On the other hand, if our widgets are luxury cars in 2008, we may interpret a similar set of facts as a one-off order.

The insight here is that real demand is not known at the time that supply is trying to meet it; it is estimated. The extent to which the market clears depends on how good the estimation is. With something like oil we understand demand fairly well, but in markets like consumer electronics the demand predictions are poor. That is why on the one hand Apple is chronically short of iPhones and simultaneously Amazon cannot give its phones away: all the estimates were off.

In short, the more your widget is impacted by technological or cultural shocks, the more likely it is that suppliers won't adjust to meet demand.

drewcrawford··on The Hiring Post
Woah! Don't be afraid to plug your new firm in the blogpost :-) I doubt I'm the only one to mistakenly ascribe your new hiring policy to your old company.
drewcrawford··on The Hiring Post
As a vote of confidence, this article moved me from "I would never ever interview at Matasano" to "I don't want a full-time job at a security firm, but if I did, I would probably start looking here."
drewcrawford··on Old-School PC Copy Protection Schemes (2006)
KQ6, in addition to being one of the greatest adventure games of all time, had some of the best copy protection.

The manual had an extensive "encyclopedic" section that was part background material, part hint book, and part ingenious copy protection. For example it included the following 'poem' as background material about one of the game areas:

      Three roses laid upon the bower, 
      A scythe for he who cuts the flower, 
      A crown, a dove, most noble race! 
      Thy bones make sacred this dread place.
As it turns out, this poem is really a solution to a puzzle where you must walk on the floor tiles in a particular order to survive:

http://i.ytimg.com/vi/WUw771rvxhc/hqdefault.jpg

There were several solutions that were cryptically hidden in the manual like this, such that people who hadn't read it would get stuck at various points.

The real genius however was that this was before the Internet, and so if you wanted hints you had to call Sierra on their special 900 (toll) number to get help.

drewcrawford··on Unreal Engine 4 is now available to everyone for free
It's unfortunate that this model really only works for large developers serving broad markets like gaming.

Whereas if you're an indie developer writing image processing code for example, it is going to be hard to find infringers and harder to strongarm them into coughing up licensing fees.

I expect this has the effect of keeping source code behind closed doors that would otherwise be public.

drewcrawford··on On Rust and Nim
Swift is not garbage collected in the slightest. ARC is not garbage collection.

http://sealedabstract.com/wp-content/uploads/2013/05/Screen-...

Once upon a time Objective-C had a real garbage collector but that temporary interlude has not, nor ever will be supported from Swift.

Finally, Swift objects (can be, as compiler decides) laid out on the stack, so unless you have some super sweet stack garbage collection technology you'd like to share with us, they aren't garbage collected.

In any case, I don't see what garbage collection has to do with safety or the borrow checker.

> I don't understand "you just promise the compiler that it's safe"

Perhaps you'd like to read the Rust Book:

> When a type T implements Sync, it indicates to the compiler that something of this type has no possibility of introducing memory unsafety when used from multiple threads concurrently.

I think "you just promise the compiler that it's safe" is an accurate summary of that feature.

> We have been measuring developer cost all along, by writing hundreds of thousands of lines of code in the language as we've been developing it: the Rust compiler is written in Rust, and we've been developing Servo as well.

Would you be satisfied if you wrote a language that is productive only for language designers writing web browsers and compilers? Because that is all your measurements prove.

I'm telling you, as an intermediate Rust developer doing neither of those things, that I am not sure if I am more productive in Rust or C. Rust is certainly safer, but I am not convinced that safety is worth returning to C-like productivity. Performance is, but I can achieve good performance in Swift.

Rust assumes that I value performance and safety equally; e.g. that I am willing to give up productivity for either one. In reality I am only willing to give up productivity for performance. There are some low-hanging safety fruit that I want (like optionals) but the higher-cost fruit like multithread safety I don't want. I think those features are Bad (TM).

drewcrawford··on On Rust and Nim
I think the question is "what is the cost" of the more novel rust safety features? In my experience, the cost is pretty high.

When you set Rust next to, e.g. swift, swift is phenominally more productive and similarly performant. And it is also quite safe (relative to C) without having all of the Rust safety features that make me want to kill the borrow checker with a rusty spoon.

I really wish Rust walked back on the more esoteric forms of safety (like thread safety, which you can't really verify anyway, you just promise the compiler that it's safe) and it tried to drive a bargain like Swift.

Rust really isn't satisfied to adopt the safety features that are "fairly low effort", it wants to break new ground without really measuring developer cost (hard to do since it's not widely used). That's really my issue with it.

drewcrawford··on Stop wasting time getting estimates right
> And if you get the estimate wrong (too low), you screw yourself and lose money on the project - too high and you don't even get the contract. In this environment, you learn quickly that estimation is vital,

In my vertical what happens is that customers field optimistic estimates from vendors much less qualified than you. But customers have no basis to know those estimates are fanciful. So they rely on a fanciful estimate from an unscrupulous vendor, and then get stuck.

Estimates are not judged on being right, they're judged on being low. In that environment, the only winning move is not to play.

Obviously in some verticals there could be people technically qualified to evaluate the incoming bids. I'm just reporting that it isn't the case where I work.

drewcrawford··on Swift Resistance
I wish this were true, but unfortunately you can't mix unoptimized and optimized code in Swift. File dupes of rdar://19527999.
drewcrawford··on Ask HN: Tricks to integrate late coding session in current workflow?
I manage people, am managed, and work strange hours.

In the scenario you describe, you have set of inconsistent requirements:

1. A developer that works strange hours

2. A need to get everybody in the same room

3. The "perception problem", a.k.a. snide remarks from the peanut gallery.

The first thing to do is to be a good technical manager and admit that you do, in fact, have inconsistent requirements. Something on this list must change. You cannot satisfy all three.

The next thing to look at is what is the best (or least-bad) requirement to change.

The simplest option is to fire the developer. I don't actually recommend that, but it is simple. Embedded in that statement is the implicit assumption that you will never again hire someone who works odd hours, and in my admittedly biased experience, people who work odd hours tend to be good, so there is a hidden cost to that scenario.

A more complicated option is to figure out how to eliminate or reduce your dependence on in-person meetings. For example, having discussions via email or on GitHub. I would probably argue that if your software developers are having meetings more than 0.5 times per day, they are not being productive to start with, so there are reasons independent of this particular developer to study that problem. For more on this strategy, I would recommend looking at the GitHub model. [1]

Finally, to address the third issue, you need a performance review mechanism that isn't attendance-based. For example, consider mechanisms that are feature-based or deliverable-based. Attendance-based performance is bad for a lot of reasons independent of any particular developer's situation--it motivates working hard instead of working smart, and so on.

The thing to see here is that you're either going to have to change the environment or the developers you place in it. Personally, I would recommend the former, but in any case, something's going to move. The advantage of changing something now is that you get to decide what to change. If you let the situation run its course, it will change in a manner and at a time that will be less convenient.

[1] http://zachholman.com/posts/how-github-works-asynchronous/

drewcrawford··on So you want to abolish time zones
While this is an amazing and thought-provoking article, I can't help but feel it missed the obvious answer to the question it presented.

Phones should be programmed to accept or reject calls by the owner, because it is a really dumb idea to be able to wake people up knowing only their phone number. Notably, this is already the case: cellphones have mute/vibrate switches, and if you have a smart phone you probably have various "do not disturb" modes that do more advanced routing.

As a followup and to actually resolve the question for the call placer, phones could broadcast their availability status and this status could be queryable by phone number.

Stardates have their own problems but I'm not convinced those problems are harder than the problems we have with timezones now. We've built up a terrible amount of infrastructure around timezone handling, we should not be scared off when stardates require unique infrastructure projects.

drewcrawford··on The Implications of Facebook Indexing a Trillion Posts
I'm pretty interested in how this is implemented, actually. Naively you could search a global index and then filter results down to your friends, but that filter seems impossibly slow. Alternatively you could maintain a separate index per person, but querying 500 indexes seems unreasonable.

Maybe they partition the graph into cliques which they index, search and then fix up with a second pass to add and remove noncliqued friends?

drewcrawford··on Ask HN: How to use small chunks of time productively
The best algorithm for interruptions I know is the one that computers use: the journaling filesystem [0].

The way it works is simple. When you want to do a disk operation, first, you write down in a special place (called a journal) what you are going to do, at a high level. "I'm going to delete this directory and all its files." Then, you go through the steps of actually doing that. Finally, you record in your journal that's what you did.

Now when power is interrupted during a disk operation you simply look at the journal and you can complete any operations that were in-flight at the time of the interruption. For example if the journal says "Delete X folder" and you see it still exists, now you can pick up where you left off.

The application to interruptible programming is straightforward. I have an actual paper journal and I will in a few words explain a task to the journal before I begin. Often I end up with a hierarchical journal, like

    get the unit tests to pass
        the unit test doesn't pass on OSX because postgres isn't running
            start postgres
        the unit test doesn't pass on Linux because the postgres credentials are wrong
            refactor postgres credentials to work right on both platforms
        one particular Linux machine still doesn't work
            Is it 32-bit related?
                No
            Are we using the same compiler on that machine?
The overhead of recording this information is microscopic, and the benefit of returning from every interruption to a page or so of context is awesome. It's almost better to be interrupted now, because I come back to a clearly defined problem, as opposed to starting on "blank slate" items with no direction.

As a side benefit, I now write really good commit messages, because I just write what my journal says I did. Which is quite a lot more detail than it was when I was trying to remember things after the fact.

[0] http://en.wikipedia.org/wiki/Journaling_file_system

drewcrawford··on The Case for N. Korea’s Role in Sony Hack
I'm something of an armchair security analyst and non-trivial Korea watcher, and in my view there's really no question it's NK. It's simply that the standard behavior and thinking of the NK regime is too bizarre to be believable by Western sensibilities, that we dismiss it out of hand.

To start with, film is something of a national treasure in NK. Official documents show KJI as being connected with the production of over 11,000 films. That is almost certainly an exaggeration, but enough of his stuff has leaked that you can take a class on it at a film school, so it's not a 'whole-cloth' invention. NK has taken bizarre steps to secure its film heritage, including organized abduction of actors and directors from foreign countries to bolster the regime's cast list.

Meanwhile, the personality cult is strong, in a way not seen even under Stalin. For example, the whole country stopped and celebrated [0] because a random citizen put out a fire near a portrait of one of the leaders. You'll find Western media outlets speculating that of course what really happened is she thwarted an assassination attempt, because the truth is absurd to Western sensibilities.

These two things combine to form a powerful motive. The last time a film depicted a NK leader, they made serious efforts to have it banned in their allied countries, although they were not at all successful. Meanwhile, successfully hacking a US company is of major propaganda value for the regime. The two targets that they have "hacked"--SK and US--are the ones they complain most loudly about internationally. So launching some kind of attack would be very consistent with their political rhetoric.

Since that time, they've developed a much more sophisticated hacking ring. There was a time when they relaxed some of the normal rules so that you could outsource your software projects to NK software developers, and, from what I understand, some large companies did. That was one of the ways they built skills. While they're pretty incompetent by nation-state standards, they seem to have improved a lot in recent years, and of course they're better-funded and better-organized than any common criminal hacking ring. It would be completely within NK's wheelhouse to devote 10% of GDP to this project even while their people starve.

Meanwhile, of course, Sony has a very poor track record on security--between the rootkits, GeoHot, Linux, etc., I don't know a lot of qualified security researchers who would feel good about working there. This has created a bit of a security vacuum and of course they have been hit by common criminals, several times in the last few years. So it's very believable that hitting them is within NK's reach.

Finally, as far as nation-states having an extortion motive again that is very much within NK's wheelhouse. They are a poor country and they are engaged in all kinds of bizarre plots to raise money. Notably, they built up a counterfeiting ring for US currency so sophisticated that we ended up redesigning the bills [1]. NK also runs sort of an industrialized Breaking Bad operation, to the extent that a lot of the country is hooked on their own product [2]. Their MO at this point is very definitely to take common criminal operations and scale them up under the cloak of a nation-state to drive revenue. It's not a leap to electronic extortion. They're basically a super-mafia at this point, and this is a new department.

As far as their being no "DNA, smoking-gun" evidence--that's true. But I think the circumstantial identifying evidence, combined with motive, means, and opportunity, is pretty compelling. The communications from GOP are as bizarre and convoluted as anything the NK regime says, and not what you'd expect from a simple criminal enterprise. If it's not NK, it remains to be explained why the hackers went to some lengths to fool real security analysts at an actually first-class nation-state, but did so in such a bizarre and haphazard way as to target an especially weak US company that does not demonstrate any particular skill beyond what others have done before. That level of convolution demands a geopolitical explanation of some type that goes beyond simple extortion, but it's much more elaborate to explain who would want the US angrier at NK than we already are, and how these shadowy figures would benefit.

Finally, as far as the "inside job" theory--it is completely believable to me that NK would be willing to throw a few tens of thousands of dollars in bribes to get inside. They spent much more than that celebrating putting out the poster-fire. So that idea that Sony had angry employees to me actually strengthens the case for an NK-based theory, as it provides a simple and cheap way for them to get inside.

[0] http://newfocusintl.com/exclusive-why-north-korea-handed-a-b...

[1] https://en.wikipedia.org/wiki/Superdollar

[2] http://www.vice.com/read/north-korea-crystal-meth-drugs-dipl...

drewcrawford··on The failed economics of our software commons and what to do about it
Having spent some time on the problem I agree generally with your approach, but the problem is it doesn't appreciate the history and context in which the current system has arisen and continues to exist.

There are basically 3 cases of successful FOSS projects:

1. Ideologically-driven, e.g. Emacs, GNU, etc. These tend to have licenses in the copyleft family

2. Commercially-driven, e.g. WebKit, Docker, etc. These are projects that are strategically important to one or several companies. They tend to have licenses in the MIT/Apache family

3. "Lone Wolf" or "indie developer". While a lot of FOSS is this by volume, what you discover is that by the time projects become popular they have generally evolved into one of the first two types, although they often preserve their creation story as part of the marketing material

The problem with charging money for code is that it's really a bad deal for the first two types. The ideology camp doesn't want non-commercial licenses because it's a "restriction on a field of use" which they have a philosophical objection about that you can google. In the second camp, the corporate masters derive some kind of strategic advantage from having a popular open-source project and charging money necessarily means the project would be less popular and so of less strategic value.

What this necessarily means is that if there's any legs to this plan, positioning it as "open source" or to the "open source community" is exactly the wrong approach, because basically all the people who are successful in that community will find it a nonstarter. Instead you have to hypothesize that there's some completely different set of people that can benefit from this system, writing completely new software (or releasing pre-written software that isn't currently considered 'open source', e.g., proprietary software). So your positioning needs to be something like "proprietary 2.0" or even "third way" rather than being connected with open source.

The real problem with this system is that I'm not sure there's a market on the buying side. Developers are used to getting things for free, and even if somebody wrote a source-visible-but-pay-$1k-to-use-it high-quality TLS library I'm not convinced that people wouldn't just keep wrestling with OpenSSL because it's free.

I have a whole blog post I'm drafting on this topic, if anyone reading this comment is interested, give me a shout and I'll give you a preprint.

← PreviousPage 5 of 29Next →