skysight-inc/HackerNews huggingface dataset:
I did not see your comment was a reply on another comment, and thought it referred to the post title. :-D
I think you can draw an analogy between probability and counting. Negative numbers seem weird and very different from positive numbers, but for many applications 0 is not a particularly interesting boundary, and you benefit from not treating negative and positive numbers as two different cases. EG, I could owe you $2 or -$4.

In probability, 50% feels like it should be a special boundary. But often there's a lot of benefit to not treating it that way, and treating a 49% belief more like a 51% belief than like a 10% belief.

It sounds trivial written out, but how often do people behave that way?
If only the Snowden docs included all the nasty domestic spying that the agencies do, I'm sure we would have substantial proof.
It feels like it's a too far away goal and too big goal.

2030 is the new 2020 where we push away dreams for the future, forget about them, try to do them at the last moment and miss the deadline.
I think it would be better to have have smaller goals with a shorter timeframe.
I am not sure Francisco de Miranda and Simón Bolivar had oil on their minds when they effectively established Venezuela as an independent state from Spain.
Exactly - that's my take on React.
Show HN: Minimalistic, free and open source launcher app for Android
Just checked for myself, and you're correct. OP could have shortened the post by 90% if they just pointed to this fact. But while technically valid, for any reasonable HTML document, you'll run into cases where quotes are required. Example:

<div class=foo bar>

At which point, if you use quotes once in your document, you should really use them throughout.
Kharkovchanka, Antarctic off-road vehicles made by the Soviets
1. Reuse
2. Reduce
9. Recycle

They missed the first point
Ask HN: What are the most secure email and messaging apps?
I wouldn’t mind having an SD slot and a 3.5mm headphone jack. The impenetrable sleekness of modern phones looks great in equally impenetrable television ads, but my real world would benefit from a bit more utility. Add replaceable battery to the list too, to swap out a dead one, or install a larger one.
It's a sigmoid, which converges to exponential far from 0 and is somewhat linear near 0.
I can tell you after suffering Vodafone and Airtel that Jio is still the fastest. At least in Bangalore.
I thought this article was about the new UAE nuclear reactor. If anything I figured solar would be smarter for a hot sunny region. But dust, heat, and fragile panels (target for attack) may not be a good idea.

At least the UAE started construction when oil prices were high. I can't imagine a Gulf state starting a reactor program now with oil prices so low.

https://www.aljazeera.com/ajimpact/nuclear-gulf-experts-soun...

https://en.wikipedia.org/wiki/Barakah_nuclear_power_plant
How can that problem be avoided? If you were to build your own company and hire and instruct people?
Apache Druid 0.19
What Is an Effect?
Panic of 1873
Yeah, I think it depends on whether you're thinking about things from a SYSTEMS perspective or a CODE perspective.

Hickey clearly thinks about things from a systems perspective, which takes a number of years to play out.

You need to live with your own decisions, over large codebases, for many years to get what he's talking about. On the other hand, in many programming jobs, you're incentivized to ship it, and throw it over the wall, let the ops people paper over your bad decisions, etc. (whether you actually do that is a different story of course)

Junior programmers also work with smaller pieces of code, where the issues relating to code are more relevant than issues related to systems.

By systems, I mean:

- Code composed of heterogeneous parts, most of which you don't control, and which are written at different times.

- Code written in different languages, and code that uses a major component you can't change, like a database (there's a funny anecdote regarding researchers and databases in the paper below)

- Code that evolves over long periods of time

As an example of the difference between code and systems, a lot of people objected to his "Maybe Not" talk. That's because they're thinking of it from the CODE perspective (which is valid, but not the whole picture).

What he says is true from a SYSTEMS perpective, and it's something that Google learned over a long period of time, maintaining large and heterogeneous systems.

https://lobste.rs/s/zdvg9y/maybe_not_rich_hickey

