skysight-inc/HackerNews huggingface dataset:
There seems to be some of kind of bias in establishing trust when it comes to quality. If someone sees a high quality work, the judgemental fuse gets triggered and the person who is judging probably tries to give them priority compared to someone who hasn't.

I had a discussion with a friend and he gave a good example. There are some people (A) who do 55% of the work (5% more than the expected) and display that in really good quality. Then there are others (B), who want to achieve 95% plus but end up getting 45%. Now from the perspective of someone who doesn't know what is going on, the 55% seems to be doing better than the 45%. Therefore, the person A will now snowball into a more opportunity, while person B gets discouraged because they wanted to do hard thing.

So, instead if B did what A did in a good way, the trust and judgement of B would have increased. There is no reward in society for trying and "failing". There is only reward for taking risk and succeeding. Probably it incentivizes people to follow into a path that can attract others.

Disclaimer: These are my opinions and they have their own biases.
I sorta kinda agree. This landing page likely does well to someone who has just spent half a day ticking each checkbox on their tech stack list with the best library they could find, and then finds this project claiming it has done all that for them. And integrated them already, so they can readily build apps for the use case they have in mind. The pitch is the tech stack itself.
In the summer you have both effects - you have more direct sunlight (more vertical angle/less atmosphere attenuation) as well as the longer days. The higher apex of the sun in summer is a sign of the former as well as the latter.
People would complain that they drop needles, that birds hang out in them and crap on their cars and sing loudly in the mornings, that they block their light, that they are scared they will blow over in a storm.

No, people want tarmac, concrete, astroturf and air conditioning.

I see this everywhere I go. Nature as an inconvenience, something to be opposed and complained about. Just watched them hack down and mulch a 500+ year old chestnut here because it dropped fruit on the road and someone complained. Never mind that the chestnut had been by that road for longer than modern France has existed. I’m sure they can plant a laurel bush and nature will heal.
Not if AI steals your job, then your backup job, then everyone's plan C has 1000x more applicants than openings, then rent doubles again, you can't afford art supplies, but you can watch YouTube videos of other people doing art (with ads) and ChatGPT can tell anything you want about art supplies you'll never be able to afford again.
For K- and J-pop concerts it is not unusual that tickets sell out or nearly sell out during fanclub presale.

Only memberships over a certain age before the concert get access to presale, and name on ticket has to match at the door.

It sucks if you are a fan of the music and don't want to be part of the whole idol worshipping part of the business, but my impression is that there is very little scalping going on.
Do you consider the rewrite a good decision because it helped increase profits or for other reasons?
> I think I have a reasonable fear that `npm ci` just for the Dagger pipeline will hit multiple minutes, and then developers who expect linting and similar short-run jobs to finish within 30 seconds are going to wonder why they're dealing with this overhead.

I was going to reply that you misunderstand how Dagger works: that your pipeline logic typically requires very few dependencies, if any, since it can already have dagger build, download and execute any container it needs - with free caching. So your “npm ci”, although technically not free, is a drop in the bucket and easily offset by the 2x or even 5x speedup that is typical when daggerizing an existing pipeline.

All the above is true… But I realize that the documentation you link to contradicts it. Reading these guides I understand your fear. Just know that these guides are, in that respect, giving you the wrong idea. In a more representative example, instead of importing a GCP client library, the script would have dagger run a GCP client in a container, with the appropriate input flags, config files and, if needed, artifacts. We will fix those guides accordingly, thank you for bringing this to my attention.

Also, soon Dagger will do exactly what you were expecting: it will execute the “npm ci” itself, in a container. So whether that script’s overhead is 3 seconds in the typical scenario I described to you, or a few minutes in the scary scenario you described to me: either way it will get cached, and either way it will have no host dependency on npm or any other language tooling: just the dagger CLI.
एक बार अपना लंड चुसवा लो
Immunotherapy is the direction we want to go, but Car-T therapy can kill the patient.

