skysight-inc/HackerNews huggingface dataset:
This is really great to see the emphasis on static vs dynamic parts in templates. Polymer, Glimmer, and some other template systems make the distinction between static and dynamic content, but React and most other vdom libraries don't.

I was looking for options for HTML templating in JS found that JS template literals very naturally separate static and dynamic sections between the literals and expressions. I've been testing a library based on them [1], and for real-world templates with large static sections, it's indeed faster than traditional vdom.

[1]: https://github.com/PolymerLabs/lit-html
http://keepachangelog.com/en/1.0.0/
It’s possible the kidnapper looked your name up on Facebook after stealing your iPad. Just searching for someone’s name is enough for a recommendation.

This has happened with some of my coworkers who I have no mutual friends with and live in a completely different city (didn’t connect to work internet or have GPS permissions on FB either).
I don't think there is a path to break even for storage alone, today. The real earnings seem to be in the transfer rates, but traffic is too low to ever consider it as anything other than an experiment. I heard Storj was going to prioritize farmers by latency and bandwidth; now that I've been reading about the turmoil, I'm not confident it will happen anytime soon.

My payout last month was ~$5 and I was in the top 30 by payout, if I remember correctly, but I had only received a couple of TB of data. This month has been much better, so maybe ~$100 but mostly because of data transfer. I've seen peak bandwidth of over 400Mbps in and out (800Mbps combined).

Interestingly, a number of the top earners have been trying to game the system by uploading a small amount of data until the shard ends up on their node and then doing the massive transfer to generate more Storj than the cost of the transit.
Energy consumption is in no way related to transaction volume. Whether there are thousands of txs per block or only one the energy used will be the same.
Not quite, even when the cap is reached, new blocks will still need to be created for new transactions, which will require proof-of-work to achieve consensus, and thus energy expenditure.
Just wondering: If you got so rich from crypto currency that you could retire, would you retire? Start your own company? Just do fun stuff? Or keep working?

I myself work, to occupy myself with interesting problems, so I would keep doing this, regardless of my wealth.
Good thing "nobody" buys Tesla's for racing...
that seems like a very useful way to frame it. Is there a source that goes into more details on this?
If it's so easy, please describe how.
Worries me that the request is made with http and the screen cap has some items blacked out.
A Pardon for Arpaio Would Put the Country in Uncharted Territory
"I'm not sure if you are asking how to transition into working in aerospace?"

Thanks for responding. Yes that's my question. I assume that domain knowledge in embedded systems, as well as aerospace science are minimum requirements?
Mining always needs to happen. Once it stops producing coins, the cost burden just moves over to the people using the currency. The mining cost only decreases if the proof-of-work difficulty decreases.

If mining becomes less profitable, fewer people will mine and the proof-of-work will tune to be less difficult, but the cost never disappears and there's still a huge amount of energy wasted in the selection process for adding blocks. If too few people mine the currency will be totally destabilized.
"Validators" is the more generic for term what are also called miners or stakers.
> something is wrong and needs to be fixed

It's already fixed with PoS... IMO the winner of the cryptocurrency-race will be a PoS-based coin.
NOx from diesel vehicles is by far the most significant source of ground-level ozone in most European cities.

https://en.wikipedia.org/wiki/Tropospheric_ozone#Formation
Yes, there is a level at which it doesn't make sense any more. In a sufficiently efficient market, that is the point we are at, at any given point in time.

I believe the bitcoin mining market is efficient enough already that we're more or less there.
Presumably large changes in throttle input (such as lifting off considerably as the mapping expected Alonso to do through the Pouhon corner) - as opposed to small variations in input which the driver would use to keep the car stable and under traction.
I feel like a lot of things, at least in ruby world where I mostly work, have gotten a _lot_ better in the past few years.

"Strictly"? Well, backwards compat mistakes can happen, but mistakes can always happen. Other than that, it's the difficulty of knowing what is the "public API". It's a time-consuming and difficult task to be clear about this. But I think semver has spurred people to try harder and get closer.
The energy expended is the security of the currency.

