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 Who wants competition? Big cable tries outlawing municipal broadband in Kansas
You're saying that there's no competition in municipalities? They're called elections. We hold them more than once a year.

Not to mention that municipalities compete with one another; it is actually easier in most places in the United States to move to a neighboring municipality than it is to switch to a better ISP. For example I would have to move over a hundred miles to get better internet access than the large, regional ISP that serves my area, and meanwhile I could move about five miles and "technically" live in a different city in the same metro area.

Finally, I am not advocating municipal control instead of private ISPs, I am arguing municipal offerings in addition to private ISPs. It is tautologically impossible for the introduction of new entrants into the market to itself constitute a reduction in competition.

drewcrawford··on Why don’t software development methodologies work?
You have successfully solved the problem posed, but it was not well-stated. In a real-world scenario, it is important not just to identify which of the 10 ideas is most promising, but to defeat the null hypothesis that the programmers should be fired and no idea should be pursued. After all, to choose the best of 10 bad ideas is to have failed as an economic enterprise.

In order for a business to be investable, it is necessary to demonstrate that it will be profitable to an investor. (And of course all businesses need investment, whether that is VC money or just a lone developer's part-time effort.)

We have avoided this problem because in the early days of software, most software was profitable. But as the software industry has grown, this is proportionally less true. And I seriously question in 2014 whether more LOC are committed each day to "black" or "red" projects.

drewcrawford··on DEA redacts tactic that's more secret than parallel construction
There's a difficult semantic problem that comes up in these conversations, how to explain...

Publishing the AACS key as Wikipedia does [1] is, as you would say, "blatantly illegal according to the plain language [of the law]. No fancy lawyering needed." In spite of the fact that is "blatantly illegal", they do it, and nothing bad happens. How can this be?

Well, the reason is because "blatantly illegal" is not a magic word that prevents people from doing things. It's not a technical measure that stops you in your tracks.

"Illegal" simply means that someone has the option to get a specific legal remedy from you. And whether that somebody is interested in exercising that remedy or whether the remedy is very good are completely different questions.

It is "blatantly illegal" to search your house but that doesn't stop the DEA, your ex-girlfriend, or the burglar down the street from doing so. The only operative question is, "what is the remedy?" And on this question the constitution is "blatantly" silent.

In the illegal search situation legal precedent has decided the remedy is that you cannot use the evidence you collect illegally in court. This is called the "fruit of the poisonous tree" doctrine.

Now maybe you think that remedy is insufficient, that there should be a fine or we should put them in jail. That is a perfectly reasonable view. But "this is blatantly illegal under the constitution" is not an argument that competently advances that position for a harsher remedy. Everybody already agrees that illegal searches are illegal; that is true by definition. Not everybody agrees about what the remedy should be.

[1] http://en.wikipedia.org/wiki/AACS_encryption_key_controversy

[2] http://en.wikipedia.org/wiki/Fruit_of_the_poisonous_tree

drewcrawford··on Windows XP gains in January but so does Windows 8.1
I had a discussion with somebody who knows about XP Embedded, which is apparently a lot scarier than regular XP. For one thing it's used in a lot of applications where credit card readers are attached, and for another thing the system requirements went from 128MB to 1GB between XP and 8 which makes upgrading really unattractive.

The path of least resistance for the people I talked to seems to be moving to embedded Linux or a Android and rewriting all the software. But they weren't terribly happy about it.

drewcrawford··on Who wants competition? Big cable tries outlawing municipal broadband in Kansas
> we don't expect the water company to deliver 400x the water to our homes than we did 20 years ago, but that's exactly what we expect of our broadband providers.

It is a 400x increase when measured by the yardstick of a software developer, but by the yardstick of "how much money does it cost to connect Joe Schmoe to a network that meets his expectations" the business has not appreciably changed in 20 years. What changes is the model number on the Cisco switch and the type of cable in the ground, but "what is the maintenance cycle on this electrical cable and power transformer" is a problem that municipalities have been successfully solving for well over a century.

I think you are confusing the practice of actual dataspeed innovation (e.g. what Cisco, Juniper, Alcatel-Lucent, Qualcomm etc., do) with ISPs like AT&T or TWC who merely buy and install equipment and service cable runs. AT&T, Time Warner, Verizon, et al do not appreciably contribute to the number of packets it is possible to send in 10 seconds, except insofar as they buy products from those companies that actually do. That role (of buying Cisco products) can easily be shifted to a municipality with no downside to Cisco. In fact, from Cisco's perspective, large nationwide ISPs operate more or less as a consolidated union of individual markets and have a lot of bargaining power, so a more diversified customerbase that doesn't cooperate as tightly means Cisco can make more money, and since they are actually the ones who make the internet fast, that seems like a positive outcome to me.

> but if your city spent $3B just maintaining water and sewer, and time warner spent $3B over the entire country then TW is winning in my book.

Of course not. $3b is the total budget for the whole city, which is mostly public safety (police, fire, EMS, etc.) The capital spending on energy is only about $200m/year, which is about 50% production and 50% distribution. If you imagine that it is probably easier to run fiber than it is to run 110,000V powerlines everywhere, the ongoing capital expenditure to run the actual fiber lines themselves would be less than $100m.

drewcrawford··on Who wants competition? Big cable tries outlawing municipal broadband in Kansas
But the nature of being an ISP is to run expensive (both in outlay and maintenance) cable/fiber to your house, and it doesn't make economic sense to run 2 or 3 or 4 lines to a customer that only uses 1 ISP. It follows directly from your argument that a person should have a healthy market of water companies serving their house, or sewer companies, or electric companies.

> running big telco networks is hard, capital intensive, and requires a lot of expertise that municipalities don't really have

Capital-intensive, expertise-intensive things is exactly what municipalities do well. They do water, sewer, utilities, police, fire, EMS, etc. My city spent just over $3b last year, meanwhile Time Warner Cable spent roughly $3b on capital expenses in the entire United States.

drewcrawford··on Let’s Bolt: low-level libraries designed to make developing mobile apps easier
This probably isn't the right place to discuss the article, but I don't think your summary is either accurate or applicable. For example, the article does include code, it does provide constructive alternatives, it goes well beyond my experience by outlining a general proof for why the problem I was working on is theoretically intractable, it was hacked on by multiple people (hence "we"), and so on.

Even if that list of criticisms were accurate, the correct response to an article that has "no code, no benchmarks, no constructive alternatives" is to respond with code, benchmarks, and constructive alternatives. What you do here is essentially say "Because this does not meet some threshold of evidence I can ignore it" instead of what rational people say, "I should collect better evidence but in the meantime let's rely on the evidence that is available".

Finally, you don't really state an articulable position on the actual issue, so the discussion does not really advance. My position is pretty clear: promises work on the platform if and only if there are particular guarantees, and the README of this project explicitly says you don't get those guarantees, ergo this library is trouble. Clearly you object to this position but you do not say, let alone defend, any alternative theory that would have predictive power over whether or not promises will work for a project and for that reason, the comment does not add anything to the discussion.

drewcrawford··on Let’s Bolt: low-level libraries designed to make developing mobile apps easier
I actually wrote a promise library for iOS (and didn't release it). The postmortem is here: http://sealedabstract.com/code/broken-promises/

The tl;dr is that you can run into trouble on the iOS platform if you don't enforce a strict 1:1 chain of cause/effects and are very careful about the timing of adding new links to the chain.

This library doesn't appear to do that, and they appear to consider this a feature, and actively push you in that direction. For example, a bullet in the readme is that tasks are "fully composable" and another bullet point discusses adding new tasks to the tree on-demand. These can work on some platforms, but iOS isn't one of them, and so this really reads like someone familiar with JS or .NET trying to add "missing" functionality to iOS without considering why these patterns are not generally used on iOS. Plus, it's trying to achieve API similarity with Android, which is a code smell.

So I would really advise against using this library, at the very least use it a in a superficial way that would be easy to tear out later. If you really want to do this promises thing, I would push you toward Reactive Cocoa, which I am also skeptical about but it's been around much longer, seems to have a much more mature API, and I know at least some smart people who've used it successfully.

drewcrawford··on The world’s rich stay rich while the poor struggle to prosper
> Your experiences of the world will cease to exist. Therefore, the only rational investment would be in life extension technologies

It is certainly not the "only" rational investment. It might be the only rational investment for a person who shares your views on the importance of staying alive and your optimism for SENS research, but there are plenty of people who fail one or both criteria, and they're not all irrational. They're just optimizing for different criteria.

drewcrawford··on 'Revenge porn' website former owner Hunter Moore arrested
Unfortunately, we have not understood each other. You are saying things like

> Should this content be illegal?

Meanwhile I'm saying things like

> it's important not just that you have bad effects, but that you have a bad intent

and

> we are not prosecuting packets, but prosecuting people

Let me try and use your terminology. There is no such thing as illegal content. There is content that is produced in the course of a criminal act. But it isn't the content that is illegal, it's the act.

I think the rest of your comment follows from that misunderstanding of my premise, but if not, let me know, and I can respond to the actual merits.

drewcrawford··on 'Revenge porn' website former owner Hunter Moore arrested
> Is it a worrying trend that website operators are becoming increasingly culpable for user content?

Well, let's be clear here. He didn't build a business that operated around hosting arbitrary images, that happened to be adopted by bad people for bad purposes. He was a bad person himself, who built a bad website, to assist other bad people. These are two very different things.

I mean, I understand how you could imagine some other website, a neutral website, that was unintentionally adopted by bad people for bad purposes, and that other website could do the same sort of damage, unintentionally, that this website did to its victims, intentionally, and that hypothetical situation is sort of similar to this one if you look upsidedown and squint.

But in the moral code of most people (for example, mine) and for that matter the US legal system, it's important not just that you have bad effects, but that you have a bad intent. This is why, for example, murder is different than manslaughter. In both cases somebody is dead because of your actions, but in only one case did you form a specific intent to kill another person. (And manslaughter is, for the record, not "no intent", but it is a lesser kind of intent, like firing a gun into a building without regard for whether or not it is occupied. It's a bad intent, just not bad enough to be murder.)

I think where hackers get hung up is in some sort of weird Net Neutrality-ish argument where any packet is as good as any other packet, and so a packet that carries revenge porn is just as legitimate as a packet that carries cat videos. Packets are neither good or bad but just are and all packets have the same legitimate claim on arriving to their destination as any other. And if you are designing a router, that sounds like a very sound principle to me.

But in the courtroom, we are not prosecuting packets, but prosecuting people. And people are more than just a function of the packets they send. They have motives, they have intents. They construct a conscious plan to do good or to do evil. And that is how they are judged.

drewcrawford··on The Death Of Expertise
The trouble I had was in the first sentence:

> I am (or at least think I am) an expert. Not on everything, but in a particular area of human knowledge, specifically social science and public policy.

At least as far as the US is concerned, public policy encompasses everything. So as far as I can tell, this person really is claiming to be an expert on everything.

"Social science" does not fair much better. NOAD helpfully supplies "the scientific study of human society and social relationships". That seems to be a substantially broad claim, on the level of claiming to be an expert in, say, physical science. While there certainly are a few people who might make a competent application for that title (Feinman comes to mind), it seems to stretch the meaning of "expert", as Feinman's expertise in, say, biology, is of a substantially different sort than his expertise in particle physics.

I think the author may be falsely attributing his frustration about being heard to the "generational" "disregard for experts" instead of his own inability to defend an overly broad claim of expertise. If this article was "I am an expert in how much money we should be spending on space exploration and nobody is listening to me" then that would be an interesting, and entirely different, discussion. As it stands it's just tilting at windmills.

drewcrawford··on Ask HN: How to find part-time developer work?
At present I derive all my income from part-time work and side projects.

The first thing is to figure out what not to do. You can't work in a field where people routinely hire full-time employees with ease. So you can't do Java work part-time, for example. (Well I mean you can, but it's like saying you can be elected to Congress. Let's do something easy.)

So, you have to start in some field where 9-5ers can't be easily found to fill the position. iOS/Android dev are like that. Maybe there are web specialities that are like that. If you have some deep expertise like machine learning or computer vision or graph algorithms, maybe those specialties are like that. But the operative criteria is to find some field that full-time employees are not easily had.

The next step is to filter by projects where time is not the biggest criteria. Because in spite of Fred Brooks and his MMM, ordinary people still believe that if you work more hours the project will get done faster, and will pressure you to become full-time. So you have to find people who are unconcerned about delivery dates, or rather, who have overriding concerns. Quality concerns. Cost concerns. If you find someone who has a fixed budget for his project, for example, if that person can get a better developer at 20 hours/week than he can at 40 hours that starts to look like an attractive value proposition. Because not only does he get a better developer, but with a lower burn rate it's easier for him to get deep visibility into where the money and time is actually going. Those benefits outweigh the benefits of completing the project faster, but only for projects that have these sorts of overriding concerns.

There's more you can do, but those two steps are probably all you need to start consistently landing part-time gigs.

It's worth pointing out as well, there are a variety of near-part-time deal structures you can negotiate (for example rotating 1 week on, 1 week off). These might be worth exploring depending on your specific motivations for seeking part-time work.

drewcrawford··on OpenBSD will shut down if we do not have the funding to keep the lights on
You know what else loses developers? Shutting down the project.
drewcrawford··on Why CCP is still using Python 2
Well I suppose it's all in how you interpret them. For example, if you look at https://wiki.python.org/moin/2.x-vs-3.x-survey?action=Attach... which shows 22% Python 3 vs Python 2 adoption, perhaps that sounds bad. But if you imagine that those 22% are the green-field projects and 78% are the people maintaining Eve Online, then that is a great outcome for Python 3. So I guess the question hinges on whether you believe Python 3 usage is highly correlated with green-field development, which is a belief I hold.

> I presume you've read

There are a lot of things I dislike about this article. One is that it acknowledges that library support can pull you to Python 2, while totally ignoring that library support can also pull you to Python 3. For example, as a result of spending a lot of time in Python 3 I have a lot of Python 3 code (e.g. what was a month ago green-field library development). These libraries are neat, and I want to use them, and it is a requirement for using them that I use them from Python 3, and they cause me to use Python 3 in the same way that Twisted's Python 2-only support causes some other developer to go to 2-only. The pendulum can swing both ways, and it's up to us as library authors to decide which way we want to swing it. In my view, the real villains here are library authors who have decided to make Python 2.x a first class citizen and add new features do the 2.x versions of their library instead of designating 2.x as bugfix-only like the Python Software Foundation did long ago.

The second thing I dislike about the article is that it ignores the obvious solution: port package X to Python 3. Now for very large libraries this may not be feasible, but certainly the subset you're going to use in your project could be ported, and of course the entire library can be ported for smaller cases. We all need to be doing more to give back to the open source community, most of us take and then give nothing, this is not a good combination. The fact that "submit a patch" is never discussed as a possibility in these "boohoo Twisted doesn't support Python 3" discussions is beyond ridiculous and exposes what I think is a very serious problem in the community. Are we hackers or are we whiners? So I think we should hack, and if we want package XXX for Python 3 we should all pitch in and work on that.

drewcrawford··on Why CCP is still using Python 2
I don think it should surprise anyone here that users with enterprise-size Python codebases aren't jumping to Python 3. PEP 373 doesn't end support until 2015, and I assume at that point RHEL or maybe even someone in the python community will pick up the torch (a la Rails LTS).

I think by far the more interesting question is what is going on with today's green-field projects (a.k.a. the enterprises in the making). Whoever steps forward to maintain 2.7 long-term will probably be charging an arm and a leg (Red Hat I'm looking at you) and so of course this is unaffordable for bootstrapped companies and ordinary folks will not be able to afford a security patched Python 2 install.

