skysight-inc/HackerNews huggingface dataset:
It couples global system state with service state. It also initializes the Mach bootstrap port name space and becomes the central service discovery mechanism for low-level tasks, thus being the centralized arbiter all in an odd position (PID1).

It mixes handling of many different service types, including daemons, so-called agents (which is just like a daemon except per-user and with muddled semantics, since they can all be per-login, per-user, GUI session or non-GUI session, but at the same time are the only category where direct user interaction is permitted), Mach services, XPC services and others. It also wrongly equivocates process types with scheduling policies, making for the really awkward and overlapping semantics of "Background", "Interactive", "Standard" and "Adaptive". Further complicating this is the LaunchOnlyOnce flag, for one-shot jobs. It's all inconsistent

Using its socket activation means you need to explicitly opt in to your daemon using liblaunch. It's not a generic mechanism like UCSPI is, for instance.

Whereas daemontools uses the actor model/Erlang philosophy of "let it crash" and restarting to known good states until dependencies are met, and systemd is based on a complicated dependency resolution/ordering mechanism... launchd is in this weird middle ground of neither. It instead expects OS services to resolve their sequences through IPC, but at the same time provides really racy and primitive ordering techniques through the KeepAlive key, evidently because users and sysadmins needed something. The result are inherently racy file system namespace mutexes like PathState, very limited network synchronization through NetworkState and a really easy to abuse poor man's dependency system through OtherJobEnabled (which actually violates launchd's own philosophy of IPC over dependencies).

In spite of its attempts to do load balancing and scheduling, the interfaces for doing so are mixed. You have standard rlimits, but also ambiguous ones like LowPriorityIO and LimitLoad<wildcard>, latter ones depending on sysctl variables.

It reportedly has weird interactions with cron because of it holding timers while sleeping: http://hea-www.harvard.edu/~fine/OSX/launchd_cron.html

WaitForDebugger is an odd key to have. Implies to me that launchd breaks standard ptrace(2) semantics.

And of course, XML plists.

In summary, even though launchd has good ideas, the entire architecture is just a mess of layering violations, semantic discrepancies, incorrect coupling and insufficient interfaces that make it really awkward to use. It tries to be the one-stop management interface for just about every unit of CPU time on the whole damned system, all of it in PID1 at that, and so naturally its abstractions become clumsy. Different tasks call for different systems to run and schedule them.
Nice! I always thought this kind of business model would work well for musicians/artists.

How much bank is Patron making in total?
We are a very visual culture, unfortunately. Unless there's a video of your average Joe driving on a regular highway and a regular car going wild, everyone would just dismiss the problem as limited to "race track" and would not connect the vulnerability to his/her own car.

edit: as per the article "researchers already did test these exploits in controlled environments and presented these tests to auto manufacturers. Said tests were dismissed by said manufacturers.".
I was ready to be indignant, but from the details, it seems the anti-virus companies are doing the right thing. The flagging is justified until uTorrent stops bundling spyware with their product.
>> In the fixing mode, Stallman was not operating as a user, he was operating as a developer.

At one time they were very often the same thing
So basically their biggest problem was that node.js machine-gun hammers the filesystem with stat calls when looking for modules. This was made worse by running on a shared folder.

Vagrant has a mode called rsync-auto which will synchronize directories into a local vm. Or you could just always have the code local to the node process. It makes more sense to have your editor work with remote files.

Next biggest problem was relational database. I think that tests requiring a SQL database are usually a bad sign, and the statement "we'd like to use transactions but our orm doesn't support them" makes me sad. To paraphrase Ben Franklin, "those who would give up transactions for a framework deserve neither". Here's some ideas for speeding up your tests, in order from best to worst.

- Make most business code rely on a service or interface. Swap that our during tests for a trivial in-memory implementation.
- Use sqlite :memory: for tests
- TRUNCATE TABLE
- Set your database to running with scissors mode (disable fsync)

