skysight-inc/HackerNews huggingface dataset:
The argument here is that Rust chose to implement coroutines the wrong way. It went the route of stackless coroutines that need async/await and colored functions. This creates all the friction the article laments over.

But it also praises Go for its implementation, which is also based on a coroutine of a different kind. Stackful coroutines, which do not have any of these problems.

Rust considered using those (and, at first, that was the project's direction). Ultimately, they went to the stackless operation model because stackfull coroutine requires a runtime that preempts coroutines (to do essentially what the kernel does with threads). This was deemed too expensive.

Most people forget, however, that almost no one is using runtime-free async Rust. Most people use Tokio, which is a runtime that does essentially everything the runtime they were trying to avoid building would have done.

So we are left in a situation where most people using async Rust have the worst of both worlds.

That being said, you can use async Rust without an async runtime (or rather, an extremely rudimentary one with extremely low overhead). People in the embedded world do. But they are few, and even they often are unconvinced by async Rust for their own reasons.
I'm fairly certain a lot of very influential software came from the hands of Bill Gates as well such as the FAT filesystem which is still used, the original MSDOS and BASIC Interpreter which made a huge impact.

Of course, that's all mostly because much of that was bundled with the original MSDOS.

Also, in terms of video games, a great deal of innovative techniques and games game from John D. Carmac, which of course also is a result from Id Software pushing it.
> About the game of life.

In the paper "Interaction Nets" ( https://github.com/cicada-lang/inet/blob/master/docs/referen... ), there is an example of 1-dimensional Cellular Automata. (Section 1.4. Example: Cellular Automata).

> About the stack-based layer of the language.

I have some concerns about it when deciding to use it, because it is so different from common programming languages.
I am comfortable with postfix notation, because I am familiar with the Forth language ( https://en.wikipedia.org/wiki/Forth_(programming_language) ).

> About Rearrange.

I will improve the docs about it.

> About `closeAllFreePorts`

If `closeAllFreePorts` is the culprit, maybe it is because of my wrong implementation of the web frontend (not the language).

I should not call `closeAllFreePorts` in a loop.

see: https://github.com/cicada-lang/inet-website/blob/master/src/...

and: https://github.com/cicada-lang/inet-website/blob/master/src/...

It is a bug that I should fix.

I also implemented a command line program and a REPL: https://github.com/cicada-lang/inet#command-line-tool

Maybe a few thousand steps will not be slow there.
The problem with the FAA is only 10% the content of the reports, and 90% waiting interminably months upon months for the reports. So if SpaceX has a list of concrete items to address, it's good news for SpaceX basically regardless of the contents of the report.
And in the end, almost everything ends up using Mutex, RWMutex, WaitGroup, Once, and some channels that exist only to ever be closed (like Context.Done), and only if you need to select around them.

It's great, but message passing it is not.
Which one? I wonder what its performance is like.

A good candidate for this is Graal. It can compile (JIT/AOT) both WASM and also LLVM bitcode directly so Rust programs can have full hardware/OS access without WASM limitations, and in theory it could allow apps to fully benefit from the work done on Loom and async. The pieces are all there. The main issue is you need to virtualize IO so that it goes back into the JVM, so the JVM controls all the code on the stack at all times. I think Graal can do this but only in the enterprise edition. Then you'd be able to run ~millions of Rust threads.
Yeah, the reason I didn't include airports in my list is because I agree that the case that these should be government run is much weaker.
Always interesting to see those in modern secular society where women are scorned for not wanting/having a career and staying home with the family come around to the reality that societies worldwide have known for centuries.
It really is, but I still favour "unsexy" manual poll/select code with a lot of if/elseing if it means not having to deal with async.

I fully acknowledge that I'm an "old school" system dev who's coming from the C world and not the JS world, so I probably have a certain bias because of that, but I genuinely can't understand how anybody could look at the mess that's Rust's async and think that it was a good design for a language that already had the reputation of being very complicated to write.

I tried to get it, I really did, but my god what a massive mess that is. And it contaminates everything it touches, too. I really love Rust and I do most of my coding in it these days, but every time I encounter async-heavy Rust code my jaw clenches and my vision blurs.

At least my clunky select "runtime" code can be safely contained in a couple functions while the rest of the code remains blissfully unaware of the magic going on under the hood.

Dear people coming from the JS world: give system threads and channels a try. I swear that a lot of the time it's vastly simpler and more elegant. There are very, very few practical problems where async is clearly superior (although plenty where it's arguably superior).
Yes! I love Elixir :) Phoenix LiveView is really amazing. I feel so fast working in it. I got hooked after watching Chris McCord's 'Build a real-time Twitter clone in 15 minutes' demo, and things have improved a lot since then.
Increasing supply is not an issue if there is demand. As long as building more fabs brings more profit(even if at smaller margin), I can't see any reason why they won't be building it. It's economics 101. Also as moore's law is coming to end, the number of fabs has no way to go but up.

Also I don't think manufacturing cost is the biggest of issue, because the margins are significantly higher than consumer GPUs which are in oversupply now for Nvidia. It's that Nvidia has to commit years in advance for the capacity.
How does perpetuation of stereotypes fix society?
As opposed to Apple’s formats, for which the parsers are definitely less buggy and likely to be hacked.
I don't think that's an entirely accurate portrayal of the situation. His team has, AFIAK, removed the compilation step from their workflow (or are trying to), deciding to ship unadulterated ES6 to the browser, so they 1) removed TypeScript, and 2) removed Prettier. Both of these require a build/compilation step, which they're moving away from. That's literally it.

