skysight-inc/HackerNews huggingface dataset:
Honestly I hope not, we have polymer notes in Canada and they tear horribly. I have lost bills just pulling them out of my wallet, most tellers will not take them unless you mend them first.

U.S. bills are excellent, and I would encourage them to continue printing them as-is.
However the Performance to power Ratio of amd just Sucks. If you don't care that amd needs more energy than you are fine
As a Google Inbox user, I've found its reminder features to be very good for these kinds of day-to-day tasks.
Agreed. As someone in the interview process once again, and being a bit more introspective this time, it's just really amazing how BS the entire whiteboard/share-scree "code this out for me" is. It seems to be a better indicator of how many of type X problems you've seen before, and employers seem to care more about if you know how to do something cold vs work through a problem to an adequate solution.
The buggy-whip analogy is interesting and applicable from a certain viewpoint ("big core" thinking in a low-power market) but I'm not sure it fully works: mobile chips are fundamentally converging toward desktop chips microarchitecturally (big out-of-order engines and wider pipelines, larger cache hierarchies, higher clock speeds, the move to 64-bit, etc), and Intel's desktop/server parts are also converging toward mobile in many ways (very power-efficient, more on-chip SoC-like integration).

In other words, they're different markets, but I'm not sure that they're so different that Intel's existing expertise couldn't allow them to build a kickass part if they played cards right. They still employ some of the world's best microarchitects and design engineers. My feeling here is that this is more of a business/execution issue than a fundamental big-incumbent-doesn't-get-it failure.
It's good for a basic flow but you write scripts to do everything... like due dates (notifications) and recurring events. Also, no mobile use -- Dropbox sync gives you viewing but no creation. It's a great idea for simplicity, but it just breaks down quickly.

I use FoldingText / TaskPaper with everything in one simple markdown file.
I might be one of those users. Could you explain what these long-term implications are?
The Imitation Game was bad?
Canada also uses polymer notes now
> incorrect usage of an API that cannot be prevented with static typing, but this does NOT include validating the user's input

This is the part I have the most contention with. Take parsing JSON for example: there are many situations in which you pretty much know that the input being invalid is truly exceptional (reading a local file generated by some part of the code, for example). There are others however where its not exceptional at all (reading incoming input from a user). So its up to the API consumer, not the producer to decide whether a situation is "truly exceptional" or not. Exceptions recognise this, and let the errors propagate through the layers so that each layer can decide whether the error is exceptional from their point of view.
Percentages mean almost nothing sometimes. I was running my own business for a while and making many hundreds of thousands - and spending $30,000 in a day didn't mean anything to me. So paying 20% vs 30% vs 50% wouldn't have made any difference in my daily life.
Aside from the binary logs, which are really not a great idea, systemd adds orders of magnitude more complexity to a system that really didn't need it. The init system could have been addressed without something like systemd. I'm old enough to remember and use Unix. Like a lot of IT guys my age, we all tend to think that adding complexity is wrong. This notion of one ring to rule them all mentality is really starting to take effect in IT. Unix-like operating systems are supposed to be non-complex. My example above, of OpenBSD, is true. Maintaining OpenBSD systems is trivial compared to similar Linux systems, and I maintain both. Sadly, I admin a series of CentOS PBX servers that are an absolute pain. A friend runs his on FreeBSD and has less than half the pain points I do. And we're running the same PBX software.

I believe in lowest common denominator everytime. Binary anything is bad when alternatives exist. Linux has given itself over to binary blobs in the name of being more attractive to corporate users. Device drivers under Linux are now almost all binary blobs. You will not see this in OpenBSD, for example. The BSD folk reverse engineer the drivers and write their own free drivers -- and they are usually far and away better afterwards.

Take the wireless chipset drivers for Ralink. The BSD guys took a 30,000 line driver and rewrote the entire thing in less than 1/3 of the code. That's just the whole attitude between Linux and BSD. Linux is a series of cobbled-together hacks on top of an ever-growing, ever-complex kernel (that really needs legacy crap removed). BSD, on the other hand, is engineered as a single OS with a small collection of pruned base programs. Big difference. If you've ever used BSD, you will know the joy of /etc/rc.conf vs the nightmare of Linux config files that live in myriad locations depending on the distro.
Loans secured using his shares in the company. He can shift the realization of the capital gains to far, far in the future -- see strategy #1: http://www.bloomberg.com/news/articles/2012-04-17/how-to-pay...
And, to be honest, teachers again. "Here's a curriculum (specs), make a series of lessons (product)".
It's typical middle-class status quo defending logic. Plantation owners paid more taxes than slaves, and lords paid more taxes than serfs. Lazy slaves.
So the poor person who needs to get to the doctor should take the slow lane, and the rich person who wants to get to the next bar faster should take the fast lane? Public utilities INTENTIONALLY are not and should not be run according to the principles of profit maximization.
Try to imagine where we would be today if Bell Labs and/or MIT had fired him for his eccentricities, "trivial" distractions and prolonged absences. Imagine if he hadn't been present when Bardeen & Brattain(and subsequently Shockley) produced the modern transistor and took off on one of his tangential side projects. Just "wow".

