skysight-inc/HackerNews huggingface dataset:
I agree totally.

That is precisely why we must transition to space based resource extraction and manufacturing.

There are practically infinite resources at our fingertips on the moon, the asteroid belts and eventually the gas giants.

What we need to unlock this are the means to economically launch a minimum viable self replicating infrastructure into space to take advantage of this.

The feedback loops that will ensue should we succeed will allow us to save Earth ecology, radically transform the human condition, and unlock the ability to explore the universe in ways that we can only imagine.
But to some approximation we do know how an LLM plays chess.. based on all the games, sites, blogs, analysis in its training data. But it has a limited ability to tell a good move from a bad move since the training data has both, and some of it lacks context on move quality.

Here's an experiment: give an LLM a balanced middle game board position and ask it "play a new move that a creative grandmaster has discovered, never before played in chess and explain the tactics and strategy behind it". Repeat many times. Now analyse each move in an engine and look at the distribution of moves and responses. Hypothesis: It is going to come up with a bunch of moves all over the ratings map with some sound and some fallacious arguments.

I really don't think there's anything too mysterious going on here. It just synthesizes existing knowledge and gives answers that includes bit hits, big misses and everything in between. Creators chip away at the edges to change that distribution but the fundamental workings don't change.
rustc does its best to recover, continue and provide diagnostics from later stages. But at the same time it is better to provide a single early error and mark the entire node as recovered to avoid further errors at the cost of requiring more cycles of back and forth, over the alternative of tons of useless knock down errors that drown the underlying cause of the problem.

We are always on the lookout for improving in this area. Having examples of cases where we conceivably should have done better but didn't is useful. As mentioned already, the complexity here is that doing the right thing for the user requires architecting multiple separate stages of the compiler to talk to each other in way more complex ways than originally intended.
I'm not an expert in this, but at least familiar with the trade.

I'd imagine with on-demand services you already have the full content and therefore can use algorithms to compress frames and perform all kinds of neat tricks to.

With live streaming I'd imagine a lot of these algorithms are useless as there isn't enough delay & time to properly use them, so they're required to stream every single pixel and maybe some JIT algorithms
I suppose we should be glad they're just being silent, not auto-responding with a poop emoji like they previously have.
E- chocolate

E- chocolate

Don’t get it.

Oh..!
> It doesn't have to be final, it just has to be reasonably descriptive of reality.

Which it only is if you limit cosmology to spectroscopy and ignore UAP. If you start to examine UAP as a real thing, and ask questions about “how”, then it all falls apart.

