skysight-inc/HackerNews huggingface dataset:
"it can answer questions and even recognize people"

That sounds like a perfect recipe to mess with people. One in a thousand times it will go "but Fred, you've asked me this question yesterday three times already. Is everything going alright?"
Ah, the PetStore example brings back memories! Wonder how many people remember it?
Beijing Regulator Orders Apple to Stop Sales of Two iPhone Models
I see a different problem here: Ethereum and the DAO were not in a mature state to handle this amount of money. For example, there is a limited support for upgrading contracts in Ethereum and the DAO was not reviewed enough to handle hundreds of million dollars.

Also, there are methods to make the software ultra secure using formal models.
For me the biggest problem with web apps in a browser are keyboard shortcuts. E.g.: does Cmd+P print the webpage or the contents of the edited document? Electron applications solve this problem. In the end it is important to stuff the stuff requiring performance into a native module and you are set. Having worked with JNI I prefer writing Node plugins and writing interfaces in HTML5 is great compared to stuff like Gtk (and even Qt)
This ^. I had to replace a dead battery in my truck a few weeks ago, and it's been all frigged up ever since - apparently all the engine tuning resets if power is disconnected.

I've tried to get the dealership to disable the door auto-locking (get above 5 mph, doors lock) "feature" half a dozen times, and I've given up, since they disable it in the software and it's turned back on before I leave the parking lot.

ABS brakes are awful, and down-right dangerous if you are not expecting their flaky behavior, and rather want them to perform in a predictable and consistent way. It's terrifying driving an ABS vehicle on icy roads.

Who hasn't had a largely irrelevant, but very expensive, sensor burn out and trip a buggy corner case in the engine firmware?

I realize I sound like a Luddite, but my favorite vehicle so far is still my first, which was a bare-bones, rusty 1985 F-150 with a four-speed manual and a straight six. It's still on the road, with over 300,000 miles on it, although it has become something of a truck of Theseus, aside from the frame and tranny. You can tear the whole thing down and put it back together with a pretty basic set of mechanics tools. It wasn't perfect - starters and solenoids tended to go bad, and mileage was a tad worse than the current models - but it's simple, so that when things go sideways, you patch up the one component that's broken, and trundle onward.
>its only job is to display text nicely with formatting, browsers are pretty good at

This is something that continually amazes me. Many developers seem to think that "display text on a screen" is easy, it's not.

Browsers can handle multiple fonts, multiple sizes, and crazy positioning.

Browsers can handle tons of different encodings (including stuff like UTF8 which can be a real pain to safely and correctly parse).

Browsers can display just about every single glyph on the planet without a sweat.

Browsers can handle right-to-left text right alongside left-to-right text (even switching in the same sentence!).

