skysight-inc/HackerNews huggingface dataset:
How much do you trust your Linux distro devs?
I will assume everyone understands the security problem when a build isn't reproducible. In short, just because something is open source, doesn't mean the compiled application you're downloading and installing hasn't had any malicious modules added to it before being compiled. It's not enough for something to be open source, it has to be reproducible as well.

I don't think there are any reproducible linux distros. Every one I have looked into requires you to download and install from an image file. That means you must trust the developer who signed that image because they could add all kinds of malicious code to it.

We always suspected that winows, mac, android, ios are spyware for the intel agencies and now it has been proven that ios has a backdoor most likely put there by NSA.

Why don't we suspect the devs of linux distros to do the same thing?

What do we really know about the people signing the image files? do you even know their names?
It's also a bit crazy how so many people trust SELinux when its made by NSA.

Is this the reason why most people don't bother trying to potect their data from the intel agencies? No one wants them doing their unconstitutional and illegal snooping in our data, them finding out that we like to listen to the rick roll music video but maybe it's simply impossible to prevent that, 100% impossible no matter how hard you try.

LSMs won't help us when the distro itself is corrupted.

Or do you actually trust that your distro image file that you installed from and any updates later aren't compromised?
Tell me which distro you're using and what you know about the devs who sign the image file and updates and why you trust them? Keep in mind they can be forced to compromising the distro and forced to keep silent.
Yeah, I was discussing this with my wife the other day. She spent about 10 minutes looking for a doodad and when she eventually found it, I was quite surprised. It took mere seconds to open that last drawer where she found it. She could have just opened it first and saved herself almost all of the 10 minutes.

It was a learning experience: always look in the place where the thing is. It saves a lot of time. Her problem was that she first checked all the places it wasn't.
As a former employee of a 100K+ person company, I've had these exact thoughts several times. I worked in acquisitions, and constantly was finding out that we were reinventing (or rebuying) the wheel internally in independent departments.
Intel Xeon D-2700* or 1700 SoC are the preferred "low power servers" in practice. Yes, they idle at 25W, but I bet you that the Xeon D-2500 will have more performance than 10x Rasp. Pi 5.

More importantly: there will be server-class features like out-of-band management/IPMI, 10Gbase-T ports, etc. etc.
That would be helpful for many corporate departments which more or less have fake missions to make their exec sponsor look cool temporarily.
I've been playing around with an idea about OOP for awhile, not sure if it'll ring true or not but I'll run it up the flagpole for feedback.

I think FP is a great way to program actions and agency but OOP is a great way to model the world. I like Rust's trait system because the polymorphism is based on what you want an object to do not what it is. But when you're creating models of the world it's usually really convenient and even accurate to use nested inheritance models. Maybe the original system for this is the flora/fauna taxonomy but it applies to a lot of things; like GUI elements or game models.

If this is correct, it might explain why the discourse is so polarized. Whether OOP is a blessing or a curse probably depends on whether you're using a programming language as a modelling language or as a logic/execution language.
…Nobody said they were going to…

Apple could request a sensor with the polarsens mask. It’s just not worth it, from a resolution & light gathering perspective. Big tradeoffs improvements in specific scenarios is not a path Apple has taken typically for their cameras.
I remember when lab grown diamonds really took off, and deBeers and others started calling their diamonds "natural"
In this case, it’s probably because they’re early stage and literally have no idea how to price it and package it.
We really did this wrong. We should get paid for every time the lines are run.
> at the cost of latency and throughput.

Compared to what?

Doing epoll manually?
https://xootr.com/products/xootr-kick-scooter-mg

These are great
Not only do companies not exist in a vacuum, but they have no inherent right to exist in the first place. Companies are graciously allowed to exist because the state (a proxy for the people) approves them, the state grants their charter, the state provides them the corporate veil and limited liability they often abuse... Companies only exist because we the people decided that the public good they are supposed to serve outweighs their downsides. And we the people should also be able to decide that a particular company should not exist, if that company operates against the public good.
Towards Permissionless Consensus in the Standard Model
I'm in the 1 camp. After several decades of C++ I know it very well. Well enough to find some of the things that those Rust and Ada people are saying about their respective languages intriguing. I'm at the point where I need to spend some time with each to see how/if they work with my problems in the real world. Because eventually you have to admit that while you can drive a screw with a hammer there are other ways and maybe it is time to learn how to use a screwdriver.
Clearly he needs a framework for making games in Rust instead of iterating through rust primitives.
They stop making it, and pay generic manufacturers not to.

https://www.nbcnews.com/business/business-news/drug-firms-st...

