skysight-inc/HackerNews huggingface dataset:
There's justifiable, moderate concern for cobalt supply as a bottleneck when it comes to ramping up EV battery production with current popular lithium ion battery chemistries. "Every turbine and every panel also requires key metals" is a claim that's either false or trivial (perhaps they've defined "key metals" as "metals used to make wind turbines and solar panels.")

It's hard to have a sensible discussion about material supply constraints for renewable energy, EVs, and electronics because it's a lot easier to affirm a baseless panic than to reject it. Some years ago I saw a forum comment like "China has a rare earth monopoly and there's not enough neodymium for everyone in the world to have an iPod." One sentence of concentrated nonsense. It takes multiple paragraphs of carefully cited evidence to demonstrate why that's nonsense. You have to estimate mass of magnets in the device, carefully show your work to justify the estimate as reasonable, further break down magnet composition to find neodymium demand per device, link to citations for crustal abundance of neodymium, link to evidence of non-Chinese neodymium resources, link to evidence of historical mining outside China, show how much the bill-of-materials cost for raw neodymium can rise before it adds $5 to the iPod cost... If you skip any steps, there's a gap left for the "skeptic" to dodge your counter-argument and keep believing whatever they believed before.

Here's a non-exhaustive list of materials that I've seen asserted as being both in short supply and critical for the expansion of renewable energy:

- Neodymium

- Dysprosium

- "Rare earth metals," generically

- Indium

- Gallium

- Tellurium

- Lithium

Of those, I'd say that only dysprosium is even close. Adding a small amount of dysprosium to neodymium magnets permits the magnets to endure higher temperatures, which makes them better suited for high-power applications like permanent magnet generators in wind turbines. But PM generators are just a "nice to have" -- most wind turbines use electromagnets instead. Lithium is very useful but too abundant to worry about. The others just aren't very important to renewable energy technologies in the first place. Sure, there are solar cells that rely on gallium, but over 99% of the world's PV cell manufacturing does not use gallium. Most is based on silicon, which is extremely abundant.

There are a lot of incentives aligned to panic about shortages more often than makes sense. Stories in the popular press emphasize shortage and panic because "we're not running out of gallium" is not a story. Junior mining companies play on the panic to lure money -- "we're going to solve the rare earth crisis and make our investors rich!" Shills for the fossil fuel status quo tu quoque renewable energy: "greenies against coal never tell you that those wind turbines need filthy, dangerous mining too." Even several environmentalists of my acquaintance have swallowed this nonsense; perhaps they've seen so many bad examples that they're pre-primed to believe it when someone says that we're even running out of materials to make wind turbines and solar panels.
Bitcoin thieves threaten real violence for virtual currencies
Desktop PC’s are upgradeable by design, and frankly require repair pretty regularly. This is some IoT shit that will have support pulled before it can break and I suspect that you know that.
Panpsychism: Erewhonians anti-machinist for fear of rise of conscious machines
Embedding the design into your code is pixie dust for code quality
Kangaroo courts, plain and simple. Sacrificing innocent people to get more of the guilty ones when evidence is flimsy.
The rest of the paper was explaining concepts in computer architecture.
This is exactly why I don't bother with forums controlled by the company I wish to raise a grievance about. Just go air your complaint on Reddit or something they don't control, it's not worth your time complaining to their forums.
The quality of this product aside, I want to comment on how great iFixIt is. With their guides, I've been doing my own phone repairs recently, which helps me keep my phone in working order for longer rather than buying a new one all the time. They're a great resource.
I'm just getting into Elixir now but even without it being statically typed, it does catch a ton of errors and present warnings at compile time.

It's remarkably useful so far. I feel like I have an extra level of protection compared to Ruby or Python.
I’m certainly proud of what we’re building and the great team we’ve pulled together. We happily support our own community of tens of thousands and growing, in the past two months alone we’ve sponsored five student Hackathons and introduced thousands of young, excited minds and the future of software development to “serverless” workflows.

These developers have built everything from passive notifiers to help the elderly [0] to smart city garbage collection bins that integrate with City’s Slack teams to notify when bins need to be changed [1].

Our team is active 24 hours per day at these events and more, shipping releases to both paying customers and free tier developers into the wee hours of the morning. We’re very lucky to have a small but motivated team of the most competent engineers I’ve ever had the pleasure of working with and we’re humbled to be working with companies tens to hundreds of times our size that do hundreds of millions of dollars in revenue combined.

So, pride? Certainly. :) I just don’t think it’s the deadly-sin type you may be insinuating. It would be disingenuous to my team, our customers, and our Enterprise partners if I wasn’t proud of the work we’re doing (that’s not to say there’s not plenty of room for improvement! We’re constantly growing and responding to customer and developer needs.). However, we don’t have a single customer that has asked for (or even suggested) any sort of foundation membership at this point. We simply don’t have the resources to be part of a committee: we are already stretched thin with many boots on the ground doing work that, yes, we’re proud of. I’m not precluding it from the future, it’s just not on our roadmap right now.

