skysight-inc/HackerNews huggingface dataset:
Xen offers a couple of ways to load and start a kernel and you'd want to start a kernel in long or protected mode. Ideally, you also use the hypervisors virtual device interfaces instead of scanning for emulated devices. I don't know if the sane startup protocol is final but here are some pieces of documentation: http://xenbits.xen.org/docs/4.7-testing/misc/hvmlite.html http://xenbits.xen.org/docs/4.7-testing/misc/pvh.html

The nice thing about ring-0 is that on modern hardware with SR-IOV, a VM can be associated with devices and the multiplexing that had to be done within a kernel or hypervisor can now be done in hardware.
> 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.

This is really too bad. The best outcome would be for the community to learn from this and build tools and practices that make new contracts significantly more reliable.

Smart contract design practices will have to undergo the same kind of gradual hardening that web servers have over the past 20 years. Let's hope it happens a bit quicker.
Similar previous discussion: https://news.ycombinator.com/item?id=11292280

And from my comment in that thread:

After having written a fairly popular 400+ page book, and dozens of documentation sets in Markdown (and having worked on a few in other languages), I have to say—Markdown is _good enough_.

It will take an order-of-magnitude difference to unseat Markdown as the 'simple plain text formatting syntax' default, IMO. But use what makes you productive and is most conducive to writing effortlessly!
Nope.

The original claim is that Netflix runs more like a professional sports team in terms of demanding performance. The argument against was that they don't pay like one.

My argument is that they pay somewhere between a minor and major league team, both of which have a "perform or get out" mentality.
> The terms of The DAO Creation are set forth in the smart contract code existing on the Ethereum blockchain at 0xbb9bc244d798123fde783fcc1c72d3bb8c189413. Nothing in this explanation of terms or in any other document or communication may modify or add any additional obligations or guarantees beyond those set forth in The DAO’s code.

Nice. So if the community ultimately succeeds in preventing the "attacker" from withdrawing his funds, which he acquired in perfect accordance with the DAO code, which is the entirety of the agreement, could he publicly bring suit for violation of contract?
Solving infra-structure problems by reeducating Producers and Consumers, are we?

Should send all those content-devs to labourcamps, one year for every full mb! ;)
So I guess its more about learning to play the interview game than anything else?
Why would investing in renewable energy and next-generation nuclear power result in substantial negative impacts to humanity?
Columbia Student: The Damage Done by ‘Mattress Girl’
Thanks for taking a look. :)
Merkel and state leaders to support the fight against Adblocker
Talk to a typical owner of an old house, and you'll likely hear something about how they love its quirks. But would they build a house the same way today? Some probably would, but others would certainly not. This actually probably applies well outside of old homes too. I suspect something akin to the endowment effect (https://en.wikipedia.org/wiki/Endowment_effect) plays in here.

It also makes sense to me that someone would appreciate a historical landmark but place a lesser value on a modern replica of that landmark. Similarly, I could imagine a person admiring a historical neighborhood more than a modern recreation of it.

> Let's drill down and focus in particular on laws about multi-family dwellings. What logic would make them good when they already exist, but bad if you wanted to build more, and even bad if you wanted rebuild them after a natural disaster?

I'm not sure the answer needs to be logical (see above), but even if it must be, I don't know why placing limits on something implies that it was never actually good in the first place. Natural disasters are another story for sure, but I would imagine that sort of massive rebuilding was not the primary motivation for the present zoning laws in Somerville.
Formal verification is the right approach. Do you know of any specifics for this goal that exist for ETH now?
This is great. Keep it up! I don't mind the copy/pasting at all (I'd rather have the video progress than watch someone type something out). Looking forward to future shows (and 30 Rock references).
They said a researcher forgot to close a gate.
I want to be sure I understand your central objection to these books. I take it that your objection isn't that trying to succeed is bad. You also probably wouldn't say that the particular advice in these books is bad, though that's an interesting discussion if you do. I'm also guessing you don't have an objection to old books in general, or to business advice in general. Is your objection that these books give advice for preventing and resolving competitive situations, and you believe it's better to not compete in business than to compete and win? This is an opinion I've encountered in places like Metafilter. (Seen you there!)
Appimages, Snaps, XDG-Apps^WFlatpaks – Developer Persepctive
Effectively the same thing considering the fact that a perfect rectangle would be impossible to make.
If the new company is adding value to your credentials and also has room to grow, then maybe its work taking the offer.

But if it's the same job, with only a few more dollars in your pocket, I would evaluate the situation a little more. As they say 'the grass is always greener on the other side', you don't want to trade 1 set of issues for another.

You've only been around for 9 months, In my book you're still 'the new guy', so I personally don't see much room for negotiation.

Don't wait for shit to change where you are at though, it wont.
Don't forget asciidoc; Markdown-like but much more powerful.

