skysight-inc/HackerNews huggingface dataset:
Two questions:

(1) Why does pro-solar have to be anti-nuclear?

(2) How quickly can nuclear reactors and associated transmission lines be built, and at what cost?

My understanding is we’ve reached the point where solar and wind are quite cheap (cheaper than nuclear) and rapidly getting cheaper. We still need to solve the storage issue, but things on that front are progressing quickly.

I am certainly in favor of nuclear power where it makes sense, but again as I understand it the situations where nuclear is more economical are rapidly decreasing. Perhaps it’s better for society to “skate to where the puck is going?”

Or perhaps I am incorrect about the economics?
Visualization of Algorithms with C++ and Python
zeptograms
The depth of Key press. The previous keys on Macbook are 1.5mm in depth, the distance it travel every time you press it, with roughly 60g of force. This has been sort of the golden standard in keyboard on Notebook ( and in many cases Desktop ) for more than a decade. Apple reduce that to 0.7mm in their infamous butterfly keyboard in the name of thinner devices. For some that might have been fine or even preferable. For many its typing experience is much worst.

Due to its reliability problems ( which may not have anything to do with the lower key depth ) Apple walked back on the design and uses a 1 mm Key travel "Magic Keyboard". And from my experience it is pretty much the same as the old Butterfly keyboard in terms of Typing experience.
Please don’t be discouraged and keep on writing quality code. Most managers at big companies are soft engineers who weren't really into the engineering aspects of the job. They’re more interested in team cohesion and deliverables. In my experience the first things to go when there is a date looming over the team’s head is code quality (code review becomes code approve) and then documentation, followed by tests. It’s really up to the engineers at the end of the day to maintain the quality of their codebase. Managers don't care unless it’s so bad that they can’t onboard new people or things are constantly on fire, but I’m pretty you can onboard a new grad into almost any mess and they’ll eventually figure out how to poke the right things, and fires don’t reflect poorly on the manager.. they just happen as if acts of nature breed unstable rushed code.. so :shrug:. Keep in mind a downside of working at a bigger company is the overarching philosophy that most code will be rewritten in 2 years. Add in that most rank and file employees are just ladder climbing anyway and, well, I think you get a pretty realistic picture. The linux kernel is good on merit and demands good engineering. The exploratory product idea that probably wont be around 6 months after launch... no so much. So find a team that actually cares about the quality of their engineering, if you have that luxury. If not perhaps seek work with a smaller company or on a project that is here to stay. Things with open source components tend to calibrate well in that department in my experience because the code is the product. Also whatever the case, lead by example. It may feel futile but it does work.
I think the rise of a well headed, free speech space is extremely important. The US has reached a point where certain topics are not even up for debate, as ruled by the court of twitter mob.
Poorly written blog post. Author even skips analysis of their own opening graph.
This is a good example of how this overall topic gets reduced to "How much abstraction?" instead of "In what ways should something be abstracted?"

Obviously an Add/Edit field are operating on the same record in a hypothetical database, so it makes little sense to duplicate the model.

On the other hand, if the conditionals within the abstracted version become too complex or keep referencing some notion of a mode of operation (like, ` if type(self) == EditType && last_name != null` lines of thinking), that is sometimes another type of smell.

But say you make some kind of abstract base class that validates all fields in memory before committing to the database, and then place all of your checking logic in a validate() method. That sounds like pretty clean abstractions to me.

And moreover, this is probably provided by an ORM system and documented by that system anyway--so that's a publicly documented and likely very common abstraction that you see even between different ORMs. That, I think, is the very best kind of abstraction, at least assuming you are already working in such an environment as a high-level language and ORM. Making raw SQL queries from C programs still contain their own levels of abstractions of course without buying whole sale into the many-layered abstraction that is a web framework or something.

This question becomes more important when you aren't just updating a database though. If you're writing some novel method with a very detailed algorithm, over abstraction through OOP can really obscure the algorithm. In such a case, I try to identify logical tangents within the algorithm, and prune/abstract them away into some property or function call, but retain a single function for the main algorithm itself.

