skysight-inc/HackerNews huggingface dataset:
I was sort of hoping the 'toothbrush test' would involve the robot being able to clean your teeth...

Years ago my father worked in robotics. The product was a very simple robot that took a piece out of a die-casting machine and placed it on a conveyor belt. There was nothing to program of any complexity, this arm had a fixed trapezium with different length sides that performed all the required motion, some sines/cosines/tangents involved to get the fixed path right. Most of the bits for the robot came from the R+S components catalogue, so usual industrial control gear, all 'tried and tested' with warranty, not 'home made'.

However, did it go well? The robot only had to do one job right but it rarely did. It probably only ever was one robot, customers were not exactly two-a-penny for this machine, even though it was in theory a very good machine. It would require on-site attention every week and some weekends. There was no fundamental design flaw, the heat had been considered, but it was a constant war of attrition on the reliability front. I would have to ask how that ended, all I know is that it was doomed, just not an economically viable adventure. Yet this was the simplest of robots for the simplest of tasks, solving a known problem that seemed to make sense to solve.

The main business survived the venture into robotics (sold to the same customers) but a loss had to be accounted for, people were laid of and the industrial unit vacated. A lot of hard work was put into it and the whole company was behind it. But it failed, reliability and support just could not be done economically.

So what are robot arms to be for outside of manufacturing, where Google wants to be with their customers?

If Google did get into the sales of these robot arms and 'learn along the way' there really is a risk that support for customers, 'beta customers', might be as all-consuming as it was for my father with his very simple robot. Then there are no resources to actually develop or iterate the product. You need to have the original creators debugging and fixing the robots in the field and there is a high likelihood that this work would take 10x the amount of available resources making actual development nigh on impossible. Much better to take the long route and get the product right before bringing it to market and avoid the trap.

Building robots is okay if that is your core business or if you have some massive factory that needs them. Here the cost benefit analysis can be done, things tested and deployed complete with a team of engineers to keep everything running. If selling adverts is your main business then maybe not.
Because it's getting exponentially and disproportionately more complicated to just make what ought to be a pretty simple e-store. At this rate I'll soon need to know how to do advanced calculus just to figure out how to make an interface that supports both mobile and desktop.
I'm all for Unicode support but definitely do not want emojies invading my terminal. It's bad enough that I have to endure them on my phone.

My terminal is an emotional clean room of sorts. There's no allowance for the emotional nuance afforded by the emojie. Only three emotional states are allowed. State 0: Deadpan zero emotion. State 1: White hot anger. State 2: Pure elation.
When we get the iPhone of robots, we're going to see a huge societal change.
One of the worst ones is those malicious "your computer has been infected" ads, that web browsers allow to disable to close tab buttons with message box windows and such. Users get frustrated, and give up and call the phone number, pay the $250, etc.

It's very hard for me to convince people that:

A. More than likely anything you do before you call me, is going to make it worse.

B. You can always just shut off your PC.
very interesting read. We looked at github issues mgt tools a while ago and settled on huboard. We didn't find codetree during our search for tools... so it's definitely a challenge to reach developers. Fine posts like this can do the trick ;-)

Codetree looks great! Good luck!
Why was he selling the website? (That would be my first question in evaluating it)
> How is this worth it for Google?

Text is more easily consumed by Google services (Search, Now, etc.) than, e.g., graphical representations, and information is more likely to be stored in text if there are fonts that support presenting the information people want to communicate. Having a font family covering all world languages (and covering the full gamut of Unicode characters) increases the scope of information that can be effectively communicated via text.
Dev jobs: A microservices architecture journey
So.. what Parent is meant in the title?
Compare countries according to Geert Hofstede's 6D model
Unfortunately a lot of private sector "Environmental engineering" jobs are about getting projects through/around the regulations.
The same mistakes will be made. The state of software development will never be perfect until the bots take over. In the meantime it's sanest to stay reality-based and just deal with what we have. Complaining is mostly blowing off steam or showing off (as the author says, arrogance).
I think they talked about this some time ago and that they were (slowly) moving away from new CRTs all the time.
It does rather boggle the mind how staunchly they refuse to get the basics down. Recent initiatives are misplaced. It's like they're building a bicycle that has heated hand-grips, an espresso machine and a stereo system, but no seat. And then mr. visionary there, instead of noticing the failures in delivery of the core experience, instead starts asking "are we limiting our users' transportation options by making them be on a 2-wheeled self-propelled device?" In other words, hey let's reconsider the ONE THING WE'RE ACTUALLY ABOUT... the Tweet. I mean if you want to kill off the company there are easier ways.
It's been a building problem with a clear trajectory for a long time, but typically people are only getting the message long after there's something meaningful they could have done.
You can see Yosemite Valley this summer: http://i.imgur.com/FSmwv6g.jpg

