skysight-inc/HackerNews huggingface dataset:
> ... BSD-style rc files, which are tiny and very readable ...

As someone who has an on-going project to replace 157 rc.d scripts from FreeBSD 9/10, I can report that the generalizations about the Mewburn rc.d system that are often made, in order to contrast it with the egregious mess that one can find in the System V rc clone on Linux operating systems, are not in fact strictly accurate.

Yes, most of the rc.d scripts are small. Yes, the Mewburn rc.d system did almost 16 years ago what people are erroneously characterizing as novel to systemd: namely taking all of the common management code out of the individual service definitions, leaving just a few parameterizations in some cases. Yes, there is a definite common coding style that is a breath of fresh air when coming from the Linux world.

But no, the scripts are not universally tiny. One problematic example currently of interest is /etc/rc.d/bluetooth, weighing in at over 360 lines. Others include the subsystems that are split across multiple scripts, such as /etc/rc.d/atm1, /etc/rc.d/atm2, and /etc/rc.d/atm3.

Nor are they universally consistent, /etc/rc.d/serial being an example of one with quite different configuration semantics to the key=value-in-rc.conf{,.local} norm.

And whilst one might rail against the problems of having a common script for SuSE Linux, Debian Linux, and RedHat Linux, all of which have different sets of init.d script helper tools (resulting in "portable" init.d scripts ending up being a case "$distribution" in...esac statement for pretty much every step), one can equally point to the fact that OpenBSD's rc.d system (https://news.ycombinator.com/item?id=8506460) has entirely different function and parameter names to the NetBSD one (as adopted by FreeBSD/PC-BSD and DragonFly BSD) as well as different rules about rc.conf and different variable naming conventions.