Happy to understand how you think Prometheus may help us, though!

[0] https://twitter.com/shivkanthb/status/965409645136199680

[1] https://twitter.com/stdlibhq/status/960179903621750794
This is an excellent and under-appreciated joke. Bravo.
In line with the same type of intentionally forgotten history, US investors and business persons built and provided a large portion of the Soviet industrial capabilities prior to WW2 [1], which the Soviets later pretended were their own accomplishments. It's a theme that repeats throughout all of Soviet history, where Communist propaganda collides with market economy prosperity, on up to the famous 1959 Kitchen debate between Nixon and Khrushchev [2], or Yeltsin's visit to the Texas supermarket [3].

Communism universally, completely failed at providing superior material prosperity, which was one of its most touted foundational claims. Worse, it failed at providing nearly any consistent materialism at all, as witnessed by the second great Soviet famine under Stalin in 1932-33 [4], in which millions of people perished.

[1] http://www.americanheritage.com/content/how-america-helped-b...

[2] http://adst.org/2015/07/nixon-vs-khrushchev-the-1959-kitchen...

[3] https://blog.chron.com/thetexican/2014/04/when-boris-yeltsin...

[4] https://www.theatlantic.com/international/archive/2017/10/re...
> Maybe Apple could have gained some respect and then market share if they would have stood firm.

The Chinese government doesn't play that respect game. Apple's stock holders also would never allow Apple to exit China without a huge hit (~50%) in their valuation. It isn't hard to see that Apple is stuck in China whether they are passionate about it or not.
Google's lead me to this one today, lol: http://ndjson.org/

I'd make fun of NIH but I'm so guilty of it too.
Because you get all of the problems that you get mentioned in the article. And on top of that javascript land is fad heavy, and whats cool today might not be cool 2 years from now.

I personally know of a story where a startup started with datomic and clojure, and it was a bad idea because datomic could not effectively delete things. Eventually they went the standard java and standard cassandra / postgres / redis type route.
Unfortunately, I only found out about HN a couple of years back in 2016. I had been looking for such a community for an incredibly long time and somehow I used to always wonder how some of my colleagues knew what was the latest in the tech scene.

Anyways, when I first joined, I fell into a bit of a depression due to the impostor syndrome :(. Fortunately for me, I had quite a few other changes happening in my personal life so I was able to snap out of it and focus on using the platform to learn and grow rather than be intimidated.

I had also recently started blogging in 2015 and I remember submitting one of my articles (it was about using gmail with mutt) to HN. It hit front page for over 100 points) and it was one of the most thrilling moments of my career!

I went on to get a few more submissions on to the front page and HN also gave my the confidence to launch my side project which also hit the front page: https://ewolo.fitness

A big thank you to everyone on here :)
I knew that there was now a default for GOPATH, but I didn't know you are able to build in any directory. When was that added?
Knuth said that doculents should be readable, but artvto be hanged on a wall.

Typesetting my thesis in LaTeX (physics, 2000) was an amazing choice. I could hardly modify anything (it is doable but requires a lot of work and in the meantime you learn that the default is better) so I was left with the content.

I knew that it would just work and took from me all the philosophical sufferingbof choosing such and such fontvsize for the title of adjusting margins, or placing a graph.
I can't speak for the author, but I made the transition from JS+React to TypeScript+React to Elm and it "changed my mind" too.

When I started with React/Redux, I didn't know much about functional programming, but I developed a certain interest... A couple years later my React stack was full of tools and libraries that allowed me to write my React apps in a more functional manner. I used TypeScript for the type system, ImmutbaleJS for immutable data structures, Ramda as a FP utility library and Recompose to call React itself in a functional manner. I also used pure stateless components exclusively... Then I switched to Elm and I realized, that the React stack I was working with was a crippled version of Elm. I'm currently writing my first app in Elm and it feels much smoother.
FYI, you posted your comment on the wrong thread.
That’s called coordinated disclosure. There can be no such thing as “responsible” disclosure, and Microsoft has disavowed that term.
Yes, the position I filled explicitly required a PhD. I would be skeptical it would be a good fit for the vast majority of people who do not have a doctorate.

While I certainly would not call it academic hell, getting a PhD was very hard for me. However, while it was hard, I loved it. If you don't love it you probably[1] do not love research, and then you would absolutely hate the day to day.