Old school chemotherapy still works as a first-line defense, and the newer stuff is getting better (paclitaxel, antibody drug conjugates (ADC)).
Hi, I am the guy who did the research. I haven't done enough analysis to see if DGA domains are skewing the sample, or more like which way they were doing it. It could be that all those domains are dormant and don't have DNS, but it could also be they are hosting a bunch of advertisement. It's a whole separate project that requires building out a more sophisticated scraper.

As per the conclusion, well, forgive me for trying to entice the reader to try the product :) Always Be Selling, right?

We did the research without trying to sell anything; it was just interesting. I'd do more, but it takes a while, and I am tired of this space, for the time being at least.

ps. It also takes forever to get the data. I had a local Clojure script running of my macbook pro, doing 10 parallel queues at a time, for what seems like days on end. At some point, my ISP (or something in the chain) suspended my access to a bunch of websites. ooops!
I'd love for this to also allow for shades of gray (the Fallout 1/2 bitmap font is antialiased). It would likely mean harder OTF exporting process for you though. Color fonts are still not supported everywhere, my last attempt ended up with PNG-in-SVG in the OTF.
Do you think it is the difference between hardware vs software?

The competition for hardware is fierce, so margins and profits are low.
Is it their fault that VC goes to SaaS and pointless startups as fast as flies go to shit ?

$120k/yr is a very good amount of money. The problem is the inflation of the tech sector because the second dot com boom we are experiencing
I tried figure out what I can build with this framework (web apps? native apps?) and what programming language I have to know to use it and after few clicks, also into doc, I gave up.
My general understanding is that a fiber is a lightweight thread, and conceptually can be implemented inside any program that wants to schedule its own fibers.

They’re distinct from CPU threads.

When I last dived into fibers I discovered windows was trying to make them a thing quite a while ago which is why we have things like [0].

Fibers being virtual threads, are recursive. In the same way you can run a VM inside a VM, you could build fibers on top of fibers (which sounds like a recipe for unpredictable performance).

[0] https://learn.microsoft.com/en-us/windows/win32/procthread/u...
I have worked with large django codebases.
If they are not managed correctly, you usually get a big pile of pasta.
I have written some tips, how to tackle such mess.
There was another news bit recently re: polyethylene glycol, to reduce the damage done to healthy cells.

https://penntoday.upenn.edu/news/suit-armor-cancer-fighting-...
They prefer term "domain investors." Honestly, there are a few that figured out how to make money doing this, and there is a whole bunch more that bought into the idea, but have never made anything out of it.

If you are curious, I did some calculus on what it takes to make good money in domain investing, and it's not pretty. https://smartynames.com/blog/business/NTJmOWIxNzAt

You will make a small fortune investing in domain space, if you start with a very large fortune.
The Shape of Things to Come – Jonathan Ive [2015]
I used to have an app that could display my iphones contact list in reverse chronological order.

That was very helpful for "what was the name of that guy I met yesterday at that conference?

The app I used has long since been abandoned, and the niche seems littered with scammy apps.
Right, we're not on Stack Overflow. So stop posting Ask HNs.

Read those two threads. They have lots of comments on how people have been using or not using Threads and the trend in usage/DAUs etc and how ppl see the social media evolution.
I'd be curious to see actual benchmarks of Kagi against DuckDuckGo and the Searx alternatives.

I've heard good things about Kagi, but I've been happy with DuckDuckGo for a long time. I'm not going to spend a lot of effort into considering to switch to Kagi unless someone can show me that it is measurably better and faster than DuckDuckGo, and is worth the price.
What the fuck does this have to do with the price of eggs?
Listened, or got beat into submission?
Text editing on mobile: the invisible problem
But people buy stuff everyday that they never actually use. Why should tickets be sacred?
In Defense of Stale-Bots
Russia sent the first man to space as an underdog. A country with a population of 1.5 billion only now sent something to the moon.

You cannot compare these.
If I understand well, is it a Model-Driven Development (MDD) framework? If yes it's quite nice to see some people are working on that.

The only famous tool I heard about it was some MOF Plugin on Eclipse IDE.
And at a different level but kind of the same philosophy, Jetbrain MPS (but more focus on the DSL part).

