15,014 karma · joined April 15, 2013
twitter: @jcdickinson element: @jonathan:dickinson.id email: similar to element
The C# compiler could do it to a degree, but there would be too many caveats to make it actually useful. Unless the JIT team has a change of heart, you're probably never going to see this.
ICE is a proto-gestapo for what it's worth - including having a way to report unwanted ethnicities. They answer to the sovereign and are not accountable to the law of the people.
We will only know the actually situation once Anthropic goes public and we can look at their books.
This is an illusion, I assure you. On a side project of mine with behavior that's very hard to translate into an algorithm (never mind code), after a few failed attempts between the both of us, I figured it out. I gave the AI (Opus) an extremely specific algorithm with detailed tests. All completely and utterly ignored (including the tests), like I never even said it. It proudly declared the work done without ever having written the tests that would have proved that wrong - it basically wrote code that didn't change behavior at all, it just gave the illusion of looking busy.
That's just a single extreme example that comes to mind, but I've had it ignore me at least 4-5 times a day this week.
If you think agents are fixing things reliably then you simply haven't noticed that they are "looking busy."
You're implying that Gamers Nexus is some form of Linux outlet/content creator. They aren't, they only started doing Linux content this year/late last year (and only plan to do it rarely).
You've taking a surprisingly hostile stance on the one (at the time of writing) pro-Linux comment that suggests that it might not be ready for everyone, and to wait if it's not a good fit.
And it isn't beef wellington vs bread and water. It's 80% lean beef vs 82% lean beef, in the majority of cases (and in either direction). And "suitable for your purposes" also means that 160FPS is really fine if your screen is 144Hz - doesn't matter if Windows does 180FPS (unless you're doing something competitive or extremely latency sensitive).
I think Microsoft can do fine without people tilting at windmills for them.
Gamer's Nexus has a pretty extensive benchmark video: https://youtu.be/ovOx4_8ajZ8?si=Cx5Q1a-lMMm14H4i . They refuse to compare to Windows, and it kinda makes sense: if it's satisfactory on Linux for your demands then who cares what Windows can do?
Here's a less professional, but direct comparison https://youtu.be/Giois6VtLPM?si=XFaVUMbea3u0AmP. An extremely important thing to note: AMD GPU. I personally have no idea what NVIDIA is like, but it sounds like their drivers are still all over the place.
And kernel-level anti-cheat doesn't work, though some (e.g. EAC) run in user mode if the developer allows it. Make sure to check ProtonDB for the games you care about. I have personally never had a good experience with Linux builds of games, so I just always use Proton now - but maybe I'm cursed because others have passionately disagreed with my experience. Either way, if a Linux game is broken/bad, try forcing it into Proton.
I don't want to say, "switch now" because it still has rough edges in terms of gaming. Better for you to have a great experience and stick around, than hate it and leave for good. Only you can figure out if it needs more time to cook based on some very light (ProtonDB) research.
I last used a Windows machine about a year ago, and I can say with confidence that the average desktop experience is significantly superior to the barrage of bullshit that Windows puts you through.
Printer is great though. I've never used a Bambu, but after a thorough round of Orca calibration this (at the time) newbie was able to get some really decent PCTG and even PA-CF prints.
Web interface can't hold a stable video stream.
Louis Rossmann has decided to put himself in the crosshairs instead, with a video goading Bambu: https://youtu.be/1jhRqgHxEP8?si=BwfoCKxujd0XwNJ0
Here's what I don't get. How is infra load any different between someone using their slicer build, and someone using their code in another slicer (or a fork)? It's still (ultimately) the same human making the same requests. If they can't handle the load then the solution is to obviously carefully manage the supply of the printers, if your infra is incapable of handling more than 3 users (accurate figure going by the tone of their blog post), then don't have more than 3 of your printers in the wild at any single time. Problem solved.
Fortran: https://github.com/ROCm/hipfort
Python (not sure about JIT): https://rocm.docs.amd.com/projects/hip-python/en/latest/
Protest this by using a paid email provider. My $60 yearly payment just went through today, is that honestly too much for the typical person around here?
Could maybe be forked with some dynamic smarts, HIP is basically 1:1 with CUDA: https://github.com/amd/amd-lab-notes/blob/release/hipify%2Fs...
Qwen-coder-next is considered SOTA for things you could actually run locally.
My stance is that anyone pointing at it in either light probably isn't taking everything into account. It's an incredibly immature theory space - are we going to get 20 more branches of it (making it modern epicycles), or are we going to see one of the current branches pay off?
Edit: and tasks.
I think avoiding async entirely might be a mistake, and I'm not entirely convinced anything better than a general-purpose async runtime might exist for a JS runtime (it itself is general purpose after all).
Avoiding std::fs is fucking bizarre to me: it's completely sync and is a really lightweight abstraction over syscalls.
I never said "binding obligation," that is the first time "binding" has appeared in this discussion and was introduced by you. Once again claiming things I have never said. Doing what you are free to do can still be a shitty thing to do.
I am a bluffing moron who knows nothing, you win.
Please don't put words in my mouth when I have clearly stated the contrary. I used the word "disclosure," that is very different to keeping things secret.
> There is no such thing as "the responsible disclosure protocol".
And yes, I admit I got dragged down to their level and beat myself with a dumb stick in the process.
No, it's commonly followed practice: https://en.wikipedia.org/wiki/Coordinated_vulnerability_disc...
I'm all for lighting a fire under the developer's ass, but we live in an imperfect world and the biggest problem that we have is end-users. We may have applied the mitigation on day 0, and updated as soon as the kernel landed in our distro - and if some of us didn't then we've even got savvy users in that "don't update fast enough group" (which is fine, which is human, but is said imperfection).
Major distros should at least have gotten a few days of notice for something this catastrophic. It doesn't help that the kernel is fixed if "normies" aren't able to access it on day 0. For reference, the standard is 30 for the developer to fix and 90 for it to land on machines. Even 30+7 would have been a substantial improvement.
Ethical security research involves ethics, and maybe they aren't referenced in university/college any more - but here's what I was taught: https://www.acm.org/code-of-ethics .
> 1.1 Contribute to society and to human well-being, acknowledging that all people are stakeholders in computing.
> [...] Computing professionals should consider whether the results of their efforts will [...] and will be broadly accessible.
> 1.2 Avoid harm.
> (Honestly, all of it)
> 2.3 Know and respect existing rules pertaining to professional work.
> 3.1 Ensure that the public good is the central concern during all professional computing work.
> People—including users, customers, colleagues, and others affected directly or indirectly—should always be the central concern in computing.
Maybe other code of ethics for CS exist; I'd like to know which ethics these ethical researchers were following.
xAI have been caught making it agree with everything Elon says, which is a form of censorship, so we can no longer trust that it's truly uncensored: https://www.theguardian.com/technology/2025/nov/21/elon-musk...
Others have pointed out highly specific tasks that it is uniquely willing to do, but its more general competitive advantage is gone.
> You: No, I wouldn't, because my own preferences are towards immediate disclosure.
And there it is. You could have said "I don't think responsible disclosure is a good idea" and moved on, but now we have whatever the fuck this is.
Bluffing sure as hell beats incapable of being wrong. I'll take it.
> In computer security, coordinated vulnerability disclosure (CVD, sometimes known as responsible disclosure)
I guess you can learn something new after 36 years.
If you are referring to what you quoted, your pedantry and sharpshooting would result in an incomplete English sentence: "that's why we have the responsible disclosure" is missing a noun. Now that we are firmly in worthless pedantry:
Protocol (n):
1.a. a system of rules that explain the correct conduct and procedures to be followed in formal situations
1.b. a set of conventions governing the treatment and especially the formatting of data in an electronic communications system
If you don't like what I said or disagree, poke holes in factual inaccuracies. However, in the reality that I am pretty sure we all share, responsible disclosure is a well established protocol that is followed by many security researchers, and was imperfectly followed here.
> Is your software AI-era safe?
> Copy Fail was surfaced by Xint Code about an hour of scan time against the Linux crypto/ subsystem. [...]
> [Try Xint Code]
More chaos makes their product seem even more attractive.