The main algorithm gets its definition moved to the base class, and the logical tangents get some kind of stub/virtual method thingy in the base class so that they have to be defined by subclasses. The more nested tangents are frequently where detailed differences between use cases emerge, which makes logical sense. It's not just that it's abstract, but the logic is categorically separated.

It's a very general pattern supported by many languages, so you see it all over the place. That organization and consistency in itself helps you to understand new code. In that way, it also becomes a kind of "idiom" which in a sense is one more layer of abstraction, helping you to manage complexity.

As a counter of that, you see code where `a + x * y - b` becomes self.minus(self.xy_add(a), b). More abstract, but not more logical; not categorically separating; not conforming to common idioms; obscuring the algorithm; and so on...

And then there is performance! Let's not talk about the performance of runtime abstractions.
I aim for 3:1 or so when working alone, work real hard for three months then have the rest of the year to pursue my own projects.
What's sensitive or not depends very much on what other information the entity doing the analysis has available. Of course raw log records are more sensitive than aggregate data. For example, if somebody is wiretapping your internet connection, then even if the connection is encrypted raw logs would let them draw conclusions from timing. To some extent you're trusting the Julia project (or at least the people who have access) to not clandestinely be in the wiretapping business, but then again you're already trusting it with arbitrary code execution on your machine, so if it were in that business, you'd have bigger problems ;).

In any case that's why it's important to be transparent about what is sent, and for what purpose and who has access, so people can make informed decisions. Ironically, I think people are jumping on the authors of this particular piece of functionality precisely because they tried to be very transparent.
Show HN: A simple Poker API to calculate the winning hand/s
Enhance your TensorFlow Lite deployment with Firebase
It's not obvious on the website but everything is on Github[0] with different repos for the forked Dolphin build, the desktop app, melee assembly...

As to dev blogs, they have a medium[1] with some interesting posts, but nothing too recent, I hope they'll do one in time with all the new stuff.

On top of the rollback, something very notable they did was realising melee has 3 frames of input lag when running on native hardware, so they managed to remove them from Dolphin when running on 120hz screens. This allowed them to keep those frames as a delay buffer without actually having a real effect on gameplay.[2]

[0] Slippi Github: https://github.com/project-slippi/

[1] Dev Blog: https://medium.com/project-slippi

[2] Post about Faster Melee, the previous netcode iteration, going into the input delays: https://www.reddit.com/r/SSBM/comments/azoiqz/faster_melee_2...
seems like in depth. thx
It's offensive in the same way as Call of Duty: Black Ops is offensive, which is "generally not actually offensive". However, it is possible to derive professional advancement from claiming that it is, so expect to see more of this in tech.

Also not offensive: Black Friday, black holes, black beans, black tea, black-eyed peas, black gold (aka oil), Black Mirror, black swans.
Thanks, that was a really clear explanation!
It helps that beyond critical fixes the kernel doesn't really have deadlines so there's time to be extremely picky about the code and commits. I think a lot of cruft and bad code comes from time constraints from business, not all for sure but a lot. And beyond that as an OSS project going back and rewriting things doesn't cost anything (at least in real money) so there's not an economic pressure against going back and addressing cruft.
> Arguments like these try to shift away the spotlight from big companies who collectively make up a large chunk of the greenhouse gas emissions to individuals.

This is the key problem, with “eat local” and all similar initiatives.

Yes, reducing emissions by tiny percentages is still a good thing. But too often, by focusing the conversation on these small individual actions, we miss the forest for the trees.
I'm sure Debubble.me means well, but misses the mark with respect to why people use Twitter. It's entertainment first and foremost. I would be interested to hear the creator's user research.

Framing every argument as a debate is disingenuous. A debate implies that both sides are of equal merit, debating only works between two people of similar values. I.E. if I'm debating a Nazi, it's hard to "debate" nearly anything in the sphere of politics because they do not believe all people are equal.