Meanwhile the statistics I've seen for green-field development are mixed-to-promising for Python 3. I know for my new projects I'm over 50% 3.3. And when the shoe drops with 2.x support EOL, I think that's going to give it a serious kick.

drewcrawford··on The Silent Majority of Experts
This comment is sufficiently interesting that I want to grab a coffee with you and talk about it IRL, but you don't have any contact information in your profile so I don't know where in the world you are.

The next time you roll through Austin make sure to look me up.

drewcrawford··on How Python 3 Should Have Worked (2012)
Your argument is essentially that one can write slow things in Python and fast things in C, and that this solves the majority of problems (let's even be generous and call it 98% of them that fit neatly into these two categories). The trouble here is that "the number of programs" is a large number, and 2% of a large number is still large, and leaves important classes of programs without a good solution.

One class of programs left out in the cold is the network server. Now a network server must respond to a large number of requests. From a basic software engineering perspective, a 16-core machine should be responding to AT LEAST 16 requests at once (much more if some of the requests are IO bound). So the network server needs some kind of parallel processing (whether threads, subprocesses, or whatever you want to suggest). Under your philosophy, programs that need threading (thus all network servers) should not be written in Python, but somebody should be stepping down to C. While it is probably true that a very small minority of network servers should not be written in Python, the broader claim is absurd; you should be able to write reasonably-performing network servers in Python with relative ease. It is, after all, a server-side language; "writing a server" should be very high on the list of "things you can do".

Now more broadly, the existence of greenlet, Twisted, gevent, and their popularity (we're talking top-100 packages here) speak to the fact that there are a LOT of python programmers who have threading-related requirements. Are they on crack? Now mix in the new standard library stuff like asyncio (3.4) and threading is clearly an important enough issue to get major attention from the core committers. Are they on crack?

Now you might operate in a world where every time you need threads is an isolated case and it's fairly simple to drop down to C. But there are a lot of people (in absolute terms; I don't know if they are in the majority) where when they want threads the right solution is to use threads.

The thing I hear from the core committers whenever the GIL comes up is "if we worked on the GIL, we would be taking lots of time away from more important things." But when you look at the things they work on instead--unicode, iterators, ordered dictionaries, argparse, etc.--plenty of people in this thread are insufficiently motivated to upgrade. Are ordered dictionaries really more important than GIL work? To me, the answer is clear. I would rather have some progress on the GIL problem than every single py3k feature combined.

drewcrawford··on NSA phone surveillance program likely unconstitutional, federal judge rules
> the difference between sports and politics is that sports don't really matter

I have some news for you. The sports industry is something like $400bn. If the Lakers have a bad night or whatever, it matters.

You may not understand why moving players around a field matters, but it seems to me that this is roughly the same sort of ignorance that would be behind the view that pushing pixels around a screen "doesn't matter". The fact that X is a hundred billion dollar industry is primate facie evidence that it is important. You may not want it to matter but this is a different thing than determining whether or not it actually does.

I guess what I'm trying to get across is that there is a certain sentiment of "silly other people, stop being bad!" that easily occurs in these conversations. The TDD debate sounds important for cars but .001% of engineers are working on the self-driving cars. Most software is mundane and these debates are 99.9% academic and are even had in the abstract without affecting any tangible software at all! In many ways, the hacker arguments are far more tribal and less practical than anything going on in sports or politics.

drewcrawford··on NSA phone surveillance program likely unconstitutional, federal judge rules
While I agree with you, I think looking at this through the lens of only "hey look some irrational muggles" belies the fact that hackers do the EXACT SAME THING.

Web vs native? Vi vs emacs? Tabs vs spaces? PHP vs... everybody else? TDD vs anti-TDD? Git vs Mercurial?

I mean sure there are statistics and facts to back these views but there are also statistics and facts behind which sports team is the best or whether the debt ceiling is bad. There's no meaningful difference.

drewcrawford··on How to send DMs on Twitter without permission
Well I think we are blurring two different issues here. The first question is whether or not full disclosure is acceptable. The second question is whether or not it is acceptable to choose it because one is not being paid.

As far as full disclosure being acceptable, there are a lot of advocates. For example Bruce Schneier, Leonard Rose, and others. Not to mention that this issue isn't in a high impact category like remote code execution, loss of data, privacy, etc. It's also difficult to exploit; it requires authorizing a malicious app. So for all those reasons separately, and certainly all of them together, I think full disclosure is a completely acceptable choice.

Given that it is acceptable, is it still acceptable to do it if it furthers our own interests? Again, I think the answer is yes. The fact it is in my interest does not make an acceptable action into an unacceptable one.

You seem to be hung up on the fact that the researcher here was not particularly nice to Twitter. But people are under no obligation to be nice. It would be nice if you sent me a check for $200. But you won't, because there's no obligation to do that. And you and I--two strangers arguing with each other on the Internet--have a much stronger relationship than this researcher has with Twitter.

drewcrawford··on How to send DMs on Twitter without permission
Well given that homakov has found this bug, there are a few possibilities:

A. Homakov could do nothing. This leaves Twitter in the same state that it is now, but it if everybody did this, it is likely that nefarious people would find and exploit bugs in Twitter

B. Homakov could donate his time, as a skilled and highly-trained professional consultant, to a $32bn publicly-traded company

C. Homakov could practice full disclosure

This isn't even close to blackmail. This is a security consultant publishing a vulnerability that he discovered on his own time, that apparently Twitter's internal security team missed. That might be embarrassing for Twitter, but tha'ts hardly homakov's problem as a third party.

drewcrawford··on A Year’s Worth of Opinions about Objective-C
I stand corrected.
drewcrawford··on A Year’s Worth of Opinions about Objective-C
A better comparison here is with C/C++/go, e.g. other languages that are designed to be fast and compiled.

In any of those, dereferencing a null pointer is undefined. The compiler can literally emit code that plays Nethack in this situation [0]. ObjC's "nothing will happen" behavior is a significant improvement in safety against similarly-situated languages.

[0] http://feross.org/gcc-ownage/

drewcrawford··on A Year’s Worth of Opinions about Objective-C
In C/C++, dereferencing the null pointer is undefined. That is a hell of a lot more dangerous than doing nothing. ObjC's "defined to do nothing" behavior is a significant step up from the other languages in the "fast, compiled, bare metal" cluster (C,C++).
drewcrawford··on A Year’s Worth of Opinions about Objective-C
Well good is debatable but arguably C++ meets this criteria. I work on many iOS codebases that have C++ layers.
drewcrawford··on A Year’s Worth of Opinions about Objective-C
In defense of ObjC's type system (which is the author's major gripe).

