jkeisling/hacker-news-corpus-2007-2022 huggingface dataset:
I think the more important aspect of that quote is just about performance vs. code. I see many cases where people are hyperoptimizing on whether or not their framework consumes 2 or 15 microseconds per request when the work they are going to do takes 100 milliseconds.

If you like the async style better, then fine, use it. Sometimes you win like that, where the thing you like better is also faster. But don't worry so much about the performance.

Web frameworks is another place I see this a lot. Crossing the streams, if you've got an incoming web request, unless your framework somehow consumes and discards the web headers, a real web request is already many kilobytes just to represent the incoming headers by the time it gets to your handling code. Using async because it has ~200 bytes per task vs a thread allocating 10K out of the box at that point doesn't make much difference because the HTTP request itself is blowing out the difference.

The spread in orders of magnitude in what is expensive and what is not has gotten so significant on modern systems that you can easily get developers sitting there optimizing nanoseconds while throwing away seconds. The old school assembly-style premature optimization where we're trying to save every bit and cycle has mostly passed away, but its replacement seems to be this; frantically benchmarking how many millions of requests per second some framework or feature can handle as if it matters when your code is going to take 500ms.
This essay also left lots of room for a non-religious person to adopt the same kind of non-ownership mindset. Maybe we should infer that this kind of happiness is something that could be cultivated without religious faith.
(Context: I'm a very bad chess player, but have been getting into it lately.)

I think we're fairly certain that chess players today would beat chess players of the past, in a regular 1 on 1 game. Assuming the old chess players didn't have time to prepare.

Chess programs can rate the accuracy of moves, so we can see how accurate past players were. In addition, a lot has been discovered about more correct opening theory - a grandmaster of the past would make many mistakes in the opening that a modern grandmaster would be able to take advantage of, simply because they didn't know those lines.
Join a gym with a spin class

25-50/mo. Tops.

20-40 per class is robbery.
At Hotswap, we're working on a migration from Typeform to Tally. If you're interested, let us know here: https://www.hotswap.app/migrations/typeform/tally
Source? According to Wikipedia, quite a few companies have an architectural license with ARM, including Intel and AMD. Maybe Apple gets a discount?

Apple may have been a founding member, but they don’t own ARM, and I’m assuming that ARM still wants to make a profit off of its licenses to Apple.
Are you possibly mixing this up with the Apple Card "request new card number" feature? In general, creating a new token requires deleting and re-adding a card.
We Germans seem to love our cold hard cash, so the incentive to get a card reader is lower. There are even automatic coin counting machines in some self-checkout desks...
Did you use KDE when 4 came out? Wow was that buggy. To me, it's all so much better these days that even if some plasma releases have regressions, they don't hold a candle to the issues I experienced with KDE 4.
Cars are getting opener, so we don't foresee needing to worry about the roads.
I upvoted it so that it bubbles to the top where it can be easily seen. Not sure if that's the motive of others.
W3C used to recommend the title to be less than 64 characters in length: http://www.w3.org/Provider/Style/TITLE.html.
I lived in Italy for a few years (Northern). Generally the portions of pasta that you ate were relatively small. You also ate a lot of fish, stews, and vegetables.

In regions of Italy that DO eat mostly carb loaded diets (like Sicily) there has been a relatively long running obesity issue. Walking is important, and it's a great thing. But even walking several miles a day does little to combat obesity when you're offsetting it with thousands of calories of carb-loaded food every day.
Yeah, the part where he wants to form some kind of Randian society in space and this part:

"Since 1920, the vast increase in welfare beneficiaries and the extension of the franchise to women — two constituencies that are notoriously tough for libertarians"

seem to be pretty good indicators that the article is completely terrible.
This is particularly awesome because my Cr-48 came with a piece of paper that said something like:

"Do not crush, incinerate, blend (guess we'll never find out if it'll blend...), ...(several other things)..."
Yeah, it was totally third-party, and labeled as such. I have no idea how the technology behind it worked - I was just a user, not a developer.
I thought this was going to be about booleans from nothing at all:

true = function(x,y){ return x; }
false = function(x,y){ return y; }
ifelse = function(x,a,b){ x(a,b)(); }
not = function(x){ return x(false,true); }
and = function(x,y){ return x(y,false); }
or = function(x,y){ return x(true,y); }

bool = and(not(true),or(true,false))
ifelse(bool,
function(){ alert("true!") },
function(){ alert("false!") }
)

Amazing, isn't it?

It gets better.

Pairs:

pair = function(x,y){ return function(f){ return f(x,y); } }
fst = function(p){ return p(function(x,y){ return x; }); }
snd = function(p){ return p(function(x,y){ return y; }); }

Unions:

left = function(x){ return function(f,g){ return f(x); } }
right = function(x){ return function(f,g){ return g(x); } }

Pairs combined with unions make lists:

cons = function(x,y){ return left(pair(x,y)); }
head = function(l){ return l(function(p){ return fst(p); }, function(n){ alert("Can't take head of nil"); }) }
tail = function(l){ return l(function(p){ return snd(p); }, function(n){ alert("Can't take tail of nil"); }) }
nil = right(false)
isnil = function(l){ return l(function(p){ return false; }, function(n){ return true; }) }

map = function(f,l){
return ifelse(isnil(l),
function(){ return nil; },
function(){ return cons(f(head(l)),map(f,tail(l))); })
}

filter = function(f,l){
return ifelse(isnil(l),
function(){ return nil; },
function(){
return ifelse(f(head(l)),
function(){ return cons(head(l),filter(f,tail(l))); },
function(){ return filter(f,tail(l)); })
});
}

Isn't it neat how you can build everything, including conditionals, booleans, pairs and lists from functions?

Note that this code was not tested in any way, so it likely contains bugs.
A critical point missing from the article --- bitcoin and the "exchanges" which form the crypto marketplace are _not regulated_ by government.

This makes the crypto markets very fertile grounds for both sophisticated wholesale manipulation and simple scams that would never be tolerated in "regulated" security markets.

One of the simplest and most popular scams is the "pump and dump". For example:

The pump --- A famous, wealthy entrepreneur announces with much fanfare that he has just purchased a large quantity of bitcoin. This enourages naive "investors" to purchase too driving the price up 20%.

The dump --- Famous wealthy entrepreneur then sells his large quantity of bitcoin and realizes a 20% gain.

If famous wealthy entrepreneur did this in a "regulated" market, he would find himself in legal trouble.

If you don't understand how these scams work, _you_ are most likely one of the people being scammed.
> We just need to monitor which patient had the treament and which didn't, globally

And you just described the reason for a control group. We simply do not have that information. Things are moving too fast and treatments have not been standardized yet, not to mention the built in variability between locations. If you want to know if a treatment is effective, you must have to comparable groups. The point of the control group is to gather that information. Just because there are many, many, global cases doesn’t mean you actually have been able to capture the data for a control. Things are moving that fast.

> But if a doctor wants to prescribe all its patient with it, he should be allowed to

And what about the supply of these drugs? There are people who do need these drugs for other conditions (I’ve read Lupus patients sometimes need it). These patients need the drug and the supply is getting scooped up by people who don’t know (a) if they have the virus and (b) if the treatment is effective. And if it is effective, is it effective for treatment of infection or prophylactically? Just because a drug is widely used does not mean that there is enough supply to distribute it to anyone who wants to try it.

These are major issues that can be answered with proper clinical trials. We know how to do this and they can (and are) being done as fast as possible.
No, because the virus takes time. Survivors aren't "survivors" until they've recovered, so they reflect the people who "would have been" critical cases maybe 10-15 days ago. But 10-15 days ago the number of cases was (depending on which doubling statistic you use) 4x-32x smaller than what it is today.

Exponential growth messes everything up, basically. All our intuition about how things work tends to be wrong in subtle ways.
If the JavaScript bundle that is being served is built on a public CI/CD service, it could be possible to do the following, for transparency and verification:

- Include in a header comment: the build URL, Git SHA-1 of the commit, and other metadata

- Sign the bundle using public/secret key cryptography

Having the build URL and sources URL help with discoverability and transparency, while integrity can be verified with the signature.

Adversary models now shift from the bundle provider to the CI/CD platform that runs the build, and any PKI used for the public key for signature verification. If the public key is versioned with the code, it can help reduce trust to a single entity (where the code is stored).
Not GP but this video gives a good overview: https://www.youtube.com/watch?v=BtN-goy9VOY
That's basically the same for me in North Carolina, only a few things /require/ you to go in to the DMV. We do have the complication of having many states and having to support people getting a new license in the state they move to so there's a constant need for people getting new IDs which needs in person to gather the info and documents about the person.
I believe running a MacBook as an always on server will pretty rapidly destroy the battery anyway.
My package is now released. 24 minutes to go from "opening the ticket" to it being approved, and another 14 minutes to go from "first publish to staging" to it being publicly available on repo1.maven.org.

Sure, a human is still involved, but it’s definitely faster than anything else in the release process.

If there’d be something to improve, it’d be (a) having a built-in publish plugin in gradle with a publish.json that easily defines the variables and adds a super simple way to publish, and (b) automating the TXT verification akin to google-site-verification (plus potentially github oauth login to validate com.github namespaces).
well, not the whole url, obviously, otherwise the router wouldn't know where to send the request
"A push on the git repo" is not something I would think trivial for a non-tech person. However, netlify also supports just drag-and-dropping a zip onto the dashboard. That's probably as easy as it gets.
I don't really understand how an E2 works if starting a new company.

Yes the company has approx $700k real revenue.

So getting started, could be as simple as paying a few hundred dollars to incorporate a company in the USA, and redirecting $150k of revenue through the new company. (easy to do as it's an online company).

Or am I grossly oversimplifying this?
I'm incredibly curious about how they're planning on monetizing, considering that that recent stab at pushing micropayments was a major flop. Ads that aren't full-fledged 'snaps' (and don't feel spontaneous) seem like a sure way of pissing off their userbase. Stories seem like an effort to push for fb's ads strategies, but whether this will pick up and become a real competitor is questionable.

Props to them for not getting acquired though, and pushing on.
I agree - whys are very important. I try to document why I do certain things with comments.

That said, is there a such thing as a commit message too long? If I were to include the thinking behind code I would have some commit messages over 500 lines long.

Currently I just create an Evernote note for each change I make, which documents all the whys, the research, the issues, pros/cons, etc. with a given change. The commit message usually gets a much briefer version of it.
It seems to me that the Amish approach starts with prejudice and outright rejection and leaves no scope for experimentation and trial dry runs of new tech. The author of the article urges reflection, but completely misses the importance of experimentation.
https://news.ycombinator.com/item?id=8811252
I doubt the author has read even half of the papers he listed.
Obviously, they would have to proceed to ban PHP (since it allows to write such software), Apache (allows to host sites), Linux (the same), any OS supporting TCP/IP and finally conclude by going the North Korea way and disconnect themselves from the internet. That or people of India wake up and give those cretins long overdue kick in the ass and get some bureaucrats that are not completely insane.
Governments are particularly vulnerable to the sunk costs fallacy, especially when the press can't distinguish between operating cost and capital cost and operates on an annual budget cycle. My go-to example is the whole Nimrod MRA4 fiasco, which involved discovering that aircraft made 50 years ago had non-interchangeable parts that didn't match the drawings. The Nimrod airframes were not airworthy and could not be made airworthy in a cost-effective manner, but nonetheless kept flying for years until one caught fire in midair with the loss of all aboard.

Edit: far more than you wanted to know on the subject https://sites.google.com/site/militaryairworthiness/
"Java is fast for long-running applications. Once the JIT kicks in, important code is natively compiled. This is why Java is big in the server space, and not so much for desktop applications."

Java is a pain in the server space. The memory footprint is bloated, so cache locality tends to suck; it's prone to nasty garbage-collection pauses (hello, latency spikes!); and now instead of one process that can crash or go funky (your code), now you've got two (the JVM and your code). And that's just the tip of the iceberg.

I honestly don't know why people started writing server software in Java, but I wish they would stop (I'm looking at you, Apache project). There's absolutely nothing that Java is "good" at that couldn't be done better in other languages...except for allowing teams of mediocre developers to write frameworks for big software bureaucracies.
It has helped me find things that all other services have failed, and I can get an idea of what it is / what category it is in before visiting the link.