Third, what of debates that have largely been settled by consensus? Would a flat earther be able to enter into debates with me whenever I retweet a photo from NASA? Debating assumes that either side is going to play by a certain set of rules. How does this prevent a DDOS via Ad Hominem?
Addressing the middle point (which you've labeled a fundamental problem)... I am not a patent lawyer (or even a lawyer generally).

However I believe the stopping point is exhaustion.

A license for X would be demanded when the first sale that uses X happens. If the IP is related to the formulation or formation of part of a capacitor then the payment for such is part of the price of that good and is not required or taken again at any other stage (other than in the price of the components already included in the BoM). Similarly, the price is reflected in the first transfer of the good, not in any final consumer sale of the unit.
Spaceship could reach 30% the speed of light
If you don't like it, write your own code!
Correlation is not causation. For example, having a healthy social life may promote both alcohol consumption and cognitive function.
Ramp up what exactly? There is no cure or treatment available to this day. This is how it looked in Italy 3 months ago during the peak, Two hospitals, not a single patient survived ventilation/ecmo at the time of recording:

Italy Cremona https://www.youtube.com/watch?v=rfkbv_WQtn0 Italy Bergamo https://www.youtube.com/watch?v=_suhYeWEcJg

Patients went in, bodies went out.
The inanity is best summed up in an image macro: https://imgur.com/gallery/QR1UXz1
I know this is a common refrain, but it’s not based in actual science. Check out MIT’s EN-ROADS project [1] and see what a tiny difference full nuclear funding actually makes.

Aside: accusing people of being unscientific while proposing a very complicated issue could “be solved in a day” kind of calls into question your credibility.

[1] https://en-roads.climateinteractive.org/scenario.html?v=2.7....
Other side of the fork here, headed to the exit because I don’t want to become a grant writing machine.
Easy to prove the point: Stop importing semiconductors and see how India or Argentina would fare.
They absolutely should be.
Error 1020

Access denied

What happened?

This website is using a security service to protect itself from online attacks.
I’m not confusing anything, but I’m using the term ”use case” in a very broad sense.

> Can you give an example of a new use case being introduced without the code changing?

I once wrote a framework for processing data in different proprietary formats from different vendors into a unified format. At first, each vendor had its own code module, and any idiosyncrasies between different data files for a given vendor were solved within that module.

However, later on, we had to split one vendor into two modules. Now, some key parts of the code had to be changed to account for this, as it could no longer be assumed that one module would handle one vendor. But most parts of the code was already abstracted over the modules, and didn’t care.

> Why would this be documented in the code in the first place if nothing has changed?

That’s what I’m asking you! :)
Then the obvious compromise tile is "869 Xeon Cores in one SSI" :) This makes it clear that it's not a normal computer, but a weird hyperexpensive proprietary cluster thing that normal people won't be interested in.
In case this isn't clear, the telemetry being discussed is only doing anything when you ask the package manager to connect to a server, to download things.
Using SaltStack to Deploy Consul and Prometheus Exporters on Illumos (Solaris)
I originally interpreted the title as 'eating locally has a tiny environmental footprint" which is opposite of the point the article is trying to make.

I'm not sure what the rules about changing a title is, but the article makes an excellent point and it would be a shame if people who don't read the article get it wrong like I did.
So can someone explain what this is? It's not very clear to me.
"Make something people want." (Paul Graham[1])