tl;dr Although protobufs are statically typed (as opposed to JSON), the presence of fields is checked AT RUNTIME, and this is the right choice. You can't atomically upgrade distributed systems. You can't extend your type system over the network, because the network is dynamic. Don't conflate shape and optional/required. Shape is global while optional/required is local.

If you don't get that then you probably haven't worked on nontrivial distributed systems. (I see a lot of toy distributed computing languages/frameworks which assume atomic upgrade).

-----

His recent History of Clojure paper is gold on programming language design: https://clojure.org/about/history

I read a bunch of the other ones. Bjarne's is very good as usual. But Hickey is probably the most lucid writer, and the ideas are important (even though I've never even used Clojure, because I don't use the JVM, which is central to the design).
Always funny to read fanatics.
Incentives to prevent planned obsolescence. I bet there's a lot of ewaste sitting at the bottom of the ocean because the market allowed software companies to obsolete working hardware, or hardware companies to make hardware where a small failure rendered the rest of the machine a writeoff.
Surprisingly yes. It has billions of dollars or optimizations and research in it over the years and can really fly. Of course you can write slow node code just like you can in any language, but a single well-written node instance can handle a lot of traffic.
Predicting the future of one technology from the development of another technology doesn’t make much sense imo. Where are our fusion reactors and flying cars ;-)?
Reduce by 10% or reduce to 90% of it's previous value
Absolutely, if management is entirely invested in it, and it becomes a mandatory part of the process (e.g. updating the wiki is a part of a release or new build), it can be a critical resource. The problem is that the organic nature of wikis lead to people believing that it will just emerge, in the same way that the relatively unstructured wikipedia eventually became a critical resource.

But citing wikipedia is often folly. The man hour to output ratio of wikipedia is absolutely enormous. It is an extraordinarily inefficient process that works because there are millions of people moving, structuring, contributing, making templates, rewording, reorganizing, etc. Eventually greatness emerged.
Traditional news media is also organized by engagement: an entire department is responsible for picking the home page of a newspaper and importance of each story.

The major publications do a better job at not sensationalizing everything, but this has been a problem since 1890 at least: https://en.wikipedia.org/wiki/Yellow_journalism

That social media naturally tends to become a tabloid magazine may be more a reflection on readers than the editor (whether human or machine).
This is extraordinarily well put.
Fanatics always make me laugh. Maybe that's how I handle.my fear of them.
"It's a non-issue" is not really a good approach to take to software licenses. The point of licenses is that they should be followed, and they should be written so that following them does not unduly burden your users. It doesn't make much sense to pick a license expecting your users to break it in ways you don't care about.
I don't think there is any rule stating that HN discussion need to stay precisely on the topic of the article discussed. In fact, there are many about topics just tangential to the main one.
Even better, you can run these in Docker as non-root. Security wise, while this wouldn't make your app itself more secure, it would insulate your host OS from getting infected. I just checked and they even have one-liner Docker commands that do just this:

docker run -d -p 8080:3000 --name wiki --restart unless-stopped -e "DB_TYPE=postgres" -e "DB_HOST=db" -e "DB_PORT=5432" -e "DB_USER=wikijs" -e "DB_PASS=wikijsrocks" -e "DB_NAME=wiki" requarks/wiki:2
ByteDance AI’s Xiaomingbot: World First Multilingual&Multimodal AINewsAgent
I fear that this will just increase the price of the products. Apple will toss the broken iphone and hand you a new one because they don't want to pay the cost of labor to fix it. Repairing reduces e-waste, competition in repair reduces prices (with obviosu caveats). You can't really get around that.
UX nightmares are not the fault of cookie laws, they're the fault of companies that don't want to respect users. If the companies behaved more ethically, there'd have been little impetus to even create such laws.
Conversation with my dog about HDMI
So dubious bash completion requiring a cluster of GPUs in a a closed cloud and the energy of a hydroelectric dam to run?
Actually you wrong. Dolar has value, because even if no one will want dollar, government will buy it for dollar. It backed on government promise.
It doesn't understand English. It knows how to make up text that looks a lot like the text that it read. It read a lot of examples of code, so it know how to make up code that looks a lot like what it read. Some of this code works, since some of what it read works. But if it read too much non-working code from stack overflow questions, it might write code that doesn't work.