I never used the social aspect much, but the public aspect is wonderful. It's a fantastic way to find related sites.
Congratulations, and thanks for the inspiring article. I have had an idea on the go on and off for a while now and this is inspiring me to get off my butt and finish it.
> There's an easy solution - have syntax that turns off parsing (a nowiki type syntax).

Okay, that's fair, but CommonMark standardized de facto standards -- it was born as Standard Markdown after all -- and AFAIK there's no de facto standard here, so it would be pretty dangerous for jgm to pull something out of thin air. I can see why there's reluctance here.

(IIRC fenced code blocks were pretty widespread before CommonMark, and even if not, being part of GFM would almost make it a de facto standard. Note that CommonMark was a joint effort among GitHub, Stack Exchange, Reddit, etc.; SE's <!-- lang --> solution was atrocious, so GFM fenced code block was an obvious win.)

Also, code blocks with language specification is apparently of way higher importance to programmers than typeset math, so comparing the two isn't that useful. (I say this as a physicist who breathe typeset math.)

Now, going back to

> you can't use this together with code blocks containing $ (meaning it doesn't work for languages like PHP and R).

Why do you need to typeset math within code blocks or code spans? Code blocks and code spans are verbatim by definition. Interpret $ inside code blocks and code spans as verbatim; interpret $ outside as LaTeX delimiters. Problem solved. Maybe I'm missing something.
Probably more indicative of the amount of usage it got vs the data it generated for them
Hi, F-350 owner here. My wife and I's other car is a Prius.