The Turbo library is not consumed like a normal package anyways, so these types were only used internally. Nobody relies on these types.

It's their library. And others have done the same recently.
I have the "MoYu Super RS3 M 2022" as maglev version and I love it. Can recommend!

I am not a "real speedcuber" tho. My average is about 40s, but it's a nice cube and I enjoy playing with it.
Thanks for the clarification and detailed response! I think your final two points are probably the two things I was failing to take into consideration here. I’m used to trying to profile medium-ish systems (like 40-50k lines of code) so that was the context I was bringing into this. In regards to the example listed in the article, you are absolutely right about being able to intuit where the hot spots may come from because it’s such a small isolated piece of code.

I’ve still got a long way to go in learning more about profiling, especially when it comes to JITed stuff or things with a heavy runtime. But it’s always nice to hear about how other developers approach profiling (it can feel like black magic to me a lot of the time).

Thanks for the article on escape analysis too! I’ll have to check that out in a bit :)
> Telemetry and spyware are not the same thing

Telemetry is spyware if it's done without the active informed consent of the user. What the collected data is actually used for isn't relevant. Consent is the relevant factor.
Most people here are criticizing this presentation (in true HN fashion), but I appreciated it. I think we need to try new approaches like this to get the message to non tech, especially younger crowd who tend to be less interested in reading long articles.
> Anyone know why there isn't a single type/interface that allows for consumers to supply any of Arc, Rc etc boxed values?

Your generic interface just takes a reference to the value inside the box.
That's a nice analogy!

If I feel at a disadvantage (as in, other people produce better work with LLMs), I'll just adopt them too. But I'm really about quality over quantity, and for my kind of work that's not looking like it's becoming that much of a niche any time soon. For other types of work - entirely different story.
I'm still struggling with this:

def do_it(*args, **kwargs) -> None:
...

You might keep the signature constant, but let the behaviour evaluate across versions, but semver-wise, you could consider that API unchanged.
Async for GUIs is also nice. Not essential, but allows you to simply lot of callback code
it's possible that they chose Zig if this started as an unpaid passion project, and it simply sounded the most interesting to them.