> Known as "reverse settlement payments," or "pay-to-delay" deals, the financial arrangements are a unique but common practice in the pharmaceutical industry. Essentially, they allow drug manufacturers in some instances to pay competitors not to manufacture generic versions of their products, thereby ensuring that they maintain patent protection for as long as possible.
Semaglutide is made by Novo Nordisk in Denmark. Maybe Denmark could buy the IP or cancel the patent?
Their creative sandbox project is full Rust from client to server I believe. I haven't kept up with it after trying the closed alpha a while ago but it looks like it's still going, and has a name now: https://wim.live

It's still only listed as coming to PC, Mac, Linux and Android so I guess they haven't broken through the barrier of shipping Rust on consoles.
A pharmaceutical company can capitalize on current successes and have enough to hire 1,000 research scientists for future developments.

Or they could take "just enough", hire 10 research scientists, and potentially not make the next breakthrough. Or the company just dies.
> I think about Starcraft from 1998, created when virtually all PCs only had one core, and its 200 unit per faction cap. Blizzard hasn't increased this cap because it doesn't necessarily make the game more fun.

Ah... Starcraft. It's 200 supply per player (hero units take 0 supply, zerglings are 0.5, and the supply cost goes up to 8 for battlecruisers for example). The limit is enforced when building a unit from a building. Map triggers can grant units and you can exceed the 200 supply limit.

The technical unit limit for the map was 1700, and was later in fact extended to 3400 by Blizzard. The EUD emulator (part of the official SC Remastered) allows for online custom games to be played without any third party tools on the player's part. Certain limits like sprites can be bypassed with this tool (for map makers) https://github.com/phu54321/euddraft/blob/master/plugins/unl...

EUD started out as a buffer overflow exploit which allowed custom maps to patch the game client's code. It was later fixed by blizzard but re-implemented as an emulator (with some restrictions).