In addition to woodworking and desiring a truck bed for that, we tow a camper with which we can boondock (dry/off-grid camp) via solar power. I purchase carbon offset credits for our trips. Not ideal, but better than nothing. I have not modified my truck in any way, especially not to "roll coal", and I report others that I see doing that. I take pride in my truck passing emissions tests and would never attempt to defeat ("delete") those controls. I would never consider blocking a charging station, and in fact we almost bought the Prius Prime plug-in hybrid when it was first released but it wasn't available in our area yet at the time. Otherwise my other car would need those chargers. We also take the Prius as much as possible, and only use the truck when necessary. I enjoy hypermiling in the Prius, too. I hate that diesel trucks like mine create other non-carbon pollution like NOx so I try to only drive it when needed, and would gladly adopt new hardware to reduce those emissions further if it didn't hurt overall efficiency. I also would love for carbon-neutral (or at least carbon-reduced) biodiesel that doesn't come from destroying palm tree forests to be an option until EV trucks are more available. I have other truck-owning friends that are also not obnoxious intentional polluters that hate EVs. Anecdotally at least, my friends and I are the exact market for the Tesla Cybertruck. My gut feeling is that there are more truck owners that think Teslas are cool and want one than those that block charging stations.

I guess my point is, next time you pull up behind a heavy-duty truck, it could be me, a vegetarian EV/hybrid lover driving a carbon-offset, emissions-compliant truck on their way to go off-grid camp via solar power, waiting for the Cybertruck to launch.
It would be nice if this tech was open sourced.
Can you elaborate on the similarities? I don't really understand PS, CUPS, or GCP, but I think an overview of how they relate would be really interesting.
>Does the US not have pedestrian safety standards?