Demonstrably by this 1.0 bun release it seems safe to say it ended up being a fine decision, no?
Yeah, a single income household isn't realistic for most Americans.
Effective Email Marketing Strategies for Etsy Shop Owners
> Anaconda's absurdly slow dependency resolver

On the one hand this is like comparing apples and oranges. On the other hand SAT is slow for dependency management not because the solver itself is slow (it might well be - I don't know which solver they packaged) but because it's an NP-complete problem.

Back to sympy: a computer algebra system (CAS) is primarily (IMHO) an algebra system, not a matrix manipulation library or a pde solver or whatever kitchen sink collection of things is in all of them. Algebra in this context means manipulating algebraic expressions and that's term rewriting and that's also NP-complete (well at least in some form or fashion, eg egraph extraction).

So in summary - there's no way out of using SAT/SMT here.

> slow, clunky, etc

Just to put a finer point on this - it's a very shallow thing to look at conda's or whomever's implementation and then paint over SAT/SMT with that same brush. The way that I usually describe z3 is that it is nuclear weapons grade industrial software. I mean jesus christ its stated goal is solving NP complete/hard problems and it frequently succeeds at this goal on problems with millions of decision variables and clauses. It is absolutely the highest tech piece of tech out there (XYZ pytorch/tensorflow ai ml thing pales in comparison) and we are all extremely lucky that it is licensed permissively and developed completely in the open (and basically by one guy!). And it is being used in many many places for very serious engineering.
It is liberating to have a choice and agency.
FWIW, I was thinking in terms of a conception-timing app.
> - The UI is... I don't know, I can never predict where a buffer will appear. Emacs in general will pop up a lot of buffers. Sometimes you can close them with q, sometimes you will have to hide them. "Inconsistent" is the word which comes into my mind.

I fixed that by redefining in my config split-window-preferred-function to my own function, which is responsible for the placement of new windows in a way that makes sense to me (which is something that no other piece of software does actually).
Yes but I doubt they're using z3 or cvc5 or any other oss sat/smt solver.
I absolutely love Procreate. Will be downloading this day one
Go look for some mines or other developed resources from 100 years ago. They are not easy to find despite most of them being well documented. I live in a rainforest so things get swallowed by the forest quickly. 100 years here means all exposed wood is nearly gone, iron is a pile of rust and the trees are almost 2 feet across.

Seeing first hand how the environment recovers after disruption tempers the environmental protectionism proclivity. Sure blatant disregard for the environment like dumping barrels of waste in a river is bad. That doesn't mean all resource use and development is.
That works for channels, but being able to wait other asynchronous things is better. Timeouts for instance.

We could imagine extending this to arbitrary poll-able things. And now we have futures, kind of.
There's an obvious difference between diagnostic data and data that's used to push ads to me.

People might still object to diagnostic data and Firefox's handling of it, but it's disingenuous to state that they're the same.
Here are the things that I think most discussions of Digital Citizenship/Information Literacy/Disinformation Mitigation etc. miss:

* People's time and especially their mental bandwidth are limited and there exist large swaths of the citizenry who are not students. This paper touches on this when it suggests that lateral research into a source is a less onerous task than reading the text itself deeply and acquiring the necessary background context to evaluate content on its own. But that still requires knowledge, skills, and expertise that a lot of the population does not have. Acquiring it is likely feasible for students, but it is not for a single mom of 3 kids working 2 jobs, many retirees, etc. A lot of America's population (the country I am most familiar with) is running with 95%+ of their bandwidth taken up at all times, especially post COVID when so many places are understaffed and it's more cost effective to force existing employees to do 2+ jobs. Tired people do not have the energy to change their habits, learn new tools, etc. There's also much less tech literacy than we would expect. As an example, my current boss who has run a successful local business for over a decade can't sort a Google Sheet. Expecting her to sit down and learn these skills when she's running a business and parenting 2 children under five is futile.

* Information Literacy skills are not stagnant as the falsehood/clickbait/etc. problem is an arms race with several well-funded and well-researched actors having incentives to adapt to whatever tools and habits people do adopt. We can't just teach one set of skills and expect them to work 30, 40+ years on. As an example, lateral researching works well if your other sources stay stable and reliable but that is not what happens. Enshittification, buy-outs, etc. mean that constant re-evaluation of sources is needed. It is not a one and done, and there are great economic incentives to fight people doing this.

* Almost all work addressing the problem has focused on people attacking misinformation and falsehoods from an individual standpoint. Most people evaluate information in some sort of community context. One reason I think that I do alright is that I have families that are all tech-literate and span 5 generations and multiple political views and none of us have turned into conspiracy theorists. If my cousins and I roast each other
for using poor information sources, we can trust that we a.) have an idea of what we're talking about and b.) have each other's best interest in mind despite our disagreements. This makes it far easier to listen to critique from the 'other' side and to have our filter bubbles pierced.

