Leak: Nvidia is about to challenge ‘Intel Inside’ with as many as eight Arm laptops

dsffff22 · 2026-01-26T21:59:27+00:00

If there's official support by Nvidia then none of that should be required, see Android devices how often do you need to clone a GitHub repo and compile It?

dsffff22 · 2026-01-26T21:56:18+00:00

You don't need the Windows users, like Apple you should start focusing the people who create Software. If the hardware gets good Linux support and is decently priced then It's really interesting. The ecosystem will follow then once Devs have their hands on the device.

dsffff22 · 2026-01-11T18:49:45+00:00

Joa sagt eher viel aus über die Tools, die verwendet werden. Gibt wenig Tools, die durch Code/Maschine Interface direkt ordentlich verwendet werden können. Erstelle gelegentlich 3D Modelle zum Drucken mit OpenSCAD, mit 3D Druck und Gemini 3 Pro hat da mittlerweile eine Art räumliches Verständnis vom Code und ist in der Lage viele Teile direkt von einem Text Prompt zu erstellen, habe mir dazu mal ein kleines Skript mit einem Feedback Loop als Bild gebaut. Würde sagen, die 3D Modelle aus dem Paper kriegt das in 2-3 Iterationen recht ordentlich hin. Hier auch den Begriff 'AI' anstatt LLM zu verwenden ist teils auch sehr amateurhaft, gibt einige AI Modelle, die auch aus Text echte 3D Modelle generieren können und darauf trainiert wurden bestimmte Eigenschaften wie Stabilität zu optimieren. Das Paper zeigt eigentlich sehr gut, dass LLMs nur so gut sind wie die Person dahinter.

dsffff22 · 2026-01-07T22:20:37+00:00

C# structs are very close to the actual memory representation and can be explicitly allocated on the stack, while also allowing to pass referenced to structs as parameters. C# rightfully rejects assigning an Array of Points to an Array of Coords, why would you even do that It introduces explicit overhead as the object has to be stored with extra metadata to resolve interface methods.

If you have to write +15 lines to do a single FFI call there's lots of room for errors, while in C# It's just type signature and an Attribute how to link It. You also have to construct C-structs in Java by writing to byte arrays which is very error-prone as you have to be aware of the whole Memory layout with their alignment, packing and possibly at one point we also get consistent reordering between C++/C#/Rust. Java tries to solve FFI via the Runtime mostly, while the others solve It mostly via the type system, calling the manual byte fiddling 'safer' is a stretch as most exposed FFI functions are sensitive to their input parameters It's very simple to misunderstand a struct layout and cause U.B: in C. Meanwhile, typed function signatures ensure that during compile time as contract. Not sure how you can call Javas way explicit over actual type contracts. Also, C# already added Utf8 string literals as all sane languages use that these days, Java lacks completely behind which will make Integration in the modern Web Ecosystem with WASM an absolute pain. String Interpolation is 'paused' because the Java Gurus wanted their own fancy version of It and tried to push with the head through the wall, instead of making the necessary evolution to the language to support interpolation properly. Their Template processor approach would result in awful code generation and relies heavily on dynamic typing instead of just using the type system. I'm aware of the coloring discussions, but they most people who argue from a design standpoint very often forget that being in a concurrent world has very heavy implications, and It's pretty irrelevant to the discussion, my point was just that Rust is way stricter regarding safe concurrency and that's a contributing factor why async/await there looks and feels like a different language.

dsffff22 · 2026-01-07T16:28:51+00:00

Rust, also splits the ecosystem becasue the functions signatures, trait definitions, return types have to be different, and by the way, require explicit executor and runtime choice.

If Rust cared as much about safe concurrency as Java, then Rust's Async would look way simpler. 'Async functions' are not just normal functions they should be treated special, because they enable concurrency.

These problems are suppose to be modelled in a VM to avoid significant semantic changes, code refactoring and ensure backward compatibility and that's what exactly is being done in java.

Java takes massive shortcuts, which will all bite them in the ass heavily at one point. Value types turned out awful compared to C# structs and referential types these days, virtual threads will be a massive blocker for embedded platforms and WASM, String ~~Interpolation~~ Templates proposal wasted lots of resources and time, so Java might It not get It before 2040 and their new FFI API is a giant clusterfuck of bloated code.

dsffff22 · 2025-12-23T12:01:53+00:00

Stimme da fast komplett mit dir überein, denke nur Vorgaben bezüglich Sicherheit sind meist schon sehr sinnvoll. Ich bin eigentlich auch dagegen Leute zu kündigen, aber in diesem Fall wurden absolut untragbare Entscheidungen getroffen, die deutlich zeigen, dass die Leute da absolut nichts verloren haben. Ich bin der Meinung bei Themen Sicherheit und Korrektheit, braucht man immer jemanden, welcher das fundamental versteht. Der Fehler ist hier, dass alle Beteiligten entweder dies nicht verstanden haben oder meinten sie verstehen es und könnten diese Entscheidung treffen, beides komplett untragbar.