[edit] I just took a look at the ORM used, waterline https://github.com/balderdashy/waterline . Why wasn't step one moving to sails-memory for running tests?
So, how do you know his heart stopped?

He got Naloxone because he overdosed on an opiate... That is not the least bit surprising...
No he did not do the wrong thing. Reporting them is completely wrong. When we report the people who protect us, well this sounds like a plot to a movie. PS: in movies usually a lot of people suffer before the resolution
AwardWallet is a great concept, but missing key integrations for me (Delta, United). If it's not complete, limited use for me...
The author actually uses the AGPLv3 for MediaGoblin:
http://mediagoblin.org/
At a minimum, I'd guess that it goes directly to PG's concept of "submarining"[0].

[0] http://www.paulgraham.com/submarine.html
e.g., Linux.
> it's necessary to get the attention of auto makers

That's mere conjecture. And it's an assertion you could easily test by first doing the remote hack in a controlled environment (e.g. a racetrack) and seeing if automakers respond before trying this on an actual freeway!
I'm assuming you have an interest in indie bookshops. Where do you go online to talk about them? Where do your likeminded friends go online?
The problem that Stallman faced could be solved with a law that prohibits software from being distributed in compiled form only.

All executable images delivered to users should be accompanied by buildable source code corresponding to the image, if at all the image can be upgraded.

Moreover, it should be lawful for licensed users of a program to share source code modifications with each other.

This is not a copyright issue at all; the rule would apply equally to freeware as well as to programs which are not freely redistributable.

The whole problem is that software can be machine translated from an easily understandable and modifiable from to a cryptic form that is vastly more difficult to understand and modify. This source-to-image translation paradigm gives rise to abuses and problems which were not imagined by the people who invented copyright.

For instance, if you and I both buy copies of the same novel written in the English language, all of its sentences are plainly understandable. You and I can discuss, say, alternative endings for the novel, and even write them up in our mutual correspondence. We could do the analogous thing with software: all that stops us is that we received it in a gobbledygook compiled form. (Plus some idiotic EULA clauses about "reverse engineering").
To be fair, even if this were a brand new product from Google people would still be speculating on how long before they decide to shut it down.
1) it didn't take "web folks" long. It was near immediately after the availability of the browser as an application platform that the advice took hold to those willing to heed it.

2) The existence of autoconf et al is not in any way preventing people from performing platform tests all over the place, so it's not like a panacea.

Sorry if you find this a bit abrasively worded, I aimed to avoid that, but you made me bristly with your implication that "web folk" are somehow lesser.
Funny Ruby Operator Names
GDP per capita doesn't mean much when you have food and shelter provided for you. I know most of my income in the bay goes to shelter alone.
Hah.

If prior HN articles are anything to go by, it's a matter of time before SWAT kicks down their doors, beats them up a bit, and maybe even a few officers "fearing for their own lives" (yeah right) take a couple of shots in "self defense" against unarmed nerds.

You're delusional if you trust in a law enforcement agency to take reasoned and measured action in any situation.
The ones that turned out to be mostly old people hitting the gas instead of the accelerator?
Doesn't need a GPL: just an irrevocable license to paying customers to be able to obtain and modify the source for their own uses. GPL is clearly superior in freedom but open-source, flexible, and proprietary model solves that with ROI for company. There's been companies, going back to Burrough's MCP OS in 60's, that did that for paying customers. We could push for more companies to do this, especially putting it in writing, to eliminate a lot of our problems.

Device drivers and firmware will still be tricky due to trade secrets involved. I'd say encourage such companies to keep a team around for paid audits and extensions of their product. That's happened with embedded and fabless semiconductor companies for quite a while. We've recently seen AMD and Intel start doing something similar for purposes of customization.

Many potential solutions that don't require convincing a company to go all free and annihilate their existence outside support contracts' race-to-the-bottom profits.
Your data must be from the industrial revolution.