edit: giving Bardeen & Brattain their due.
A documentary I saw said that the polymer is really special and hard to produce, so probably the method is patented.
I'm afraid you still haven't answered my question. Aside from binary logs, what binary blobs are you referring to in systemd?
> Doing that you also kill accessibility

?! What web frameworks kill accessibility, exactly?
Unless you automate commits, using git is quite a bit of process overhead when you're just adding one item to your inbox or checking one item done.
You get social security back.
This is just depressing. How was this not tested? This is complete sign reversal of a control output; you'd think it would show up immediately.
Silicon Valley's most secretive startup is scooping up Palo Alto offices
That's my impression too, and I've always been impressed at the longevity of US banknotes. Unless they actually start to rot, or are torn apart, they are shockingly tough.
It seems like the core error was in the inertial measurement unit: it would be a common cause between the reaction wheel failures and the failure of the despin burn.
In my eyes mozilla's stance on security is patronizing towards power-users because it assumes that every addon and every non-root application on the system is potentially hostile.

Thus the goal is to prevent free interaction between processes or between addons and native in general (unix philosophy anyone?). Everyone has to suffer just to protect those who click on "yes, install" whenever prompted.

The result are less powerful APIs in the name of security.

Just look at addon signing. Mozilla refuses to add an off switch to that (and thus user control) because they fear that some other processes already running on the user's computer might inject unsigned addons. In my eyes this is a crazy kind of threat model that basically writes off the user's system security as a lost cause and tries to defend FF against that lost cause. It's elevating mozilla's needs over interoperability between applications.

Imagine if awk refused to run unless the parent process is bash, signed by canonical, because they deemed some other shell's argument expansion as potentially confusing to the user or something like that. Crazy, right?
This is the real point. I have my issues with systemd.

For example, I just had an interesting discussion on GH with Varnish packers about changing a daemon arg (in that case, the bind address/port).

The way systemd "recommends" to change the arguments passed to a daemon is to write a drop-in file (i.e. /etc/systemd/system/service-name.service.d/something.conf) that overwrites the ExecStart line. To do so, you have to do:

[Service]
ExecStart=
ExecStart=<original ExecStart line with wanted changes>

For Varnish, this isn't the end of the world - it only needs a few arguments - but it's still a lot less simple than the pre-systemd "standard" for Debian, which is to use a /etc/defaults/<service> file to allow changing daemon args via variables. This method can be still used (via either EnvironmentFile, or via built-in systemd "Environment=" statements) but the former is specifically mentioned as "not recommended" by Lennart, and the use of Environment= in service files seems very much like a feature that no one is keen to acknowledge or make use of, and it has it's own issues, as the way variables, white space, escaping etc are handled is specific to systemd and not immediately intuitive for someone used to a shell environment.

But as you said - those issues, are not enough to give up on the benefits of Debian stable. In theory, all packages in Debian stable that need an init script are supposed to still supply a sysvinit script (I was actually quite surprised by how many packages rely on systemd's ability to load sysvinit scripts and don't ship their own systemd service file) so you could choose to use sysvinit instead of systemd, for now at least.

I do appreciate the theoretical goal - you describe how your daemon should be started, and let pid1 handle the specifics of actually starting it - to me that makes it much easier for a lot more people to create reliable daemon packages.

I just wish the project wasn't taking such a "everything plus the kitchen sink" approach.
> Plastic money will have a really hard time being pushed to US conservatives.

> They will treat it like an invasion of their liberty, like some sort of socialist/libertarian push with some sort of a secret agenda.

What the heck are you talking about? That makes absolutely no sense and I would need to see some sources of that. I'm a conservative and anything that cheapens the cost of currency is good. Heck, I know a lot of conservatives that wouldn't mind getting rid of the $1 and $5 bills for coins since it would save money over the long term.
I certainly would like to read an article on "This is your brain on stories" that would highlights and explores escapism, role of story-telling, etc. That would make a nice book as well.

