skysight-inc/HackerNews huggingface dataset:
A fork would also mean that Debian (systemd edition) would not have to keep legacy init script support. You could have a 'clean' systemd in around Jessie+1 I imagine.
It's only 2 lines even restricting yourself to the standard library

#include <fstream>
#include <iterator>
#include <numeric>
using namespace std;

int main() {
ifstream nf ("numbers.txt");
return accumulate (istream_iterator<int>(nf), istream_iterator<int>(), 0);
}
Decoupling systemd is a feature desired by system administrators, who are responsible for installing and managing most debian and debian-based distros.
I think there's a change happening, some new cars can be started by button-press when the transponder (replacement for the key) is somewhere in the car (e.g. in your trousers' pocket).

And then, of course there's the other aspect that in some cases you absolutely want to be able to cut power to your engine. Wasn't that exactly the case with Toyotas drive-by-wire throttles that apparently made people unable to stop their cars?

Still: When you look at the electrical system for, e.g. a commercial airplane, you'll see a dozen different independent power-supply busses that can be fed from each other, different engines, or batteries. So that in case of power-loss in one or a few of them, not all safety critical systems black-out.

I don't claim that such complexity is helpful or desirable in a car, but with the majority of drivers relying on computerized systems it probably makes sense to make power supplies more redundant.

{probably that's already happening, and I'm just unaware of it?}
I think that this observation is not as relevant to the task at hand that it seems. The author is in the same position as the implementor of a VM, who has to decide which operation will be a primitive and which will not be.
What is actually more important than anything else if you care about performance is which operations are likely to be called from hot loops. It's classic optimization wisdom except that you can only work on expected scenarios rather than real-world uses (until you release your stuff and other people use it).
So a 100x slower abstraction is ok(-ish) as long as it's not somthing to be used in performance critical sections.
I don't get blocking some ads. What does it hurt to have a basic banner add next to the story you are reading? They took the time, effort, and money to create content you want to read why block it?
I understand blocking ads that take over your page but not basic ads.
"So nine times out of ten the salt is retained in the leaves of the plant, so you’d have to eat many many kilos of potatoes before you’d exceed your recommended salt intake. But some of the salads are heavy with salt"

Then how are the leaves disposed of, I do not know. Fed to pigs or burnt perhaps, if they were simply used as mulch you would still wind up with a buildup of salt in the soil.
Rhianna seems to churn out plenty of crap on a regular basis.
I've read the article and this blew my mind:

"[...] if you took all of the cars that GM has recalled this year and lined them up bumper to bumper, you’d end up with a line that would wrap around the earth four times."

That's 30 million cars.
I don't think that any of the scientists/philosophers/mathematicians mentioned (not even Hawkings) can damage Aristotle that much. Aristotle is kind of far and away in terms of perceived importance. Perceived because I don't know the body of work of all the people mentioned in the article.

IMHO these ancient scholars from whom western civilisation started, will be read and re-read from the original text, studied and re-studied much more thoroughly and many more times in the years to come than Russel of Hawkings. Maybe unfortunately so, maybe not. I'm not able to judge any of the names mentioned in the article. That's just a feeling, only time will tell.

As other posters already pointed out, when science comes at play, we have to understand the dynamics of ancient Greece at 400 BC, with their lifestyle, beliefs and lack of knowledge (in any science: physics, chemistry, etc.).

However the most important body of Greek philosophy is the questions/answers surrounding men, existence, purpose (in life), knowledge (inherited or learned?), etc. Because these are universal questions that any human being with acceptable intellect will have to confront in his lifetime.