If a transaction is confirmed by 1 TWh of proof of work, that much energy is required to alter it, meanwhile the bitcoin network has expended even more energy.

It is still young, and the exponential growth in energy consumption is going to stop as an equilibrium is reached.
In spite of the lawsuits, Google is actually a big contributor to the OpenJDK and a common presence at Java Languages Summit.

As for Kotlin, it remains to be seen how much uptake it will actually take.

Despite all attempts from Apple to push Swift, many keep on using Objective-C.
“Send Parsons Immediately”
I mean, I understand why, it's because often you want to relate it to cost, and electricity is priced in $/KWh, not in ($/sec)/watt.
Thanks for asking. It's one posting back on my blog from the link at the top of this HN thread. ;-)

https://blog.kamens.us/2017/08/24/backing-up-from-unix-to-ba...
Title came from https://thebrowser.com/share-link/87jB.
If as a user, these types of things anger you, please just stop using the product.

These practices will continue to get worse as long as users put up with it.
My favorite quote:

At one point, a young church member, a mountain of a man who just a few weeks ago preached against the theory of evolution — “I ain’t come from no monkey,” he said — reaches for the jar of strychnine. He takes a sip.
I'd say a better title for this article/graph would be "How would electric cars affect CO2 output in European countries?" or something along that line.

There's far more to a specific car being a good idea considering the differences between EVs and ICEVs (but of course the needs vary inside countries as well). However, an electric car is much less attractive in a land of long distances where you often need to keep the batteries pre-heated to provide even reasonable range (and even keep your warranty!) – even if the country's electricity production is not dominated by fossil fuels.
Here in Bavaria, every single wild boar shot still has to be checked for radioactivity, quite a few have to be destroyed for too high radiation values. Equally, it is recommended not to eat too many mushrooms from the forest. All of this due to the Chernobyl accident more than 30 years ago.
It reduces overall emissions by a lot, and saves thousands of lives even beyond that.

Dismissing any solution that doesn't 100% fix everything is a great way to never accomplish anything.
Mobile Money Transfers Could Help in Fight Against Hunger and Poverty
The hashing is merely a way to choose a random block. It's not a proof and it doesn't do anything fancy. It just picks a random computer to say "this is how the transaction history looks".

The energy increases with the volume of transactions because there will be more people calculating hashes. The more people mining, the harder they make the hash calculation so that the target is ten minutes. More transactions = more people mining because there is more demand to verify blocks.
In fact, in the white paper it's just described as the decentralized time stamp server and that's its entire purpose. The term "blockchain" and all the hype about its magic powers came later.
That's not so bad. The typical mode of failure for fibre lines is not flooding or tornadoes or landslides or anything else that would affect both sides of the road at the same time. It's someone digging up the road, which is unlikely to happen on both sides simultaneously.
Simplifying Vue.js development
This should work in Plasma app launchers. (If not, file a bug.)

A .desktop file (which, among other things, registers apps with these launchers) has a GenericName field for precisely this purpose. For example,

Name=Firefox
GenericName=Web browser

A possible source of error might be that the application developer did not enter a GenericName (or one that is not helpful, like "KDE clone of $gnome_app").
A JIRA Wiki.

Could be better
I think the problem is that the batteries can't handle sustained power drain without overheating, so accelerating hard for too long will put the car into a mode where it won't do so anymore for a while.
That's correct. In normal conditions, the vast majority of tire particles are very large and stick to the road where they are eventually washed away by rain. Not small enough to hang in the air and end up in our lungs.

Aerosolized tire particulates are mostly a problem in tunnels, where they keep getting thrown up into the air by passing vehicles and recirculating.
A literal comparison to paper bills isn't quite right. A small sheet of linen/cotton paper could represent $1, $100, or hundreds of millions of dollars (eg., a stock certificate of a million shares of Apple stock).

