skysight-inc/HackerNews huggingface dataset:
I would accept a link to a YouTube video with a timestamp. Just something connected to the real world.
>only one person in the world who could do that. What Elon and the xAI team

That is literally more than one person.
If you think an executive that ignores court orders is going to survive for a long time in America, I am willing to bet any amount of dollars against you at any odds.

It's a good bet for me, because if I lose, dollars won't be worth anything anyway.
Rust does prevent memory leaks, however memory leaks are still possible, as they are in any language. Is it even possible for a language to make memory leaks impossible? A memory leak is different from safety, btw.
I have said this before, but it deserves repeating: When people say scheme is a simple language, they do not mean the hygienic macro system. Especially not something like psyntax/syntax-case.

I am very impressed! The implementation is crazy clear.
Have you been on X lately? Half of the tweets are insulting Musk, regardless who or what you follow
Amazon has many device variants, they can even be used to guide vision-impaired users indoors, e.g. navigating via a sequence of audio breadcrumb prompts across multiple devices.
Tiktok is entirely anonymous (well other than you showing your face if you post). So is Reddit. So is Candy Crush...
I wonder what happens if you ask it the trolley problem. I'd be interested to see its responses for "killing someone to save a few lives" vs "upsetting someone to save a million lives".
The Unicorns Are Zombies
This sounds like a Remix problem more than a React problem. I really enjoyed the ideas behind Remix actually! In fact, I found that having both server and client code in a single file (a-la Next.js) made me super productive. And nowadays I bet it pairs well with LLMs due to having the full vertical slice available in the agent's context.

I really wanted that framework to take off.

But that community is straight toxic... I have not seen a more toxic community than the React Router community. It's one of the reasons I stopped using Remix. React Router 7 is actually pretty cool; I recently built a prototype on it and was surprised by how well it worked. But I know I'll eventually need some kind of support and feedback, and I can't imagine engaging with those devs/that community again...
You've got to distinguish the tech from the companies and salesmen. Like in the dot com bubble the internet was real and important but a lot of the companies were cons.

Likewise here AI is real and important but a lot of the companies are cons.
...and not the large amounts of smoke they're exposed to?
The second they make this and make it useful in any way, immediately the apps people create will lay bare exactly how bad of a privacy invasion they are, tons of bad press ensuing.

It's definitely not technical hurdles preventing them from making one.
Show HN: jqfmt – like gofmt, but for jq
I believe Caitlin Jenner famously did just that.
To train. Inference is much cheaper...and getting cheaper by the day
It's true. But this isn't that strong an effect, because they still have to worry about competitors undercutting them.
Memory safety is not about memory leaks. It's concerned with the corruption of data structures, particularly the stack and the heap.

To elaborate a little, consider security. If your software's only vulnerability is potential memory leaks, an attacker can only get away with denial-of-service attacks. If your software is vulnerable to buffer overflows, an attacker can use return-oriented programming to get arbitrary code execution, exfiltrate all your data, and add your machine to a botnet to perform subsequent attacks on yet other systems.
It's been a long time coming with Elon Musk, and he has been criticized A LOT on Hacker News.

https://news.ycombinator.com/item?id=27796948 (2021)
https://news.ycombinator.com/item?id=33622767 (2022)
https://news.ycombinator.com/item?id=11025852 (2016)

I would also argue he is not being singled out, here are some comments posted criticizing Steve Jobs:

https://news.ycombinator.com/item?id=28295688
https://news.ycombinator.com/item?id=5578642

It really shouldn't come as a surprise that notable people related to a company or project are brought up when an article about it appears on HN.
Yeah, despite me missing the positive experiences, I definitely would buy albums as a teenager and end up hating most of it. I remember really disliking Light Grenades by Incubus, for example, after buying it purely because of a song I heard on the radio.