Edit: apparently it read a lot of Github repositories, so most of what it mimics is working code.
This feels too similar to my default mode of thinking, which is risk aversion, and constantly thinking about what can go wrong, and then steering away from that. Is that because this concept isn't really for me, like it's more helpful for go-getter optimists?
How is this structured legally and what are the tax implications? Have you spoken with a tax attorney about it?
> They can change the license to a closed one from a certain version in the future.

You're right if and only if by "they" you mean every copyright holder whose contributions would exist in the future version (including, say, the contributions of the very person you're responding to). But if by "they" you mean the project leaders acting without the cooperation of everyone who holds copyright, then that's a no.
Ardour is free and open source.

You might also want to try LMMS. Pair it up with ZynAddSubFX as the synth and you have a pretty competent studio.

Relevant submission: https://midination.com/free-music-production-software/
To just try things out instead of thinking, watch and see what happens rather than parse all of the code in your head. Maybe I'm just intellectually lazy though
Go to the shop in the corner and get it replaced in few minutes.

Back in the days I replaced my iPhone 4s battery myself but it's not worth my time now days. Nothing complicated, you just need steady hands and sharp eyes but it's better done in the shop because they would have tools to hold it still and they are used to do it - so less chance to screw up. The replacement batteries often come with the special screwdriver that some people pretend to be impossible to get. In case you don't have the screwdriver a pointy knife would do too.
Yes, I feel like developers tend to evaluate tech businesses from the perspective of the tech that they generate, since that is the goal of a developer. It's sometimes hard to remember that making tech is simply the means to an end.
Amazing that they designed and built this very novel vehicle in 3 months! Built in the 1950's and still being used 50 years later.
It seems like that should be easier with an electric drivetrain. Much of the complexity of modern vehicles is the controls for the fuel injection, transmission, timing, and the like. An electric motor—perhaps even without a transmission—is a hell of a lot simpler.
Also, add the open source part meaning everyone can audit how it works and fork it if needed, and the network effects preventing said forks.

Being protected from double spend or 51% attacks by having everybody in the world cooperate, because it is in their own selfish interest to do so, is indeed unprecedented.