You have to compare Bitcoin to the concept of money, like U.S. dollars, but not literally the paper. A comparison to bars of gold is OK however since that is money and not a representation.
If you look at the seriousness the human race dedicated to creating safe nuclear energy, it looks almost comical:we settled on the first technology we found(pressured water reactors), because it fitted best for the requirents of the Navy at the time, not because it offered the best safety for citizens, far from it.And than, in the name of safety, we created an environment that prevented from new designs to become commercialized.

Why wasn't it safe ? Because that type of reactors creates a lot of high pressure radioactive gassses , and in the case of an accident, those gases spread far.

But we now have reactors types that (a) can't physically blow up , their temperature is limited, and (b) contain very little to no radioactive gasses , so even in the worst case scenario, we'll be just left with an enclosed pool of radioactive material, which is safe.

So please don't judge nuclear by it's past.
I don't know about GitHub or GitLab, but in my entire professional career, I think my total downtime due to failures in locally hosted Git repos is zero. Likewise I don't recall ever having a problem due to locally hosted bug trackers or code review systems. This stuff isn't hard, and we've been able to do it reliably for a very long time.

What certainly has wasted a horrible amount of my time in recent years is working around build systems and package managers that are so badly designed that not only do they have a dependency on some online repository in the first instance, they also make it difficult or impossible to download and cache those dependencies in a supported way so that you can have 100% reproducible builds with nothing but locally hosted resources. Surely this is just about the most basic requirement for a robust software development process?
> But if it turns out that we'll need an active (as in "needs manpower") care-taking of this waste for several thousands of years

We don't. Dig a shaft half a mile deep in bedrock in a tectonically stable area, and anything you put there will be safe for the next million years.

But that's kind of expensive, so we keep dumping the shit in the ocean or in shallow graves in the backyard.
Then you might as well stop using your smartphone and all 3rd party apps on it.

The vast majority contain SDKs which tattle your whereabouts, contacts and other interesting tidbits to advertising networks.
PoS deserves research but it's far from shown itself to be viable as the dominate consensus mechanism.
That brings you to the mess that is mobile app launchers.

The problem is not whether the cue is visual or textual, the problem is that were cannot all agree on how to categorise thousands of apps in a way that is useful to all of us.
Recent convert to Dark Sky. Highly recommend it. One of those increasingly rare instances where you can pay upfront for quality software.
That's a rather impenetrable, buzzword-laden way of saying exactly the same thing as the grandparent post: everything moves through spacetime at c, which is a velocity expressed as a 4-vector of constant length. Increase one component and the others have to decrease to maintain the length.

Put all your velocity into the time component and you can't move in space. Conversely, if you put all of your velocity into the spatial components, you will freeze in time like a photon.
Wealthy enough to really never work again? Yes, I'd absolutely "retire." I'd still "work", in the sense that, say, angel investors work, or people own real estate; I'd also still write software in my free time.

But for the most part, no I wouldn't continue doing what I do now because I'd stop consulting and I would never again be an individual contributor. I'd probably devote "professional focus" to investing and academic research in math and cryptography while traveling all over the world like Tom from Myspace.

I think in conversations like this the dimension people like myself are talking about is freedom. I'd still work on what I'm passionate about even if I was wealthy, I would just cease doing it in a way that I don't have total control and direction over my work. That circles back to my original point - my passion for my work is not nearly enough of an incentive for me to do it if I'm not doing it with total autonomy.
I hope we're not building hydro power plants for the sole purpose of supporting the Bitcoin network. The energy may be "clean", but these projects have their own impact on the surrounding ecosystem.
the article includes some interesting insights but doesnt develop on them IMO.

Women seem to own the social kingdom well men own the financial/corporate/professional one generally. Just as in the workforce women can be passed over with equal qualifications for a job, men of equal "attractiveness" have a much more difficult time getting sex. Obviously, industry and society vary but i think this is the same issue: societal roles.