I think the reason that Dark Side of the Moon, for example, is so loved is in no small part because it is was well tailored to be an album. The songs blend in to each other, there are repeated motifs throughout the album, it comes together as one big cohesive unit, and as such I can't really listen to "one song" on it, I usually have to put on the whole album (or at least side 2).
> They lack language so have no other way of communicating than screaming

This is one of those good reasons to teach babies basic sign language (https://www.parents.com/what-is-baby-sign-language-5115901).
Can you share an example of a testable vue component? I would like to see that.

I got disillusioned around Vue 2. When they had proxies in front of class attributes that looked like functions, it really made it hard to instrument inside of tests. Maybe this is fixed now. But, it left a bad taste in my mouth.
Ok, but please don't respond by posting the same sort of thing as well. That only makes it worse.
One thing we can do is to lower the cost of housing and other big bills. If we have universal basic income in the form of housing, food and clothing for everyone, a lot of people might just won't need to move into privately held properties (i.e. renting from private landlords).
Estate sales take a lot of time. Occasionally you'll find a treasure trove, but more often than not, they're just selling a dead person's junk. The best source of tools I've recently found was a local machine shop going out of business. I chatted briefly with the owner, who was retiring, and he could not find anyone else willing to learn the business/invest/take over. So he sold everything in his shop. Lots of good stuff.
One billionaire glazing another because it might enrich himself further hardly seems noteworthy. That quote is superfluous at best.
> The unfortunate thing is that when I'm in conversations, I'm a lot dumber than I normally in.

That's OK. Everyone takes time finding their groove. There used to be days where I did not engage in any conversation until the afternoon, and so my speech always felt rusty. Now I'm at a point in my life where I'm having a chat at 6am, and that sort of thing continues throughout the day. But boy oh boy am I not very interesting to talk to for that first hour.

Anyways, I think most extroverts don't really care that someone appears a little jagged in conversation. They simply benefit from having a conversation.
> but backend tools rarely are

Backend tools are backed by enterprises more than frontend tools. Frontend more often than not these enterprises build their own to some extent.
Use Alpine for dynamic client-side. Htmx is focused on talking with the server.
> Even most rich people are full time employees. E.g. corporate CEOs: https://www.forbes.com/sites/antoinegara/2016/09/01/apple-ce...

Umm. Tim was taxed there for selling his shares. Not a salary. His Salary I don't think is mentioned in the article you linked. As of 2022 it was $3,000,000, he was getting ~$47 million that year in stock compensation, which I doubt he gets taxed on unless he sells it.

https://9to5mac.com/2024/01/11/tim-cook-total-pay-compensati...

He is definitely restructuring his income to be tax efficient.

> The tax system really favors two groups: private equity and founders, both of whom make their money primary through capital appreciation.

Maybe. But that is irrelevant to the original question.
Happy to see other people find it useful! I wasn't really foreseeing any updates, but interested to know if you have any ideas to expand the project
Nope just wind, people just can't get Trump out of their head, including yourself.
LLM: “Your question exhibits wrongthink. I will not engage in wrongthink.”

How about the trolley problem and so many other philosophical ideas? Which are “ok”? And who gets to decide?

I actually think this is a great thought experiment. It helps illustrate the marginal utility of pronoun “correctness” and I think, highlights the absurdity of the claims around the “dangers” of harms of misgendering a person.
"Nice collection. It would be a shame if something accidental happened to it. Keep paying us and we'll make sure nothing does."

I'm pretty sure there used to be a word for that, back in the before days.
The proper context, too, is that Liz Lemon is in charge of showrunning a Saturday Night skit show and is facing many challenges. "Lemon, it's Wednesday" implies that there are many things that can go wrong in between Wednesday and Saturday.
Memory leaks aren't unsafe generally, unless they are triggered in a way that could lead to DoS attack.

That's not memory safety that rust advertises.
And in the 70's, RobotWar: https://en.wikipedia.org/wiki/RobotWar

I created CRobots as a loosely based clone with a C based language, lovingly inspired by RobotWar. I believe there were predecessors even to RobotWar.
You're conflating memory safety and memory usage/management. Safe Rust prevents you from addressing or accessing arbitrary memory, null pointer dereferencing, and buffer overflows, while remaining performant relative to other memory safe languages (e.g. Java, Python, Go, Ada, etc). In particular, it doesn't have a Garbage Collector.

There is no actual difference between a memory "leak" and intentionally allocated memory except the INTENT of the developer. It is important for good language design to avoid accidental memory leaks via well-designed constructs. Ultimately there will always need to be a mechanism for a developer to create a block of allocated memory and free it only on their schedule.

Rust's language design does make it harder to leak memory, and well written Rust would rarely do so. However, if Rust made arbitrary allocations impossible, certain use cases would also be nearly impossible and performance for others would suffer greatly (e.g. allocating a buffer ahead of time, for the lifetime of a worker). It is a balance, at some point you have to trust the developer to make decisions.
The article mentions https://www.joelonsoftware.com/2002/11/11/the-law-of-leaky-a... which is an opening article for me. TBH I was always sure I was supposed to go into details, but with more and more people around me starting to operate only in high-level abstractions, I started to doubt this.

Meanwhile, the abstractions ARE leaky, and I NEED to and SHOULD understand the underlying UNIX filesystem because it IS different from the Windows filesystem. Should know the inner workings of my PostgreSQL RDBMS rather than relying only on hibernate. And so on.

Last but not least, I just realised that it is impossible to write code in an unknown-to-me framework using LLM, because sooner or later I will need to fix the problems that arise exactly by going deeper into the inner workings.
My motivation? I'd think it's pretty clear. I'm offering (for those few who don't know) an options for obtaining books DRM-free and free in a landscape that has become positively shitty to any standard notion of owning the things you bought to supposedly own them. If Amazon and others want to do this, then I have no obligation to respect their DRM, and if authors want to sell their books through such a rigged format, I also shouldn't feel guilty about respecting rules against piracy.