A stronger version of this is "Solve an urgent problem." (Caleb O'Dowd, Gary Halbert)

- A person with high blood pressure may want to lower their blood pressure, but a person with 90% blocked arteries absolutely needs to lower their blood pressure. Otherwise they will die.

- A person may want to get their dog to sit on command, but a person whose dog is barking uncontrollably will either be evicted or forced to get rid of their pet.

The common thread I see with successful companies/strategies is focusing on the customer/users' needs and desires. A common thread I see with failed companies is a focus on themselves and/or their product; they barely think about the customer/user. The problem with this is the product is not the greatest challenge for a business; sales and marketing is the greatest challenge for most businesses. "Build it and they will come" only happens in the movies.

So pick a niche and solve their urgent problem. That's another thing: if your product is for everyone, no one will be interested. Pick a narrow, specific niche where there is competition. If there is no competition, there is probably no money. (Look at what happened to Segway.) Another way to say this is "Desire cannot be created. Like sunlight it can only be focused and transformed." (Paraphrasing Eugene Schwartz.)

Money (profit) is a side-effect of creating value. (Which might explain the similarity Paul noticed between successful businesses and charities.)

Of course, you can pick counter-examples of successful businesses that did not do this. There is more than one way to success. This is simply the way to decrease your chance of failure.

Also, during recessions, the businesses that target niche markets and solve their urgent problems tend to survive, while other businesses die.

I could go on, but these are probably the most important points...

[1]: http://www.paulgraham.com/good.html
Honk honk!
Can’t spell “dairy” either.
It is clear. There is a UUID generated on the user-side to identify them.

It’s one thing to collect statistics of downloads on the server side and another thing to profile me. It’s pretty clear to me.
The key points of Software Design X-Rays
I know a guy who added basically full collaborative support to IDA Pro, doing something similar (IIRC, hooking all state transitions). Some people are just way out there.
i'd be curious to hear more about how you've built a career around something as specific as django (if i'm understanding you correctly). does not seem a broad enough skillset for the sorts of places i've worked, and it makes me wonder if i'm being spread too thin.
In 1965 I took my driving test in a BMW 600, the two-cylinder big brother to the Isetta. Here's a photo of the car and the rest of my family's fleet of cars and motorcycles as of 1966: https://imgur.com/a/ria9buN
I agree that many issues with bad code could really be avoided by first thinking about the solution a bit, of which the code is just an expression.

I'm not advocating weeks of architecture astronauting without code feedback - because practical considerations (e.g. the compiler can't deal with this kind of code due to some limitations) matter - but some people seem overeager to just start writing some code "and see what happens".
It was funded by the Friends of a Mediterranean Diet Society ;)

Make a proper dinner every day, with actual ingredients, eat it in peace, with a glass of wine. It'll do you good, and leave separating the effect of the wine from the effect of the other mediterranean staples to the pedants.

https://www.amazon.com/fnord/dp/0091925320 for example.
As of right now, the post is 3-hour old, has 391 votes, second only to another post in the top 60 posts, and yet is is ranked... #59.

HN mods have likely flagged it as flamewar, or non relevant, or both, effectively contributing to the soft censorship on the topic.

Content platforms have many challenges ahead of them.
Don't do that. Don't attack the speaker instead of the arguments. You don't know anything about me.
WHO discontinues hydroxychloroquine treatment arms for Covid-19
Doesn't CLOS count? That was a lot earlier.
This is too much like 1950s auto design. Tailfins for your phone!

In 1955, the auto industry caught up with the pent-up demand from WWII. Suddenly, making cars wasn't enough. Now they had to convince people to replace their old car even though it still ran. That's when auto styling became exuberant. All the automakers had tailfins. Big tailfins.

Peak tailfin was reached in the 1959 Cadillac Eldorado. Tailfins then shrank, until by 1965, they were completely gone.

Tailfins are what you do when you have no clue how to improve the product. By 1955, car engines had enough power, automatic transmissions and power brakes worked, suspensions were smooth, and air conditioning was available. Getting from point A to point B comfortably was pretty much solved. Solutions to the hard problems in fuel economy, safety, reliability, and handling were not yet available for production cars. So chrome and tailfins dominated.
So based on that quote either they don't know what blockchains do and don't do, or they're just straight-up lying.

Voice requires the use of EOS coins, the creator of which paid a $24 million fine to the Securities and Exchange Commission over its 2017 ICO.

From https://davidgerard.co.uk/blockchain/icos-magic-beans-and-bu...