It is a duck-typed language. This is the philosophy that "if it walks like a duck... it's a duck." This is the philosophy used by lots of modern languages like Python, Ruby, and JS.

Meanwhile there is the statically-typed system, which wants you to declare things to be ducks explicitly (or to pick up a duck declaration through an inheritance system). This is the philosophy used by Java, C++, etc.

Anyway, the author's gripe isn't with ObjC's types. The author's gripe is with any duck-typed system. The whole point of these type systems is to avoid providing any strong guarantees about types. If you want strong typing, use a strongly-typed language. C++ may align better with this author's programming ideology.

It's also worth pointing out that runtime type checks are, all else being equal, slow. ObjC is used primarily in mobile environments where speed is a concern. As the author discovered, you can opt in to type checking by using NSAssert. This forces you to think about whether the cost of a dynamic type check is acceptable. NSAsserts are also disabled by default in release builds, so this gives you checking when you need them (development) and speed when you don't (production).

C++'s type system is deliberately constructed in such a way that the compiler can do the bulk of the type enforcement, which is much faster than runtime type checking. Alternately stated, this means that the programmer must write code in such a way that the compiler can infer/enforce type checks, or else they will get type errors. The author's complaints about not enough compiler errors seem to suggest to me that he would be more at home in a language like C++ that is specifically designed for this purpose.

