kuschku

Is that the version that looks like old reddit, but also only loads just as few comments as new reddit, and just as few nesting layers?

> If GPU were from the get go designed as a parallelism tool first and video game tools second the hardware architecture and the language would probably be different than today and simpler (and if the competition between the duopoly didn't sabotage things)

Sony tried that with the PS3's Cell processor, just a wise parallel vector processor instead of dedicated hardware.

If you knew how to use it, you could get great results, which is how Naughty Dog's games became so spectacular. But if you just tried to port an existing game, things went downhill quickly, which is why GabeN talked on stage how much he hated the PS3.

Oh and this complexity led to lots of games just switching to one of the existing engines that supported it natively, and started the modern dominance of Unreal Engine. But it's also why engines introduced more parallel architectures, which a few years later became very useful when quad-core processors in PCs became mainstream.

I understand that it feels that way, but this has been widely studied and it's just not the same.

When you repeatedly follow directions, you'll learn how to take that path.

But when you repeatedly read a map, or walk an area on foot, you'll also learn the roads and areas you're not taking nearby, and learning the spatial relationships between these places.

A lot of learning happens through the mistakes we make, because they teach us a lot more about our environment. Whether that's a physical landscape or a codebase.

When you search for a bug, you'll look at maybe one or two files that are related to that bug, but also 10-20 files that aren't. You won't consciously remember the content of those 20 files, but your mind is building a map of their spatial and logical relations, which helps you the next time.

We learnt MIPS assembly as part of the processor design class, where we built a DLX processor & emulated it running our code, and then we learnt x86 assembly as part of a class on debugging & reverse engineering (which is also where you'd usually have the good old bomblab assignment). That was in 2014.

> Remove GPS and people will have to figure out how to read maps again.

It's not GPS, but turn-by-turn navigation. Remove that and people's spatial understanding of their environment improves significantly, and this improvement persists even long after the experiment, and they'll even be able to use turn-by-turn navigation better.

Which aligns with Anthropic's reports that people are able to use Claude better if they understand their own codebase better, and that increased Claude usage leads to reduced understanding of the codebase.

When society replaced walking as the primary mode of transportation with driving, people started going to the gym to keep their body in shape.

We should probably be training spatial perception (replaced by GPS), understanding of algorithms and data structures (replaced by coding agents), too.

Where Schuko is common, we just put fuses inside powerstrips themselves, often integrated with e.g. lightning protection.

> And for the times when 240V (or 208V) is a better fit, we have that available to us relatively easily.

But those are the situations where we then use 3-phase 400V

It's definitely easier in a minimalist & tidy home. Our rugs have no fringes, cables are either rolled up or permanently installed & hidden, chairs are stored at night upside-down on the tables they belong to.

Sure, it's not perfect, but it's still really convenient.

The trick is dialing the things in properly once, and then reaping the benefits over and over again.

e.g., my home is always vacuum-proofed. It automatically runs through all rooms except for the bedroom at night, finishing just before my alarm clock rings, then vacuuming the bedroom an hour after the last person's alarm clock has rung.

This way I never actually notice it, but the home is always perfectly clean as if by magic.

Similarly, if you use separate dishwasher detergent, antisurfactant and salt, and properly dial in your water hardness, it'll be able to clean everything no matter how dirty the dishes are. Including dried-on tomato sauce. Just put the dishes in, and they'll be clean the next day.

Of course it takes a bit of effort to set this up, but then it just works for a long time.

Similarly, I'm a big fan of handwriting software with care & focus on quality, which takes a bit longer at first, but then allows you to trust the software to continue running for years to come.

> What community contributions? Linux is mostly corporately developed with Google being one of the major contributors.

Linux has a lot of corporate contributors, but it's been a long standing problem that many of these only add new features that their new pet project needs. Long-term maintenace and improvements is often done by volunteers, and many important subsystems rely entirely on volunteer work.

This was also famously an issue with e.g. AMD's GPU driver, which was appreciated as it allowed a mainstream GPU to be fully supported with an in-kernel driver, but the disadvantage that now volunteers had to maintain hundredthousands of LOC of code, most of which was autogenerated hardware interfaces with little documentation, which made refactoring and cleanup work almost impossible.

> Google also fully maintains the ART VM running on Android - despite Oracle, the owner and developer of Java - famously wanting a piece of it.

Had you followed the release notes, you'd have noticed that that hasn't been the case since Android 8 Oreo, when the entire Java standard library on Android was switched from Apache Harmony to OpenJDK. That's why Android was finally able to move beyond Java 7 and introduce modern functionality, fix the broken NIO implementation, and add JSR-310 Date and Time fuctions, just to mention a few of the improvements since then.

These have been developed by the Java community, including corporations and individual contributors.

Google also made that argument, and further argued that they could do it better.

Which is why they planned to replace the entire kernel and services with zircon and fuchsia, and a new Android runtime ontop.

Guess what, turns out Google actually does need the community contributions of the Linux and Java projects.

One of the largest issues of LSP is that each language implementation needs to do everything separately, and that means each language will work differently.

Imagine if all the editing tools in microsoft word were specific to the language you used, and if you mixed German and English, each had different tooling.

Now if you mix Rust, HTML, JS, and CSS, they'll all have separate tooling, seperate "go to definition", and separate refactoring. Worst of all, none of them can see the definitions of the other ones.

So what you'd actually want to do is parse each language into your AST, with proper annotations as to what is what, and have all the "go to definition", the UI rendering, highlighting, refactoring, etc all done generically by the IDE ontop.

Which is much much closer to how Jetbrains IntelliJ does it, and why their tooling can handle "find usages" on an HTML element to find matching querySelector in .js files and matching selectors in .css

And if you subscribe to the AI stuff, you'd also want your AI to operate on this AST so it can learn skills that generalize across all languages.

That's always been the deal: they can build their OS on the work of many volunteers, and we in turn can build our projects on top of the OS.

Google is trying to take from the community potluck without giving anything back.

Who is this "he" you're talking about? Or were you referring to an LLM? If so, the correct pronoun would be "it".

Your english is really good, except for that little mistake.

I actually managed to travel from one star system to another in DSP without warp, they happened to be just close enough that a full inventory of fuel was just barely enough to make the trip.