The current price seems extremely undervalued. I believe it is due to factoring-in the legal risks for when government realize a currency they can't control (block people they don't like, see eurodollars) or inflate at will (regardless of the reason, good or bad, it's about control) is a threat that must be legislated away.
Just compare it to car tires and it doesn't sound so expensive anymore :)
Is the well-documented feature the dependency array or the ability to suppress linter rules? The note at the bottom of the documentation section for the dependency array recommends using the linter rule: https://reactjs.org/docs/hooks-effect.html#tip-optimizing-pe...
Why did you put 'in the traditional sense' in quotes, as if you were quoting the parent poster, who clearly wrote "in the classical sense"?
So is investing in construction the solution for all petro countries?
Do people get fined or cited for ripping up the terrain due to negligence or is this a free for all land that you can drive on without much repercussion?

I just recall reading that at Burning Man for example, lighting a fire on the playa gets you a fine for permanently scarring the landscape. So, in this case, a truck leaving a 2 foot gash in the salt -- is that not something that carries a penalty?
I played with the K on the word HACKS at the top of the screen for far too long.
> If they are the sole copyright owners (no external contribution)

That's not the scenario gary-kim laid out; you've failed to satisfy the constraints in the premise.
Great doctors can have worse mortality rates than average because they tackle the most marginal / difficult cases.

It would not be wise to compare mortality rates between dentists and heart surgeons and conclude that dentists are the better practitioners and should be doing the heart surgery.

With that said, the article is intriguing. They followed 30 day mortality, which might not quite be a long enough timeframe. This metric penalises surgery which might be trading a higher "up front" risk for many more years of better quality life and rewards treating a patient who is more likely to die without surgery in the next 30 days.

The conclusion of the article could still be true but it seems one of those findings that (as usual) warrants further investigation.

If you have ever been the victim of a metric that can lead to perverse outcomes like "LoC per day" or "tickets closed per week" then I think you can appreciate.
Any chance of providing a donations API? This sort of no-fee approach would be amazing for building all sorts of charity-focused apps, from walkathons to nonprofit crowdfunding campaigns, public matching campaigns etc. The minimal functionality would just be to allow a site to direct a user to a page that allows them to complete a grant for a particular amount to a specific nonprofit and receive a callback when the grant is submitted.
> I enjoy Ben's articles, but this one has way too many opinions

Oh, I had to laugh at that. He's a commentator!

Good grief.
Apple has been making and achieving smaller goals with shorter timeframes for a decade now. They committed to and acheived carbon neutrality for their first party operations already and are now incrementally pushing that out to their supply chain and product lifecycle.

Based on past evidence this is not likely to be a set and forget arrangement for Apple.
Only in specific situations, where the site is using Apache and has .htaccess files enabled. I would argue that using Apache in the first place is non-optimal, but enabling arbitrary .htaccess files for clients is also a potential disaster.

Then again, I suppose there are enough people out there who just want to FTP up their wordpress code and call it a day, so... ugh.
I have an "Invert"-related question for the HN hive mind — see below for the question, and why it's not off-topic: I'm a pretty-senior lawyer and part-time law professor; I'm working on turning some of my accumulated contract clauses and course materials into a "fair and balanced," annotated, contract framework, in the form of a plain HTML document w/ some CSS styling, to support using shorter contracts in business.

EXAMPLE: Instead of doing a full-blown NDA, parties could agree, in an email exchange, that Party A will keep Party B's confidential information secret in accordance with the [name] Confidential Information Clause — presto, an enforceable NDA (in most jurisdictions).

I'll be posting the whole thing online for free under some kind of Creative Commons license, in part for my students, and in part in the hope that if people start to use it, eventually I won't have to spend so much time reviewing random contract language for clients.

The current corpus includes clauses for confidentiality; consulting services; software warranties and disclaimers; limitations of liability; terms of service; payment terms; referral payments; channel partnerships; consulting services; indemnity ground rules; and other things.

I'm trying to follow (part of) the Unix philosophy: Each clause should do basically one thing, and do it well, with as few dependencies as possible (maximize orthogonality).

The materials also have numerous planning checklists for spotting issues that can come up.

The clauses incorporate typical wish-list items that work for both sides. In a prior life, I was the general counsel for a software company, and customers' lawyers liked that balanced approach very much because it reduced their workload; our sales people likewise liked the fact that the balanced approach helped get us to signature sooner, without screwing around with anatomy-measuring, "art of the deal" game playing.

The clauses are extensively annotated with citations to real-world cases where problems arose — sometimes, big problems — explaining how the clause language seeks to avoid the problems, again in ways that work for both parties.

For improved readability, I'm using Python-like indentation to avoid long, wall-of-words paragraphs of dense legalese. (That's proving very popular with my clients' business people.)

HERE'S THE QUESTION: Apropos of the "Invert" subject of the posted article, should this contract framework be positioned as:

1. a vitamin — "balanced, readable terms to help you get workable contracts to signature sooner,"

or

2. aspirin - "learn from others' failures by adopting the [name] framework in your contracts."

All input gratefully received.
There Is Nothing Wrong With a Traditional Career
I disagree strongly here - there really is no incoming pole in the government and the outgoing pole is incredibly ineffective. The US (as an example) doesn't have the ability to effectively decrease monetary supply by simply failing to redistribute taxes - the total national wealth of the US is currently 105 trillion[1] while the total tax revenue is somewhere in the 3.5 trillion[2] range - it would take 30 years to cycle the full value of the US through the government at the current churn rate, the GDP is significantly smaller and (at 22 trillion) would likely take six years to fully process.

Money can be thought of like a battery - sorta, but more like a bank of batteries - each one of us has a certain earning and spending potential that constitutes the voltage we're contributing to the economy - and it's all of us tiny batteries that contribute a much large proportion to the over all monetary flow than the big contributors like government (who are, by comparison, in the minority).

1. https://en.wikipedia.org/wiki/List_of_countries_by_total_wea...

2. https://en.wikipedia.org/wiki/United_States_federal_budget
The following articles also go into more detail:

- https://web.dev/coop-coep/
- https://web.dev/why-coop-coep/

although I think the Mozilla article in the OP is a really nice, succinct high-level overview.
The big issue I'd expect you to hit is that you're doing ML without CUDA, and there's just inherent problems to working in an environment where your hardware isn't the first-class citizen.

ROCm/HIP/HCC is a broken ecosystem as of today. The 5700XT launched last year and still doesn't have support. I have some faith that they're going to get it straightened out in the next year or so, but today you're just asking for trouble if you're trying to use pytorch or tensorflow without being on team green.
I highly doubt reform will be high on the list of priorities for a corrupt regime in decline. I would expect that the poor and middle class would suffer far more and first.
The upshot here is that choosing the max entropy distribution as your prior isn't enough, you also need to choose some particular way to formulate the problem. Particular formulations (travel time vs. speed, here) imply different max entropy priors, even though the formulations are equivalent. Worse, there are infinite equivalent formulations, all with different implied max entropy priors.

You can get around this by choosing a non-max entropy prior, like [1], or by deciding on the One True Formulation for your problem. But (Bayesian) updating on the other formulations of the problem won't do it, because there isn't any information in the other formulations -- they're equivalent (by def).

[1]: https://en.wikipedia.org/wiki/Jeffreys_prior
Winning the lottery won't ruin your life
Open source software prompting a license popup is actually an anti-pattern, a common mistake. Open source software under a license like the GPL or MIT/BSD should never throw it in a click-through EULA in the installer, because those licenses are copyright licenses, and the disclaimers aren't legal requirements to use the software (you don't need to agree to them to use it, they are just legal boilerplate).