[1] Probably because many things can make life miserable. A bad adviser being #1. I was lucky to have an absolutely incredible adviser who really helped me through. Of course, the other challenge is the very poor salary. I had a wonderful support network and no college debt so I could survive, and even then it was hard.
I suspect that's part of it for sure. A lot of what conservatives have been getting upset about over the last few decades is diffusion of power away from well-off, white, straight men to everybody else. Loss of power still feels like a personal loss, even if systemically it's a move toward a more equal structure.
> But are language enthusiasts really better hires in general? I've known many of them who loved the theory and toying with a language but were not any better at producing actual value than the average joe.

I think they may be safer hires, anyway. They will be able to program themselves out of a wet cardboard box, which is more than you can say about the average Joe who may just be good at bluffing the interview.
Damn you Richard, you hired all the best Elm devs and cornered the market :)
Thanks for sharing this.
"Once, after I suggested a problem, he[Frigyes Riesz] he repeated it slowly twice to make certain he understood. Then, absolute silence. After half an hour, he exclaimed "Ja uj. I have it. Yes, I have it.", and he leaned to me, his eyes full of joy and mischief. But that was the end of it. He never made me privy to his solution." - We can learn a lot by working with individuals like these, who sometimes reveal nothing about their method in solving a problem, evoking (mild) stress/frustration upon others until they too solve the problem or at least spend some good time thinking about it.
A programming language capable of building the whole stack from the boot loader, usually written in Assembly, drivers, all the way up to user space applications.

The only programming language for a single platform, besides a little Assembly for hardware integration.

The traditional CS definition of systems programming languages on OS research literature.
It’s something I’ve begun to notice in almost every piece, like it is now worth some kind of internet points. It pops up in texts that are otherwise completely ‘serious’, even more formal ones, which is unsettling. Not exactly what I’m looking for when reading news about a tragedy, business failure or science.
You could go do reason @ facebook messenger (I dont work at facebook):

https://reasonml.github.io/blog/2017/09/08/messenger-50-reas...
Clojure is sufficiently different from typical Lisp dialects and their implementations, that it forms its own language family.
So was Trump’s election campaign. I’ve been saying this since he announced his candidacy. Convincing people to walk to the polls and vote for a certain candidate is no different than convincing them to buy a product. It’s marketing. And in marketing, black hat tactics always win, at least in the short term. They lose in the long-term because some controlling algorithm adapts to their strategy.

An election is a short term ad campaign. Convince people, get the vote out, then it’s done. So black hat tactics will be successful against white hat tactics because there is no time for the system (often the same used in advertising) to evolve to respond to the tactics.

Unless there is a force to stop this sort of weaponization of data, the problem will proliferate and the strategies will evolve. Only structural forces against such weaponization of data can allow the “white hat” strategies room to thrive.

Our political system selects for rule breaking, obstruction and obfuscation.
I hope you note that you don't have an actual argument here. You're just shitting on something it's not even clear you understand.
http://fortune.com/2017/05/23/microsoft-claims-unique-cloud-...

https://docs.microsoft.com/en-us/azure/china/china-welcome
Yes, I use it to trigger actions on certain messages in one of our APIs instead of hardcoding them.

Incoming data -> is it a valid messages at all? -> if it is a message of type x, hand it over to class X -> if it is a message of type y, hand it over to class Y -> etc

I found that to be a very easy way to setup a general-purpose processing pipeline.
There is some discussion here. https://news.ycombinator.com/item?id=16396554

You won't actually find an argument from me that Damore didn't behave stupidly, assuming he wanted to keep his job. However, whatever debunkings might there be to Damore's memo, neither Google, nor rags like Verge, nor even Economist provided any. Economist went as low as referencing Zunger's "pathetic bleatings" that make Damore's memo look like a Nobel material. And "social science"s wounds are mostly self-inflicted -- those few arguments that were presented against The Memo came mostly from departments of "womyn's studies" where results are determined long before research starts. Just look at what happens to Peterson (his scientific bona fides seem to be beyond reproach) when he tries to speak.

Google's internal discussion groups are quite weird, but apparently inciting street violence is perfectly fine. I think it would have been reasonable for Damore to expect that a memo that at least pretends to be objective, and does not call for any illegal activity would be acceptable as well.

Shold Google have a right to fire anyone over anything? I believe so. But if they fire Damore for reasons they give, which really are complete bunk, and do not fire the "I'll punch you in the face" crowd, they are hypocrites, and might get mauled themselves in the end.
What does that have to do with Elm's commercial viability? The only conclusions I can draw from that are about Prezi's commercial viability.
I wrote my (phd) thesis recently, which mean I got to do a survey of the various templates for that purpose.

