skysight-inc/HackerNews huggingface dataset:
> "A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version. Identifiers MUST comprise only ASCII alphanumerics and hyphen [0-9A-Za-z-]" [1]

I think they should use 0.0.1-pre instead of 0.0.0. The version 0.0.0 I would consider as "the development have not started yet".

[1] http://semver.org/
> Did you really chose your nationality ?

Naturally one doesn't get to choose their initial nationality.

At some point, though, you (may) have the option to emigrate elsewhere, and assume another nationality, and thus assume that other nationality's perks and burdens.

> Say I want to live by my own rules, outside a nation. What are my options ?
> Similarly, can I "give up" my nationality and if so, what happens ?

Depends on how much you're willing to give up. For instance, you can liquidate all of your assets and, say, start living on a boat in international waters. Or if you're willing to ilve on a sovereign country's land, just move into a forest where no one will ever find you. Depending on freedom-to-roam laws, that may even be reasonably legal.
>You know how free speech is about protecting the speech you despise? Same goes for human rights.

Interesting, but speech is much easier to define than what makes a human. If we disable or remove parts of someone's brain (or if they're genetically different), at which point do they stop being human? What if there's no brain at all? I would say a bunch of meat isn't deserving of human rights. But where is the line, what if the brain has no emotions? Or no pain? No concept of self? No empathy?
Red Hat's marketing muscle to "embrace and extend".
Or VVVVV https://en.wikipedia.org/wiki/Vi_veri_universum_vivus_vici
I want to learn Redux, these are 20 videos that I have planed to watch: https://learnredux.com/view/hmwBow1PUuo.
300Mhz. But you can work around that...

http://virtuallyfun.superglobalmegacorp.com/2011/01/10/windo...
When I freelance, they just ask if I can get the job done.

When I get hired, they want me to do dumb tests.

The only difference for them is that they can stop paying me right away when I freelance, but when I'm an employee they have to pay me for at least 2 weeks to go (at least in Germany were we have 6 months probation time on new jobs, where you can be fired easily)

I made many people I worked for happy, but many people who gave me tests wouldn't even consider me as employee.

