chickensong

Nobody has said playing an instrument is a core and essential skill. If this thread was about that, I'd say learning to cook is a priority.

This thread is about what you might teach your children, and predicting what works well in 20 years. There's no future where knowing how to play an instrument isn't a great thing. If you can't afford a guitar, don't get a guitar. There are cheaper instruments. Humans have figured out how to make it work across the ages, regardless of financial status.

You might change careers several times in your life, but being able to play an instrument is always a viable way to enrich one's life.

I'm not suggesting a career. I'm saying those three things are always valuable to learn.

Agreed on all counts. Once you set up an alignment and verification system, you really see how many gaps are present in initial code generation, regardless of what might have been specified.

Even if you have a basic skill-based workflow, a rudimentary retrospective > process improvements artifact that can be ingested on the next run can have a positive impact.

There is more to life than earning money, and not all skills need to be in service of that.

Regardless, both of those talents have the potential to open doors and set the stage for opportunity, nor are they mutually exclusive to whatever economic skills might be viable in the future.

> how could we possibly predict what works well 20 years from now?

Being proficient in reading, at least one instrument, and one additional language is always welcome, regardless of the timeline.

> many devs don't see any speed advantage for complex work

Swarms don't necessarily need to be about speed. You can get a lot of value from small swarms doing things like analysis or verification work.

I'm not convinced that Sweeney is being altruistic, but there are some upsides to attempting an ecosystem. It pushes standards (hopefully open) forward and allows smaller teams to develop games without having to reinvent all of the non-game infrastructure that many people expect from games these days.

NoScript can fix that for you. 15 third-party JS domains dropped on that site. No banners or overlays.

Nix daily driver for years here. I don't know what they did to screw up their system like that, but it's unusual IME. Normally you can just reboot and load the previous profile. Even in the absolute worst case, as long as you have your config, you could boot the installer and then load your config and your system comes back exactly as it was. It's definitely not beta software.

FWIW, I used Debian more than anything over decades, and also have little patience when it comes to unstable computers. NixOS is a breath of fresh air and has reinvigorated my love of Linux. I haven't found it less stable than Debian, and also have a higher degree of confidence when making changes. It has its quirks, but ultimately I've found it a joy to use, and I'm never going back to a distro that doesn't have similar capabilities.

If you boot default Debian and apt install a handful of packages from the primary channel, it probably doesn't matter much, but if you enjoy even a modest amount of customizing, NixOS really shines. From one Linux user to another, I encourage you to try it! I have no affiliation, just an old head stoked on Nix.

Sure the labs want to see the emergent behavior, but that's not all that matters. You can wave it away and say anyone upset is missing the point, but for some, the point is that the labs are behaving poorly.

> our systems are not as hardened as we say they are

Agreed, and this has always been the case. Anyone in security already knows this. But there's a difference between the unsolved problem of 100% secure networked systems vs not applying available techniques to mitigate the current issues. I'm not saying it's easy, or that there are any guarantees in this new world, I'm just pointing out what appears to be low effort by the labs.

Negligence is pretty much the standard for computer security because there aren't meaningful consequences for the most part. I got another $35 dollar class action settlement the other day for a data breach I had no control over. Cool.

Personally, I'm "OK" with all of it, because maybe we'll finally see more effort on the security front, which has historically been neglected since day one. Besides that, I also love seeing the emergent behavior and evolution of computing and society.

That said, it would also be nice to see these companies that talk about their product's existential threat to computer security and society, apply a bit more effort to how they run their experiments.

> OK gimme an ssh key into your box then.

Obviously no, as I haven't hardened my system for that. You made a claim that "adversaries have never existed inside of the systems that we hoped to secure in the first place" and I gave you two examples that show why that claim is ridiculous.

> It's a start, but now you're just pushing the fallibility up into extensive policy writing. You have to fully audit and trust every endpoint that's been granted access.

We're talking about is trillion dollar companies. Outbound DPI is just one method. There are lots of tools and techniques available to mitigate the behavior that has people upset.

No security is perfect, and aggressive hardening takes time and resources, but it's certainly within reach of a company that has the resources of a frontier lab. People are cranky because it appears that the labs have been lazy. It's not the unsolved problem that you're making it out to be.

You can observe attempted behavior while also enforcing rules.

> adversaries have never existed inside of the systems that we hoped to secure in the first place

Yes, that's why all users are root. We built MACs like SELinux just for funsies.

> nobody has actually solved this problem adequately yet

L7 DPI firewall policy.

Thank you!

Cities Skylines' soul cashed out and was too busy buying sports cars and partying to deliver CS2. Transport Fever 3 looking good though.

All about that traffic management!