Which is exciting.
And they had survived the impact, and were capable of, but unable to, exit.
My entire experience of being bullied (there wasn't really any at my school, not sure why) is that one kid made fun of my acne. I just shrugged and then he said "you are cool." I thought it was a strange phenomenon.
> This is why I call C a minefield.

Computing is a series of "minefields." At least you get a map of this particular one.

I'm far more confronted by public facing APIs that involve user authentication than I am of any particular documented set of language facts.
I've written a ton of software, both backend and embedded-like software in C++.

What are people writing that requires such fancy/extensive usage of the borrow checker?

I can't even remember the last time I had to use a shared_ptr... unique_ptr and other general RAII practices have been more than enough for our codebase.
Do people even have cable TV anymore?

Six seconds on the Google shows 58 million households in the United States. So, roughly 145,000,000 people.

You make the tech bubble mistake of believing that high speed internet is as ubiquitous as coax.
FINALLY I GOT MY LOST BITCOIN BACK ALL THANKS TO TSUTOMU SHIMOMURA

Hello everyone I want to use this Medium to say big thank you to TSUTOMU SHIMOMURA for they helped me recover my stolen crypto worth $250,000 through their hacking skills I tried it I was skeptic but it worked and I got my money back, I’m so glad I came across them early because I thought I was never going to get my money back from those fake online investment websites . you can also contact them via Email: tsutomuhimomurahacker@gmail.com or WhatsApp via: +12569564498, or Telegram @TsutomuShimomurahacker, and I’m sure you will be happy you did.
Dead telephone network theory.
Ehh... I'm very skeptical of those streaming services.

I tried Stadia once. Played Celeste. The results were very interesting. I didn't exactly perceive latency, but I did perceive that the game felt wrong. As a result, my favorite game of all time was not fun when playing on Stadia. If I didn't have the local version of the game to compare against, I would probably have blamed the game, because again, it didn't feel like latency was the problem.

I dunno, maybe that experience was skewed by the fact that Celeste is probably one of the most timing-sensitive games out there and I'd played it a lot... but now I'm worried that anything played via one of these streaming services is just going to be subtly less fun. I think I'll stick to local gaming.
What makes you think I didn't?
You ask 100,000 humans each to make a photo realistic rendering of a alpaca playing basketball on the moon in 90 seconds, an LLM is going to outperform every single one of them.
There’s very likely a dedicated service for delivering frames.

That’s service would technically be a “microservice” even if it is a large service.
Thanks, I’ll check that out. Lately I love finding stuff like this not only for myself, but for my kids eventually who I’ll probably need to indirectly nudge here and there as your post doc mentor did.

That all sounds great to me. I can say with certainty that it would have sounded terrible 10 years ago. How can you waste all that time not advancing your career? The irony is that the PTO and holidays absolutely do advance your career in the sense that they make you a more complete, fulfilled person who can keep cracking away at their career in a steady and consistent fashion for the decades to come. When you’re 25 you have no idea how badly you’ll need that, and how soon.
You can achieve some level of OO design by using traits (the generic kind, not the dyn kind), but I think the functional style and inline testing gives you a ton of nice properties for free!

Rust also pushes you to refactor in a way that really pulls out the core of your problem; the refactoring is just you understanding the problem at a deeper level (in my experience)
Everyone else is missing the point here. SMIC (China’s main semi fab) isn’t the company manufacturing these chips. They haven’t broken into anything close to 3nm-class chips yet. This just means that TSMC is going to manufacture a 3nm chip for Xiaomi. The important part for China here is this proves that they can design modern chips, not they necessarily have the manufacturing capability yet.
I think it's telling that whenever someone raises concerns about any element of Rust, no matter how constructively, they're always met with a wall of "you must not truly get the borrow checker," or "you're using Rust wrong," or "stop trying to write <C/C++/Java/etc> in Rust!", usually with zero evidence that that is in fact what is happening. There's never anything to improve on Rust, it's always user error / a skill issue. If there ever surfaces any audio of Linus Torvalds and Ken Thompson discussing the pros and cons of the borrow checker, I expect a sea of patronising anime avatars to show up, seeking to explain Rust's invention of the concept of ownership to them.

Rust is really nifty, but there are still (many) things that could be improved in Rust, and we'd all benefit from more competition in this space, including Rust! This is not a zero sum game.

Honestly, I also think many people just want a nice ML-like with a good packaging story, and just put up with the borrow checker to get friendly C-like syntax for the Option monad, sum types with exhaustive matching, etc. This is a use case that could very much benefit from a competitor with a more conventional memory model.
I don't think that's true, or at least, you're jumping prematurely to conclusions and sort of begging the question too.

The "U" just means "unidentified", not "contradicting our understanding of physics" or "extraterrestrial intelligence".

There are many life forms on Earth that remain unidentified by many estimations, and we keep discovering new organisms. "Unidentified" doesn't have to violate our understanding of the universe.
The question I addressed is "does the lensing work the same from the other end". It's a very specific and clear question, and the answer is "no it does not", because if you reverse a telescope lens you get the opposite effect (from zoom-in to zoom-out)

The question of at what distance and relative velocity are the two locations so far apart that light can never make it from one to the other (due to expanding universe) is a completely separate issue.
Bluesky would really benefit from a notional ($1/year) signup fee. That small bit of friction makes a vast difference in knocking down all kinds of spam, at the price of being considered a bit uncool (for having a revenue stream).
> "I was told Elon is going to be very involved in this,” Jones said during a live broadcast on X... Jones noted that lawyers for X were present at the hearing, adding, somewhat mysteriously, “The cavalry is here. Trump is pissed.” (He later elaborated that “Trump knows I’m one of his biggest defenders.”)

Someone should remind him that Trump isn't President for another 10 weeks.

And if X wants to enter a bid, they should have to justify why they should be allowed to, given that they did not enter a bid when it was at auction (or even register as a potential bidder).
I had buffering issues but then backed off and let a bit of it buffer up (maybe 1 or 2 mintues?) and then it was fine for the entire Tyson Paul match. There was no reason I needed it to be live vs. a 1 or 2 minute delay.
What advantage do they offer in 2024?

They exist in places where the internet infrastructure is not adequate for constant multiple streams.

Content is king. And there's lots of content on cable that is not on streaming. Just consider local and regional news and sports.

Many residential buildings, like the one in which I live, include cable TV with the rent. Why add more clutter and expense for streaming?

There are plenty of other reasons. Your position seems to be "stop liking things I don't like."
There is no answer. There are only improvements.
Can't say I agree, or that this matches my experience of writing Rust.

I don't memorise how it works, I've just learnt what it rejects and why, and this in turn becomes clear as to why it's rejected that. Very rarely do I find myself going "oh bother, now I suddenly need to `Rc` or `Arc` this, I suspect because I've just gotten into the habit of suspecting when I anticipate things will run afoul and structuring things from the get-go to avoid that. Admittedly, I'm not writing absurdly low-level code.

I wonder if the authors grounding C++ is making life harder for them? Often when I've had to teach people Rust, getting them to stop writing {C/C#/Java}-but-in-Rust is the first stop on the trail to "stop fighting and actually enjoy the language". Every language has its idioms, just because you can, doesn't mean you should.
It’s both well known and self evident that communication is richer in person for the vast majority of people.

Not really something worth arguing about.

Water is also wet, but I don’t have a specific source to link for that.
Well you have to convince somebody to pay researchers for their time, which ultimately means selling your idea to non-experts.
What are you doing here then?
A certain subset of conservative evangelical Christians have this whole shtick in which they construct a typology of worldviews – see for example "Hidden worldviews : eight cultural stories that shape our lives" (IVP Academic, 2009), by Mark Sanford and Steve Wilkens, both Azusa Pacific University professors. I can't remember if I've read that specific book, but it was either that book or a similar entry in the genre.

In the abstract it is an interesting idea, but their approach to it is very tendentious. But this post reminded me of it, because it is gesturing in the same direction, even if it never proposes a specific listing of worldviews.
Are you serious? You think they don't care about this except if the stock 'takes a bit hit'??
There is a wonderful book about the blind man who was probably one of the earliest innovators in using a cane for echolocation. "A Sense of the World" by Jason Roberts is the story of James Holman, who traveled the world in the early 19th century despite being blind, often being in a great deal of pain, and having limited mobility.
I don't click random, likely dangerous links, but it's good to see you've been rendered speechless. I like that.
Same for me. I wanted to contribute, but the amount of dependencies needed to get a local build to run was a major hurdle.
In 2012 Youtube did the Red Bull stratos live stream with 8m concurrent users

8m vs 60m. And not in 4K. Not a great choice for comparison.
On demand is easier precisely because having a huge library in all data centers is relatively cheap. In actuality you just have a cache, collocated ISPs that pulls from your origin servers. Likely you have users all watching different things so you can easily avoid hot spots by sharding on the content type. Once the in demand content is in the cache its' relatively easy to serve.

Live content is harder because it can't really be cached, nor, due to TLS, can you really serve everyone the same stream. I think the hardest problem to solve is provisioning. If you are expecting 1 million users, and 700,000 of them get routed to a single server, that server will begin to struggle. This can happen in a couple different ways - for example an ISP who isn't a large consumer normally, suddenly overloads its edge server. Even though your DC can handle the traffic just fine, the links between your DC and the ISP begin to suffer, and since the even is live, it's not like you can just wait until the cache is filled downstream.
They moved from AWS to on-prem sometime in the last year or two: https://newsletter.pragmaticengineer.com/p/bluesky

And I don't care how many resources you have available to throw at it, plenty of sites would still fall over with the kind of growth they're having.
I think the issue is Garry Tan's video RFS merged "LLMs for EDA" with "Purpose Built Compute" for specialized usecases. The title "LLMs for Chip Design" doesn't help either.

From my reading of the RFS (not the video) it appears they are essentially asking for the next Groq or SambaNova.

Personally, this kind of communication issue would give me a long pause if I was considering YC for this segment, as this is a fairly basic thesis to communicate, and if a basic thesis can be muddled, can the advice provided be strong as well, especially compared to peer early stage funders in this space?
Fair enough, but the problem in this analogy is that this learning isn't always useful or productive in any way. This is more like doing arithmetic in a sort of maths notation where every result must be in base 12 and everything else must be in base 16. Sure, you can memorise the rules and the conversions but you aren't doing much useful with your life at that point.

Obviously, the borrow checker has uses in preventing a certain class of bugs, but it also destroys development velocity. Sometimes it's a good tradeoff (safety-critical systems, embedded, backends, etc.) and sometimes it's a square peg in a round hole (startups and gamedev where fast iteration is essential)
I think it'd be fantastic to not need it in the first place. It is just utterly beyond reason that this is even a thing.
Optimized latency can deanonymize, so better to layer anonymization on top.
A vibration motor on the index finger could make it... multifunctional.
Yeah, I think friend-to-friend (F2F) networks are the most natural and take the most reasonable approach to spam resistance.

I don't think badges will work, because who assigns the badges? Friend groups IRL are generally not led by a single tyrannical leader. You just end up making a forum with a single owner.
The protocol for a torrent is that random parts of a file get seeded to random people requesting a file, and that the clients which act as seeds are able to store arbitrary amounts of data to then forward to other clients in the swarm. Do the properties about scaling still hold when it's a bunch of people all requesting real time data which has to be in-order? Do the distributed Rokus, Apple TVs, Fire TVs and other smart TVs all have the headroom in compute and storage to be able to simultaneously decode video and keep old video data in RAM and manage network connections with upload to other TVs in their swarm - and will uploading data to other TVs in the swarm not negatively impact their own download speeds?
Isn't that the implication? If you're on a platform with a lot of low quality bitterness and another one pops up with less of that, just move. If it happens again, move again. It's not team sports, you shouldn't feel loyalty. The only problems are practical, rather than psychological.
I haven't read the book, but my experience is that the way to make things flexible is to make them simple as possible.

When I've used (or built) something that was built in the style like you're talking about, it's almost always wrong, and the extra complexity and stuff now makes it harder to do right. It's not surprising: unknown future requirements are unknown. Over building is trying to predict the future.

It's like someone building a shed and pouring a foundation that can work for a skyscraper. Except it turns out what we needed was a house that has a different footprint. Or maybe the skyscraper is twice the height and has a stop for the newly-built underneath. Now we have to break apart the foundation before we can even begin work on new stuff; it would have been less work if the original just used a foundation for a shed.
Dark energy is literally this - it just means something is different than predicted by current leading theories.

There is plenty of evidence that either dark matter or an alternative is needed and CDM is just the most popular take.
> Rather than the traditional response of blame and punishment for the bully

Well, that's bullshit. Often the "traditional response" (at least in my day) was to blame the person being bullied, sometimes along with the bully as well.
Is there another book you'd recommend - more recent than SICP - for how to avoid programming yourself into a corner?
Just so you know the 518 is back in production as of a couple years ago with an updated sensor. It is by far the best mouse ever made, still to this day.
That is fine for professional recipes, when you cook for dozens of people. But for home cooking, if they say 25-35 minutes prep time 40-60 minutes cooking time, I’d expect them to count the cutting in there.
Nice work mate. I hope it all makes you happy!
I do have to ask, I have worked in codebases which used lifetimes and didn't lean into Rc/Arc and vice-versa.

I used to think Arc/Rc was a shortcut to avoiding the borrow checker shenanigans, but have evolved that thinking over time.

You do mention it in your comment so wondering if you have anything to share about it
How big an increase is that relative to the increase in users?
A theme I’m noticing more frequently as Rust gains popularity is people trying to use Rust even though it doesn’t fit their preferred way of coding.

There is a learning curve for everyone when they pick up a new language: You have to learn how to structure your code in ways that work with the language, not in the ways you learned from previous languages. Some transitions are easier than others.

There should come a point where the new language clicks and you don’t feel like you’re always running into unexpected issues (like the author of this article is). I might have empathized more with this article in my first months with Rust, but it didn’t resonate much with me now. If you’re still relying on writing code and waiting for the borrow checker to identify problems every time, you’re not yet at the point where everything clicks.

The tougher conversation is that for some people, some languages may never fully agree with their preferred style of writing code. Rust is especially unforgiving for people who have a style that relies on writing something and seeing if it complies, rather than integrating a mental model of the language so you can work with it instead of against it.

In this case, if someone reaches a point where they’re so frustrated that they have to remember the basic rules of the language, why even force yourself to use that language? There are numerous other languages that have lower mental overhead, garbage collection, relaxed type rules, and so on in ways that match different personalities better. Forcing yourself to use a language you hate isn’t a good way to be productive.
I think OP is likely overusing references. The vast majority of code doesn't need to deal with explicit lifetimes.
It would appear that our cones align well enough to keep the intersection positive (the conversation semiprocrastinative)

I shant say that artbasel doesnt exist. Shall we align yet more finely to note that the various subtypes of the highest level “markets” serve to distort the market so as to stay (mildly) (dys)functional? A taxonomy of the various markets for lemons/_lemons is in order? Restnt biz is further enough off the manifold that i might not find it that interesting, convince me.

>honeycomb… sheer mass

It might be nice to expand on what senses of these words are alluded here.. “honeycombs“ are nice skeletons that (math)phykers found they cud feed into the vN (inker) blackbox & get out some interpretable Rorschach zombies. (Plausibly) Marketable Schlep to put off the potentially ikigai busting hard thinking ?

[2] coevolution? The mainstream, prodded by NPs, might evolve towards dropping the interpretability/identifiability reqs?

KST?
>Off-Topic: Most stories about politics, or crime, or sports, or celebrities, unless they're evidence of some interesting new phenomenon.

This was further exacerbated because the linked study seemingly ignores what happened on the day specified to demonstrate their narrative.

Essentially, the linked study placed the cart before the horse.
With all the galaxies out there, it seems likely that Earth should be in the focus of lots of systems of this kind. Hopefully in the future we'll be able to find and use these galactic telescopes!
Those are the times when you identify who is there to help and who is there to be performative.
Do you feel this is similar to the idea that a problem can be approached either analytically or as a simulation?

Sometimes the math is too hard, so we create a world with some initial values and let things play.

The insights may then help us build the models or equations. But we couldn't get there just by thinking hard long enough.
That and the art of computer programming
I’m sorry but I genuinely don’t understand your critique. Is there a simpler way you could phrase it?
It'd be neat if you could create conditional blocklists.
Like only whoever X person AND Y person block will be blocked from my feed. And so on...

I don't think that'd solve the problem, but it would marginally help (and should be better than the status quo)