drewcrawford··on Show HN: We built Triage, an iOS app that unites all your dev tools
It would be nice if it actually did unite all my dev tools. Some things that are preventing me from using it:

* For some definition of something, I am a member of between 3 and 5 GitHub organizations, Triage requires me to pick one.

* I actually track errors with a custom thing, there doesn't seem to be an API, an email box, or some way to rope it in to Triage

* TestFlight is a notable omission on the mobile side.

* Logging products are a notable omission (splunk/logentries/papertrail/loggly/etc.)

* Issue trackers are a notable omission (Trello, JIRA, FogBugz, Lighthouse, etc.)

The result of this list is unfortunately, no dev tool I use actually integrates in a way that makes the product useful for me.

drewcrawford··on What the Fluck
> what is it that would make us do things, what is capable of driving and changing society?

The same thing that it has always been. There is nothing new here.

If you look at the populist changes to society throughout history, they are fixing problems that are literally unimaginable to modern western sensibilities.

For example, the average age upon death of a working class Londoner in the 1780s was 19. [0] Can we even imagine that? People, in huge numbers, dropping off at 19? So that's how we got labor laws.

Consider the civil rights movement. It's tempting to blur this with today's racial "tensions", but back then there were cities that would post signs threatening to shoot blacks on sight. This was common enough that there's probably one within an hour's drive of where you are right now [1].