Off-topic: I've read an essay some time ago - can't find the link :-( - saying that especially today the difference between the body of knowledge of a top notch scientist and average peasant Joe is chaotic. Might be, but thinking how Aristotle, Euclid, Newton or Gauss would have felt in their era when talking to a peasant is a lot more scary to me.
No. Even the pro-fork advocates (even the above article) see the Jackson / Vernon proposal as a much better idea (choice of init systems with a systemd default)

No. IMHO Debian is less a distro than a democratic experiment - and systemd shows it is working. If you don't like systemd (and I vastly prefer my FreeBSD world) get on board with the democratic process - it is always messy, frustrating, driving you insane slow. That's how you can tell it is working

Don't fork.

Edit: Matthew Vaughn is an actor not a Dev.
Unfortunately they (AMD) didn't reassign those opcodes for some other purpose - they've just become completely invalid.

Instead, a whole row of useful general-purpose increment and decrement instructions was replaced by 16 REX prefices. A bit odd if you consider that the number of BCD and segment prefix opcodes they made invalid would've been more than enough to be assigned to the new REXes, and still maintain a consistent encoding...
> c::a$"\n"

The code is full of these things, that looks conceptually a lot like Perl oneliners (which I don't mean in a negative way). But the trick to coding with these short idioms is to make sure your input is strict in a very specific way that fits your particular problem.

A nontrivial codebase could not be written in this way. A real life editor would for example have to the concept of active parts of files to edit files larger than fits in memory, the ability parse different encodings and line endings without changing the on-disk format unless asked for, and many other things (and this just to implement the bare bones of an editor from the 80s).

This looks a lot like a macro language, with its many ready made functions for accessing ctrl-key sequences, cursor movements etc. Would it really hold up outside its problem domain?
1.2 hours per frame sounds about right for a feature. Also, apart from Moore's Law, there's a Blinn's Law ( http://en.wikipedia.org/wiki/Jim_Blinn ) - As technology advances, rendering time remains constant.
The idea of a server based fork of Debian is kind of appealing in some ways, like the Fedora server and cloud projects[1][2] which are quite interesting work, aimed at a (sub)distribution with focus on particular use cases, not the kitchen sink approach.

[1] http://fedoraproject.org/wiki/Server/Product_Requirements_Do...

[2] https://fedoraproject.org/wiki/Cloud/Cloud_PRD?rd=Cloud_PRD
> The issue is that Gnome, KDE, and other software requires systemd.

This I can't wrap my head around, why does Gnome for example need systemd? There are standard ways on GNU/Linux to do everything it needs in a unix fashion (by deferring to small specialized tools):

shutdown
reboot
whoami
uname
mount
...

These and similar tools (or libc functions) give you all information you need (username, etc.) and system functions a desktop environment needs (reboot, hibernate). You then only need something like udev for plug-and-play (which is available without systemd, and as a part of it), and interfaces to the X/Wayland server and the audio system (which are both not a part of systemd). This seems to be all stuff that can easily be abstracted away in one module per OS. I don't see why you have to tightly couple your DE to systemd. (Unless, you are using your DE as a vehicle to push systemd, which I hope is not the case...)
Why is it that so many opponents of systemd can not spell its name properly?
Just use coreOS and docker on the server and leave the init system discussion to the desktop people.

There are some fundamentally different and sometimes conflicting requirements regarding the startup process on a server and on a desktop machine and I think systemd which is obviously desktop driven will be the catalyst for a split between server and desktop distros.

I don't think classical desktop environments have much future personally, but that's just my gut feeling.

Server will definitely move further into modularization of services, and that will make init systems there less and less interesting.
But isnt that proposal kind of too late, the process has already chosen systemd?
I don't mind free stuff, but to be honest I don't see why you release it for free. Seems like you had something sustainable going on. One person selling everything he owns to pay 3 persons' salaries don't seem sustainable.
The ignition switch in question seems totally unremarkable. I wonder why it was redesigned in the first place? Why not use one of the many existing parts GM had at the time?

Also—somewhat of a nitpick to an otherwise good article—the Bronco II is a completely different model from the one driven by Al Cowlings during the O.J. Simpson chase. That was the full-sized Bronco. When details like that are wrong, it usually makes me suspect the accuracy of other facts in the story (although in this case, the article seems otherwise accurate).
CoreOS is entirely based on systemd. Fleet is a distributed systemd. It is far more systemd oriented than any other distro, having built it in as a core feature form day one.
Yes, ~January 2012 was initial integration... with a great many reservations and expectations for change as per the LWN link you quote. See https://github.com/torvalds/linux/tree/master/net/openvswitc... for recent changes, also https://github.com/torvalds/linux/tree/master/net for general networking changes.
That is not what I'm saying. These statements are formulated in a way to make them sound reasonable. But there are no (scientifically) previously demonstrated results. None at all. If you were to make specific statements, you would at least open the questions to further research.
Can't we just agree on:

1. APNG for low-color/lossless content.

2. MP4/WebM for video-like content.

3. ???

4. No more GIFs = Profit.
Very interesting. One reasonable benchmark would be uppercasing a string as described in the article vs the usual way.
Movie was most probably rendered at 4K and 24 fps (double for 3D), and more realistically and more probably at 2K - with actual resolution depending on the aspect ratio. Lots of smaller companies are using amazon directly or 3rd party render services built on top of amazon, but bigger aren't and won't. For example: http://www.zdnet.com/for-peter-jacksons-weta-digital-the-clo...

Also, it's not really practical to use amazon-like service for production previews if you don't have a fat pipe running to it, so there will always be a need either for a small local farm or high end gpus or both.
"Allonge" is very much about FP and - more importantly! - about the uses of FP in a language with mutable state, objects and so on. It's more pragmatic and immediately useful than The Little/Seasoned Schemer, but this doesn't make it any less about FP.

"Spessore" is about OOP, but described from unusual angle: it reminds me of "The Little Java, a Few Patterns" in this regard. It's a great description of how and why OOP works, from the most basic concepts up.

Reg's articles on FP in JS and Ruby let me fill the gaps in my knowledge I had because of having no formal education in maths. I was interested in FP for years, and I learned much about it on my own, but Reg's texts made it all "click" for me. I definitely recommend reading all of them; unless you're really familiar with this stuff, from both theoretical and practical sides, I can guarantee that you'll learn something new and useful.

Really, go read them. See also https://leanpub.com/coffeescript-ristretto if you prefer CS.
In hindi also there is a simliar saying "Dudh ka jala chach bhi phoonk phoonk kar peeta ha" meaning
Someone who is burnt with milk is very careful while drinking buttermilk as well.
If Ritchie and Thompson knew the damage fork-ing would cause to the open source community, they would have never implemented the idea, as a system call in UNIX[1] in 1971.

[1] http://cm.bell-labs.com/cm/cs/who/dmr/man21.pdf
The band Kilo had a "crowdsourced music video" based on the same concept: http://donottouch.org/
The website could be replaced by a much shorter version simply stating "I dont like SystemD. -anonymous".

The author is essentially making a threat, that there will be a fork of Debian if the project does not give in to his demands. Then he states that he is totally not just speaking for himself, but for a much larger group, and in fact claims to have the majority on his side. I have a hard time evaluating the seriousness of these claims, as there is no intend to back up any of this.

As far as the arguments go, there is nothing new here. The concerns have been stated before, and have been heard, too.
<sarcasm>Yeah, that's why.</sarcasm>
How to start a startup without ruining your life?
Or just shut up and put your efforts into maintaining https://packages.debian.org/jessie/systemd-shim

Also, critique starts with "We like controlling the startup of the system with shell scripts that are readable".. How on earth is a systemd service file less readable then a hundreds of lines bash script?

Also relevant: http://www.itwire.com/business-it-news/open-source/65684-deb...
One of the major reasons why the finance industry works such ridiculously long hours is that small, arguably-understaffed teams are better at keeping secrets and maintaining client relationships and more easily held accountable for their errors.

Aircraft leasing is a well-defined, finite market with most of the commonly-leased aircraft types having well-understood risk characteristics, and the lessors can and invariably do buy reputable independent opinions on market lease rates, residual values and empirical data on market activity (they can buy them by contacting me, actually :-) ) In many respects it's more risky to throw a large team at building a model to come up with a contrarian view.

Needless to say, the airline will throw far more people at trying to ensure they can keep up with the lease repayments and bills from actually operating the aircraft and there are quite a few lawyers and technical consultants involved in the final signoff and aircraft redelivery. Similarly, some teams involved in supply chain management and business development at Maersk must have spent a vast amount of time figuring out the logistics of filling larger ships in future, which based on how little time the last generation of "biggest ships ever" stayed in service is a much bigger gamble than most airlines will ever make.
Where is this banner coming from? Whose servers are you contacting to get it? Whose javascript is it running? Is it loading flash or java rather than an image? How many people end up tracking you for requesting "one banner"?

As far as I am concerned the advertising industry has screwed themselves over by allowing security threats to be delivered via their networks.
You can also chose to ditch them and not support anything that requires systemd.

Yes, really.
That was also one of my inspirations! (That and cursors*10)
Maybe it is the mobile website, but I can't find pricing or source code. Is it free / open source?
on the contrary, systemd is a feature desired by system administrators, who are responsible for installing and managing most debian and debian-based distros.
And in crond you have three places to look. So?
Comments are available after tokenisation (https://docs.python.org/2/library/tokenize.html). They're indeed not in the AST but you can get at them for analysis.
Systemd provides interfaces to reboot/shutdown as non root api which is controlled by polkit. It also allows a non root process running as part of an active session to get the DRM FD and other device FDs as part of the logind interface.
Your attitude is exactly the problem. "Shut up and do what I say" is exactly what systemd is about.
>SystemD betrays the UNIX Philosophy

Not so convinced by this. "Those days are dead and gone and the eulogy was delivered by Perl." -- Rob Pike

Systemd in debian would have an easier time making friends if it didn't usurp PID1 for roles that are currently outside PID1, and if it didn't encourage software which is currently init-system agnostic to grow a dependency on a specific init-system implementation.
1. There are already systems that before your appointment , gather detailed data and history and display it to the doctor is a condensed and efficient manner. For more details, see[1]. In general : " history taking in this manner is more efficient than the traditional method and allows more time for discussing the assessment and plan. Best of all, it is also associated with better clinical outcomes."

But they aren't commonly used. It's probably because of medical conservatism coupled with business and status reasons.

And in some cases it does help to have the medical interview with a person. But wouldn't a cheaper nurse armed with a great software tool, offering a 20/30 minutes appointment is better than 7/10 minutes of a doctor's time? In some places in the british system that's what happens and research says the results are comparable to a doctor , with patients being happier.

2. There are crowd sourced solutions like you specify. The one i know is a ycombinator company called crowdmed.com . At least according to the media they do bring something very good to the table, but they're very new so it'll probably some mote time to see how they function and scale.

As an aside, there's an an expert system by a company called isabel healthcare, that in the hands of a regular family physician ,can enable regular physicians to diagnose rare and complex diseases at the level of top diagnosticians.It's available via cloud.I'm sure almost no physician of anybody in this thread will have it.

3. Not sure who is to blame, but i think many of those problems are common globally to some extent. Maybe the british system is somewhat better with the policy of employing lower level providers across many roles.

[1]http://www.aafp.org/fpm/2007/0700/p39.html
Do people not have better things to do with their time? It doesn't make sense.
Looks like the Squeeze LTS project[1] could use some help[2] and the team proposing a fork are server type folk reading between the lines. Good fit of skill sets and a way of generating positive outcomes quickly to build confidence? So fork from squeeze forward updating strategic packages?

PS: I love the 'how long are your beards?' line. Obviously, I'd rather Debian didn't fork and that we kept choice for server people in one of the larger Linux distros just on an 'ecological diversity' basis.

You can do a window manager on top of X with systemv right now in Jessie [3], the '--no-install-recommends' option to apt-get is helpful. But the result will be seriously old-school. Its rather fun for surfing in cafes and wasting time on forums but for my day to day work (not programming) I prefer a full fat desktop like KDE/Gnome.

[1] https://lists.debian.org/debian-security-announce/2014/msg00...

[2] http://www.phoronix.com/scan.php?page=news_item&px=MTc4NTE

[3] http://sohcahtoa.org.uk/osd.html
You can do this with a normal cursor too. Get the cursor to the edge opposite the one you want to get to. Press escape to go into loose lock mode (not sure how to describe this).

By taking your cursor down outside the box, it doesn't register as being too far away (stays yellow). You can loop your mouse around to the other side outside the window and instantly your cursor catches up when you re-enter on the opposite side.
Very good point. In huge systems such as a car everybody can not know everything. But in this case, if the ignition switch team does not know how their component affects everything about the car or how important it is the responsibility should move up to whoever writes the specs on the ignition switch. First of all for designing a system with a single point of failure in the first place, secondly for not loudly notifying ignition switch team that their component is vitally important and a single point of failure. As i also said in a post above, way too much attention is given to the faulty switch when this is actually a much larger system design error.
There is not right now, although I hope to add some plugins for common IDEs and editors. You may have success using https://github.com/davidhalter/jedi-vim though - the guy who writes it is adding static analysis.
> similar in capability to SQL but around 1000x faster

If it's really similar in capabilities, why not strap an SQL parser on it and sell it? You can do it client-side to avoid wasting performance where it matters. Surely there's money to be made in the database business if you are an order of magnitude faster than everyone else -- let alone three.
Stock Market Volatility: The Good News and the Bad News
> Maternity leave is paid by the government not by the employer in all the countries I heard it exists in.

In the UK, it is paid by the Government for the first two weeks. The employer is then required to pay the employee on a reduced basis for six weeks before the Government takes-over again for 33 weeks ( edit: at a standard rate not associated with the original salary ).

There is no financial support for the hiring or training of another employee to provide cover during the period of absence.

Source: recent personal experience
Bandit looks like a really great addition to the various Python checking tools. Expect some pull requests soon!
And if that service file screws up how do you troubleshoot it? You end up diving in to the source code of systemd, versus fixing a bug in your script.

And don't get me started on binary log files.

As was said before, buster, your attitude is the problem. It's the same as the systemd developers and those within the community.

SysVInit has served me thus far with no issues.
There's an end? Aw, man! I tought it was just big bunch of randomly chosen levels. How about a counter? Something like 'this is level 123 from 444'?

Surprisingly awesome game tough!
I was specifically thinking of the php matching issue, which I've seen a few too many times to be comfortable with. People shouldn't copy and paste configuration from the Internet, but they do, and I wish nginx wouldn't make it downright dangerous.
It's a solution to CS107 assignment 1 :
http://web.stanford.edu/class/cs107/assign1.html
My experience with functional programming helped me understand the use of register machines (aka imperative programming). FP has a better ability to cut and expose clean abstractions, while register machines conflates things quickly, making it hard to see if it doesn't fit your brain's inner working. Being on the other side helped me see these hidden structures (whether or not I change the way I write C code for instance).

edit: typos, also I believe https://mitpress.mit.edu/sicp/full-text/sicp/book/node105.ht... is a good example of bridging both worlds. Mapping a scheme to a register machine. Sussman's videos were a real eye opener.
I read the 'shut up' line in the post above yours as more along the lines of 'do something useful, post bugs, show some commitment' rather than 'shut up systemd is the Only Way'.

Perhaps the sponsors of the linked site are doing bug reports on packages like systemd-shim and others. Perhaps the upstream project members involved are ensuring that they have init scripts for systemv available. They could add a question with links along those lines easily.
Just curious, have you ever used systemd and ran into a problem where your service file screwed up and you had yo read systemd's source code or are you making this up?
I almost started to surrender to the latest gmaps until I used bing maps which reminded me how simple and smooth the previous gmaps was. OSM is nice too now.