I don't know if I would have been a bad employee for the testing-companies, but I never had issues with employers or customers who hired me, so I have the feeling the companies who didn't hire me were missing out.
Because scope creep means more and more packages have systemd as a hard dependency.
Well you could do it for decades with VMs but that's pretty heavyweight ;-)
Sounds like an excellent way to spend some time in jail.
100M clear text passwords stolen from Russia's biggest social network
You didn't provided any real argument besides the obvious one - change.
I use systemd on my Debian servers and i just don't see it as something bad. I have created systemd services that i use and it's really convenient.
EaseUS MobiSaver for Android 4.1 Crack Full Version
"There is also concern that it forms a system of interlocked dependencies, thereby giving distribution maintainers little choice but to adopt systemd as more user-space software come to depend on its components" from relative wikipedia article (https://en.wikipedia.org/wiki/Systemd). This does not sound any good.
What really struck me was the fact that desktop community (not sure if this would be happiest word for it, but I think you'll understand) is dictating the fate of whole Linux. For me Linux was and is primary a server OS. Than worsktation one, and on the last spot consumer desktop OS. I mean for desktop perspective systemd maybe isn't that bad, but for servers I am sure there are better solutions.
> Even if it is 100% true, I am not impressed.

You are not the only person to come to that conclusion. The entire situation is bizarre. Usually highly rational people are suddenly acting like an angry mob. Requests for information and explanation are ignored or shunned.

> We can make our community hell on earth.

I've been watching major parts of free, democratic society crumble for several decades. Normally change is slow, but recently we seem to be accelerating the transition into hell. The transition isn't limited to just our community: the same attitudes that treat accusations as evidence and polarize people into ideological tribes resulted in violence at a recent political rally in San Jose. Tribalism is growing rapidly, and I am absolutely terrified that society is far closer to the breaking point than anybody realizes.

> All we have to do is let the provocateurs be us.

As Walt Kelly famously said, "We have met the enemy and he is us."
160k for junior and 220k for senior? Doesn't make any sense to me.
The process turns a request for binary DNS data into into XML, feeds it into the sytemd/dus ecosystem, which turns it into binary DNS to send it to the forwarder. The binary DNS answer then gets turned into XML goes through systemd/dbus, then is turned back into binary DNS to feed back into glibc.

This reminds me of http://thedailywtf.com/articles/XXL-XML and the "XML fever" that infected most of the enterprise and otherwise software developers many years ago. Whenever I see some system XML-ifying everything, it's usually a good indicator of grotesque complexity elsewhere in it too.
Yes, it is much more convenient, and as an init system there isn't much wrong with it. But in software change for change's sake alone is simply wrong, it creates friction because a lot of knowledge has to be discarded and then has to be replaced by different knowledge. Large amounts of regression testing suddenly become useless which will generate ample opportunity for re-hashes of old bugs and issues (see linked article).

Modular designs are good, monolithic designs are bad. Dependencies are bad and so on. Lots of choices at the design level were made against fairly hard won knowledge on how to architect complex software systems. All these dependencies translate into 'all or nothing' and that is never a good thing in the software world. It's just another form of lock-in, something that the world of closed source software is good at and I'm quite sad to see it pollute the world of open source.

Edit: I suspect a lot of the pushback against systemd - mertited or not - is because a lot of people in charge of little parts of the bazaar have seen their pet projects cast aside by the major distros and taken over by the systemd devs. In a world where street cred is a big force in motivating people to contribute to open source being maintainer of 'x' where 'x' is part of each and every linux distro out there and then to see 'x' taken over by systemd in a fairly rough manner without any kind of co-operation between the old maintainers and the new kids on the block there are bound to be a lot of ruffled feathers. But that's not technology, that's just ego.
It's the most vocally hated possibly. Certainly not the most hated. While systemd has its share of issues, it's overall high quality and reliable. I can think of far more globally hated software (Flash).

Make a note that systemd-resolved is not systemd, merely "part of the systemd umbrella". -resolved is not widely deployed at all.
Former NASA chief unveils $100M neural chip maker KnuEdge
Don't forget Alpine Linux
I did it for years too and I would never do it again, no matter what the pay is. I guess it is a matter of options and taste, but I find commute and working in an office every day quite close to living in hell.
From my experience - Flow is still very "unstable" and in heavy development. I haven't tried TypeScript at all, so I cannot compare that.

It's absolutely true that Flow team is merging all pull good requests, fixing issues (the backlog is big - 500 issues - but TypeScript has 1000, so it's not incomparable) and the system is made dramatically better every release.

But there are still rough edges, especially when working with ES6 modules and import/requires/etc.

Again, I don't know how TypeScript compares, I learned Flow and am just using that.
I don't think it's really all that bad; several big, popular, widely-deployed distributions are using it and most people appear to be getting on just fine.

It's just that people against it are extremely vocal.

I do dislike the idea of binary logs, though.
"just"? Sorry no

Well, yeah, kind of...

rapist sociopath

Hey, geeze. People were talking about plagiarism over here, why'd you have to bring up the "R" word! There's kids on this site for christ sake!

Seriously though, this really is just a lot of drama going on. On the internet, no less.

Quotes like this come to mind:

Build your cities on the slopes of Vesuvius.
Of course not. Isn't laziness one of the traits of talented programmers?
A good description of why it's superior to init scripts: https://www.reddit.com/r/archlinux/comments/4lzxs3/why_did_a...

I don't know enough about resolved to comment on this new development, but as a sysadmin I much prefer systemd as an init system.
TeamViewer users are being cracked in bulk, and we still don’t know how
VK.com hacked. 100 million plain-text passwords leaked
You don't provide any argument. 'It runs on my machines' is akin to 'it runs on my laptop'. Previous system was working, battle tested, was _not_ broken, was not polluting user space. And these are just a few arguments fished from above and other commends here. Now - to defend the new system which will have to prove it's value and stability in the next 20 years or so- what good is it? What awesomeness brings to the table?
One problem with "take on people for a trial period" is that it's more risky for the candidate too. If you happen to be unemployed then doing a trial-work-period is obviously an improvement on not working at all, but otherwise I'm going to be reluctant to quit my current job for an "after a couple of months we may say sorry, didn't work out" setup. (That's different from the current standard '3-6 months is a probationary period' because right now the assumption is that unless you actually screw up you get the job, so it's not an in-practice risk for a competent employee. With a more definite "trial period" approach the employer is going to be more likely to say 'no' at the end -- otherwise the "pick who to trial" question is still just as high-stakes as "who do we hire" was and they haven't gained anything from the change.)
> Flow uses nominal typing (similar to functional languages); whereas, TypeScript uses structural typing (similar to Java).

Most statically typed languages have both nominal and structural types, and, if anything, functional programmers use structural types to a much greater extent than Java programmers:

(0) Haskell and ML: Algebraic data types and type classes (Haskell-only) are nominal. Function types, parametric polymorphism, module signatures (ML-only) and object types (OCaml-only) are structural. Type synonyms are of course structural. Type inference makes it practical to work with definitions whose types would be quite large if explicitly annotated, so programmers don't shy away from parameterizing types by four or more type parameters: http://hackage.haskell.org/package/lens-4.14/docs/Control-Le... , http://hackage.haskell.org/package/pipes-4.2.0/docs/Pipes.ht...

(1) Java and C#: Classes, interfaces and variances (C#-only) are nominal. Generics and wildcards (Java-only) are structural. No type synonyms and limited inference make working with syntactically large types very inconvenient. And guess which is the most vilified feature of Java's type system among Java programmers themselves...
How else would you send the data to dbus? dbus is xml-based.

This is caused by resolved requiring a separate forwarder. "XML" isn't inherently bad.
Good initiative.

Clojure developement is driven by the needs of Rich/Datomic these days, it's understandable this might be frustating for users who wish clojure was more community driven, and exploring other areas.

I personally gave up on it because of this (I used to do clojure full time).
Update: http://arstechnica.com/security/2016/06/teamviewer-says-ther...

IMHO this underscores the necessity of never using a memorable password on a remote service.
Because it started small and OK. When distros made the decision to switch, it looked OK.
It has proliferated into something else since then and none of the distros seems to be willing to take a step back.
Debian 8 comes with systemd. There is a fork [1], but not really popular.

[1] https://devuan.org/
Things to look for when buying an apartment
What solution do you suggest instead?
It seems to be a common mindset among python developers. You often hear the reason you can't have something in Python is because it's theoretically impossible, impractical and too difficult - but then it happens in another language. I was convinced that dynamic languages would always be slow (see https://wiki.python.org/moin/Why%20is%20Python%20slower%20th...) but then Google gave us V8.
systemd is a good thing (tm) - I recognize that and am grateful for it.

However.

In the beginning a lot of distros were "forced" to accept systemd because udev was merged into its codebase.

Systemd is great, but its group of devs are absolutely fucking terrible at public relations. Sometimes they make changes that upset users. Like the recent one that has (logind?) by default killing all user-created processes when the user logs out (this surprised people as it became a new default). Or the security incident before that where systemd made it possible for users to get access to framebuffer contents. Sometimes things happen.

It's just made worse when you go to the systemd group with your problem and they act like what they've done is correct and everybody should just live with it. Sometimes we're wrong, sometimes they're wrong. Poettering writes up these really long posts which are mostly good reads, but sometimes he calls us neckbeards who want to live in an unchanging, static past.

Great project, great code, great devs - but terrible attitudes [sometimes].
It would be an excellent example in a security talk 10 years ago. If anything it should be used to promote better authentication solutions.
I believe the passwords came from the 2012 LinkedIn breach and was referring to the original criminals. If you have the criminal energy to steal that data you might as well use it. I don't think there was anything white hat about that incident.
This is a partial fix, but it's not enough. An attacker performing man-in-the-middle attack can respond with the previous version of "version information file", preventing the update.

Imagine if there's a vulnerability in one version of KeePass2, and the fix is available for it. MiTM attacker sends the previous version so that the app doesn't know that there's an update, and the attacker has more time to use the vulnerability.

HTTPS prevents this. They should do both.
Browsers have their security model. On the other hand, when you install an executable binary or a Node.js program, you don't expect to have the same security model.

This project fits in the latter category. It does not claim that downloaded binaries are protected by a sandbox, and the only security claim it makes is the following weak one: “The generated code should be unable to access any memory outside of the addresses allocated to it”.
Official local news: This never happened.

Slightly less advertised news: This never happened, the data is from a 2011-2012 leak, and everyone from it was forced to change passwords long ago.

The "33,236 times" password is actually mildly obscene, meaning something close to "everything went to hell". Doesn't make any special sense to me.
Wonderfully worded. I'd throw that to Bill Nye at big think on youtube at see what he has to say. He loves "far out there" explanations for everything like that
Any ideas on who would target him?
I've mostly lurked lately and have firmly vowed not to touch a systemd-related thread ever, but I'm waiting for a long compile and I'm going to bite.

First, please, let's get the unix philosophy crap out of the way. Most of the modern Linux tools don't follow it. The people who passionately hate on systemd for not following the unix philosophy happily use Grub2, LibreOffice and whatnot. The Unix philosophy is nice to have, but quality software that does not follow it exists, nonetheless.

The advantages that systemd has brought are hard to downplay. It gets a lot of hate because they're essentially non-existent for desktop users (and don't give me that shit about dynamically mounting storage devices or parallel startup and whatever, because those were available way, way before systemd was a thing). The unpleasant truth is that desktop Linux is largely irrelevant for a lot of the major players in the Linux world, and for the very few who care about it, the only relevant target is corporate workstations, where a tight integration with systemd is desirable.

tl;dr it has real advantages which are desirable to most of the companies that pour money into Linux stuff and, unsurprisingly, these can dictate much of Linux development at the moment.
Under a severe pressure from a vocal and extremely tribal minority, of course. There are no technical reasons to do it.
I think this advice is even more pertinent:

> How should I deal with revisions in the 0.y.z initial development phase?

> The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release.

Source: http://semver.org/#how-should-i-deal-with-revisions-in-the-0...
Animated Visualization of WWII Fatalities
> All these things just worked 10 years ago.

While I massively dislike the systemd approach, this is not true either.
Using wifi, mobile connections on linux were a massive pain unless you already spent countless hour on writing your own fixes for you own setup.
CSS Specificity: a visual guide with icons inspired by “The Shining”
I know a guy who is building an All Relay Computer, no transistors.

I don't think he has a webpage though.
Oh please let us finally arrive at the Jurassic Park interface. It's a UNIX system, I know this!

https://www.youtube.com/watch?v=J1VE6C0H2bU
Damn. I was going to say we need this in Japan, but it does mention a Japanese one. I wonder what the costs are like though? Worker hours and electrical).
Something I notice is that the country as a whole is becoming a whole lot more like those states no-one wants to live in (e.g. New York, New Jersey, California & Illinois) and a whole lot less like those states people want to be in (e.g. Texas). That doesn't seem good.
Because there are a group of Linux users out there who are more interested in creating a desktop-OS than a Unix-OS.

Honestly, at this point, why not rename SystemD to svchost.exe and set it up to use .reg files for configuration?
Credibility and trust: Microsoft blows it by forcing Windows 10 on users
I maintain Linux servers. I also write backend/server software. systemd is a Godsend. It's infinitely easier to write a systemd init script, than it is to write a robust init script in shell.

systemd (by leveraging cgroups) makes it easier to 'track' started processes. It makes it easier to stop/kill processes. It also provides handy security features (e.g. PrivateTmp).
> dbus is xml-based

"D-Bus is low-overhead because it uses a binary protocol, and does not have to convert to and from a text format such as XML." https://dbus.freedesktop.org/doc/dbus-specification.html
Do you have reason to believe that they wouldn't have, or that they would do so, if it were GPL3+ licensed?

Apple famously doesn't provide any "recent" GNU tools because they're GPL3+ licensed, when they were previously GPL2.x and less restrictive.
My new dev/deploy target is freebsd. It's actually kinda nice. It treats the user with respect and doesn't pretend to know better.
And DUNS number is also pretty useless as it is based on location (not organization).

A search on sam.gov for "lockheed" results in 207 records (all probably the same company).
“No Facebook systems or accounts were accessed… The affected accounts have been re-secured.”

Sounds to me like they weren't very secure to begin with. So they would be "secured" now, not "re-secured". It's crap like this that makes me miss George Carlin.
New mobile app hopes to ease diagnosis of neglected diseases
Check out the radio broadcast: http://www.wwiifoundation.org/students/real-time-radio-broad...
Evidently, money is more important that security.
You said you "still don't use a pwd manager". Learn from Zuck's error and start using one today!
So, a MITM would be able to prevent automatic update notifications?
Show HN: Import Balsamiq Mockups into CanvasFlip using this simple interface
"There are only two kinds of languages: the ones people complain about and the ones nobody uses." -- Bjarne Soustrop
How to Pick the Good Health Apps
it'd be funny to fork devuan and replace init with systemd.
It usually boils down to the following simple principles and techniques:

A: Probabilistic data structures and algorithms
For example you can quickly estimate if a very large set contains a certain key with bloom filters or estimate cardinality with hyperloglog.

B: Divide and conquer
Just divide your data to workable pieces and combine partial results at the end. Hadoop is a popular infrastructure for doing this. Other example is doing pieces of work in memory and saving it to disk by chunks and reducing it later to get the final result.
How do LIGO know they detected gravitational waves
I see that this change (systemd) is mostly driven by desktop software dev teams. If linux chooses to care mostly about the desktop aspect (IMHO previous such experiments like Unity were total flops but I'm not an expert) instead of its server one then maybe that's the opportunity for BSDs to cover up the void. Not a bad thing at all.
But you can still run gnome on Ubuntu (I do), and Linux without a graphical interface at all.
Identifying People from Their Driving Patterns
If you do not like unity, you can just use ubuntu-gnome like me. IMHO, Unity is horrible, but you have the choice to not use it. There is no need to complain.
Getting a Yubikey? What about this?
https://news.ycombinator.com/item?id=11690774
Thanks I was wondering what it meant. Lol. Guess it's a bit of a prophetic password
Social Recruiting Tips to Attract Best Talent
There is a certain appeal to committing to something 100%, to pushing it absolutely as hard as you can. But the cause has to be worth it, because you are going to sacrifice everything else: friends, family, the basic enjoyment of life. I don't see how anything FB is doing is remotely worth that kind of sacrifice.
Safe VSP – 30 year old Commodore 64 bug demystified (2013)
I am not sure what your colleague means with "too damn hard" - I used it once in production code to optimize distribution of lots on an assembly line, for example.
That was a COBOL program dynamically preparing the equations and then calling a C routine (copied straight out of the "Numerical Recipes in C") and that was all.

Of course you have to get a bit of practice about how to represent your problem in terms of equation and objective function, and yes, there are cases where it can become quite complicated and/or become intractable due to variable explosion... but it is not necessarily so.

(I cannot suggest a book, sorry, but if you want to contact me in email we can go over your problem in general terms and see if I can provide some general advice, maybe?)
I started using freebsd two weeks ago. My usual ruby stack carried over just fine and so far it's kinda fun. The stack being sinatra, thin, nginx, postgresql. I assume any other sane backend stack will carry over just as easily.