Be very careful about attempting to claim some kind of moral high ground on interoperability and standards. (-:

Also be very careful about notions that the Linux world sees the Bourne Again shell as the only shell, some rather silly statements by some people who should know better notwithstanding. The adoption of the (Debian-modified) Almquist shell as /bin/sh by Debian and Ubuntu, and its significant effect on bootstrap speed, is quite famous. And my experience is that the Z Shell is quite popular, for starters.
It's none of their business what sites I've been to.
It's also not available at the first moment of the boot process.

But it is this kind of stuff that they are trying to change (as usual for systemd, without fully thinking why people do it differently now).
We're not going to subscribe to your anti-internet paywall site, WSJ, sorry. The net is free. Why aren't you.
The bigger scam is that getting the insurance claim denied will probably still either raise his rates or drop him altogether.

This is a pretty extreme case of a household hazmat issue. 99/100 times, the pragmatic answer is to maintain deniability, make it as safe as possible and get out if necessary.
Replacing a bad system (sysvinit) with another bad system (systemd) is just change for change's sake.
I believe bestaudio[ext=m4a] should be wrapped in quotes.

>"bestaudio[ext=m4a]"

(First time I've ever used it but it wouldn't work for me without the quotes)
Wow, that all really, really sucks. Hope it's all fixed soon.
A Young Entrepreneur in the Making
Imported species in Australia have caused an ecological disaster: https://en.wikipedia.org/wiki/Invasive_species_in_Australia

The same is true for New Zealand.
Please have a look at MSYS2. It's far, far easier to use than cygwin and even has `pacman` as a package manager
I was driving in SF for two month a couple years ago. Lyft took a 15 or 20% cut right off the top, then I covered taxes, gas, weekly car wash. I also included the time when I ended a shift, but had to get back to my apartment, or had to take a break to fill gas or grab some food in between rides.

After that stretch I drove periodically when I wanted some extra money. It's very flexible on hours.
Also msys2 which is well maintained.
For serious claims, it's better to hire a public adjuster.
Does anyone have a positive experience with ads on mobile?
I don't think it's that simple, especially when talking about things like "luxury" development that changes the city's housing standard.
Interesting perspective. My experience has been the complete opposite - writing unit scripts used to be a real pain, but systemd unit files take two minutes and just work every time.

My machines start much faster with systemd too, which is a nice side effect.
>for the most part, the police aren't broken.

>>I'm calling bullshit on this.

I have to agree with "for the most part", if you're talking about 90% of the interactions with the general public, things are just fine and dandy. Unfortunately a measely 10% of interactions means way, way too many go wrong. "For the most part" isn't good enough for me, and it shouldn't be good enough for America.
Well, that and making cut-and-paste work across X applications.
And creating "fragile" models because they don't have the tools to reproduce their own experiments. How many authors of academic papers in ML could reproduce the exact same results a year later? I would guess around 10%.
Which one is acceptable? Someone breaking into your home to use your coffee maker or someone asking to borrow it for the weekend?
I know you can't possibly accurately hit someones extremities, never made that claim either.

My post was in response to you making it sound like wounds to the extremities would be equally likely to kill as wounds to the center of mass, which is definitely not true.

And thanks, I've already got a range membership.
What can Gordon Ramsey teach us about user experience design
Thanks! I'll look them up.
Not significantly. Some parts of Bionic (Android's libc equivalent) is based on BSD equivalents, but most of userland is Android-specific.
I actually have a technical rationale for avoiding systemd, among others.

This is a comment I was supposed to send to chris_wot in the systemd v227 announcement thread, but his posts got nuked by dang.

Here goes:

----------------------

systemd tries to force various system resources into the Unit abstraction, to a rather mixed effect. Some are IPC resources (sockets), others are abstract entities which are driven by a lower-level primitive (services that drive jobs), yet others still claim to wrap resources but really drive util-linux binaries (mounts and swaps). The information hiding/encapsulation is inconsistent, too. I'm not shielded from the dirty details of transactions and the seven different job queuing modes, and when they actually blow up in my face, the debugging context is very scarce.

All of this takes place in an ad-hoc graph engine that I cannot really observe. I can look at approximations of it (systemd-analyze), but I have no way of directly manipulating it, only indirectly through normal operations on system and service state of which the effects I cannot reliably gauge as they undergo systemd's heuristics. Moreover, I cannot checkpoint the graph state to disk, so I could e.g. replay and reboot from a known-good system state manifest. systemd snapshots are ephemeral (in-memory) and moreover do not fully preserve the graph info, anyway.

systemd clearly has an identity crisis between whether it wants to be an eager or lazy service manager. Publicly, it recommends laziness through so-called socket activation, but in practice people mostly tend toward using the dependency system. The dependency system, of course, exists mostly to calculate ordering requirements for parallel startup. This however comes at a cost of non-deterministic ordering, whereby a service can be malignantly reordered, breaking the boot sequence (NFS seems especially prone). This is somewhat inherent to parallelism in general, but is particularly undesirable given parallelism serves no other purpose beyond startup speed optimization (for which process checkpointing I maintain is a better solution).

Between all of this intermediate complexity, I can end up in stuck start/stop jobs, cyclical transactions and dependency loops without knowing the exact origin, because the graph engine doesn't supply me with sufficiently good debugging context.

And the worst part is that most of this is not even a reliability/fault tolerance thing. The Unix process model has no semblance of anything resembling a "transaction", nor is the Unit object versatile enough. It's all heuristics on a private graph engine meant to topologically sort the edges, so as to accommodate systemd's dependency system (which conflates hard service relationships with softer ordering requirements, and is generally inflexible)... yet at the same time you're actually expected to lazy load everything, but barely so in the real world.

Oh, and of course, handling anything related to Unit objects in PID1 creates an unnecessary coupling between global system state and service state in particular, on top of all the intermediate complexity of the graph.
Ideally, it shouldn't matter? They should be judged on what papers they write/innovations they make.
I do understand why insurance companies don't want to pay for things that happened before the policy took effect. Otherwise people could do harmful things, take out a policy, and then file a claim. All sorts of bad incentives.

On the other hand, it's pretty frustrating in our case!
Data Center Computers: Modern Challenges in CPU Design [video]
I get:

youtube-dl: error: no such option: --youtube-skip-dash-manifest

As an error, am I missing something?
Traditionally, this would be a job for m4:

$ cat examples/config.yaml.in
user: USERNAME
password: ifelse(PASSWORD,`PASSWORD',`defaultpass',PASSWORD)
files:
patsubst(esyscmd(`ls'), `.+$', ` - \&')

$ m4 -DUSERNAME=somebody examples/config.yaml.in
user: somebody
password: defaultpass
files:
- README.m4
- examples
- sempl
Yes - see:

Cache-Control

Expires

max-age

See https://developers.google.com/web/fundamentals/performance/o...
You're either replying to the wrong post or didn't read mine, shooting at "hands or legs" is ridiculous but wounds to ones limbs are still far less likely to be lethal... Which is all I'm suggesting.
> if you have a fact-based concern, we may be able to address it.

I didn't quite enjoy this dismissive tone, so I'll be more pedantic than usual. The study you cited is interesting but it's not the end all of gun control discussion. It's barely even the beginning.

First, it considers Brady scores at a state level to try to find correlation. Gun control legislation might be at a state-level but that's a nonsensical level of granularity. My concerns are about my neighborhoods, poverty, and guns. Not the state of California as a whole with over 35 million people.

Second, from the article you cited:

> Perhaps even controlling for those factors, there will be other missing factors that are hard to control for — for instance, maybe as the crime rate increases, calls for gun controls increase, so high crime causes more gun restrictions, or maybe calls for more freedom to defend oneself increase, so high crime causes fewer gun restrictions (e.g., liberalized concealed-carry licensing rules). And of course when small changes in the model yield substantial changes in results (e.g., if you calculate the state gun scores differently, the results will likely be different), you know how little you should credit the output. Figuring out the actual effect of government actions, whether gun laws, changed policing rules, drug laws, or anything else, is devilishly difficult.

is a succinct summary of why this comparison study is meaningless. It's a good retort to someone who says that gun control leads to fewer deaths but it has so many caveats and such imprecise applicability that the only useful take away point is that at a state-level with some gun-control scoring pattern (viz. the Brady Campaign scores) discounting ALL other factors, gun-related deaths are not correlated to gun control.
I understand how insurance works, but you haven't really addressed what I'm talking about, which is that insurance companies often don't seem to understand how insurance works. You can't expect to make a profit off of every account - it defeats the purpose of an insurance scheme altogether. If an insurance company raises the premiums on a person after they make a claim, or drops them from coverage, even when the nature of that claim does not raise their risk profile, then they're doing it wrong.
That will work if you're tethering via WiFi, but Windows won't let you set an "Ethernet" (RNDIS) connection as metered, presumably because no Microsoft engineer has encountered such thing as a bandwidth cap.
Basically Car Insurance isn't to protect you. It's to protect other people from you. Which is why someone can get in an accident while driving drunk and their insurance company has to pay.
The way I see it, it is certainly possible for one entity to gain enough computing power to control 51% of the Bitcoin network. However, once you do that, if you actually do any of the bad things that you could do, people will notice, and consequently trust Bitcoin less, so the value goes down. So why make the huge investment to control Bitcoin for nefarious purposes if you will make it worthless in the process?
That is undoubtly one of the drivers but to my point, it would only matter if it was a driver that might explain why non-residents are more likely to get a PhD than residents.

I could see that being true. Perhaps non-residents value a PhD for family or cultural reasons more than residents do.
I've now linked that from the article; thanks!

(I read that page when I was first reading about this the night of the spill, but had forgotten about it. Holohan is amazingly knowledgeable about old heating systems.)
I don't get the distinction. Why is saving a stream to an mp3 space shifting but recording a broadcast to a vhs not?
Chem suit and breathing gear $100-$200.

Mercury vac: $1500-$2500

Take your time with the work, and definitely have your home inspected after. But if you don't have $50,000 for this kind of clean up, you can definitely do it yourself.
Public school teachers don't seem terribly underpaid to me. In Seattle the 2015 starting salary is $44,372[1], which is about $60k when adjusted for a 12 month calendar. That's a solid middle class job that favorably compares with other similar career options. There is another 30% in benefits/hidden comp (health care and pension) on top of that[2]. And there is significant upside for ambitious teachers who want to focus on increasing their earnings.

[1] http://www.seattletimes.com/seattle-news/education/pay-varie...

[2] http://www.wsj.com/articles/SB100014240529702036875045766553...
C1XX uses new features fairly aggressively. For example, it uses lambdas, auto, range-for, etc.
There are a lot of incorrect assumptions and general misunderstandings in this article about how mobile networks operate generally, and about how Project Fi and the Apple SIM work specifically.

Would it be great if we could choose a wireless network to join the same way we choose a WiFi network to join? Absolutely.

But that's not going to happen without the consent of carriers. It's not a technology problem that can be solved by an outside entity.
I like it, as well. It simplifies many things and no practical functionality is sacrificed.

Most arguments against sysyemd appear to be appeals to tradition, not based on any technical deficiency. In actual use I have found no fault with it and it does make some things easier.

The only argument against sysyemd that I find somewhat sympathetic is the fact that there is always a cost to pay when migrating to and learning about something new. This is certainly true. However, I find the user experience of systemd to be superior, and this small upfront price seems worth paying.
How Will Facebook's New “Reactions” Impact My Ads?
> there wasn't any mention if they were a) necessary,

They were not. It is never necessary to have 10,000 global variables. If you have 10,000 global variables you are systematically Doing It Wrong. (That's not to say it's uncommon. From my experience I strongly suspect that it's a very common practice.) As one of the witnesses put it, quite correctly IMO:

"And in practice, five, ten, okay, fine. 10,000, no, we're done. It is not safe, and I don't need to see all 10,000 global variables to know that that is a problem,” Koopman testified.

Trying to justify this is like trying to justify not having a bug tracker. Which, BTW, they didn't.

> b) implemented correctly,

There's no way to check 10,000 global variables to see if they're implemented correctly, and that's the entire point.

> and c) out of how many variables in total?

That is completely irrelevant.

> they claimed that every software within the system can access them to me this sounds that your stereo or the rain sensor for the wipers can override data for the breaks,

This was the ECU, it only controls the engine, not the radio or the wipers. It has tasks for stuff like monitoring the engine and wheel speeds, the accelerator and brake pedal positions and controlling the fuel injection. And all of those tasks were only an extra header file and a typo away from stomping on one of the 10,000 global variables belonging to another task, but that isn't even the issue. The issue is that there is no way to trace the flow of data in the system because it's completely unstructured.

> but that might be true only if everything is running within a single application.

Welcome to the world of embedded RTOSs, where everything is running within a single application. It's not a PC. "Applications" aren't a thing. There's certainly no memory protection.
I think another pertinent point would be that until currency existed poverty did not exist. Humans have managed to exist (and in many cases thrive) on this planet for at least hundreds of thousands of years, and by some accounts millions of years. Only the smallest fraction of that time has currency (and thus poverty) existed. Not that barter / exchange did not happen, but official fiat currency certainly didn't exist. And even if people possessed a commodity for trade, they didn't need to use it to survive.

I don't have numbers on it, but would love to know if any studies have been done. My hunch is that, at the lowest levels of income across the planet, actually "needing money" to survive probably hurts their livelihood more than it helps.
How much money, and what odds are you offering?
https://www.betterment.com/ has a much lower minimum, but your point stands.
Actually, I have a dSLR myself. But I'm a tech nerd and extremely aware that most people are nothing like me. Most people just take selfies on their smartphone cameras, run them through an ig filter, and call it a day.
I don't know of many people who actually liked sysvinit. It's mostly apathy due to its low surface (though actually sysvinit is still monolithic and overly coupled compared to members of the daemontools family like runit or s6).

It's a red herring, anyway. People have been replacing classic BSD and SysV initialization schemes since 1992 [1], but systemd was the first to penetrate the scene quite massively for a plethora of reasons that no one can seem to agree on.

[1] http://blog.darknedgy.net/technology/2015/09/05/0/
We bought the house in February. We might try to sue people, but it's pretty clear the previous owners don't have much money. (The house was mortgaged to within a few-k of the selling price, and they had stopped paying their monthly payments. Which made it pretty hard to actually buy the house! http://www.jefftk.com/p/house-buying-timeline)
The mathematics that needs to be solved to produce weather forecasts isn't embarrassingly parallel in the way something like Ray tracing is or in the way the BOINC projects like Folding@Home take advantage of. The mathematics involved is attempting to model the continually interacting, global state of weather across the planet in order to determine what it will be like at various places on the planet.

These models are extremely reliant on being able to "share" data between parallel operations, if computer core 1 is doing a grid cell, and computer core 2 is calculating things about a neighbouring grid cell, it will need to know things about the grid cell core 1 is working on. These models run on supercomputers in order to facilitate efficient parallel processing in an environment where each node can access the memory of surrounding nodes since promptly accessing such memory is necessary for the models to be computed "faster than real time".
ah yes, the old "everything must be perfect before we are allowed to change anything" scree.

The only thing this accomplishes is ensuring no progress is made, ever.
The ‘Get My Shit Together’ Afternoon
There wasn't a return on investment for pursuing a PhD for me, I'd venture to guess that I took a salary hit by staying in school for my bachelor's degree vs. dropping out.

But the work that I do isn't research, and I'm not advancing the field -- just solving business problems. If I was born in the late 60s vs late 70s, pursuing an academic career would have been a great option, but that ship sailed.
Has someone made a resource where noobs like me can go and read about why systemd is "almost comically bad" in a succinct fashion?

I've seen a lot of political stuff, and a lot of claims that sysvinit ain't broke so we shouldn't fix it (which makes little sense to me), but haven't seen a good resource discussing technical merits, or the lack thereof.
Except, of course, that /etc/init and /bin/sh being on "their own partitions" is the opposite of what was actually the case in the original filesystem hierarchy. (Hint: Yes, /etc/init not /sbin/init .)
That's sorta the way society has functioned for millenia. In the 20th century alone, hundreds of millions of people have died miserable deaths because some guy in power had an incorrect model of reality.

It sucks, it's not fair or just, and everything would run more smoothly if we were omniscient beings living in a completely egalitarian society. Unfortunately, that's not the reality we live in. In the meantime, we accept it as simply fate or vulnerability, and muddle through as best as we can.
The downward pressure is self-limiting: if less people mine, mining difficulty drops automatically.
Well, in fairness, systemd isn't really a matter of changing sysvinit. It's changing the entire low-level userspace, so there's a lot more one can object to, in principle.
I love reading things like this that show the startup community is growing. Good luck Jared!
https://news.ycombinator.com/item?id=10354181
An outdated version of youtube-dl, is all I can think of – run `youtube-dl -U`.
Insurance rates usually go up after a claim even if it's obvious that the claim doesn't reflect a higher future risk, though.
How I Start – C++
Linux on laptops hasn't been an issue for a while...

The surface pro 3 is fairly well supported, and I've been using linux on MacBook Pros for years.
Does this company have a track record? What assurance is there to an investor this startup will actually pay out?

Also, I'm rather curious about the math behind the business. (Note: I am a programmer. I could best be described as having a low and/or dangerous level of knowledge about investing).

If assure.li has 7 customers buy insurance for their $100k investment at 15% (so +$15k insurance premium), they are making $105k. If one of those companies "fails", assure.li now pays out $100k and now are left with $5k. If two customers fail, assure.li is now down $95k.

It's pretty widely cited that nine out of ten startups fail. assure.li seems to be betting that 90% succeed: even splitting the difference and saying 50% succeed, it seems to me this company will run out of money very quickly. An insurance company with no ability to pay claims is not a very useful insurance company.

Or am I completely missing something here?
Free trade is not the primary force. It's secondary behind more foundational liberal economic policies, those being property rights, rule of law, fair enforcement of private contracts.