My POV: I'm a librarian from a tech family who has been online for over 30 years. I've also done professional fact-checking and worked in politics/civics communication.
Was Svelte’s decision made in the span of a few hours by a single person, who also silently removed a bunch of other stuff in the same PR?
Apple makes high quality speakers and headphones, that’s the cross sell.
If you use telegram, welcome to join https://t.me/CicadaLanguage
and your second income is taxed at your marginal rate, to pay for a $1 of child care you need around $1.33 to $1.50 in income. Put another way, avoiding $1 in expenses is like earning up to $1.5 at work.

But the real issue is what the article points out, that this often leaves the stay at home parent “trapped” and dependent on the working spouse. What do you do when you’ve been out of the workforce 20+ years, kids out of the house (no child support), and you need to support yourself now?
This is the experience I've made with remote work. Whenever I was at the office, I spent way more time hanging out with colleagues and socializing. When I'm at home, I'm way too worried about seeming like I'm slacking off to actually really slack off.
This is odd, the article confidently states: "ECU's Dr Muhammad Rizwan Azhar led the project which discovered lithium-ion batteries, although a popular choice for electric vehicles around the world, face limitations related to cost, finite resources, and safety concerns."

But https://en.wikipedia.org/wiki/John_B._Goodenough says that someone else did that.

Am I missing something or is that claim in the article incorrect. ECO or mr. Azhar are also not mentioned at all on the wikipedia page about Lithium-Ion.
It is nowhere near as damaging as the phone market though, by a massive margin.
More discussion few days ago:

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

https://news.ycombinator.com/item?id=37410023
There are some alternatives to O2, various molecules that contain oxygen which react readily. But those same properties that make them good oxidizers (namely, reactivity) also make them toxic and difficult to handle.
const pattern = /I hope this (\w+) finds you well\./;

if (pattern.test(text)) {
console.log("is ai.");
} else {
console.log("not ai.");
}
Congrats, Jarred. Have really enjoyed following along with your progress on Twitter. Excited to give Bun a deep dive :)
wait delivery apps there give plastic cutlery? why?

that's never been a thing at any delivery service ive ordered. Seems disgustingly wasteful. Who is even getting a delivery to a place that doesnt have cutlery?
Disliking async/await does not make someone "generally bad at programming". This is a childish ad-hominem mindset that has no place in technical debates. Rust's decision to adopt async/await over green threads was intended to keep the runtime lean, not because it is an inherently better abstraction. Java certainly could have async/await syntactic sugar around its existing futures api, but project loom has greater ambitions by retrofitting asynchronous IO onto the existing thread api. The authors are certainly not "simply wrong" for this decision.
The other large visible change is a purge system for the engine bays to prevent future ongoing fires.
Solo probably failed because the average cinema-goer does not want to see a Han Solo spin-off with Harrison Ford replaced by an unknown B-list actor.
Not a single mention of Erlang. Haskell's parallelism is very much inspired by Erlang's model.
Lots of discussion over here: https://news.ycombinator.com/item?id=37405695
Apparently we can’t. That worked because there were no bacteria that’d consume the biomass and release CO2 back then.
Yeah my thought was the up/down votes could be used to have a "Trending" or "Most Popular" section on the site. But that RHLF idea is interesting too — I've had the same problem with tiled images, and so fine-tuning on highly upvoted examples may help
My wife and I would like a housewife to run the household - please dm me!
They changed this a couple of months ago. Twitter is no longer chronological. On top of that Blue get promoted, having more reach.