"The legal EOS Token Purchase Agreement is a frankly amazing document that everyone should read.[1] US citizens or residents are not to buy the tokens (though EOS assures us they totally don’t constitute a security – hear that, SEC?); the tokens are defined as not being useful in any manner whatsoever; forty-eight hours after the end of the distribution period, the tokens will no longer be transferable; the buyer promises not to purchase them for speculation or investment. If there’s any legal problems caused by you buying these officially worthless things, you agree to indemnify EOS."

[1] PDF: https://davidgerard.co.uk/blockchain/references/EOS%20Token%...
If you’re trying to start another venue with a stated specific bias, there is every reason to believe that it will (eventually, if not immediately) become exactly as limiting and echo-chambery like the rest of them.

However, if you’re trying to not do that, and create a truly open environment, you run into the problem which was perhaps best described like this:

“If you’re against witch-hunts, and you promise to found your own little utopian community where witch-hunts will never happen, your new society will end up consisting of approximately three principled civil libertarians and seven zillion witches. It will be a terrible place to live even if witch-hunts are genuinely wrong.” (Emphasis in original.)

— https://web.archive.org/web/20200618093842/https://slatestar...
SAP offers similar technology on their Enterprise Cloud using POWER9 interconnected nodes:

https://insidesap.com.au/sap-hec-to-run-on-ibm-power-system-...

https://www.youtube.com/watch?v=djtqJ4P3OnU
Thanks. That's a good example.

Three months ago deaths were doubling every 2 to 3 days. That's some of the little data we really have. Same virus (although there are speculations that perhaps now there are multiple forms). We're being more careful about transmission ... except when we're not. We seem to be better at treatment. Vulnerable population is unchanged.
Not sure about this exact study, but studies like this usually ignore confounding factors that cause people to abstain. The headline leads people to think that they should drink a bit to achieve the result, but that’s usually never the case.

For example there were a bunch of studies about how sleeping 10 hours per night has lower mortality rate than sleeping 12+ hours (oh no - are you sleeping too much?!?), but upon further review they realized that people who are really sick or alcoholics are more likely to sleep 12+ hours per night.

In this case, wouldn’t be surprised if there are reasons people fit into the zero drink category (health issues) that are associated with cognitive decline.
"> Discussions about the topic started late last night after David Kleidermacher[1], VP of Engineering at Google, and in charge of Android Security and the Google Play Store, withdrew from a scheduled talk he was set to give in August at the Black Hat USA 2020 security conference."

it's usually entitled white people who feel immediately offended by this. With entitled I mean, finished university working at a top position in a large company on a 6 figure salary. It's never the worker POC who is slaving away in an Amazon warehouse or working 3 jobs in the gig economy to feed their family. It's just a cheap way to get your name in the news and to me (personally) these people are very misguided. They're well read no doubt but nevertheless wrong. Guess it's easier as an exec at a multinational company to pander to this rather than tackling their transfer-pricing crimes they commit with their Double Irish / Dutch Sandwiches[2].

Banning language like this is a very dangerous path:

“Don't you see that the whole aim of Newspeak is to narrow the range of thought? In the end we shall make thought-crime literally impossible, because there will be no words in which to express it. Every concept that can ever be needed will be expressed by eactly one word, with its meaning rigidly defined and all its subsidiary meanings rubbed out and forgotten. . . . The process will still be continuing long after you and I are dead. Every year fewer and fewer words, and the range of consciousness always a little smaller. Even now, of course, there's no reason or excuse for commiting thought-crime. It's merely a question of self-discipline, reality-control. But in the end there won't be any need even for that. . . . Has it ever occcured to you, Winston, that by the year 2050, at the very latest, not a single human being will be alive who could understand such a conversation as we are having now?” -- George Orwell "1984"

[1] https://www.linkedin.com/in/davekleidermacher/

[2] https://en.wikipedia.org/wiki/Treasure_Islands:_Tax_Havens_a...