KOMAscripts wins, hands down. This is cute, but KOMAscript is just ridiculously featureful and customizable. It's also very well documented, can be adapted to any page format and has very good typography.
I'm looking at the behavior of the search tool on the page, which makes a request to https://instantdomainsearch.com/services/all/<query parameters> through AJAX and gets streamed lines of JSON back as a result. It's not doing DNS queries from JS or whatever.

Looking at the behavior with curl and wireshark, what I see is that a full, new connection to the service does spend most of its time in DNS lookup and HTTPS handshake. It takes about 0.1~0.3s for the actual data to transfer.

What the article is recommending is basically, don't make a request per JSON object. (It streamed back 69 objects for the query I tried.) Using one connection to transfer the information saves a lot of overhead -- and I don't have a problem with that part of the advice.

What I mean is, instead of using JS at all to do this (and consequently triggering a 5 second initial page load, etc etc.), have the server build the page the traditional way, and send that -- that's still one connection for that data transfer, and with a light page design and keep alive connection, the page load time does not seem like it would be significantly different here (most of the time is going to be in that 0.1~0.3s for the query to execute regardless) -- but the initial page load time would be significantly faster on slow connections.

If your queries do actually take many seconds, sure, maybe there would be a benefit there, but I'm not seeing the value on a page like this, and I really don't want people to take away the idea here that they should redesign their sites to use AJAX to "reduce latency on mobile" by default as it won't help, and in fact, tends to make things worse.
That's a good way of looking at it, thank you.
Avro aims to deliver drugs to children and the elderly through skin patches
Yippee!
I'm sure that some people do that, but to cast everything in that light is just laziness.
Nutritional yeast has very little to no fat. Eggs and whey have large amounts of saturated fats and cholesterol. Yeast has no cholesterol.
quick google search found Columbia University's formatting requirements.

https://gsas.columbia.edu/student-guide/dissertation/formatt...

doesn't seem to be anything that particularly hard to follow with any template.
If you use named arguments, can't you typically rearrange the order?

Don't get me wrong, I use destructured arguments in js and it works fine, but I thought named arguments in other languages solve that particular issue as well.
Yeah, I guess you are technically correct as far as being explicit. Maybe intuitive is a better description. A newcomer could read public/private and quickly understand its meaning as opposed to capitalization being a learned convention.
The screws will get loose and will introduce unwanted vibrations unless the structure they're on is very firm (and heavy, and expensive). All parts that can be vibrated out of position will (this is a speaker with a long travel woofer) and on contacts oxides will form, further distorting analog signals.

Sometimes, making something easily fixable also makes it worse.

I can imagine a couple joints that would not bring too much vibration problems, but the speaker would be larger, heavier and costlier to manufacture. Soldering wires or flat pads instead of removable connectors could fix the remaining issues, but that would come at a price in the form of extra manufacturing steps.

Finally, a Kindle is a flat board with components on both sides and a plastic shell around everything. This is a mechanically complex thing, with lots of consideration paid to details.
I tried this. Bought into the company vision despite lack of experience/desire for RoR. The plan was to migrate to microservices. This happened too slowly and rarely and I ran out of enthusiasm working with a legacy monolith. The scaling problems we're interesting although they could be sidestepped other ways.
Show HN: Spendbook, a web app to track your expenses
The website is: https://www.spendbook.net/main I am posting this on behalf of a friend who built it so he can get a feedback - he doesn't have an account and when he created one his post was killed.
Is learning IT fundamentals on-the-job even possible today?
Google left after Chinese state sponsored hackers attacked their servers, IIRC.

Check out Operation Aurora.
Probably the most important piece of that article starts with "Rosen: Is there any area for progress in the law and might your dissents in sexual-harassment cases be vindicated?".
Fairly early on I worked on a project that was size constrained due to pretty severe storage restrictions on the target device. Within a year we hit a point where every feature we added required that we first make space for it by winnowing down the rest of the code. Sometimes that was making the code more sophisticated, but most of the time is was more of a Antoine de Saint-Exupéry sort of expedition. It was a constant battle but in retrospect it's some of the most rewarding work I've ever done.

After that project I intuited that projects had a maximum complexity after which the wheels fall off, so to keep a project growing past that point you have to remove accidental complexity before adding new intrinsic complexity. For the limited sample size I have direct or indirect access to, this really seems to hold. And in fact someone told me that RPI teaches something very close to this in a required class for one of their Masters programs in CS.

Abstractions do not fix this problem. They put it off until the next performance emergency happens. It's an avoidance tactic and kind of paints you into a corner. Ultimately you're not looking for an abstraction (I mean, it is, but so many bad things are also abstractions that I hate to use the word for this situation). You're looking to model the problems actually being solved. You're looking for the truth.
Sorry but at this point I don’t think he’s ever going to return to earth :p