I don't know what it is like outside of the United States but here everyone has the common sense to know "don't walk in front of moving vehicles" as you are taught as a child "look both ways before crossing" over and over and over.

You can put all of safety features you want on a vehicle, but if they hit a pedestrian there is a VERY good chance they will die. That's a lot of force and a little bit of rubber or plastic won't make a lot of difference, I say this as someone that lost a very dear friend to a hit and run as a pedestrian and lost another friend this year that was stationary on her motorcycle and someone rear-ended her and killed her (effectively) instantly.
Funny; I agree with the conclusions of the article in general, but not in their specific case. As long as you're looking for "original and heterodox" ideas in the field of Virginia Woolf (1882-1941) criticism, an example I did not make up, you might as well be nice about it. This guy deals in subjective issues full time, being a critical ass is sort of silly when there isn't a right or wrong.

In engineering and science it's important to be critical and for all ideas to stand up to the sandblaster of truth. But in literary criticism? Seriously?
They're not a product company. They're an advertising company.
This may change, but that does not mean all their efforts should be put towards changing it. They're expanding and creating their existing market, while putting feelers into others.
I thought the article was going to be about doing 80's style development in 2010 (i.e. using Turbo Pascal in DOSbox/Open Watcom etc).
I'm currently working on a non-traditional "pay for downloads" site specifically targeted at iPhone apps to begin with. I have taken the plunge, registered as an LLC, and the site is almost completely built (expected launch in < 2 weeks). I will post on HN when I do launch but if you want to know more about it or are interested in being part of the launch shoot me an email at matt dot sencenbaugh at gmail