I recently got into listening to podcasts. I noticed that I really don't like the "get together to discuss a topic" kind or the "here's a 2 minutes segment from the radio news" but really do enjoy one-hour long political, history and documentary podcasts.
Install WordPress – The geek way
Slavery / undervalued labor is an interesting twist, as I imagine it would factor heavily into the value calculations.

The "more work (but still net positive food production)" vs "storage / transport" calculus seems like it would be interesting as different variables are changed. (Side note: I am not oblivious to the social evil we're talking about, but it is historically relevant)
Darnit, I was hoping the polymer notes would have a much longer life. Is the Canadian notes the same types as the Australian or New Zealand ones?
Logo designs with a clever concept
It's not like he doesn't consider it software, just that he's OK with not being Free. That said, small details at the edges hardly invalidate a philosophy.
Meh. Systemd is pretty great. The *Nix purists hate it, but it solves a lot of problems and does it fairly consistently. I love using it in Fedora now where journald has basically replaced syslog completely.
One potential issue is that data prices in the EU differ quite a lot between countries. For example, I have an Austrian drei.at prepaid card where I pay around 10 EUR per month for 10 GB of data (I have to recharge the card at least once a year so that it doesn't expire). In some other European countries the price for one GB of data is more like 10 EUR instead of 1 EUR.

So one of the use-cases for perpetual roaming is to buy "cheap" SIM cards from another country and to then use them in your (more expensive) home country, which would lead to an asymmetric roaming behavior between the two providers (so one of those providers would have to pay the other one).
CV of failures: Princeton professor publishes résumé of his career lows
The core of systemd revolves around units, but the "systemd ecosystem" has expanded to logging (journalctl), bus management, a new way to set the hostname (hostnamectl), a login manager, fstab parsing and disk management, a new session/login management framework, networking (systemd-netword, or is it netctl now, or do people use NetworkManager? I'm on Arch and ended up choosing netctl but I still don't understand all the tradeoffs), and I'm probably missing something.

Don't get me wrong -- I actually like some of the new thinking, appreciate parallelized bootups, and think service units are cleaner than the old /etc/rc.d mudball. I'd rather have things Just Work(tm) than play with wpa_supplicant and hibernate configurations on my laptop. But it's been a lot of new stuff to learn for someone used to the Old Ways, and it's kind of astonishing how fast systemd pieces have taken over different domains.
Definitely free to dispute! It's just my personal view. I get this view because I have never come across any situation throughout history where wealth did not work this way.

If you sell fish, and do really well at selling fish, you'll acquire wealth. That wealth will let you build bigger boats than someone without wealth. Same seems to apply to everything. Even little apps on the app store. If you make a successful app, you get a large following of users. This will give you a springboard of users when launching your next app, and having all those users on your old app gives you valuable data on how to build the next one.

Do you see where I'm coming from about the nature of wealth?
>Shifting to CS, how do you even know a specific algorithm/data structure might help with your problem if you don't have a rough idea of its specifics?

In general, these things are well implemented in either the base language or a library, and thus both easily searchable and well covered in practical examples. It's unusual for 9-to-5 non-R&D developers to be solving a problem which hasn't been solved before at the algorithm level, the job usually revolves around connecting pre-made components together and specializing them. As such, you really only need a loose knowledge of the fact that things like binary trees exist. Being able to hand-write one isn't useful and may be a liability depending on the temperament of the developer.

Your hand-rolled implementation is unlikely to perform better by any metric than the pre-made one, and it'll probably be less platform independent and more buggy simply because it's newer and looked at by fewer people.

In 95% of all software development today, rolling your own version of any off-the-shelf algorithm is a mugs game and actively bad practice because it places the foundations for technical debt. You really don't want to be hiring people who roll their own just because they can.

Now, if you're going to be working in the R&D or experimental areas of software development, kind of where the Oculus driver crew are at the moment (as an example), then sure, you definitely need to know the inner details of these things.

The problem is that we're interviewing everyone as if they're going to be writing high-performance drivers, when most of them are never going to work at that level and wouldn't want to.
To finance this, a bank will want to see they've managed to hedge their business and are in the business of capturing those spreads rather than speculating on the widening of that spread (only to have it contract). Interestingly, this may be exceedingly hard to do on the open market and may require setting up an expensive structured product with the trading group of some bank, where they pay you a fixed price each day and take on the daily/monthly (and particularly in power markets, term) risk. That won't be cheap, especially if these aren't located to one of the major grid nodes where there are liquid markets available.

Basically, I'm just wondering how hedging costs affect your numbers.
You could say the same about the A-10.
It again seems like you didn't read the article.

> [i]Tim Urban points out that the typical advice for procrastinators — essentially, to stop what they’re doing and get down to work, is ridiculous, because procrastination isn’t something that extreme procrastinators feel as though they can control.

> “While we’re here, let’s make sure obese people avoid overeating, depressed people avoid apathy, and someone please tell beached whales that they should avoid being out of the ocean,” Urban writes.[/i]

That's a direct quote from the article.

The research supports judgement-free internal thought life. Not support systems. AA isn't a solid comparison but it's close. But apples to oranges doesn't help when the problem is apples. Let's stay focused on what the research says.

Also, I'd consider myself a hardcore procrastinator. My issue could be a symptom of ADHD or something else but I fall in the 'hardcore' category. And it's something that I still struggle with but 'sucking it up' or 'just stop procrastinating with social support' won't change my situation, something deeper needs to occur, which is why I mention the beliefs. Our beliefs affect our behavior.
The F-16 as well as the F15 and AC130.

the F35 is a trillion dollar paperwieght that should be scraped, I would be more in favor of ending that trillion dollar gift to Lockheed by way of the corrupt military than ending the A10 program

//For the record, I fucking hate the F35, it is by far the worst aircraft ever produced by the US Military
The Secrets of Buying
It really isn't. The A10 is basically a flying tank meant to be hit and survive. The Iraqi army of desert storm was a "modern enemy" with pretty decent soviet gear at the time. US gear was just that much better due to us spending such an obnoxious amount of our GDP on our military. A manpad doesn't have remotely explosive power of the AA that hit the A10 in this video, don't believe me? See the pictures yourself:

https://www.youtube.com/watch?v=o7JM82fa5ZY

There are literally dozens and dozens of similar stories. The A10 is simply put the most effective CAS tool the US Military has or ever had. CAS is a very important part of US warfare and just because they might be against an enemy with better anti-air doesn't negate the need for boots on the ground, which require CAS for maximum survivability. Most likely the Stealth B2s or RQ-170 Sentinel would be sent in first to quickly take out as much of the AAA as possible.

Disclaimer: I'm a veteran of Operation Iraqi Freedom II, and flew the Shadow 200 TUAV. I targeted several times for A10s and have heard the BRRRRRRRRRRTTTTTT up close.
Even in the Bay Area, I think this track would be an extreme exception rather than the rule. And the Bay area itself is somewhat of an exception. Vast majority of programmers in this country live outside the Bay Area. Another consideration is that 150K in the Bay Area hardly goes as far as 150K in other locations.
CSS code driven artworks
Where Snowden goes back in time and reveals American military and intelligence secrets to preempt its transformation into a global surveillance and military superpower?
systemd is itself a series of something like 70-odd binaries. Why? Why not keep it text-based? It works for others.
Inspiration is everywere.
And I am a server user of Debian and happy with systemd. Finally an init system that can reliably detect failing daemons and that allows me to set restarting policies.
I'm not sure how it works; does that insurance still cover you after the event? And if you have made a stupid mistake(not defending or even giving a view about Fred here) you are personally liable, aren't you?
It was better than "Enigma" certainly but it still wasn't as high fidelity as it could have been.
The genius featured in almost all the CS textbooks who never won a Turing Award. I don't even know exactly where that ranks on my list of reasons for strongly disliking the ACM, but it's on there.
> So she lasted like 4 years before the company failed?

Took 4 years for the company to fail, you mean?
Also, Google Keep has reminders note that integrates with Android timer.
Sysvinit scripts were shit. But as the AVGN might say, systemd took that shit sandwich and served it up with a side of buffalo vomit. It doesn't solve the "rat's nest of dependencies" problem, it makes it worse. Because now you have more moving parts which hard-depend on each other in various intricate ways and introduce unreliability into a formerly reliable startup process, combining the worst aspects of monolithic software with the worst aspects of modular software. Because development of components of systemd takes place in a bubble, there's not much room for feedback -- like is this a sane way to do system logging, network discovery, process group management, etc. That's easy to integrate with other pieces of software from the community? The systemd way to solve the integration issues is "pressure the major distros to adopt systemd. Then they'll HAVE to integrate with us!"

It's possible to run sysvinit sanely, by having a few startup scripts that source in the appropriate boilerplate. Slackware's startup for instance has always been manageable.