I am not sure yet if I adhere with MDD principles, but at least it's good to see a modern tool to try it out.
Windows has its own fibers facility which does some things for you but still leaves the scheduling to the application so it's still fibers. It's a little confusing in the article but they look at the Windows API as a kind of API template - what do you need to implement to have fibers. Then they describe their own implementation.
elim is mile backwards?
Not interested. I would feel bad for overcharging people and getting rich from that. And if I would charge them the actual costs, then I would mostly just destroy that guy's business and save some thousand people each a couple of bucks on some utilities that they almost certainly do not really need and are voluntarily paying for.
Or a garbage denier
> Isn't it fixed during the decoding process though?

For Wuffs' image decoding, it's flexible up until decode_image_config returns. It's fixed afterwards.

In practice, that works fine for BMP, GIF, JPEG and PNG (and I'm confident will work for WebP too). No in-situ dynamic allocation (with or without sugar) needed. Even though, for the libjpeg-turbo C code, `grep mem..alloc_ jd*.c | wc -l` shows more than 50 "allocation" call sites, Wuffs' JPEG decoder does just fine with just the one work buffer.
I have to be honest I am a bit skeptical at that. That is more than a 2 star general with 20 years of experience gets. I know there are special pay bonuses but I have never heard of any that high. How did they manage to get a 200k salary for a role given the military/government's pay schedule?
So I think Inmight have the ticket market worked out - it's been puzzling me.

So we can easily solve ticket allocation on a "fair" way - London 2012 olympics was a good example. Everyone who wants tickets for an event signs up and there is a (verified) random selection and the lucky winners paid (I think) a tenner.

This is because there was no profit maximising incentive for the Games - it was a PR exercise for UK government.

Now for a Taylor Swift concert there is profit maximising.
I am going to say here it's Taylor's manager who is the cackling moustache twirling villain of the piece to avoid upsetting Awiftians but hear me out.

Profit seeking manager arranged a contract like Katy Perry below [0]. This basically is a leak showing Perry arranged to be able to sell her own tickets to "resellers" - ie people she knew would sell on StubHub for higher than face value.

But to protect his clients reputation he wants to keep this selling of tickets at high prices a secret.

So imagine there are 1 million tickets for a tour, over 50 days at 20,000 tickets per event (no idea of this is right seems ok-ish). Then hold back 10 days (added by extra demand!) and then only sell say 50% of tickets at the low price, there are say 400,000 tickets available to fans. But release them slowly - extra demand / seating allocation, verifies fans first etc etc. The point is to guage demand - if 1000 people try to buy tickets on day 1 for a stadium, and only 500 manage to get through the process you know there are 500 disappointed people out there so sell the other 50% for that day on that stadium to reseller (your mate) who will go on stub hub or ticket master selling to people who just missed out and will pay higher prices.

finally a market that makes sense. Why is the process slow, awkward, convoluted? Because it's a signalling mechanism for reselling you higher priced tickets without affecting the reputation of the client

[0] https://www.vulture.com/2011/05/katy_perry_reserves_the_righ...
Duplicate https://news.ycombinator.com/item?id=37630338
It is the other way round actually. There are no reports from L2 (and there are no other systems in the field in numbers) because people take over before something happens. If the drivers would not have been there, we'd see all those accidents.
Worst Case Optimal Join Algorithms.

Tecnically they started in 2008 with the AGM bound, but most meaningfull algorithms have been developed after 2012.
To be a bit pedantic, the dangerous effect of the vacuum of space is the lack of oxygen and rapid suffocation, apparently within seconds: https://en.wikipedia.org/wiki/Effect_of_spaceflight_on_the_h.... The other effects (like ebullism and freezing/overheating/sunburn come "much" later in minutes).
> On Saturday, September 23, at 6:50 A.M. UTC (2:50 A.M. EDT or 11:50 P.M. Friday PDT), the sun will be directly over Earth’s equator, which is how astronomers define the equinox.

Article starts out by specifying the time of the event
This looks great. Is there any way this can be integrated with bank accounts, credit cards and mutual fund transactions? In India specifically?
My parents spent quite a bit of time in Perth, and I went over for a holiday a little while ago for the first time (I live in the ACT). I hadn't expected how far it feels from the rest of Aus. Of course, I knew it, but it's different when you're over there.
Google loves to mess with other browsers, in ways that evoke plausible deniability:

https://news.ycombinator.com/item?id=29551802

https://news.ycombinator.com/item?id=20658912

https://news.ycombinator.com/item?id=17606027
Let the concept of nations and borders die with the 21th century.
Surprised neither the article nor anybody in the comments mentioned that the event inspired the movie Agatha with Vanessa Redgrave and Dustin Hoffman. It's at least not bad.

https://en.m.wikipedia.org/wiki/Agatha_(film)
> Fibres, goroutines, promises, futures, job queues, etc, are poor substitutes for Actors.

They are not necessarily substitutes, they are lower level primitives that allow more complex models, like Actors, to be implemented.

All execution models have trade offs; and sometimes we might prefer an execution model without deadlock, livelock and starvation. So for a general purpose language, a complex model like Actors is ideally a library and not enforced as the only way of achieving concurrency.
Thanks so much for the extra detail! That's great news about them finally adding support for the camera.
I hadn't thought of this part. I don't think that's the only limitation, though.

Even with a spherical planet, no atmosphere, and 0-diameter sun, there might at most be a circle on the planet that experiences equal day and night.

The planet, after all, is still rotating around the sun as it is rotating around its axis. It doesn't stop rotating around the sun at precisely the moment that the Earth's axis is orthogonal to the Earth-sun gravitational vector. Hence the day and night lengths are continuously changing, not changing once per day.

So I imagine that there is at most a path/line/circle on the Earth's surface that has equal night and day by this measure, and at a minimum, a point, but I'm not mathematically inclined enough to calculate this.

Edit: Same line of reasoning: https://news.ycombinator.com/item?id=37629367
I think it’s more complicated than that. It’s not just incentivised stuff from intel. There is little to no market for high end stuff from AMD. Some vendors tried and it didn’t sell. Most of the workstation consumers I know won’t touch AMD after a couple of bad experiences. Even had one myself where I had to dump an AMD desktop because of reliability issues which went on for months.
Looks like chat-gpt generated. Too many generic buzzwords, too few actual information.
Me too, if I had to choose between a rich thief and a poor thief, but I'd still like to be asked first.
Sounds about right.

But all they need is a little paragraph giving clear context to technically literate people, of what they are looking at. A chance to educate is not to be thrown away lightly.

I actually want to know. My work takes me places. If I am on a page today, I might need what they have tomorrow.

I am sure they tried, but it is frustrating, and feels myopic, which probably isn't the TLDR/buzzword they are going for.
Totally get your point. I'm not just concerned with support itself, but durability. I had experiences of printing for 24H for a couple of years, and Minis can do that with minor servicing (from time to time the nozzle requires to be changed, the PTFE tube inside the hotend, too. In one of the Minis the thermistor stopped working. Easy tasks, and if you have 3/4 printers you just remove one from the line for a couple of days). Now, the A1 looks solid, but there is to see if it is solid and if the printing speed it is tuned for will not ruin the parts soon, if printing a lot.
From the code samples it looks like it might be Ruby, but the documentation doesn’t seem to confirm or deny it either way.

EDIT: I accidentally clicked on the ‘past submissions’ link on HN, and if the titles of its other submissions are to be believed, the language is actually Elixir.

EDIT2: Yes, it’s probably Elixir — the front page mentions it once or twice (though not prominently; I had to search for it).
I want to think of marketing as a way of providing valuable content and explaining why your product might be just what the consumer needs (potentially helping them with their problems).

What's described above really doesn't fit into this view, but is definitely how I've seen people "play the game". ChatGPT-generated fluff, copied content, and the same tips & tricks, inspirational stories, etc. you see repurposed all the time on different platforms - especially LinkedIn.

I hope marketing can be good and value-adding but, the way it's going right now, we're due for a change.
It did. Both the EU and the US slapped Intel on the wrist years ago.

Now we're "fining" them a few million while pumping billions because we "need fabs in Europe". We do, but not theirs

It's entirely wrong to give money to intel, whoever you are. They are the devil and have treated us horrible. These guys deserve nothing but contempt
Not really, a transient ipfs node works just fine.

There are stable nodes to bootstrap a new node into the network. More initialization that if you were using http, sure, but it isn’t as against the grain as you suggest.

https://github.com/ipfs/ipget
The trick here is to get the hell away from JSON quickly. I only ever use jq to turn JSON into text and then use my crusty old tools on that.

If I’m working on my own thing I’ll use a text based format.

Although recently I parsed json out with head, tail and sed. It was numeric data nicely formatted in lines so it was easier to just remove all the semantic structure than actually parse it.
Cranks are a scourge…
For those wanting to do this programatically: pip install tiktoken
> What we lose is simply not worth it

Can we take a step back and think about what we "win" with "inline pictures, colours, links and tables"?

> for the point 1% of people who use mutt.

It's not only using mutt. There are actually quite a few things that you lose by using HTML e-mails. You just don't know them, and so you consider that the way you use e-mail is the best.

Not saying that you are wrong, and maybe 99% of users actually don't want to use e-mail like those 1% you mention. But before you say so, it would be great if you considered those use-cases that you don't know. Because maybe those 1% using mutt have a valid point :-).
Intel fanboi alert
Bolt's AR Snapchat Lens Reimagines Cities with Fewer Cars
This topic is underrated and extremely important in YOUR career. Youngsters believe rewrites are for old people who didn’t get their code right.