Feminism in its new age way seems to demand equality in the workforce, inequality here IMO stems from historical roles. I think woman have as much trouble breaking into top roles as men do on getting an attractive date on tinder.

I see these roles changing and the anecdotal evidence suggests this but we will see.
That's a real problem, but it's still orders of magnitude less harmful than coal.

(Also, as a Kentuckian I'm curious what "the equivalent of Kentucky" is.) :)
Yes, though one has to go through quite a bit of trouble to actually show that. The big problem is, that speed of light is defined with reference to a background geometry and gravitational waves are a distortion of this background geometry. (And this has of course not be shown yet, however this observation, if the rumors are true, would be evidence for that.)
> It might even be more important than a static type system, at least for some apps. But you can have both.

The important thing is not at which stage in the compilation pipeline the bug became obvious, it's at how many seconds elapsed it became obvious.

I generally found that working in untyped js with a workflow prioritising fast iteration was much better for finding bugs quickly than working in Scala with its advanced type system and miserably slow iterations.

But as you say, it's possible to have both.
I beg to differ :) About the finesse, I mean. I posted a link, and it brought massive traffic and subscriptions to my blog — no finesse was needed. Then I asked my colleague to post another link. My fault is I did not warn him about the community rules regarding titles. But I wrote the admins and fixed it as soon as I became aware of this. In the meantime I found a way to give back to the community. And you're shooting me down for it?
The point is expend work to create signatures, creating a crytoeconomic cost to state changes.
A couple of points worth highlighting:

1. The Lamborghini can sustain this level of performance whereas the Tesla can't. So even if the Tesla can beat the Lamborghini within this particular set of constraints, it won't beat the Lamborghini in any sustained racing environment.

2. The Lamborghini Aventador SV weighs roughly 3,800 lbs, whereas the Tesla Model X weighs roughly 5,300 lbs. Really impressive for such a heavy car to beat a much lighter car even in a drag race.

3. There's a conversation to be had here about the practical value of acceleration over ability to reach top speeds and sustain them - especially on normal roads and in daily life. One can argue that rapid acceleration and a top speed of 90 is far more valuable/useful than slower acceleration and a top speed of 200.
There's primecoin, which uses a proof of work based on finding a special kind of prime number, which (they claim) has use in the outside world, at least the academic one.

https://en.wikipedia.org/wiki/Primecoin

Generally, to have a useful PoW, it needs to meet some criteria:

1) Easily verifiable

2) Necessary work on the problem is easily quantifiable and estimable

3) Problem can be programmatically generated from random data.