http://asciidoc.org
Structuring React and Redux Applications
Interesting. I'll have to do a bit more research on this.
The Parasite Underground
Speaking as an American, not eating meat, buying (currently) much more expensive cars, and not being able to afford to fly are huge quality of life impacts.
Downloading Missy Elliott – Teary Eyed Mp3 Song
https://archive.is/wmqqR has it without paywall
To clarify, for the Cyrillic impaired, like myself: the last sentence is basically: "yak yak yak", right?
You're right; I somehow assumed BAML would contain CIL, but instead it's as you said.
Not hard to believe, but would it be possible to provide an example or two of Apple winning a patent claim in court via a ruling in China? I would find it hard to believe the for a valid claim that just because a company is Chinese that it would have any impact on a case in the America.
Iran: Software Engineer Salaries
Hungarian Notation is not, and was never, for representing the type of a variable. It's about usage of that variable. "c" represents a change, "w" means width, "x" means horizontal position, "ix" is an index into an array. All of them are `int`s, but "cw" "cx" "ix" and "x" are all different kinds of variables.

http://www.joelonsoftware.com/articles/Wrong.html
Horsehit - mass opinion obviously matters a lot more on this subject, since there is no way to enforce our arbitrary kowtowing to Paul Graham's wisdom. What is he going to do, yell at us for down voting incorrectly?

This is our website. Maybe pg 'made' it, but we use it. If most of us disagree that is what will (and should in my opinion) happen.
I still use Babel with TypeScript.

This gives me the benefit of TS (specifically, typing), on my preferred development machine (Windows, where FB Flow is really crappy), while getting language-level polyfills (like generators) from Babel.

A nice side effect of having TS "compile" to ES6 modules is that Babel's nice-module-loading is used, which means I can just "import _ from 'lodash'" and never have to mess around with "* as" and the endless manipulation of .d.ts files.

That said, there are still things missing. In particular, object spread support, which is so nice when using Redux.

I've thought about maybe doing a Babel precompile, followed by TS for typing, then a Babel "real compile", but that's probably just crazy.
I can never understand why dumping pollution into the atmosphere and making other people bear the costs is categorized under "capitalism" and "free market," while making people actually pay for the costs they impose on others through pollution is considered "redistribution" and "communism."

When somebody burns coal as part of their business and pollutes my air, they are basically imposing a tax on me to subsidize their business. That's not capitalism or economic freedom, that's socialism for business.
Completely true, until you need a feature that the less powerful format does not support. Then you are back at the beginning, regretting spending all that time learning something that won't fill your needs.

ReStructuredText is not hard. Yes, unusual features are hard to memorize, but a quick google search beats it being impossible every time.
Former Apple engineers launch SnapRoute, an open-source networking startup
Data Science for Social Good with DataCamp and DrivenData
>> consider how tedious it is to open a new bank account

You make it sound like a person needs to open a separate bank account for every transaction, which is clearly not how people manage their finances.

I'm in the same eli5 boat. I can't fathom why anybody would put real cash into such a system. It comes across as "because I'm rich as fuck and can gamble away my money on a stupid tech system that is not realistically viable". Just... why would anyone use this? It makes no sense, unless this just offers a way to attempt to hide one's identity while participating in illegal ventures.

I know a lot of tech nerds. Not one of them would ever join a system like this. I just don't get who is voluntarily subjecting themselves to this insanity. Can someone out there who has actually used Ethereum explain why they've done so? I would really appreciate some kind of insight into this whole concept, as I just don't understand.
> No-one can write bug-free code

Perhaps, but nobody can write a bug-free legal contract either, and no legal system is without bugs.

Sadly, for the legal system, many of the bugs are due to corruption, so they are actually more akin to systematic exploits being done again and again by malicious actors (who often happen to be wealthy or powerful).

Also, in terms of how drastic this bug is, suppose $5M gets stolen over a few days. If the community can strengthen itself and become resilient to a whole class of attacks, that is likely far superior to a meatspace improvement in contract law, which would likely take years to become law (and would be selectively enforced once it did).
Not old, but seasoned with salt (white hair). :D
Nations that conduct deterrence patrols on SSBNs have built up many decades of experience in terms of sealing up individuals for months at a time, operating in an unforgiving environment and being self reliant for that period. There's a surprisingly large pool of information potentially available to learn from.
Ask HN: What do you think about steemit.com?
I know very little about the blockchain and ethereum and all that, and I would love to hear an opinion about steemit from people who understand this stuff better than I do.
I agree with your points. But the miners who actually have a say, if I am not mistaken, are the big ones and the pool owners. These are just a small fraction of all people running mining software.

A soft fork will undeniably require distributed consensus. It is the number of people with the actual right to vote that may be worrisome.

Perhaps the pool owners should extend their voting rights to their pool contributors, pooling votes as they pool mining shares.