These are definitely things that enhance gameplay for custom scenarios.
https://youtu.be/HEv_U9WV4PA?t=1541 (yes, that is a battlecruiser shooting nukes)
There's a convoluted process that they can game to extend their exclusivity with the FDA see e.g., https://time.com/6336840/patent-manipulation-insulin-prices/
Could you not lay this same criticism at the feet of the other political parties as well? Due to the way plurality voting works, the incentive of each party is to be as large as possible (at the expense of group consistency), and the incentive of each individual is to align themselves with only one party (at the expense of accurately expressing all of one's views).
We're doing more and more of our back-end work with Rust. The main reason is the performance it provides. It's not just great for our end-users it's also so much cheaper in the modern world where we pay per mileage in the cloud. Part of what we really like about Rust, however, is actually exactly the variable ownership because it makes it very straight forward to enforce and control data-integrity and avoid race conditions. Even for programmers who would struggle to do so in C or C++.

I'm not sure whether or not that's even useful in game development. I've never done any form of game development beyond some Chess game I programmed in my first year of CS 30 years ago. But I'm actually really curious as to why you've struggled with variable ownership, because I'd frankly like to improve our on-boarding processes even more for new hires.

> my other biggest problem is that they keep painting other non-Rust things as being fundamentally flawed for not being Rust

Rust has a cult and it's best not to pay too much attention to it. Don't get me wrong, we're seeing great benefit in not just using Rust over C/C++ but also replacing more and more of our C# and Python services with it, but it's a very immature language and like any other programming language it's still just a tool. If it works for you, use it, if not... Well, use something that does.
Ask HN: Any Alternative to Stripe? (Startup-Friendly)
Moral Drain
I've never seen someone claim it's easier to issue credit in a cryptocurrency than a fiat currency before.
> It's like showing a video of an iPhone taking ages to load a web page or a very grainy photo that it took

LOL. The disclaimer "Sequences Shortened" on ads came about because of other manufacturer complaints to the FTC about very early iPhone ads very much editing sequences to make the iPhone look faster than it was.

> FSD has come a LONG way in 5 years.

And has an even longer way to go. Usable means things like driving in Pittsburgh in winter at night, not "hey, look, it no longer causes near misses attempting to figure out a roundabout in suburban California in the middle of the day".
Tesla employee claimed he does email during commute to work just two days ago on LinkedIn. Maybe his car has some kind of special software??

Can't find the OG post, but it was discussed on reddit, for example

https://old.reddit.com/r/jobs/comments/1cbh024/trending_on_l...
From what I’ve seen, Tailwind Labs isn’t a fan of collaborating with other companies - no knock on them just seems like they don’t feel the need to
Absolutely agree. I think people saw that a lot of games are written in C++ and got confused into thinking that the right thing to do is to build your entire game in a systems language. The fact that we have games written entirely in C++ is mostly just due to the enormous amount of inertia that game engines have, and the fact that many of them have origins that go back decades to a time when the programming language landscape and broader development ecosystem were completely different.

And now, the most popular generally available game engines right now are:
Unity - C++ in the engine, C# for game code
Godot - C++ in the engine code, GDScript or C# for game code
Unreal - C++ in the engine code, somewhat mangled C++ for game code BUT with also one of the most capable and widely used visual programming setups I have ever seen

I wouldn't be surprised if the "next great game engine" had a Rust core and some other language- I mean why not C# at this point?- for game code.
No.
You don't need ability to DI every single functionality.
And you can still do DI with global state, just with less granularity.
Weddings and funerals. Time to break out the family recipes...
I've been writing Rust professionally (and predominantly) for ~5+ years now, with brief detours in game dev. I'll defer to others who are dedicated game devs, but overall I think this article is well written and a healthy thing for Rust overall. We need this kind of breakdown if things are going to continue to improve.

I'd say I only have two somewhat arbitrary comments on this piece:

> Rust on the other hand often feels like when you talk to a teenager about their preference about anything. What comes out are often very strong opinions and not a lot of nuance.

This is a rabbit hole of a topic so I don't want to go too deep into it, but this isn't a Rust-specific issue (though it may be a current Rust issue). I've seen this same pattern play out across so many languages over the years, from Lisp to Rust to everything in between.

A very unscientific and definitely not charitable way I've thought about this over the years is that programming, by nature, is an OCD person's dream. We wind up with a pretty large chunk of people who seemingly move language to language in the hype cycles in search of some weird nirvana level that is likely just unobtainable. I feel like Rust has slowly started shedding this as the community has grown/matured and some people have moved on to the next hype cycle but I often find myself wishing it'd happen faster.

I write Rust because when I sleep at night, I just don't get woken up by being paged for nearly as many weird edge cases. The Rust I write often has a litany of compromises because I want to just get shit done and move on with my life, and the remaining guarantees are still good enough. The number of times I've had to tell people to leave it be is definitely higher than it should be.

> I know that just by saying "global state" I'm immediately triggering many people who have strong opinions on this being wrong. I feel this is one of those things where the Rust community has created a really harmful and unpractical rules to put on projects/people.

This isn't really a Rust-specific thing, though I can't fault the author for including it. People have been beating the drum of "no globals" for as long as I can remember... and simultaneously, as long as I can remember, game devs have come out of the woodwork to politely explain that the programming they do is often under very different constraints.

I still periodically use global state for things because it's just faster at points, and no, I've never cared if people get annoyed by it.

Anyway, here's to hoping this leads to positives for the community.
The following heuristic has become increasingly true over the last couple of decades: If you have some kind of "charset" configuration anywhere, and it's not UTF-8, it's wrong.

Python 2 was charset agnostic, so it always worked, but the improvement with Python 3 was not only an improvement – how to tell a Python 3 script from a Python 2 script?

* If it contains the string "utf-8", it's Python3.

* If it only works if your locale is C.UTF-8, it's Python3.

Needless to say, I welcome this change. The way I understand it, it would "repair" Python 3.
I’m not sure I’d describe San Francisco as a whole as being clean and shiny at any point in probably in living memory if you take cities like Singapore as benchmarks. But in 1990s- maybe 2000s say it was probably not advised to walk on Howard especially after dark and generally south of Market was often viewed as sketchy.

I’m not sure it’s just about hybrid either. To the degree that at least certain cities are increasingly seen as having more cons than pro I expect a lot more people will pass especially to the degree they’re not more convenient for working. Of course this can become a cycle as it has in the past.
Galaxies have the advantage of emitting their own light. Planets reflect only a tiny fraction of their host star’s light, and the inverse square law hits twice.
He did not "win in court", a consent order means both parties agreed to a mutual resolution prior to a judgement occurring. If I had to guess it was settled this way because of the time, misery and tremendous cost that would otherwise be involved for all parties. "Wins in court" suggests some thorough process leading up to a final evidential determination made by a judge. That is not what happened here, it'd probably be more accurate to say the parties were motivated to cooperate via their solicitors under looming threat of enduring that process.

No skin in this game, but looking at it from the respondents' perspective, 20k split between 4 is incredibly attractive: 5k and an apology to put an end to any threat relating to the issue, given the alternative of potentially unbounded costs to demonstrate innocence with a tortuous and uncertain outcome. From the claimant's perspective it is more confusing, triggering such a heavyweight process then settling for so little given the claimed harms suggests all kinds of things, not least including the kind of advice he may have received given the strength of the case as his solicitors understood it.
The problem with right libertarianism, IMO, is that private property rights (as opposed to personal property / "right to that which you're using") broadly necessitate coercion. The notion of abstract ownership of, say, a piece of land that you have never even visited in your life and that you do not currently occupy - which is necessary to e.g. lease it to someone for actually to live on it or otherwise do something useful with it, and then collect rent from them for that use - requires coercive force to prevent people from just using it without paying said rent to you. This is also why any realistic model of a right libertarian society requires government large enough to provide this coercion as a service.
Rust ain't Go but anything Go has can be used as an argument that Rust should try to do better in certain areas. ;)

Perhaps learn another language like Haskell, Swift, or Kotlin before Rust.

Get cargo-bloat, cargo-cache, and cargo-outdated.

Setup a memcache server and use sccache to accelerate Rust, C, and C++ compilations. It's not 100% but it's pretty awesome for things compiled at a stable build location.

Just like any platform, avoid dependencies wherever possible and use minimal crate features. Some Rust crates have an npm-like problem of dragging in zillions of dependencies.
My expectation is that whatever logic held up last quarter held up this quarter. It's possible the optimal allocation is some of both, but what's the tradeoff that would drive that instead of one being mathematically superior to the other?
Sounds like a losing strategy for most customers and businesses

Why not pool costs and split profits. Everyone gets less.. less risk, less losses, less profits.
> Government is just a stationary thug and it has no other goal except of collecting as much taxes as possible.

You were speaking the truth, right up until you got to this line. Governments are beholden to the people, you wouldn't be able to adjust taxation legislatively if taxation was an authoritarian function of the state. Don't accuse the government of being a "stationary thug" when it's the politicians you elect that vote on these issues. If you legitimately believe what you said, you've bought into a defeatist ruse.

In reality, a government's greatest plausible obligation is to protect it's people, and that's what crypto regulations do. You can be as sardonic about it as you want, but tax and sanctions evasion is a crime and crypto exchanges will be treated as aides and abettors as long as they choose to deal in crypto.
I think if we got to the point that we could not rely on Supreme Court rulings being upheld without the mobilization of troops, we will already be in a situation of fundamental institutional collapse anyway, and questions of constitutionality and legality of anything will become moot as we descend into a raw state of nature.
I've worked on Ambient Engine and now on the Bevy engine. I totally agree with these points, very valuable.

I only make some comments from my professional (audio) perspective:

We need the highlight author's affirmation of cli. Rust's tui (ratatui) is great. I used it to make Glicol-cli [1]. If you are a Linux user, you are welcome to test the music production of the code.

Speaking of game audio, I actually think rust is perfect for audio. I have also continued to develop Glicol [2] recently, and my recent goal (starting tomorrow) is the bevy_glicol plug-in. I want to solve bevy's audio problem on the browser.

All in all, even though I've had my share of pain with ecs, I still think rust is very valuable for game and app development, maybe not multiplayer AAA, maybe practical apps.

[1] https://github.com/glicol/glicol-cli

[2] https://github.com/chaosprint/glicol
How is this not a blatent antitrust violation?
Precisely. If these systems aren't or can't be engaged on a Pittsburgh street at night in a whiteout, then I don't much care.

Tesla jukes the stats by "Oh, this won't go well, so we're not even going to try", which isn't an option for human drivers, short of "don't drive at all".
That's neat. Source?
So you believe it's possible that at the time they had evidence to prove the allegations, and thus acted in good faith, and now suddenly they don't have any memory of said evidence? That's an interesting case that I expect we'll be seeing medical papers written about soon!
> And my other biggest problem is that they keep painting other non-Rust things as being fundamentally flawed for not being Rust. "It's not memory safe" is the biggest one thrown around, but when was the last time memory safety was actually a big problem in games? Unity uses C# which is garbage collected, Godot uses its own scripting language which makes it nigh impossible to leak memory, Unreal AFAIK has its own tools that makes memory management trivial. Rust game development feels like a solution looking for a problem to fix.

Memory safety may or may not be important in games, but the ability of engines like Bevy to analyze system dependencies and automatically scale to multiple CPUs is a big deal. Job queuing systems have been popular in gamedev for a very long time, and Rust's insistence on explicit declaration of mutability is a big part of the reason that "just works" in Bevy.
I think I found it:

>> Their lack of care for perf

>> I have to explain yet again
It is completely unreasonable that you are not allowed to speak factually about events that you personally experienced simply because you are not able to conclusively prove that they happened.
Threading, probably.
When I’m reading a piece of paper lying on the table and I need to focus on something at the bottom, I physically push the paper away from me, I don’t scoot backwards with the chair. Not saying that your preferences are wrong, I just firmly believe that “going down the page” itself is something that only happens on a computer screen and has no natural physical equivalent where moving something towards your body would make sense.