Browsers have a simple way to apply multiple fallback fonts (just in case your font of choice doesn't have the unicode 'HEXAGRAM FOR DIFFICULTY AT THE BEGINNING', it can fallback to a font that does).

Browser can apply simple CSS transformations to rotate text (even in 3D!) in a pretty performant way.

Browsers handle all of this, without the developer needing to spend more than 5 minutes even thinking about it, and it does so looking great.

Yeah, other UI libraries can handle most of this just fine as well, but the browser is the one platform that i've been impressed at just how well it handles typography in general. I remember how much of a fight it was to write text that went vertical to label a graph in business basic...
At my last job we were on Azure and publishing was like a two-click affair.
> but they didn't halt trading until they were asked to, so clearly it wasn't totally in their interests?

I didn't stop eating excess salt until my doctor asked me to do so - and it was totally in my interest.
The best way to quantify something like this is a "wisdom of the crowds" method: basically let everybody vote and then aggregate the results.

For this to work, however, each of the people voting have to come to independent decisions. The crowd can be as dumb as the dumbest person in the crowd if the crowd falls victim to groupthink.

What I'm trying to say is that you shouldn't let anybody tell you how to vote. Just vote for what you want to happen. Make the decision based as much as possible in complete absence of being influenced by anybody else.

If everybody does that, chances are the result will be the right result.
That's true, but for a public cloud service, you wouldn't let random people run arbitrary code based purely on inet.d or systemd socket activation.
I think PDO is the accepted way to do it but I'm not a PHP developer.
That isn't really clear at all.
> I never have any time to ... engage in creative hobbies.

Hmmm. Sounds to me like your profession, your hobby, and your passion are all aligned. I hope you know how rare and wonderful that is!
As a technical writer, I have a few quibbles with these points:

1. Dry sucks...but humorous can be worse.

In the mid-90s, I worked at a company that used a DOS add-on to fax from an accounting program. One day we were in a panic because it wasn't working properly, so we dug out the manual. It was all of 10 pages, the last of which was a list of jokes about 'How to Safe Fax' (as in safe sex).

Similarly, I've heard of a government system from the 80s that would display animated monkeys onscreen when an error occurred, and another program with the classic error message "Oopie!".

Humor has no place in documentation.

I think of technical writers like other professionals - doctors, lawyers, etc. Often, you consult a professional because you're in a crisis: you're sick, you're facing a lawsuit, or you can't get a program to work properly.

Research shows that 80% of people don't refer to documentation at all until there's a problem. So when someone's reading documentation, it's a good bet they're in a crisis.

Humor doesn't help. When a reader needs assistance or is in a crisis, humor can come across as silly or insulting.

Humor can also confuse, especially if the reader's first language isn't the same language as the documentation. And lastly, humor makes translation and internationalization harder. Some concepts don't translate across cultures.

2a. Before you start, make sure you understand your audience.

This is the key starting point for technical writers. Who is the audience for your documentation? Is it the average end-user, a developer, a system administrator, or someone else? Once you know your audience, you'll know what information they need spelled out and what they already understand. You'll also know what they'll be looking to achieve, and how you can write documentation to help them meet their goals.

5a. Use illustrations only when necessary.

Illustrations and diagrams can be costly to create, update, and translate. Don't use them when a list or table would do the job.

I would add the following two points:

8. For longer documentation, always include a revision table at the beginning of the document. This helps readers (and writers who may update your materials in the future) to understand what changes have occurred.

9. Identify external hyperlinks that do not link to URLs. For example, I would write a hyperlink to a PDF as <hyperlink> (PDF, 3.6MB). This provides the reader with a preview of what they can expect to find.
I am fascinated with prediction markets, is there an existing place to do this now with ethereum?
I don't think that is the same - There is no claim that rules of written law always gives the most favourable outcome. But rather that the written law (or contract, in this case) allows for the reality of human error or omission by leaving space for human interpretation, enforcing the underlying intent, rather than strictly enforcing 'bugs' in the contract.

After all, there are almost always small mistakes in complex systems. The system of case law is, essentially, a structured way of turning differing interpretations into a stricter framework over time.
I think what the parent is trying to say is that there's more than one way to ensure a given event occurs.

Imagine that I have a specialised piece of brain that deals with catching a ball in flight. That piece of the brain fires on the current input and makes adjustments to the position of my hand appropriately.

In the micro sense, in terms of the feedback loop involved, my brain might be predicting the path of the ball for the next tens of/hundreds of milliseconds. But there's no way to ask it "where is the ball going to be in 3 seconds time", only "what should my hand do next."

So in the macro sense, the brain isn't predicting the path of the ball, only what should be done in any given instant.

Or something like that....
Machine Learning: Hidden Markov Models in Python
It should probably at least look at word boundaries.
As far as I can tell there is a lot of future predictions with basically no real evidence both for an exit and a remain.
The main thing is you have some control over your local government and you have (almost) zero control over whatever the EU does. I think the question ins't what would happen but how far do you trust your career politicians in the UK and the rest of the EU.

Have fun with the choice, wouldn't know which one I would choose.
Serverless apps should be stateless but should work in conjunction with stateful apps. Unlike Heroku, Cloud Foundry, OpenShift, and other traditional PaaSes focused on supporting long running applications and services, serverless frameworks offer a new kind of a platform for running short lived processes and functions, also called microflows.

The distinction between the long running processes and microflows is subtle but important. When started, long running processes wait for an input, execute some code when an input is received, and then continue waiting. In contrast, microflows are started once an input is received, and are terminated by the platform after the code in the microflow finishes executing. One way to describe microflows is to say that they are reactive, in the sense that they react to the incoming data.
Google promotes Services on Google App Engine to be used in a microservice fashion. If you create a new project and click on Services, they include a link to the docs about microservices. So if we go by that, it seems to be more microservices than serverless. Based off the article, the serverless (FaaS) bit would be Google Cloud Functions.
Too much about the UK's status in the EU is subjective and opinion-based for us, or anyone else, to give you an objective answer. I'm afraid that this is an answer that's going to have to come from you.

I can only recommend the following. No one on the Remain side is going to understate the benefits of remaining in the EU, and no one on the Brexit side is going to understate the costs. They may overstate these things, but for whatever reason, overstatement is generally easier to detect. So listen to the Remain folks about the benefits, listen to the Brexit folks about the costs, dismiss the BS from both sides as appropriate, and then decide for yourself: are the benefits worth the costs? If you believe they are, vote Remain. If you believe they are not, vote Brexit.

This is not a perfect process, but the perfect process does not exist. Do the best you can with what you have, and that will have to be enough.
Public debate around this is an appeal to sentiment. The winner is whoever rouses more rhetoric.

I don't see how the crowd can help in this. My sense of the situation is that everyone is uninformed.

Richard Dawkins says "Ignoramuses should have no say on our EU membership—and that includes me"
https://richarddawkins.net/2016/06/richard-dawkins-ignoramus...
It's described as "sans adjectives" but in the demo it removes only an adverb (really) and a verb (love).
The Children's Illustrated Guide to Kubernetes
Augur and Hivemind are the two that get talked about the most. Neither are out.
Nice article, and I am going to give webpack a try. I took an eDX class in Typescript a year ago and really like the language but decided modern JavaScript was getting "good enough." I regret that decision sometimes because Tyoescript really is better IMHO.
Understanding Reactor Pattern – Thread-Based and Event-Driven
Indeed, but you have bug-safety law around the world which incorporates something like :

"If there is a typo, error, fraud, crime etc. a contract is considered invalid or the part of the contract that is flawed"

With software bugs you have something similar :

> NO WARRANTY. THE SOFTWARE IS PROVIDED TO YOU “AS IS” AND “WITH ALL FAULTS.”
I think a key to our success is that almost all the areas you describe were built before cars. Montreal was once the biggest city in Canada, then declined.

So we have a large amount of housing/commericial stock when neighbourhoods were mixed used and designed for walking.

I'm actually not sure you could build Montreal again in Montreal. (I mean, I really don't know what regulations are like for new neighbourhoods)
I expect the attacker either found a contract allowing them to short ether, or made some similar arrangement. Unless it's an attack on tech itself for personal reasons, someone's getting a lot of real money today...
I'm glad Vue.js is starting to get the exposure it deserves. I've been using it on all my projects since its very early stages, and it's by far the easiest, and most enjoyable reactive front end library that I've found. Minimal, simple syntax, that focuses only on the view/model portion is exactly what I wanted.
Just to mess with here, I would move my mug back to the group and take her mug out and place it by itself. ;)
Reimage Pc Repair 2016 Crack and License Key Download
It works really well, but it doesn't have history scrollback