One model might be NP-complete problems. Users feed in problem instances they want solved, with a bounty. You find out how many guesses it should take. A valid proof of work then requires solving enough such problems, combined, to exceed the difficulty threshold. (You'd also need to solve one based on the current known transaction history.)

The problem there is that it's hard to know if a given NP complete problem instance is "one of the hard ones" and to find such instances.
Wait wait wait isn't Storj what Pied Piper ultimately turned into, plus a cryptocurrency for extra hype?

Life imitating fiction imitating life...
I don't know why you're stretching so hard to make it seem like moving pollution away from population centers isn't an excellent benefit and likely to reduce in many fewer deaths from direct exposure to pollution.

The comment above was referring to local pollution in cities (which directly kills thousands through diseases related to particulates in that pollution). Relocating that pollution does solve that problem.

(PH)EVs also produce much less particulate pollution from brake dust due to the use of regen to brake (which is why they can go several times the normal replacement interval for brake pads).

The creation of pollution is a separate problem from the location of that pollution. Yes, EVs don't magically prevent the creation of pollution, but they can severely limit the creation of pollution in population centers, where they have the most immediate effect.
Swift seems to have both those qualities, if I'm interpreting you correctly.
I don't know how to say it without you taking it as a personal attack, but I think it's important to say so you can take the opportunity and learn or at least think about it;
If you say things like that I quoted, you are incompetent and you have to learn a lot. I feel I have to say this because you send the wrong message to a wider audience which I really hate.

Also I skimmed your library httplib2 and it's at least terrible to read.

Again, you can take this as a personal attack, flag this comment also, be mad or whatever, or buy Clean Code and start reading, also start learning more about Python idioms from people who are really good at it, e.g. Raymond Hettinger, Armin Ronacher
The problem with POS is that you do not have a mathematical guarantee of immutability. It costs nothing to try to stake on different blocks, and every counter-measure relies on the fact that the network is not partitioned.

This would be fatal in case of a remote crash vulnerability, because an attacker could partition the network at will.

Or a nation/state could cut internet access.

Without real world energy, you lose byzantine fault tolerance.
Best of luck to you.
Too many menus. Too many applications.

Applications:

Web Browser

Email

Text Editor

Terminal

User:

Switch User

Log out

Restart

Shutdown
And even then there is lightning induced fire. Plenty of natural fires start that way and there is no reason why your building can't be the starting point of one. Though fortunately most DCs take lightning protection quite serious and are probably amongst the harder buildings to ignite.
Bitcoin miners would also use electricity at low peak times, unless the cost of hardware dominates the cost of electricity. In practice the mining operations seem to be concentrated near hydro plants in China, where there is an oversupply of carbon neutral electric power.
This might be a good time to share what is (in my opinion) the absolute best weather app for iOS: Hello Weather. It's minimal, functional, and beautifully designed.
T7 is quite a bit larger than lit-html, and requires a vdom reconciler still. lit-html is self-contained and < 2k minified and gzipped.

I also didn't want to use vdom because it doesn't encode whether nodes are static or dynamic, and even static sections are diffed. That's extremely important feature for performance and memory overhead, which is why I'm happy to see that emphasized in Moon.

Also, coming from the Polymer team, where we've had a lot of success using <template> elements to stamp out large pre-defined DOM trees, I wanted a system backed by those.
There used to be, but it was removed after customers found out about it and complained. Now you get a warning and big disclaimer, but it isn't limited.

Source (and plenty others if you google): http://insideevs.com/tesla-remove-launch-power-restrictions/
Oh, I totally agree with you there. In all honesty, "my game" is TSR's MSH FASERIP. But I wasn't talking about the system, the mechanics, etc - I commenting on the fact that in the article linked, the author calls V:tM a LARP, and while he wants to make it sound hopeful, my grognard alarms were going off about the way he said it.

Will he always look down on games that are not D&D? Does he now, a decade later? I honestly don't know. But I do feel that his research here is lacking; and the question I'm forced to ask is, if he couldn't research what the WW games actually were (or if he did, couldn't represent that in black-and-white), what else did he miss?
But we also have empirical evidence that they generalize incredible poorly, namely the existence of imperceptible (adversarial) perturbations which can transfer across images and networks and are catastrophically misclassified.
Yeah, that's inaccurate. The major portion of that energy expenditure is keeping the bitcoins that aren't moving secure.

Put another way, this is saying it is estimated to take about $800M it keep $40B of bitcoin secure.

This is probably a bit expensive in terms of comparing to fiat currencies (But then we are probably not covering all the real costs of those currencies)... but bitcoin is still in the technology adoption life-cycle and has not yet become a currency.

When the inflation of BTC has declined and it has become fully adopted (assuming this happens) then the numbers will likely start to make a lot more sense.

Also, the vast majority of transactions in about 2 years will likely be happening off chain using lightening network and the like.

Those transaction fees will happily be covered by merchants who are currently paying %2-%5 per transaction to Visa et. al. and will be more than happy to pay %1 or less to Bitcoin to manage a lightening channel.

Really, it will be companies disrupting Visa building payment networks out of lightening channels and they will have to keep fees really low because LN is open source and anyone can compete with them.
That's incredibly sobering.
With $30M shouldn't they have dozens of people polishing their product?