We have decades of data from dense European cities that indicate better health and quality of life. Also just look at the health of rural people versus urban people in the US--the obesity crisis ain't happening in cities.

>The reason why a lot of cities aren't better for the environment is that the insane cost force many people out to the cities edge who then have to commute in

That's not urbanization. Urbanization is where people live densely, removing the need for so much driving. Half of a suburban family's energy use is devoted to driving.
> Except for the loss in innovation due to companies that will not touch GPL for fear of being forced to divulge the trade secrets in their code.

That's exactly the point of the GPL. Look, we as human beings would be all better off without trade secrets, without closed source, and with the explicit permission to tinker, modify, and improve the products we use every day.

You as a user should want all of the rights afforded to you by the GPL. You should want to know how all of your devices work. You should want to be able to do what you please with them and not just what the company you bought it from wants you to do with it.

Yes, we get it, companies don't want to tell people their secrets, but that's not the fault of the GPL. It's the fault of every user like you who is apathetic toward proprietary software, who thinks it's okay to exploit and profit off of others ignorance while perpetuating a legal framework that mandates that ignorance.
You seem to be equating 'acting within the law' with both moral conduct and efficacy (from the perspective of the charter). This is denying that efficacy from the perspective of the company, contra the law, moral code, or the charter could have a positive outcome. In fact, it appears that successful corporations are constantly pushing on all 3 restraints, and in the marketplace, corporations that ride the edge are more competitive, thus more successful, and therefore deliver greater benefit. How then does it make sense to immediately dismantle a corporation that breaks the rules even in a small way (destroying huge amounts of value)?

It seems that you're advocating a 'punishment as deterrent' strategy for society along the lines of capital punishment. "If you violate the rules even slightly, you will be executed." Is that a good strategy for encouraging lawfulness while preserving efficacy? And is law the perfect (or the best) mechanism for encoding moral behavior?
Nobody was hurt because they rolled the dice and got lucky. There was a non-zero probability of injury or death that was completely unjustified.
I feel terrible for her family as well, perhaps not even knowing exactly what led her to do this (in which case some people may end up feeling guilty).
Yep, totally agree with you. Good job for phoning the police. People need to know that's not ok!
If you read the article, you'd know full well that the researchers already did test these exploits in controlled environments and presented these tests to auto manufacturers. Said tests were dismissed by said manufacturers.
a) Desktop gaming is a province of Windows.

b) Why would Microsoft have a story for Mono? Mono isn't a Microsoft thing.
Looks like Caustic's technology at work:

http://www.techeye.net/chips/imagination-to-buy-caustic-grap...
What's the plastic bag used for?
As we have discussed before ;) I would think it smarter to allow developers to hook into the code generation process so it can be integrated in their own toolchain and processes.
I also wrote a guide to PR for startups, that's more "DIY for free" than about hiring an agency. I've never had any trouble getting plenty of write-ups (from a couple dozen major blogs/sites for average products to the cover of Time Magazine for another).

I used to sell the book, but it's online for free http://austenallred.com/user-acquisition/book/chapter/press/
Ehh... yes, but to change is not necessarily to fix, and that is the sort of change I was talking about.

And there are a lot of changes that can be made without disrupting users. I haven't heard anybody yet say they don't want minor security updates to be installed automatically, so long as they don't go around breaking something else or reorganizing the UI or doing some other dumb thing.
Team EnVyUs: Call of Duty, Counterstrike and Starcraft 2
Reporter: "Seriously, this is fucking dangerous. I need to move."

And that was while the security researchers caused the radio to blare so loud that he couldn't hear them on the other end of the phone. The more I see, the more I think they were really negligent in how they planned this out, and I was already firmly in that camp.
Good point. I made a similar one referencing the fact that Burroughs mainframes used to come with source to let customers do exactly that. So, it's a proven model. Plus, there's all the dual-licensed code out there proving you can make it charging reasonable rates for commercial use, let free use be free, and give source to both.
> A growing demographic of highly-skilled college-educated liberals will transform government’s role to be about directly investing in citizens, funding them to become as entrepreneurial, civic, and healthy as possible.