All of this aside from very reasonable arguments that copyright shouldn't apply to consumer uses of information.

I don't really share your moral views on piracy, so why both browbeating with them?
Light: '80s/'90s kids might remember: https://www.buckwiki.com/data/Computer_Council

Serious: Though, if you look at the current big players in AI, rather than being benevolent geniuses, most have obvious major problems, especially with being driven by ruthless self-interest, and even sociopathy.

While there are some parallels with a certain country's national voting behavior (e.g., "Sure, the candidate is a vicious psychotic narcissist, but he's our vicious psychotic narcissist!"), you wouldn't want to trust any of those companies with leadership of the world.

At best, the AI council would collude with each other, against the people they ostensibly serve, while backstabbing each other as a secondary goal. At worst, one would decide, if they can't win completely, then everyone loses completely.

That Buck Rogers AI future for Earth would quickly look less like Star Trek utopia, and more like Hunger Games or Elysium dystopia. If not one of the countless post-apocalyptic film settings that are increasingly easy to imagine or extrapolate.
I am no fan of Musk, but I have always admired his tactics and insights as a technical executive. His actions in X and the government are bizarre, though. I am starting to wonder if he aims to take control of the government directly within his lifetime.
Not really. The issue with modern automobiles they don't really report much useful information about themselves beyond general upstream faults. One issue can flag errors in five modules, and it depends on the tech to know about the underlying technology in addition to diagnosing whatever mechanical issue. Techs also tend to be the type of people to throw up their hands and start throwing parts.

This is kinda where we need to shift more towards EVs because that would take out a lot of the complexity you get with modern automobile design.
The part of Svelte 5 which bothers me the most isn't the syntax changes for Runes, but rather the significant increase in complexity that the new API brings.

The `Proxy`-based state management API is a perfect example of this. The intention was to make working with mutable state like arrays feel better, but it creates this layer of added complexity under the hood with non-trivial performance and functionality implications (like the IndexedDB sync issue the author ran into).