Business apps only last for 15 years max. Every app requires a rewrite after 10 years, apps that don’t do it weren’t actually important for business.

Software stacks are flimsy. Apps need to support NPM, then Kubernetes. There are new security discoveries and way to prevent them. How do you list your libraries if you are not using NPM? Also we need to move the app to the cloud because installed software is not fashionable. The original software may be reasonable, but assumptions and expectations change.

Why don’t we see them more often, then?

The response is: Because they are worded as “Brand new app from scratch” in job descriptions, and because NPM hasn’t finished its 10-year cycle yet. But rewrites they will come, and you better be have a methodology for that.

When you build an app, one day, a requirement will be to make apps easily rewritable.
https://github.com/WooooDyy/LLM-Agent-Paper-List
The first rule of rewrites is don't. That is almost always the correct decision. Like Lucy and the football, if you're sure that this rewrite is different, you need to consider how that'll happen.

If you build in parallel, you need to decide what work will go into the existing system and how long the new system will take. Do you pause new features? If yes, I guarantee you that'll be an issue. I also guarantee it'll take longer than you think it will. If you don't pause new features, you'll be chasing moving goal posts so it'll take even longer. All of this is significant extra effort that you have to hope to recoup somehow with the new system.

Remember that it won't take that long before your new system is also considered legacy.

Once you have that new system, how do you deploy it? Dropping it in place is generally a high-risk strategy that'll greatly slow your migration.

Instead of the above, what you generally want is to do partial rewrites in-place using infrastructure you may need to build but you'll want anywhere. Here is the progression of, for example, a backend migration:

1. Double-write to the old and new backends. The new system is just a dummy, eseentially. You won't be using it (yet). Do offline verification on the old and new backends. Look at metrics for double-writes vs single-writes (eg latency, general performance, crashes);

2. Start reading from the old and new backends. Do a comparison of the data retrieved from both. Log and flag any instances where the data differs. You've now verified the new backend;

3. Start reading from the new backend;

4. Stop writing to the old backend.

This requires things like a robust experiment framework so you can, for example, double-write for 1% of your users and then compare the two groups easily across a wide range of metrics to see if there is any unexpected regression.

The point of all this is you can do partial rollouts of any of these steps and, more importantly, a rollback is trivial.
At some point, it is good to die, to make room for the next generation, no matter how great you are. Others deserve a shot, too.