However, the AGPL is an EULA, so in fact it should be included in click-through screens in insallers, unlike every other open source license.

The AGPL doesn't require you to distribute modifications only if you distribute the software (that would be a copyright-based requirement and it's what the GPL does). It requires you to distribute modifications if you offer access to the software. That's a huge difference. And as I wrote in the other comment below, the interpretation of "making medications" is horrendously ambiguous, and can be interpreted in two way: in one way, the AGPL doesn't offer any protections over the GPL (so it's useless), and in the other way, every user of the software is using a "modified version" and thus required to offer it to any downstream users they provide access to the app to.
For more evidence consider magazines from the front counters of grocery stores. That stuff is at grocery store checkouts, by popularity it's more representative of what people like than say... pg's essays.

That Snapchat's (curated!) discover tab looks like that suggests to me that this content really is just popular with people and even human editors recognize that.
How do you handle a useEffect that relies on state, but you don't want it to run on first render? I usually have a separate state that is "firstLoad" and toggle that in the effect and exit out, then its free to run on successive invocations. But typing this out - it makes me the think the dependent state itself should be driving if it runs or not...
Cyclon Distributed Data Framework Using Arrow
Hands-on: The $300 Kano PC, a “build-it-yourself” Chromebook competitor
In Chrome we already require these headers on mobile, and plan to require them on desktop soon.
This is a Shenzhen company, they probably know 100 different local smartphone OEMs and can order directly from them if they wish.
Are you working on expanding beyond US nonprofits? That would be a requirement for competing with Benevity for customers that are multinational corporations.