That caused so many arguments between me and a former girlfriend.
As an outsider, this is stunning to me: why isn't there a contract revokation mechanism? Considering these things are programmable, it could be something as simple as a killswitch hash sitting in a lawyer's safe somewhere, right?
Pouring concrete on top of fertile land so you can grow plants in hydroponic systems is absolutely a waste of fertile land. They could poor that concrete and put those greenhouses anywhere. Put them somewhere with bad soil, and leave the good soil for growing food.
There's definitely a performance tradeoff, one which I reference a little in the latest part and will definitely talk about more when I get to drawbacks (likely in the 5th update.) There's definitely a big class of applications where FaaS with its current limitations isn't a good choice, but I wouldn't say that class is universal.

12 factor statelessness I read as meaning more application / domain state rather than infrastructure state btw.
Depends how you define attack, really.
Of course. But human contracts require human judgment and it is precisely the psychological fear/mistrust/puzzlement of proponents of machine contracts that leads to their political adoption of the idea. I don't think there's necessarily an objective risk/reward analysis behind preferring one over the other, just a matter of personal temperament.
> The story that Jesus was unmarried was probably promulgated by the Roman Catholic Church, with it's uniquely weird attachment to celibacy.

The discipline of clerical celibacy in the Latin Rite of the Roman Catholic Church (at least one non-Latin Rite Church in union with Rome existed at the time, and there are more now) was a explicitly a adopted in response to repeated scandal, not theological necessity (which is why it is a discipline of the Latin Rite and not a universal law of the Church.)