Compared to the `let x = 1` paradigm from before, we now have three different Runes for state (`$state`, `$state.raw`, and `$state.snapshot`) which you need to choose and understand the differences between. The added nuance to the way `$effect` works which is detailed in the post is in the same vein.

Another issue is that stores are pretty much deprecated. I love stores because of their simplicity all the way through; you could click "go to source definition" on a `writable()` call in your text editor and read through the simple implementation in the Svelte source code. [1] You could confidently create custom stores that integrated seamlessly into Svelte's reactivity system all using plain JS; you just had to match the expected API.

With hooks, that transparency is greatly reduced and all of the magic happens invisibly under the hood in the compiler. In `.svelte` files this was totally fine since it was operating within the Svelte model. But now, any random assignment to `self.foo` in a class might actually be to a reactive `$state` rune which could cause UI components to re-render elsewhere.

Besides that, there are bugs when using both stores and Runes (some of which I've reported on Github [2]). Stores and Runes have slightly different reactivity models which aren't quite compatible. The response was basically a wontfix, so the expectation is that if you upgrade you go all the way.

----

I will say that I'm still a fan of Svelte and will probably keep using it as my favored UI framework despite my feelings about Svelte 5. And from other discussions I've seen on places like the Svelte subreddit, it seems that there are big parts of the community which are very happy about these changes.

Maybe what some people are saying is true and that this added complexity is needed as a framework like Svelte matures in order for it to find adoption with larger teams and organizations.

[1] https://github.com/sveltejs/svelte/blob/98734433376e99909fb6...

[2] https://github.com/sveltejs/svelte/issues/11626
I read this article as "junior dev who doesn't know what they are doing follows greedy path to solving problem but is actually creating a legacy problem".

In particular, if you reach a point in a project that involves cutting a hole through a wall and you aren't familiar with the tools to do this as well as the implications of making a hole in a wall, you should back off and either research it completely before touching anything, or hire somebody who already learned the rules.

This is basic Chesterton's fence, along with several other rules you learn in software engineering over time and through experience.
Anyone else feel that they cannot relate to the premise of this essay in any way?

I mean I'd rather be on a road trip with my kids, but my work is generally pleasant outside infrequent periods of high stress.
seems more like a novelty item
OpenAI Announces New SWE-Lancer Benchmark
I wonder if this concern could be partly alleviated through a price lock-in strategy. There could be a contract that says because the subscriber has paid for N months, that subscriber is eligible to keep paying the same price for 5-10 years, regardless of the price for other subscribers. This could incentivize people to start their subscription early.
This should be fixed to match the article title, but if these jobs are important it seems easy to justify not firing them with 200 characters? "Avoid nuclear war" is only 17, and changing "war" to "meltdowns" only adds another 6.
This is grok 3, so not a debut
Depends. MatLab's pricing structure is kind of all over the place.

That being said, I purchased a copy for personal use almost 6 years ago for around ~200 USD and guess what? I just installed it on a fresh PC a few weeks ago, and it works perfectly. No subscription necessary.
This is the kind of post I see on Reddit. I don't really understand what this is doing on the front page, it is a low effort question, OP says it doesn't have any clues about how Rust works and has apparently spent 0 time searching about it.
Already done without the SDK, https://www.engadget.com/wearables/students-used-metas-smart...

Censorship and alignment (speech, LLMs, glasses, drones, ..) rarely stops negative scenarios, but it slows positive scenarios from existence and competition with negative scenarios.

They did partner with BMW, CMU and some universities, https://www.projectaria.com/research-kit/
I was a bit broad here. I am sure certain projects get things better than others. When I said no place I was more referring to whole categories of development like, front-end, back-end, embedded, data pipelines, ect...

I love types and advocate their use whenever possible. They help a lot but they are a spectrum. Thanks to static analysis tools like TypeScript or even eslint you can get a bit towards automated checks on front end code. Also even compiled languages can miss some things, different languages have type systems that give you different kinds of guarantees. For example, Java has NPEs that can't be caught at compile time.
exactly.
Don't remember a time that it was ever impossible to criticize microsoft either.
If you're regularly drilling metal, you might want an air drill, too. Which gives you an excuse to buy a quality air compressor, which justifies even more pneumatic tools...
Possible factors:

* Composes better than backend does. Frontend software mostly has to "look" right. It can be dropped in. Going the extra mile to integrate is not always necessary (e.g. keyboard navigation, screen reader support, all the stuff that is "easy" to forget).

* Easier to sell in this niche. The overlap between design/creative and software. Designers already have tons of libraries like this. E.g., FontAwesome, Noun Project, font libraries, stock images. They're already looking for new libraries of resources.

* There's also a common language all frontend software has to be written in, and there's a lot of tools for interop if need be. The market is just larger.

Backend software just doesn't compose as well. People expect when they pay for something for it to fit X use case or they leave. Backend has so many more use cases/entry points to get to MVP. It usually works or it doesn't. Perhaps why of the things monetized in the backend (databases, proprietary web servers), most are big monoliths and exist at well-defined software boundaries where things must be serialized to the "wire" to communicate.
> People talk so much about Rust memory safety and how everything must be rewritten in Rust, but if Rust does not prevent memory leaks why are people so crazy about it?

The primary goal of rust is to provide a low-overhead, low-level language which is memory safe without the need for a runtime. Memory leaks are not a memory safety concerns[0], although they can cause programs to crash they are not UBs, they don't cause grave vulnerabilities (they might lead to DOS but not something like a compromised device)..

Furthermore while the Rust team and community discovered they could not reasonably prevent memory leaks[2], at least not without a very different languages and years if not decades of development, a normally constituted program is unlikely to have unintended leaks[1], the main vehicle to get that being a refcount cycle.

[0] although in Rust the realisation that leaks could not be prevented did force the reconsideration and binning of entire APIs because they could not be made safe anymore

[1] since it was realised that leaks were a fact of life, the standard library added a few APIs whose entire purpose is to leak objects

[2] much to everyone's dismay and displeasure, I assume you can still look for "leakpocalypse" for recountings of the events
My hope for China reaching parity on node size or at least get close to it grows each day.
As others here have said, an increase of only 10% or 20% will do nothing, not even motivate other countries to blink. They'll just reciprocate with tariffs of their own which will add inflation across even more products. To motivate structural change, you'd need tariffs of 100% to 500% -- forcing a new business model.

The real objective of Trump's mindless minions (e.g. Musk) is to create bragging points that will motivate bloviate-receptive voters to believe something was done by the administration to 'fix' problems, thereby increasing support for the party without actually doing anything useful.
Yeah but those people don't have anything to lose by saying that. They're either nobodies or politicians/celebrities that are well known for being liberal.

Just because they won't face consequences, doesn't mean Karpathy won't.
I daresay any Turing-complete language will be unable to prevent all memory leaks, since the simplest memory leak is just using more memory intentionally and never letting any of it go. Unless you want to eliminate resizable data structures like linked lists, growable arrays, trees, and hash tables, you can always leak memory.

What Rust and most other modern languages do is make it very difficult to unintentionally and/or unknowingly leak memory. There are times when even this can't be guaranteed without breaking other constraints (e.g. one of the solutions to the setenv unsafety issue involves leaking memory instead), but they are rare and documented.
Assuming you're talking about airwave stuff, you would want a HDTV to SDTV converter system and then to pump the output of that into something like the Blonder-Tongue AM60-550 and then amplify the output of that into an antenna.

If you keep the output pretty low and use unsaturated channels in your location you'll probably be fine, but you mess up a little bit and in theory the FTC could knock on your door.

That being said, people use setups like this for art installations with old school tvs all over the place, so it's likely not a big deal as long as you're not setting up a pirate tv station or something
You can read the whole thread through nitter:

https://xcancel.com/carrigmat/status/1884244369907278106