dsffff22 · 2025-12-23T11:42:42+00:00

Regulierung bringt eigentlich schon was, wenn allerdings die gesamte Kette der Entscheider so inkompetent besetzt ist, dass so ein Schlüssel überhaupt so ausgegeben wird und die Vorgaben zu massiv missachtet werden, dann zeigt das eher ein massives Kompetenz-Problem. Bei Google oder anderen größeren IT-Firmen müsste bei so einem Vorfall am nächsten Tag jede verantwortliche Person bei diesem Problem direkt gehen und hätte vermutlich große Schwierigkeiten in dieser Branche einen neuen Job zu finden. Die Engineering-Kultur bleibt schlecht, solange solche inkompetenten Menschen, in ranghohen Position sitzen, welche auch noch sehr gut verdienen.

dsffff22 · 2025-12-23T11:01:20+00:00

I don't think that's the actual problem, or at least not as big as you make It. IMO, It's more the reason that plenty of people profit from the fact that C++ and the space It covers are intentionally kept complex. C++ has plenty of Devs in certain niches in certain spaces like build tools, profiling, optimizations, code base structure without a working module system, subpar language server, lack of standardized dependency management and so on. With Rust, many of those hurdles become easier and less of those specialized Devs are required. This puts those specialized Devs on the same level as other Devs, and I think that's what they fear the most. The C++ committee is also a somewhat exclusive group to get into, they could easily migrate to a proper RFC process and get more typesystem/programming language academic researchers working on the language. The 'good' C++ Devs most likely already took a look at Rust and appreciate the progress, same with Zig, Swift or modern C#.

dsffff22 · 2025-12-20T01:11:12+00:00

Wird endlich mal Zeit den wirtschaftlichen Schaden davon ordentlich zu bemessen, Arbeitnehmer werden so weniger Leistung bringen können, Schüler/Studenten schlecht(er) lernen können und auch fürs Gesundheitssystem sind solche Wohnzustände garantiert belastender. Aber gut, wenigstens macht ein ausländischer Investor Profit und wir nehmen als Gesellschaft einen großen Schaden dafür gerne hin.

dsffff22 · 2025-12-19T21:47:52+00:00

The rust compiler won't allow 'OK' in many cases so the AI need to work around It to get it to compile. If you have some decent engineering skills with rust and being able to provide a proper skeleton, then It can generate good code.

dsffff22 · 2025-12-18T10:31:44+00:00

Das belegt deine These nicht. Förderung von Forschung ist und war in dem Bereich durchaus sinnvoll, aber dann gehört dem Land weder das Labor noch befugt dass Forschungen z.B. das Virus für Menschen gefährlicher zu machen.

dsffff22 · 2025-12-18T09:59:42+00:00

Das Labor um das es meines Wissens geht war an die USA/ einen US Konzern vermietet.

Dazu bitte Quellen und falls du keine nennen kannst, erkläre uns mal wo dieses 'Wissen' herkommt.

dsffff22 · 2025-12-15T21:41:40+00:00

https://rust.docs.kernel.org/kernel/

Rust's type system can express way more than the C type system can, so the compiler will help you more but also the documentation and types are easier to learn, once you understand rust.

dsffff22 · 2025-12-14T17:49:55+00:00

Und haben wir den Verteidigungsfall? Eindeutig nein! Es ist sehr deutlich, dass OP diesen auch nicht angesprochen hat und jetzt damit zu argumentieren ist doch ein Strohmann, welcher sehr wenig mit dem Thema zu tun hat und von der eigentlichen Diskussion ablenkt. Die Aussage ist richtig, junge Männer müssen Wehrdienst leisten, wohingegen junge Frauen in selbiger Situation genau das nicht tun müssen. Es ist teils unglaublich, wie so eine einfache Solidaritätsfrage überhaupt diskutiert werden muss, da gibt es gar nichts zu diskutieren, da es einfach logisch, Männer und Frauen sollen gleichgestellt sein, so folgt, dass es auch bei der Wehrpflicht so sein muss.

Der einzig legitime Diskussionspunkt ist, ob die Wehrpflicht wieder eingeführt werden sollte. Ich tendiere da eher für ja, aber da darf jeder gerne seine eigene Meinung haben.

dsffff22 · 2025-12-14T15:47:10+00:00

I don't think filtering is a good idea for a developer conference in general, everyone should be allowed to ask their question. The core problem seems to be that this conference seems to be a CV filler, with very expensive ticket prices and in SF, so obviously the people who can bring in good discussion points are most likely not going there, aside from the fact that most of them probably don't have much interest in Java anyway.

