skysight-inc/HackerNews huggingface dataset:
The shuttle program had several problems, but perhaps the biggest was something of a "design by committee" issue. Too many interested parties wanted it to do too many things, making it somewhere between bad and mediocre at all of them, to say nothing of the costs.

To build reliable, economical rockets and spacecraft (at least those burdened with the task of escaping Earth's gravity well), you need to be able to intensely specialize and streamline them to the greatest degree possible, with what complexity remains pulling its own weight several times over. They need to be really good at one thing, with any other use cases coming as a bonus.
I see him very different since he signed off on that covid paper code.
Using agents improves this dramatically if you want to try again. Putting a linter, test runner and self reflection in the loop fixes a ridiculous number of LLM issues.
Let the enshitification of Wikipedia begin. There is NO link to the video of the interview of the defendants, and the prosecutors and politicians who supported the charges: If you watch for a few minutes, you easily recognize that 1) The defendants are rather astute, and the prosecutors and politicians are ... well... two full sandwiches short of a pic-nick:

https://www.youtube.com/watch?v=BR_v5xl4Jnw
> Some developers have problems, because they don't understand its abstraction.

I think the point of this new syntax is to lower the cost of understanding the abstraction. You keep the familiar clause syntax but let clauses be chained into pipelines in which the actual (semantic) execution order is the same as the written order.
In the olden days, these towns wouldn't pay you money, they would pay you scrip issued by the mining company[0]. This could only be used at company-operated stores, so miners were imprisoned in the towns. Moving back literally wasn't an option for the people that worked there, but if there was no other jobs around, where else could you go?

[0]https://en.wikipedia.org/wiki/Company_scrip
Forgot they had a user success list, thanks for pointing that out. Seems grim, but looks like things can only improve in the future at some point
It is essentially “don’t roll your own crypto”, but instead being screeds of complexity it just highlights a few very basic and simple things that seem “obviously fine” to folk that are unfamiliar (eg doesn’t touch on any complex reasons for it being bad, and doesn’t just say “you’re stupid”). It then gives examples of these basic problems causing real world failures, and it then just says “this is what you should use instead”.

Eg it’s very to-the-point, doesn’t spend all its time talking about how the professionals are awesome and better than you, and gives actionable recommendations. Most “don’t roll your own crypto” articles don’t do that and just come off as being elitist, and don’t actually _help_ the reader.
They're the angry stock market rodeo clown people.
Funny you mention the Habsburg because it reminds me one of the reasons pointed for the Austria-Hungary empire’s disaster in WW1. It was precisely the lack of cultural and ethnic cohesion.

The author channels a lot of clash of civilisation, which I am very fond of.
Pricing AI Products Differs from Traditional SaaS: The Complex Reality
Pricing AI products is far more complex than traditional SaaS. Here’s why:

1. Variable Costs: AI models have unpredictable costs tied to usage, unlike the fixed costs of SaaS.

2. Dynamic Usage: Costs fluctuate with demand and model complexity, requiring advanced metering.

3. Feature Access:AI needs flexible pricing for different models and features, unlike standard SaaS paywalls.

4. Scaling Challenges: While scaling SaaS mainly involves managing user growth, scaling AI products involves dealing with performance and cost management across various models and workloads.

Controversial Questions:

Are AI companies making a mistake by forcing traditional SaaS pricing models onto their products? Is the industry ignoring the unique needs of AI pricing, and if so, what could be the consequences? How would the pricing space evolve?

Thoughts?
I'm speaking from a practical cooking perspective, not a technical physics perspective. The radiation from flames or the sun affects food very differently than microwaves do.

For the same reason, I probably messed up other physics technicalities. It would have been nice if I added a caveat I guess, but so it goes. My mental model may be simpler than the truth, but it's a lot better for achieving practical results in the kitchen than nothing than "microwaves heat stuff up fast", which is what I had before and is a really shit model that fails to explain most of their odd behavior.
Yeah, I pay for a few hundred gigs. Forget exactly how much.

I don't use the desktop app because I have nothing from my desktop to sync. It's all in the cloud to begin with (gdocs, etc.) or in github.
Laziness Does Not Exist (But unseen barriers do)
the author has some recommendations, to quote formatting):

> Suggestions:

>

> Generally, String

> If you deal mostly with string literals but want some flexibility (like clap), generally you'll want Cow<'static, str>

> If a profiler says your strings are a problem:

> Try different crates and settings for that crate out with a profiler

> O(1) clones are important when doing a lot of clones.

> For one-off allocations, they are slower.

> For short-lived programs, look into string interning

i.e. author thinks you should profile with your own use case