The widespread Christian acceptance of the belief that Jesus was never married long predates this.
They are not always terminated, in an effort to avoid cold boot startup times. In fact, they run much like any other service framework, where your code is behind a function lookup, and called when an appropriate request is received.

AWS Lambda in particular will spin up a new container running their framework, which will then stay alive for a period of time before being terminated.

With socket activation (using xinitd or systemd) and a minimal framework, you could implement much the same on your own VMs.
Welcome to Old Developers Club. :)
What if the attacker made their move before it could be blocked?
We all know by now CO2 and CH4 leads to a warmer planet. We also know what's driving greenhouse gas levels to rise across Earth. Contributors are deforestation, intensive animal farming, and primarily the combustion of carbon fossil fuels like coal, tar sands, oil, natural gas etc. But here is the underlying problem, despite us knowing how bad things are, (97+% of scientists who study this field agree we are causing the planet's climate to shift away from the temperate climate we thrived in) not enough is being done at present to truly solve the problem.

What really is disheartening and what no one in the media and government is talking about is how in 2015 CO2 levels rose by the largest amount in human recorded history. 3.05 PPM

http://www.esrl.noaa.gov/gmd/ccgg/trends/gr.html

We are being lied to and mislead by our governments that uniform actions are being performed to save the planet for the future of man. Vested interests in the fossil fuel industry continue to drive climate change. Yes, solar energy is starting to become incredibly efficient but not enough of it is coming online in proportion to fossil fuel burning that persists and is also installed annually. If we do not rally against it, our ability to live on this planet is at stake. The lives of our posterity are also at risk because of the burning. It will not be until we take extreme actions not on a country level but as humanity together that we will slow the burning and save ourselves.

What are these actions you might ask that will actually be effective? These can range from banning fossil fuels entirely, global carbon pricing system, banning deforestation, changing human diets, extreme uniform investment in renewable energy and potentially fourth generation nuclear reactors, more funding for developing nations to install alternative energy sources, and to shift the transportation grid towards sustainability.
Unlike traditional contracts, the idea was that smart contracts were going to eliminate the need for enforcement or dispute resolution. So that law is enshrined in code.

But this incident has set a precedent, at least within Ethereum, that the project leadership will intervene to enforce the spirit of a smart contract.

So what now are the benefits of Ethereum smart contracts over the traditional legal system?