(Disclaimer: I hold a small amount of ETH and participate in a mining pool.)
ain't nobody got time for that...
Spotted this earlier on Techcrunch - https://techcrunch.com/2016/06/16/beamery-raises-2-million-t...
Thanks for the feedback. Seems like a happy medium would be to copy and paste from an editor that is on screen.
Markdown also supports non-hash mark headers, similar to RST, but it is a bit tougher to deal with its h1 -> h6 progression than RST. The RST rules are clearer and standardized, whereas Markdown's are not and especially vary between engine implementations. One more area where CommonMark standardization may help some time in the future, but doesn't quite impact today.
> The suggestions you mentioned all have substantial negative impacts to humanity - arguably as much as climate change itself

I think that assertion deserves to be examined a bit more closely.

We are already effectively subsidizing the fossil fuel industry to the tune of 5+ trillion USD per year [1]. This is a figure from the IMF that includes direct monetary subsidies as well as externalities like public health, environmental damage, etc.

So the question now becomes this: would switching to renewables cost more than that? If we started dumping that same amount of money into renewables and corresponding infrastructure, how quickly could we switch away from fossil fuels? If we do some impromptu calculations based on current cost of solar panels, batteries, etc., it seems like it might take maybe 20 years.

Obviously it's not that simple in practice, but I think this demonstrates that humanity could theoretically switch away from fossil fuels without enduring any severe hardships. This isn't a problem of the technology not being good enough[2], or renewables being too expensive: it's just a political/organizational problem.

[1] http://www.imf.org/external/pubs/cat/longres.aspx?sk=42940.0
[2] With the possible exception of jet planes, for which batteries aren't good enough to provide a compelling alternative yet. But I would guess that when the electric car market really starts to take off, battery tech will start improving a lot faster.
My choice is Markdeep: https://casual-effects.com/markdeep/
The Present State of Container Orchestration
If you're taking shingles, chances are you don't have a true flat roof (or just a terribly built one), since those are supposed to continuous roofing in order to withstand water puddles. Back in the day the only material available was asphalt tar, which obviously isn't very fireproof. Modern alternatives such as EPDM and TPO though are plenty fireproof, especially if placed on top of polyisocyanurate insulation (which doesn't burn, only char) instead of directly on the wood deck.
Imageflow, a 17x faster ImageMagic alternative and more secure
Edge cases of jsonb queries and best practices.
Really not that true; meaning yes, China copies a lot, but so does everyone and being able to copy someone takes skill. Look no further that the American auto industry for a historical example of this.
WTF. There is the equivalent of millions of dollars in this blockchain? How?! Who willingly puts real cash up front for this kind of thing? Just... what?!
> It wasn't the best thing in the world but you could actually setup reply videos which made conversations possible.

I had completely forgotten about that system. I really enjoyed video replies. Not only did they foster discussion, it was a great way to learn, discover music, and the replies allowed a great collaborative humor to develop as well. I seem to remember that they were starting to become very spammy about the time they disappeared though.

>That was the best part of YT at least for vloggers even if they didn't like each other

I remember reading a scientific paper a while back that suggested social networks grew much better when they had [likes/eprops/upvotes/etc] than they did without, but allowing negative feedback (beyond comments) stifled growth. We naturally try to surround ourselves with like-minded individuals as well. Our natural tendencies coupled with incentive social networks have to censor information that we disagree with means we all live in bubbles where our ideas are rarely challenged.

The YouTube reply system made viewing content from the "other side" really easy. I'm pretty sure I watched more vlogs from people I disagree in a single month before that feature was taken away than I have in the entire time since, especially with the new changes to the "recommended videos". Which is a shame. It makes it much easier to demonize the other side.

As a side note, someone on Reddit made a snide joke about the Demosthenes/Locke story arc in Ender's Game and how unrealistic it was; the point being nobody gives a shit about two bloggers having a fight. That story arc might actually make sense on YouTube, given how much better we empathize with people in a video than we do with people who are hidden behind the written word.
Slower cars kill you slowly. Dropping the speed from 40 MPH to 20 MPH means it takes twice as many milliseconds to grind you against a planter, mailbox, bus, parked car, etc.
> I get all that but I still am unsure of what you mean.

Direct database access would be like exposing ODBC from the DB directly to a web application. You either have to trust that the application doesn't do a "drop table ..." or hope that the DB has fine-grained enough access controls to prevent that.

Whereas in a SOA design, the API endpoint runs your code that gates access to the DB.
Yes, which makes the title more ridiculous. The same thing will happen to a roomba if you leave it running on an open space. I can see the headline now: "Evil vacuum cleaner robot creates havoc on city streets."
By this definition, we've been running "serverless" on Google App Engine for most of a decade.

* We don't monitor how many instances are running and don't really care. Our "functions" are http endpoints. GAE spins up or down instances to meet the load. Our interface with "instances" is just the size of the bill at the end of the month.