In 1932, the year that the Nazis came to power, German unemployment was over 30% [2]. That is basically unimaginable for most countries today, and those that are in this ballpark have exactly the sort of unrest (e.g. Greece, Spain) that probably leads to social change. It's certainly way different than anything you see in the US.

The thing is, NSA spying or whatever don't really rate a mention next to any of these. Sure, it is a violation of your rights but people don't rise up for "on paper" sorts of causes.

It is easy for HN and the educated leisure class to paint everybody as "apathetic" or whatever. But out in the real world, 58% of Americans spend at least one year below the poverty line [3]. People aren't worrying about the Orwellian society because they're worrying instead about how to pay for Christmas presents for the kids.

If you really want the masses to care about whatever HN's issue of the day is, the first step is to figure out how to get the masses into the educated leisure class so that they have time to care.

[0] https://www.wsws.org/en/articles/2001/02/orph-f20.html

[1] http://sundown.afro.illinois.edu/content.php?file=sundowntow...

[2] http://www.theholocaustexplained.org/ks3/the-nazi-rise-to-po...

[3] http://en.wikipedia.org/wiki/Poverty_in_the_United_States

drewcrawford··on Jury: Newegg infringes Spangenberg patent, must pay $2.3 million
I have no special legal knowledge, but I spent several years within spitting distance of this district, so I know the area, was in the jury pool, and as far as I know might still be close enough to be called as a juror.

Based on that experience, I am inclined to disagree with your general premise. While these lawsuits bring a tiny bit of additional business to directly-related service industries (hotels, copy shops) my observation is that most of the "big money" stays within the legal industry, which is mostly based in the home locations of wherever these companies are. It is further my observation that the East District Court is not unusual in the kind of business that it brings to the surrounding area relative to other district courts (e.g., if not patent lawsuits, other suits) so there isn't much of a desire to protect its reputation as a patent court.

Finally while these stories do receive "national attention", this is pretty much entirely within the software development community, and patent lawyers. Ordinary people in East Texas don't follow any stories about patent lawsuits ever. They're boring.

Here's a benchmark for you: I am a software developer, who lobbied my congressman about patent law earlier this month, and on the day this lawsuit was filed, I was 45 minutes from the court by car. I am the textbook case of a person who would be following this story. Today is the first day I have ever heard anything about it.

← PreviousPage 9 of 29Next →