EDIT: Not sure why HN removes indention between a leading > and the start of the text, makes quoting unnecessary hard
I have good news re: information flow rates
Should we introduce a SUBSELECT keyword to distinguish between a top-level select and a subquery?

To me that feels as redundant as having WHERE vs HAVING, i.e. they do the same things, but at different points in the execution plan. It feels weird to need two separate keywords for that.
I thought "the right way" was to do everything in Rust :-)
I suspect these programs are mostly an attempt to claw back some people lost to the brain-drain that the region has been experiencing for decades. $10k over 5 years is not enough to seriously convince most people with no ties to the area to relocate there.

I have family roots in Cumberland and the nearby areas of West Virginia and MD and I still wouldn't consider moving back. But, if you still have a good relationship with family in the city and were already considering the move, this offer might look more compelling.

I believe Vermont also had a similar program for several years - offering a similar amount of money for people to move and work there in VT.
Kind of, but space in the social sense of "set of places and people agreeing on what is local time", not the physical one.

We need to record that whenever we want to talk to people about time and schedule things for them, just like we need to record their language and regional format preferences.

In other words, you might not need that level of metadata for a physical simulation, but you'll definitely need it for a calendar app. For everything in between, it depends, and the safest bet is accordingly to just do it, if you can.
I’ve seen papers that combined pre-trained vision and language models, trained them together on image/text pairs, and then used the new model for things like text extraction. Could your model be plugged into such a design?

I’ve always wanted to scan whole books by just feeding
Pictures of their pages into an AI. Prefer preferably with minimal labeling requirements. I also see this as a way to generate more training data for language models from old cheap books. Do you think your model could help with that?
Um, this looks really, really good.

Yo @yoknapthawa, can this be finetuned on an M3 chip? How much RAM is needed? What are the current low hanging fruit-type tasks you think the community could go at? What's latency like? I didn't see anything on the page / in the paper / github about speeds.

I'm also curious about the classes you use for the segmentation task -- do you have a list of them somewhere?

Finally, your generalization results are all on photorealistic images, did you do any looking at paintings / animation / other? I'm curious how broadly the generalization goes.

As always, thank you for opening the weights.
I had the same thing happen to my Pros, with one being much louder than the other and the noise cancelling barely working, and it turns out they just needed cleaning. A couple years of gunk and dust getting in the vents and speaker grill and one of them was noticeably worse than the other. After cleaning it turns out both were quite degraded and are now much better with fully functioning noise cancellation. Worth a try if they're otherwise good and you want to keep using them.
I misread gp's comment, we're in agreement.
yeah, take tips from scientists instead.

Branyas believed her longevity stemmed from “order, tranquility, good connection with family and friends, contact with nature, emotional stability, no worries, no regrets, lots of positivity and staying away from toxic people”

Sounds like solid advice to me.

[scientist] Sinclair said [..] improvements in vaccines for flu and shingles, statins, and other medications would help increase life expectancy among older people. [...] he said governments also needed to take action to help individuals to make healthier choices.

Sorry, I think I prefer the advice from the old person.
oh bugger all, and I'm content with that. I don't think he is though. he just doesn't seem okay. if I were that filthy rich, I'd pay somebody to make sure I'm not coming across as a lunatic, I wouldn't joke about buying a blog and then panic when I can't pull out of the contract. i wouldn't tell advertisers to go fuck themselves and then sue them for not advertising on my blog.
The initial version of SQL was called "Structured English Query Language".

If the designers intended to create a query language that resembled an English sentence, it makes sense why they chose "SELECT FROM".

"Select the jar from the shelf" vs. "From the shelf, select the jar".
she is good too. but musk did 0->1 work. She did everything else
no accident, it takes real cunning and lack of empathy to get that rich.
When the mean free path is longer then a typical ballistic trajectory that these molecules and ions are typically on, they do not exhibit any properties associated with gas. Importantly, the property of expanding under pressure to fill a volume is not exhibited.
I think this new syntax is more imperative (you tell the DB "how" to get you the data). The old syntax is more declarative (you tell the DB "what" you need).

The big advantage is that the SQL engine can optimize the how if you focus on the what -- especially after so much research has been don building query compilers.