> The ultimate goal is to make life as close to the college experience as possible: a life dedicated to research, exploration, and creativity, while automation ensures that everyone has enough food and leisure time to pursue their unique contribution to the world.

I read through the charts and think the conclusion is a bit of a stretch.

My (admittedly anecdotal) experience with those in the industry seem seem to be wary of formalized education.

Also, not sure about how the representative sample (time? sample size?) was obtained and some of the questions seem like they were designed to elicit a certain response.

Example:
Do personal decisions, such as eating healthy, affect most people in society, thereby justifying government involvement in our everyday decisions?

I imagine the response would have been very different if everything preceding the "thereby" was excluded
My first thought would be an ever-increasing accent, which becomes unintelligable when the comment is so downvoted that it can't be seen. Dunno how practical that would be to implement however.
Nowhere in the pod spec is there a way to specify resource constraints or even hints (https://github.com/GoogleCloudPlatform/kubernetes/blob/maste...).

So even if the scheduler is vaguely resource-aware (I'm not convinced that's true) it would be entirely static, based on things like container count.
Ok, there was another factor. When a site is the source of many stories marked lightweight, it eventually gets penalized as a lightweight site. We have software that does this, plus moderators do it.

This was the case here: that site has been the source of, not spam exactly (which is why it isn't banned), but a lot of unsubstantive and/or derivative articles. The post you submitted is an example of the latter, since it was derived from a Reddit thread.

The penalties I'm talking about don't make it impossible for a story to get traction, but they do set the bar higher. So you were right that it was randomness, but the randomness was also skewed.
Lufthansa flight has near-miss with drone near Warsaw
Maybe I'm missing something but why would you do this, even in your own DC, with no authenticity or authentication as core components of the tool?

Interesting the performance they get, but it seems like running the server/receiver indefinitely would be a not-so-good idea.

?
> Just because automakers are seemingly keen on ignoring security vulnerabilities does not justify putting people's lives at risk.

So condemn the auto manufacturers for putting hundreds of thousands - if not millions - of lives at risk instead of yammering about a couple of nerds who put at most 2 vehicles in probably-nonfatal danger in a worst-case scenario.
>- logging/monitoring/alerting

As a maintainer of Fluentd [1], an open source log collector now integrated with Kubernetes [2] and Docker [3], happy to see this out =)

[1] https://www.fluentd.org
[2] http://blog.raintown.org/2014/11/logging-kubernetes-pods-usi...
[3] http://blog.treasuredata.com/blog/2015/07/07/collecting-dock...
Especially by Google, who has done a lot more damage to purchased companies instead of growing them.
An open source, beautifully designed Hacker News client for iPhone
This is the same Craig Kerstiens as Postgres Craig Kerstiens. I didn't realize he was into this kind of stuff, too.
> Use sqlite :memory: for tests

Then you run into issues where the functionality works on SQLite, but not on your real database.
Good catch. I just saw another article her eabout "PR for startups," more useful than anyone realizes.

>One of the most surprising things I discovered during my brief business career was the existence of the PR industry, lurking like a huge, quiet submarine beneath the news. Of the stories you read in traditional media that aren't about politics, crimes, or disasters, more than half probably come from PR firms.
Your comment made me realize i can't remember seeing promising medium or small size companies merge and make this kind of announcement.

I mean, you could very well see this kind of company merge with people doing an advanced IDE, or even corporate frameworks.

Maybe they usually prefer to create commercial partnerships rather than merge shares.
Because Apple has a patent on it.
Thank you, I noticed when I refreshed and clicked unflag.
Tor users must now provide a phone number to open a new Twitter account
I don't think there is any 'special ray-tracing hardware' they are simply leveraging the existing GPU with some algorithms and be able to to have faster, better looking shadows compared to the usual algos. Someone correct me if I'm wrong.
Oh cool, thanks for the explanation! And I take it what's in the black box is the key to figuring out how to make AI truly alive?
Isn't it possible that employee and employer can have a non-antagonistic relationship? What if the "discussion" was intended entirely in the interest of the employee?

In any event, it seems to me that it was good advice given the context.
This post is full of great general advice that's not specific to Node. In Ruby-land, we've been talking about the same things for the past few years, complete with 'omg how many stat calls are we making again?'

I'm sure others were doing the same before Ruby too. The wheel keeps turning...
I formerly did the same, but it became insufficient.

There are at least 4 cards that I need working at all times: (1) Debit card, as you mentioned, to be able to withdraw cash in a pinch, (2) Chase Sapphire Preferred - card with no FX fee, (3) Corporate Amex for charges I don't want to take on personally, (4) Starwood (SPG) card to amass a non-negligible amount of points on hotel stays. And maybe a 5th on which I'm trying to spend a large amount on quickly (for example - I might be planning to put $1500 on a random card with a big signup bonus, and it might be critical for me to get points I need for an upcoming reservation)

I of course have all of these loaded into my Coin, but each has failed enough times (forcing me to use the debit) that I started carrying the others as backup. Then I found myself carrying 5 cards....plus the Coin. And if Coin is targeted to users like me (who carry multiple credit cards, optimizing for different uses)....then what's the point?
Doesn't sound like you're unit testing well then. I'd take good unit tests over integration tests any day. Integration tests are inherently flaky.
Try operations at a company that isn't GPL-phobic. It's not like there's a shortage of them.

I mean, does your company run Linux knowing what license it's under?

I'm frankly boggling at the idea that a company will seriously try to stop operations from touching GPLed software. Unless you're a 100% Windows shop and the actual license for everything you use is "proprietary".
The End of Videogames
The actions - according to the article - of auto manufacturers in response to prior more-controlled tests is exactly equivalent to that. The manufacturers basically said "hey, thanks for showing us this crash-test footage that shows our vehicles are literal fucking coffins on wheels; we don't really care", leaving the researchers with no results after taking more "sane" measures.

Researchers perform controlled experiments. Controlled experiments are ignored. Researchers opt for more damning (though less controlled) experiments to further prove their point, and now they're suddenly the bad guys here.
People in industry seem to be "excited" about everything nowadays. The word is completely overused
Been playing with this. It's super handy when I'm working from home and need to show people my files without committing or heroku-ing or anything.

Thoughts?
Well, to be fair, one of the patterns I've seen with Rails projects is to move as much out of Rails proper as possible, and treat it just as your web/(maybe)database interface.
Yep - we've run into a lot of really unexpected behavior with it and with the ORM (Waterline), so we try to restrict ourselves to "the minimum possible framework subset that gets the code to run".

For example, we disable `dynamicFinders`, don't use policies, don't use blueprints, don't use Waterline's associate/populate/destroy, don't use the "turn any controller function into a named route" setting, don't use globals, disabled all of the Grunt/websockets junk, and overwrote all of the error response handlers.

The result is that day to day we're writing something that resembles an Express app with its own `routes` file. We're looking to move off of Waterline/Sails entirely, it's slow going though since we're a small team and it's tough to prioritize that, as it "works" now.

Every company has parts of their tech stack that don't do a great job - we're somewhat fortunate this one is easy to mitigate.
Bionic eye implant world first
Very often, the merchant would just assume I was using an Amex e.g. Amex Black....even though the display read VISA. This, of course, caused a decline...not worth the trouble to argue.
Why should my mother have to change device-wide settings on my device just because she wants to read something using it?

(Yes, people do lend their devices.)
building web / android G play games in c# / Unity; rolling a mean stack on google compute - hope to build a nice front & back-end using angular & some other stuff. Pretty fun so far. trying to get better at ruby & jscript...