It looks quite beautiful, with the fall foliage, leaves changing color.....then you realize those are evergreens and are changing color because they are dead.
You should read the links I shared with you to further your understanding of the situation. There are not a fixed number of jobs to go around. Otherwise, how do you explain that from 1900 to present, both our population, number of jobs, and GDP have grown quite a bit?
If you find CSS hard to grasp you should seriously consider actually learning it instead of randomly writing words in the hope that things will stick.

Over here, CSS class is given on the same level as the Programming 101 classes. The class you give to new students because it's easy.
Working class white men make less than they did in 1996
In other words, it is useful to people who are doing it wrong.
> For instance :scope. CSS4Rocks says supported in all browsers but IE. caniuse.com says its only supported in FF and mentions it has been removed from the current specification.

I can't find :scope on caniuse.com? There's Scoped CSS there, but that's a largely unrelated (and, as you say, abandoned) HTML feature.
I think that you are looking to the GPL from the wrong perspective. I also made this mistake.

GPL does not force you to licence your application under GPL.

Instead licensing your application under GPL allows you to use other GPL licensed code.
It might not be if you were working with the native toolkit on Mac or Windows, but for a cross platform application it's probably easier than something like Qt (and is already known by many developers).
Did you guys look at Waffle? My buddies made that with a few interns a while back.
worrying about != building political will for the significant changes needed
When I see the nested <div> tags in modern web pages, mainly to support CSS, I really wonder, what was wrong with tables again?
Sciter is definitely an option.

http://sciter.com/
No slashed-zero (or even center dotted) in the monospace version.

smh
I'll admit I'm way out of my depth here! But wouldn't the fact the planets experience orbital decay that ultimately cause them to be pulled into the star they are orbiting, mean that heliocentric is "more correct" when discussing a planet's relation to a star?
Very good read!

But, in fairness this isn't a failure of the S905 SOC. It is a bug in the second stage bootloader that fails to authenticate the next image.

The SoC BootROM validates the RSA signature of the second stage bootloader.
https://m.signalvnoise.com/press-release-basecamp-valuation-...
Update to Twitter outbound IP configuration (may affect Cards)
> Abstract interpretation as formulated by Cousot consisting of ...

Abstract interpretation is the general theory of Galois connections on program representations be they syntactic or abstract Kripke structures. Any sound abstraction (i.e. reduction) of the state space -- syntactic or semantic -- that preserves logical properties for the sake of verification is basically abstract interpretation. Widening/narrowing are just techniques to create sound reductions through fixpoints; I don't think they're essential to the concept of abstract interpretation (Cousot calls model checking, type systems and deductive proofs special cases of abstract interpretation).

> You can't quote Hilbert to claim that ZFC is the accepted foundation of mathematics and then quote Goedel to say that this doesn't work.

I didn't "claim" that ZFC is the accepted foundation. It is the normally assumed foundation so I picked it, but the choice is irrelevant.

> Most startups in SV are better funded and staffed than pretty much every formal verification project.

And need to build far bigger things.

> this is apparently a constant factor.