* Async task processing is also just an http endpoint function. We even have a little bit of syntactic sugar so it looks like we're just adding functions to a queue.

* We have no ops or devops staff. We just deploy code that implements functions (http endpoints).

* Persistence is also scaled by Google; there's no database server, just an API to read/write data that scales infinitely (or at least, scales with linearly our bill, not limited by the dataset).

It sounds to me like the article is trying to distinguish between "serverless" and PaaS by describing PaaS done poorly. For the longest time, GAE didn't even expose the # of instances servicing your app. They've exposed a lot more of the underlying constructs since, but you can still ignore them unless you're trying to hyperoptimize your bill.
> Consider a business that needs to reason about the probability of a law passing, severity of global warming, or any number of other difficult to predict events

Like the probability of a smart contract being exploited via a loophole? ;)
Even more ridiculous: The final pay check, in full, is required to be paid on the day of severance. (at least in california)

This include earned vacation.
I don't know why you're getting downvoted, seems like a very prudent and informed sentiment to me.
> The press release was issued, I think, sort of as if it
> came from some sort of independent or cross-vendor project,
> and there’s the snapcraft.io site to back up that impression,
> but every Snappy committer is a Canonical employee

That's a pretty old trick. Google pulled exactly the same with Open Handset Alliance few years ago.
Birth control doesn't help when people want to have lots of children. Having lots of children is an essential survival strategy in a poor country. If you want them to have fewer children, make them wealthier.
Pffft, dial up days are over. Thank you for using large images, looks great on high-dpi.
When working in an entity, use whatever the team is using obviously.

Otherwise, if you haven't learned any of those two and are wondering which one you should pick, it's cool, because

> You especially don't want to spend very much time learning the intricacies of a new markup format, unless you absolutely have to.

is moot anyway. Starting to write in RST is not more complicated than starting with MD. No need to learn the minute details to write basic documents. You will have plenty of time afterward to refine the thing once you're accustomed to it and feel the need to produce more advanced outputs.
We're in agreement there, I'd prefer a USB link to a proprietary automaker module interface buried in the dash. The bigger problem is to me is that auto makers don't want to make a simple elegant peripheral interface as much as they want to own more of the value in the vehicle - which leads to more complex modules and are likely to put more effort into a more easily outdated interface.
I must add Asciidoctor. Which is mostly compatible with Asciidoc, but even more powerful.

I have spent a lot of time trying to make Asciidoc create beautiful PDFs for technical documentation, but Asciidoctor makes it all a lot easier to customize its own stylesheets.

The only negative thing about it is that it is hard to install since it typically isn't found in your distros package repo by default.
Many people here stating that its purpose is tainted if they can just undo what the attacker did. After all, why not just have a centralized authority after all?

I haven't researched this deeply, admittedly, but I think the idea is that they're using consensus from the community in order to undo what the attacker did. In other words, if the community didn't support it, it wouldn't be possible to do at all. Contrast this with a centralized authority that didn't need community involvement at all.
We use https://github.com/domaindrivendev/Swashbuckle to generate openapi/swagger spec.
"Our ancestors were around" is a useless thing to say. Every single extinct species had an unbroken chain of ancestors going back to the very first life forms.
I love Fogus's take on 100:10:1. As opposed to this highly linear ever-winnowing flow, Fogus uses 100:10:1 as a way to keep a list of spitballed ideas, a list of things he might want to work on that all have sincere promise, and one thing picked to focus on. Instead of being process driven, focusing on getting one thing done well, Fogus lets himself switch among his 10 picked items. The 10 is a way to swap out when interest wanes. 100:10:1, my approach to open source-
http://blog.fogus.me/2015/11/04/the-100101-method-my-approac...

This process speaks to me a ton (a whole lot more than Nick's rigorous phased development process). When my attention and care for an interesting, creative project wanes, I can either dig in my heels and try to make myself code, or preferably I can switch to some other promising piece of development. Having a deck of other ideas decreases the context switch time- when a project is in a lul, there's already other great gems prepped, and one of them can re-inspire me.

Quite the contrast. I wonder how much of it is due to Fogus's focus on developing open source software, versus Nick' focus working on physical board games.
I find typescript pays off with the excellent intellisense and refactoring in editor support. They did a great job of having the language service and compiler use same core code base.
That depends on whether you think of a contract as an interface or as an implementation.

A contract should present an interface that includes a declaration of its behavior. The declared behavior should be well defined, and if a bug in the implementation is discovered, the contract should be updatable to fix the bug. There could even be futures expressing the probability that a contract will be found to have a bug.

The willingness of participants to use a contract would depend on the chances that something about the interface is bug-prone, untested, etc.

As long as bugs do not result in reversal of money flow, the incentives seem to align properly toward a well-defined approach for declarative contracts.