The way I see it, at least with traditional contracts you have the benefit of a trained and experienced judge making the call in case of a serious problem.
Asus Chromebook Flip Gets Android Apps
Apple Ordered to Halt Sales of iPhone 6 in China After Patent Rule
Satellites? GPS? I think you need to look up what airborne actually means.
No, it doesn't. We already grow more than enough food to feed everyone. And our population is going to level off. There's no need for industrial nutrient production facilities, we can grow delicious food instead.
The death of apps has been greatly exaggerated
Still an outstandingly exciting adventure!
I wrote this attack up last week -- a solidity dev initially noticed this bug, but seemed to think it wasn't a big deal. http://vessenes.com/more-ethereum-attacks-race-to-empty-is-t...

The comments here are generally spot on; it's a combination of problems -- upgradability is designed to be hard because other people's money shouldn't be easy to steal, programmers are not used to making whole programs reentrant, existing documentation underplays risks, or alternately just tells people to do the wrong thing.

A better language would help, better documentation would help, better standards about how to write the programs would also help.

And, of course, more eyes are helpful. I'm an outsider to Ethereum, and got a very polite response, overall the community has been great. That said, there just aren't enough people looking at these contracts right now.
Vast majority however means most mining pools. In practice that's not that many people making the decision.
> whoever exploited the vulnerability now has a "safe" source of income in a few weeks.

Well, that would be safe (in the sense that you got money according to the contracts in the ETH network), but the problem is that the developers are trying to take this money away from the exploiter! I.e. they're trying to undo whatever action was enforced by a cristalized contract everybody agreed upon!
A system not vulnerable to such simple attacks?
Hahaha! Let me go refill my popcorn!
You can find some links to those systems here

https://news.ycombinator.com/item?id=11856479
Time Warner Cable Suspends Broadband Upgrades After Merger
Rotary engine advantage in torque? This is nonsense.

The Wankel's design limits the eccentricity of the crank shaft which consequently limits torque to relatively low levels compared to a contemporary piston engine of similar fuel consumption. There is no torque advantage to a Wankel, it's at a disadvantage.
Race to Empty: TheDAO exploit published last week
That's far from ubiquitous. And while speeds may be high, data transfer costs are also still quite high. Most people have a monthly cap. Halving (made up number) the data consumption of FaceTime has a very positive effect on that.

Also, battery usage difference should be small as video codecs are usually implemented in hardware on phones. I would expect the radio and screen to make up for the majority of power usage, not CPU/GPU.
Catchup is a fun game, but prototyping it would not be difficult, for the kind of person that plays games like Havannah at Little Golem. Cat Herders is similar.

I suspect that people who play lots of different abstract games have a lot of prototype components on hand—stuff like different size square and hex boards, generic abstract pieces. Hex is a classic of the genre, and yet has gone long periods without affordable commercial sets being widely available—it's easy to build. Slither is a game you play with a Go set. Catchup you would just need a printed Hex board and some glass gems.
Number 5 had treads and a parachute. Mobility was definitely not a problem for him.
Aka: "Another probabilistic programming paper." They hacked on a 3D physics engine to make it capable of Monte Carlo sampling and inference, and then stuck a deep neural net on the front to do some parameter inference more easily.
Why do everyone mixes a decentralized system with a self-controlled system? Decentralization doesn't mean there is no power to regulate or no coordination between users/agents, it is just a model of architecture for a system where power belongs to local entities. That absolutely doesn't mean that there aren't rules and bodies to defend them [1].
[1] https://www.intgovforum.org/cms/wks2015/uploads/proposal_bac...
> The species responsible for this has no natural enemies against which we compete and will therefore continue unabated until all resources have been consumed and the system collapses.

This isn't remotely true. There are tons of bacteria and viruses which are parasitic towards us. We compete against them.

Nevermind the fact that the greatest competition always comes from your own species. The greatest check on human expansion and prosperity is humanity. We kill, maim, and restrict each other on grand scales.

There is also no historical evidence that a single species has ever been responsible for a mass extinction, so I find it odd that you're assuming we'll be the first when there is a historical record that spans billions of years. That's just arrogance.