If you want to focus on the "how" then perhaps a "bare bones" DB like Redis is more in line with this kind of thinking.
With Freight Off the Rails, Rare Open Tracks for Canadian Passenger Trains
The total cost of the shuttle was around $200 billion. A Saturn V launch was around $1.2 billion (today's dollars).

The Saturn V could get 44.5 tons to the moon.

So instead of the shuttle program we could have had whatever amount of moon base you'd get with just under 7500 tons on the moon.

And that's assuming a very expensive Saturn V, in reality the system would have become cheaper over time due to optimization and amortization.
One more nail in Boeing's coffin.
If we simply stored all timestamps as "number of seconds since X" then we could safely convert that to whatever timezone, apply whatever leap adjustments, apply daylight savings time, convert to whatever calendar, etc anywhere we want

Instead of browsers/libraries handling all the complexity (standards and localization, dst, leap seconds, etc), couldn't we just do all our math and logic in this format and then convert back to whatever when we need to display a time to a user.

It seems like saving a #seconds along with lat/long information is enough to handle all timestamp use-cases.
I think that engineers and analysts each have very different relationships with SQL.

When I was doing data science, all the other DS folks would be perfectly content to read and write queries that were hundreds of lines long. There were plenty of minor bits to pick, but it was a great lingua franca for describing data processing.

But engineers hate SQL because they generally only need a tiny little subset of the feature to enable transactional data updates. So they write an ORM to do the subset of SQL they need and never get the opportunity to be indoctrinated into the SQuLt
This is commercial market optimization dressed up as health news to increase profits by preying on consumer health insecurity. Reducing waste is good, but this societally abusive way of going about it is repugnant.

> Fattoria La Vialla, a family-run farm in Tuscany, sells OMW to customers in the UK

There it is.

https://paulgraham.com/submarine.html
The smallest page size tends to get entrenched in the rest of the system (for things like linker page sizes, IOMMU interfaces, etc.,); growing the smallest page size might not be a viable option in existing systems and it might be easier to introduce intermediate-size TLB entries, perhaps formed by consolidating adjacent contiguous PTE's..
Kelsey is not against Kubernetes, just like he isnt against Microservices.

But like me he wants you to really THINK and CONSIDER why you should use Kubernetes and Microservices in the first place.

Kubernetes has its place.

Single servers have their place.

Monoliths have their place.

Microservices have their place.

In the end, its all about tradeoffs.
I laughed out loud, so I disagree.
Where did the overlap of JS and Rust knowledge come from? Is one a day job and the other tinkering? Are both somehow "work"?
Oh god your comment brought back so many horrible memories. At my last company we had a reporting system in NodeJS that ran daily reports for clients around the globe, and whoever set it up decided that the reports should be set to 00:00.

The amount of hell that ensued was never-ending. I'm not sure we ever truly fixed the issue, it's so hard.
> If you assume willingness to learn CVS is in line with being able to provide valuable contributions.

This, but also: "can you make an effort to conform yourself to others instead of forcing others to conform to you;" Inexperienced people often lack the visibility of their elders, so it really makes sense to see whether they can lower their ego.

> Some fresh out of school smart people might consider it a thing of the past. And just decide not to deal with it. Like COBOL.

Are you using "smart" positively or not? Being smart is often frowned upon in SE. Then, driving smart people away still is a good thing.

If you meant positively... considering things of the past to be useless by mere virtue of being of the past, is definitely not a positive character trait, so we'd have a contradiction.

Side note, but the problem with COBOL is not that it's old; to quote wikipedia:

> COBOL has been criticized for its verbosity, design process, and poor support for structured programming. These weaknesses result in monolithic programs that are hard to comprehend as a whole, despite their local readability.
Looking at this reminds me of Apache Pig. That’s not a compliment.
After a long hiatus from the startup world, I've finally decided what I want to build next.

A service that provides AI with its own email.

It sounds kind of backward at first (it's slower than chat and its... email) but after careful consideration I think it's worth exploring for these reasons:
1. It's used by everyone and integrates to everything.
2. It's non-realtime communication gives more time to the AI to create higher quality responses and actions. Also naturally unlocks some cool capabilities like "Do X every Monday at 9AM".
3. It acts as a digital identity on the web.

To be honest, I really really wanted to go with a B2B product after my last [B2C product](https://www.indiehackers.com/product/ryeboard) but I'm back in the B2C arena because I have a gut feeling this will unleash another layer of productivity with AI for pretty much everyone.

I admittedly do not have a solid use-case in mind nor have I done lots of customer calls/research. But I want to make sure from day 0 that we're building something relevant for customers instead of vaporware so I'd love to get in touch with some people who are interested in this kind of product. I'll provide 6 months of free service for those that get in touch with me for their troubles!

Reach out to me through the site in the post!
FTA > There are also no indicators of compromise.

I find it fascinating they are able to detect these things and report them to Microsoft. The security companies obviously have to be on the endpoints to see any of this. However, it doesn’t seem like this depth of detection extends to protecting customers.
> we still haven't figured out how to provide a decend meal every day for all the children on our spaceship Earth.

We produce more than enough food to feed every person on Earth and then a few billion more in the future. We simply choose not to. It isn't a technological or logistical issue, but cultural and political.
Anyone here with developmental dyscalculia managed to overcome it and get into math? I have no clue how to deal with numbers, I know this is weird to say but it feels like they don't exist for me.
This is a good post, but there's a little too much ritual in here about password-based KDFs for my taste. Put all the mainstream KDFs on a dartboard, yes including PBKDF2, and throw a dart. I think you'll be fine. Bcrypt, the most popular password hash, has held up surprisingly well, and scrypt might still be one of the best options.
I filed a GitHub issue two weeks ago about a bug that was enough for me to put it down for a bit, and there’s been not even a response. Their development velocity seems incredible, though. I’m not sure what to make of it.
Aviation is insanely reliable. The 777 flew thousands of flights per day, every day for 18 years before its first fatality.

It’s why scandals like the 737 Max are so appalling. We know better. Boeing knew better.
Can't we just shape the mined platinum into rods and drop them into the oceans from orbit? Or onto rival mining companies, for that matter?
Trail runs a cryptography practice that does assurance work for cryptography engineers. They're not writing to encourage randomly-selected HN readers to design their own cryptosystems.
I don’t think the last link is related. Different database.
Yes it is and it is not the first time having such contigency plan.

Quite recently there was a Soyuz with crippled cooling and the contingency plan for the American astronaut that came with it was to evacuate via Dragon if there was an emergency before new Soyuz arrived.
I also came down to say the same thing -- Joda's library was the best library to deal with date & time
( Now with all the changes copied to the standard library, I haven't used that library in years )
You guys should try and get acquired by Cognigy.
this is what you are looking for i believe (web archive format)
https://en.wikipedia.org/wiki/WARC_(file_format)?oldformat=t...
I do not know how well X is doing as a business, but Musk buying Twitter has certainly helped to wrest it out of the hands of the left and to shift the Overton window. It could well be that to Musk, the political impact is well worth billions of dollars.
You may want to check out the contents of java.time [1] and it's subpackages to see what I mean by stuff.

[1] https://docs.oracle.com/en/java/javase/17/docs/api/java.base...
> If we simply stored all timestamps as "number of seconds since X"

That works – if you never want to represent dates in the future (because we don't know how many leap seconds there will be in the future). But that way, you'd be incapable of implementing even a trivial calendar application involving more than one timezone.

> couldn't we just do all our math and logic in this format and then convert back to whatever when we need to display a time to a user

We could – using all the libraries encapsulating that complexity.

> It seems like saving a #seconds along with lat/long information is enough to handle all timestamp use-cases.

That's even worse, since often that's not available, and even if it is, now you need a database representing local UTC offsets as polygons on the surface of the earth!
Kelly had a subversive quality to him that is probably almost impossible to institutionalize; I think it's unusual to find that mixed with some nationalist pride -- in that way, I see him as a product of the war, and the postwar boom.

That plus his broad multilateral intelligence -- seeing design and implementation as one thing that one could expect to understand and possibly master -- stood out for me, reading about him.

Anyway, if a leader like Kelly is needed for a skunkworks, that itself may be quite difficult. I'd guess most large companies would take a functioning "almost as good as" Skunkworks any day, if they could tolerate the guy/gal running it.
Well, the OP could probably get their benchmarks to run faster if they passed MAP_POPULATE, which would make the mmap call block for longer.

In a pedantic sense, the mmap call is already blocking, because any system call takes longer than e.g. stuffing an sqe onto a queue and then making 0 syscalls, and it could take a variable amount of time depending on factors beyond that one process's control. I don't think anyone actually needs to offload their non-MAP_POPULATE mmaps to a separate thread or whatever though.
>Look at Seattle, Oakland, or the Hollywood hills. They're all built on rugged, mountainous terrain just as difficult as the Appalachians, but they don't suffer the same issues attracting wealth because their economic situation is so different.

Wrong. Seattle, Oakland and Los Angeles are mostly built on much flatter parts of those areas.
California entire geography is about "Hey, check out these massive valleys or coastal land we can build in." Same thing with Washington State, Seattle is in between Cascades and Olympics where there is all this flat land to build on. Yes, they running out of land and building into mountains now. That problem is like having FAANG scaling problems. It sucks but it's good/manageable problem to have and you have massive checkbooks to help solve it.

Have you been to Appalachia? It's not on the coast and does not have these benefits. If you want to compare it to West Coast areas, it's more like Sierra Nevada. Inland Mountains with only small valleys to build infrastructure in.
Backup Tables Laravel Package
Perhaps due to hormonal changes?