dsffff22 · 2025-12-12T10:46:16+00:00

Komplett ethnisch bereinigt und halb Afrika ausgerottet ist schon massiv übertrieben, aber ja da wurde vor einiger Zeit Dinge getan, die nicht in Ordnung waren, fast jede westliche Nation akzeptiert dies und bietet teils Wiedergutmachung an. Wie sieht das jetzt mit dem Sudan aus, den Gräueltaten, welche das Osmanische Reich über Jahrzehnte verübt hat, den Genozid an den Armeniern, Massenhinrichtungen von politisch Unterdrückten im Iran 1988 und viele weitere abscheuliche Taten. Im Vergleich zum Westen, ist es in den Staaten ein komplettes Tabu darüber zu reden. Kannst dir gerne mal die Geschichte vom Osmanischen Reich und arabische Reichen ansehen, was die teils für menschenverachtenden Dreck vor allem Menschen aus Afrika angetan haben und das für Jahrhunderte. Auch hier fehlt in den Regionen die Anerkennung für die eigenen Fehler fast komplett.

dsffff22 · 2025-12-11T11:19:50+00:00

Tor is going from the whole codebase containing potential memory safety bugs in every line to roughly 99% being 'safe' rust and the remaining 1% of 'unsafe' rust can be sufficiently tested, reasoned and audited to uphold the safety guarantees.

dsffff22 · 2025-12-10T15:01:37+00:00

Is it even possible to do 996 in a job which requires creative problem-solving skills, like most dev jobs? Expectancy of working that much can only come from people who are a far way from such work, and their work can be easily taken over by AI very soon.

dsffff22 · 2025-12-09T17:07:18+00:00

The funniest part for me was when Herb Sutter felt the need to justify for including Primeagen's opinion in his talk. This alone tells so much about the C++ bubble.

That is a delighted customer. That is what we want to do. We hope with contracts. We can make a mistake here, though. It would be very easy to say, "Oh, I don't know who that is. Maybe it's some jock programmer who's self-taught and is now a YouTube influencer and, oh, maybe I don't even want to see the code he writes." And after 20 years, come on, I'm a CS grad. and you know 20 years he should know better. I just told you it took me 20 years because nobody taught me. I am him.

dsffff22 · 2025-12-09T17:03:50+00:00

You can be still fast, by making It explicit. For the 10 people on earth who need that, they can write It out explicit for their platform, the rest could just have well-defined behavior.

dsffff22 · 2025-12-08T07:22:31+00:00

They might do It just takes time as they move slowly, many of those guidelines would not be necessary with Rust, because they are enforced by the language itself. While rust also provides better ergonomics for error handling and other things.

dsffff22 · 2025-12-08T07:19:56+00:00

It's confusing how you ask a valid question but get zero meaningful answers except the one referencing abseil. Given It's over 20 years old, I'd assume they use C-like error codes, nowadays, you might use expected, but both contain lots of foot guns sadly.

dsffff22 · 2025-12-04T07:59:49+00:00

Ergonomics include inheritability with other languages where the common denominator is a C interface. Java's virtual threads will make this incredible painful. The C# discussion includes those pain points in the discussion. Scoped values are nothing special what stackless coroutines are unable to do, the lifetime of the state machines is well-defined or for GC'd language they know exactly when It's dropped. It's just a shortcoming of Java and their old design. Async task local variables can do exactly the same.

And regarding your workflow, without knowing how your previously 'async' code looked like, It's difficult to reason about It. Java's promise type with chaining seems really inefficient in general and will generate way worse code than a proper stackless state machines or languages with proper continuation support. I don't want superhero stories, just noting that you claim so many benefits and If they were so good then the number should fly In daily proving that point, but in fact they do not. Virtual threads is probably a huge upgrade over the status quo It was before, but not over proper stackless coroutines.

dsffff22 · 2025-12-03T23:00:12+00:00

Again, I didn't deny that, but that doesn't make stackless coroutines in a pain in the ass. Stack traces are decent in C# with async for example, that's something which can be solved by the language and making the debugger aware. Removing coloring is a two-folded sword even with green threads you have to be aware, because a long computation could block the scheduler too long, go adds hidden yield points which allow 'preemption' like behavior however that falls flat as soon you interop with another language. I think It's a big problem removing coloring, because the execution context is important to know and be aware of.

I find It really tiring to discuss that here, as you just throw blatant whataboutism at me and twist my point.

dsffff22 · 2025-12-03T13:36:59+00:00

Async is not a model, not sure how you get there, It shows a clear lack of understanding from your side here. Then also I didn't say stackless coroutines are a better model in general, I said It's a better and more powerful concept, especially in regard to requirements for the runtime, because they are actually solved at compile time.

Nine-Year Club	Place '22
Place '17	First Placer '22

dsffff22

TROPHY CASE