I deleted my Twitter account before all that, all too often I cannot even see Twitter deeplinks anymore.
> Honestly how did we convince half of society that it was liberating and freedom to be able to slave away for a corporate wage day in and day out?

I think because until recently, housewives had a very poor standard of living (e.g. women couldn't reliably get credit cards til the 70s, very traditional views of a role of a woman in a family). It's not a surprise that the subsequent generations (Gen X and Millennials) were raised with distaste for the housewife lifestyle.
And many things that exceed existing standards objectively somehow lost out to exceeding standards or inferior standards coming later. The success of software in particular is about being at the right place at the right time as well as interoperability. Plan9 is generally considered a technical improvement over Unix, but where is it, who uses it? Redox can improve or Unix all it wants on a theoretical level, but it will probably never outcompete it due to interoperability and because of that it won't attract the developers to add the necessary features to compete with it.

Linux in particular started because a student made a task scheduler on his home computer with no real goal to make a Unixlike kernel, and it grew into it and it so happened that at the time there was a big vacuum for a free Unixlike kernel. kFreeBSD and kMinix were not yet free at that time, had they been, Linux would have no doubt stayed a hobby project.
It's hard to measure the actual impact of LATAM remote or other types remote on US salaries. It is possible that if US companies didn't have the ability to hire remote engineers, the US salary would be 2x as much. The US hires a HUGE number of remote foreign engineers - it's just not reported in labor statistics.

Your original comment suggested the H1B folks actually push down US salaries. If that is true, then LATAM workers who work US hours should also apply a downward pressure on US salaries. My company hires like 30 LATAM engineers, 10 US engineers and 0 H1Bs. We simply will not hire junior US engineers - completely idiotic use of capital. However we will pay 300k for a staff / principle US based engineer. That engineer will lead a team of 5 LATAM engineers and level them up. This model is going to have a downward pressure on US based salaries if enough companies adopt it.
Virtual threading is fun and all until you find out SimpleDateFormat and a bunch of other classes built tight into your standard library aren't thread safe and now you need to go through your program and find out what else you missed. Go too has these fancy green threads at the cost of manually locking resources and finding out about race conditions when you forget about them.

Futures aren't a fundamental CS mistake, they're a design decision. You may disagree with that decision, but the advantage Rust brings is that you don't need to worry about thread safety once your program actually compiles, at the cost of different code styles.

Neither asynchronous processing design is fundamentally wrong, they both have their strengths and weaknesses.
I've often wondered how widespread "okay" is. I remember standing on the deck of a Washington State Ferry about 20 years ago, listening to a couple of Arabic men speaking. At the end of a long string of Arabic words, one of the men said "Okay?" with exactly the same inflection an English-speaker would, to solicit agreement, and his companion echoed "okay" in the apparent affirmative.
Lots of discussion on the official post over here: https://news.ycombinator.com/item?id=37408776
https://archive.ph/1RUu1
Ya I am a fan of Doom Emacs too. It is the world of Vim wrapped in world of Emacs. Best of both worlds.
How is it not liberating to not be dependant on another human being for everything?
A well written native app will always perform better than a well written web app.

I'm considering performance to be more than just UI responsiveness. I include CPU, battery, network, and memory usage.
Burner phone number.
those other three sites were built by the US government though, SpaceX operates them.
I was hoping their big announcement was going to be Procreate for PC, but I'm happy for all the people out there who will benefit from better accessible tools.