Sorry for the plug.

As far as a lite version of apps I think its a dangerous path.... I think it can be a valuable tool but only if you find the right balance between what features to include and what to lockdown in the lite version. In the end I think it really depends on how the initial launch goes. If you find that you aren't getting much traction perhaps you should release a lite version for a few days. If after a few days you notice that the lite version hurts your sales... simply remove it.
"So the bottom line is that an Aeron only really costs $500 more over ten years, or $50 a year. One dollar per week per programmer.

A nice roll of toilet paper runs about a buck. Your programmers are probably using about one roll a week, each."

http://www.joelonsoftware.com/articles/FieldGuidetoDeveloper...
I've just updated and it certainly feels slower. Menus take forever to load.
To be fair, I don't think much of "SEO Best practices". It's still attempting to game an algorithm to push crap to the top where it doesn't belong. I'm a fan of natural search results.

I just don't care to see the constant beating on any subject over and over again and it's at the point that hearing the name "Mahalo" makes me grind my teeth.

I haven't really seen much quality from what I've used of Mahalo; to me it's mostly adsense spam and skeleton pages. I'm sure there's someone out there finding it useful but it really does seem to be mostly making revenue off of adsense and SEO "best practices". If you can sustain a business off this, great.

I just don't care to see the subject beaten to death constantly. If people don't like Mahalo, then they should create something better to push it out of the way rather than endlessly whining about how much it annoys them.

When you use terms like "Hater SEOs" it just sounds absurd. I say this having been involved in part of that side of the web world in the past: SEOs are the used car salesmen of the Internet. Nobody really needs them yet their crappy late night TV Ads manage to find enough suckers to keep them in Pomade and Leisure Suits year after year.
the more I read about evolution, emergence, etc, the more I start to feel that life is almost as common as rock, and not all that much more interesting. all it needs is a highly interactive environment of molecules. water and carbon works in our environment, and I'm sure there's other ways it can be brewed. carbon based life is likely to be the most common only because of the multitude of ways that it can be transfigured.

anyway, given the right set of conditions, which shouldn't be all that uncommon in the universe, life is a matter of time, not a stroke of luck. so, in my completely amateurish opinion, I think any planet that would be immediately inhabitable (by us) would already be inhabited. however, I'm sure there are plenty of planets, Mars even, initially barren (at this moment) that we could terraform to our purposes. as I alluded to in my first comment, we're natural born terraformers, and we've done that already (in this case for the worse) on this planet.
Of course i can do that per to-do. But imagine if we have 10 or more to-do list.
Interesting, could you please elaborate more?