I would be extremely careful saying that. It is a constant factor when extreme care is taken to keep algorithms "braindead simple" (as someone who'd worked on seL4 once called it) and when the program size is kept to somewhere between tiny and small.

> but I'm positive that we can meet your deadline of "before the heat death of the universe".

Yes, obviously. The problem with all formal methods, though, is that the deadline isn't the end of the universe, but something that is considered affordable. My personal issue with manual deduction in general (I have more particular concerns with some PLT approaches) is that the approach is less amenable to approximate verification. In other words, making full-program end-to-end verification cheaper would not affect most software as it would still be too high a price (at least for the foreseeable future) to pay for something most software doesn't need. A bigger impact would be to reduce the cost of gaining the currently (or somewhat better) attainable level of confidence.
There has been an Eternal September in systems administration.

The sysadmin niche has recently been flooded with young people coming from development backgrounds (which, today, the cutting edge is dominated by languages like JS and Go and Python), and they are approaching systems administration from a software development point of view -- attempting to abstract away the systems themselves, set up repeatable and testable environments, that sort of thing.

There's a lot of it that's not bad, but as always happens in these situations, they're ignoring the advice and experience of everyone that's kept the lights blinking for several decades now, and those older folks are finding it impossible to keep up with the flood of new people.

If anything kills this project one day, it'll be that it's no longer considered "okay" to connect to an individual server over ssh at all; you're supposed to use an IDE-like interface in a web browser, that connects to a service written in Node, that uses an API to download crowd-sourced pre-written web server configurations from a paid service, that then spins up a new VM using an API from another service, that then installs a daemon written in Go, that then installs the new web server configuration, and then all of your data gets migrated over to the new server and the old one gets decommissioned. If you actually ever touch a server or, gods forbid, edit your own Apache or nginx configuration files, you're a fool and an old-timer and you should retire.

(Inspired by an actual comment I saw on HN not too long ago.)
I remember in the late 80s/early 90s it seemed like all the environmental stuff was about the ozone hole and acid rain. By the late 90s it seemed to be all about preserving the rainforest to the exclusion of almost anything else—incidentally, did we... win that one? Or hopelessly lose it so everyone gave up? It seems like the chatter there has dropped to almost nothing, though for a while it was the environmental issue.

Global warming per se didn't get center stage until later. I don't remember hearing much about it back in the days of soda-by-the-pitcher and Made in America signs on racks at Wal-Mart (gave up on that one pretty fast, haha).
Its a .zip...
I do not see this issue with default filter lists.
It's disingenuous to describe FISA as "expiring next year", without mentioning that Congress is very likely to immediately reauthorize it in some form.

(https://en.wikipedia.org/wiki/Foreign_Intelligence_Surveilla...)
Snap, Inc
Out of memory allocating 2147483664 bytes after a total of 270336 bytes
One of my highest voted comments on HN was a fairly inane complaint about systemd; it's very hated on HN.
Kitura – A high performance and simple to use web framework
This argument works in general, and as much as it annoyed me as a user, I accepted for Google and Facebook changes in the past.

The problem with Applying it to Twitter is that they have never been as big or universal as people assume they are. The median number of tweets from an account is one, active in-stream users lagged freaking Google+ for years, etc. Their shoddy, unintuitive product is practically designed to be power-user heavy, and the network has been so since the beginning. Having a user base thick with big influencers like journalists, celebs, and politicians is a blessing, but Twitter couldn't understand that and blindly followed Facebook's playbook, despite being a hugely different company.
Lessons Learned from Presenting My Thesis Proposal
I think the answer is precisely the realization that heliocentrism is a convenient framework for specifying the correct relationships. If one formulated their geocentrism-with-epicycles model to be precisely equivalent to heliocentrism in all physically observable details, just with Earth as the origin to their coordinate system, and acknowledged this equivalence, then that would be perfectly correct as well, albeit unduly cumbersomely framed. But the useful thing is that insight, that what happens is equivalent to the clean heliocentric model, whatever coordinates you might prefer to think of it in terms of.
Interesting, the site is now redirecting to apple.com. I hope someone didn't get in trouble for this.

Btw, did anyone take a screenshot of the page?
It's also about 1000 times larger ;)
It's not really strange, if you map maslows heirarchy to a corresponding job (either the outputs or the individual worker satisfaction) then it makes sense to make these moral/honorable distinctions.

The world's Basic needs are realized through industry and agriculture

The worlds Psychological and Self Fulfillment needs are further up and are realized through services.
How to ask users for permission to use Location Services?
> I see nothing wrong in using same public key to log in from a particular machine to a number of remote machines.

There is nothing really wrong with it; it's a good way to reduce the burden of managing secrets. The downside though is when multiple remote machines need to be contacted because a private key was revoked. Then again, a common need for revocation is a compromise of the machine on which the private key(s) is stored, which can often mean a number of private keys need to be revoked. I think the ideal is still to have unique key pairs for each client-server combination.
I think you're right. One looks like an attribute (caniuse.com), cssrocks is :scoped, a pseudo.
From Shippo's homepage:

"Shyp uses Shippo to automatically get rates from multiple carriers, and create shipping labels at the lowest prices.

Shyp accepts orders from their app, and sends shipment information directly to their fulfillment center to be processed, same-day. Weight, dimensions, and other information about the item are then sent to the Shippo API and a shipping label is generated.

Shippo helps power Shyp by providing them with a way to automatically generate discounted shipping labels."
This was covered.
There is a theory in economics that while resources may be limited, through substitution economic growth is limitless. If growth in an economy is limitless, the economic value of a company is potentially infinite.

http://freakonomics.com/2014/01/24/can-economic-growth-conti...

I'm not saying this is right or wrong, just trying to explain the thought.
Lennart Poettering's response to this was interesting:

> The bug is caused by an error check that filters out garbage sent to PID 1. The check works correctly, except that the resulting action is a too harsh: instead of complaining and dropping it will abort the process.

* https://www.reddit.com/r/linux/comments/54yfcd/how_to_crash_...

In fact, the opposite was the case. The root of the problem was identified in the GitHub bug report:

* https://github.com/systemd/systemd/issues/4234#issuecomment-...

* hhttps://github.com/systemd/systemd/commit/d875aa8ce10b458dc2...

What happened was that Lennart Poettering removed an error check that filtered out zero-length messages. This left the flow of control to fall through to a later point where an assertion, that had been earlier added by Lennart Poettering with the assumption that this check for zero was in place (as it had been at the time), then triggered.

Of course, no-one that I have seen has yet asked why "" as a command-line argument to systemd-notify results in a zero-length message in the first place. After all, according to the doco that would be length 1, a single terminating LF byte, not zero length. That said, the server still should be proof against zero-length network input.
Snap, Inc. is the new parent company of Snapchat
In particular, note that if you were doing this experiment more than a month ago, there was no threading support (except on master); there has been support for distributed computing from the first release. In the new 0.5 release there is support for multithreading, but it's still (as Viral said), experimental.
Next-gen APM finds root causes–not describes the symptoms
Bigfoot spotted lurking under bald eagle nest
We had to stop using this font as it didn't support back tick(`). Try typing ` multiple times in the search box.

We had reported this to Google some months back but got no response.
A Map of Wireless Passwords from Airports Around the World (Updated Regularly)
> They are now, but the uninformed reader can't assume that that's static throughout history.

Scientific ideas are not discussed freely. They are driven by funding, which is disproportionally awarded to novel results. Non-novel results or failures to reproduce are overly ignored and under-funded.
The ozone hole is closing, so that's a win, but also a bit of shuffling deck chairs.
It's not a criticism of the qualities of Rust. It's just an assessment of the current state of affairs. Maybe Rust will gain the mindshare in 3 years. We'll see. I personally think having something better than C but as ubiquitous and supported as C would be awesome. Is it Rust? We'll see in 5 years.
Pentagon paid PR firm $540M to make fake terrorist videos
I think you're overthinking it. Making simple games isn't hard. Just sit down one day and write a clone of Tetris in 24 hours, adding some twists of your own if you want. If you do that, you'll be a million steps ahead of anyone who thinks, "I should make a game someday." You'll have learned more than any book or tutorial can teach you, not just about technical matters, but about your own abilities. Or just join a 48 hour game jam and make some small thing with some friends.

After making some small things like that, you'll see how easy it is to just jump into some cool idea you've been thinking about. If you don't do this, and instead just plan out some big multi-person hobby project, there is literally 0% chance it will ever get finished, or even started. It's literally never been done before.
Geocentrism and Heliocentrism are not just calculation frameworks for making observations of the sky. They are also an attempt to create a model of the fundamental rules that govern the heavens, and then to create observable predictions based on those rules.

Heliocentrism is the better model of the two, because the paths of the planets are dominated by force of gravitational attraction to the sun. This force is what you model, regardless of your frame of reference. You can use this model to create observational predictions for any point in the solar system, but the forces that your modeling are essentially the heliocentric ones.

But to your larger point: In my grade-school science class, we were all taught that heliocentrism was itself supplanted by the discovery that the sun is rotating around the galaxy, and that modern cosmology doesn't center around anything at all. Heliocentrism is still more accurate than the geocentrism that it replaces, but is still regarded as a stepping-stone to modern theories.
1. JavaScript's ecosystem is really huge. There are lots of libraries to help you quickly get a useful product out. (The problems you will have will arrive later and will be problems caused by building a large application in JavaScript.)

2. Electron and React allow you to create desktop applications similar to how you create web applications. This make it easier to recruit engineers to work on your project. This also means you can follow modern best practices.

3. There are perceived benefits to tools that are created with web technologies in how easily they interconnect to the web. For example:

- This terminal supports displaying a website within itself.
- You get things like cascading style sheets for cheap, rather than needing
to build your own theme system.

I think it also gives a lease of life to the terminal environment. There has not been very much UX innovation there for a long while. Hyper in many ways is already much more interesting.
Ah, I thought they only renamed the original company (Snapchat, Inc.), didn't know about a new parent company.
Maybe he needs to stop managing both Square and Twitter at the same time.
I think people are more apathetic and disenfranchised than lazy, and by design rather than nature.
By the by, because it's really interesting, prohibition wasn't intended / wasn't understood to apply to beer and wine by the vast majority of supporters of the amendment. Some people leveraged white nationalism / anti-german racism, including the fact that many brewers were German, to pass the Volstead act which banned all alcohol. And by all alcohol I mean nothing like all alcohol -- there were many widely used loopholes, including getting a prescription from your doctor, buying grape juice with a warning to drink it within X days or it would ferment and become alcoholic, or even becoming jewish (10 gallons per person per year!). It really was a ban on some persons some of the time.

If you're interested, read Daniel Okrent _Last Call: The Rise and Fall of Prohibition_

https://www.amazon.com/Last-Call-Rise-Fall-Prohibition/dp/07...

Good thing the American public learned our lesson and never did anything stupid like that again.