budgefrankly

Drawers were a big feature of early MacOS X, as an alternative to NEXT's multiple columns. App's inherited from NEXT (email, finder, etc.) used columns still, but newer apps used drawers.

It was really well integrated, if the window was too close to the edge, the window would move as the drawer opened in a single smooth animation.

XCode in particular had drawers everywhere.

As iTunes became successful, and everything wanted to be brushed metal, drawers began to disappear in favour of columns.

It's quite hard on the modern internet to find images of that old UI, but here's Preview with its right-hand-side drawer: https://mac.elated.com/2007/05/09/displaying-images-in-the-r...

> changes too fast

The core language has been static for ages, and breaking changes are handled by the edition system so you can use a modern compiler to build code on old syntax. Since the 1.0 release ten years ago there have been four editions.

It's absolutely not changing too fast

> depends on third party libraries that change faster than I can breath

No it doesn't. The standard library is already sufficient for a lot of work; and there is an unhosted version with a "core" version of that standard library which has zero dependencies.

Modern Rust, Java, Python, TypeScript etc. developers choose to use a lot of third party libraries; but that's only because the tooling and ecosystem are both good enough to facilitate that. Nothing about the language forces it.

> Most managers are no longer technical, and just create bloated middle layers that slow everyone else down.

> The only managers that are decent are the ones that have kept their technical skills sharp.

Alex Ferguson was a terrible footballer when he was managing Manchester United. Yet they won the premiership in 6 of his last 10 years in that role, and have never won it since he left.

The skills that make one great at doing work on ones own aren't necessarily the skills that make a _team_ of 3, 6, 12 people all collaborate with one another, and with the other teams within the company.

Good management is rare, due to the tendency to promote engineers into the role instead of hiring people specifically trained in that discipline, but when you're in a well-managed -- and hence highly focused -- team the results you can all obtain together can be impressive.

Telegram isn't even encrypted, at least not in the sense of the on-by-default end-to-end encryption used by WhatsApp, iMessage and Signal. In reality its selling point is that your chat records are placed in foreign jurisdictions so your local police can't easily access them.

https://blog.cryptographyengineering.com/2024/08/25/telegram...

Ultimately the only way to be completely sure is to use an open-source app like Signal that you've either built yourself from source you've inspected; or sourced pre-built from someone you trust.

Yeah, Swift looks like someone started trying to port a C# syntax onto an esoteric object-orientated C-dialect (similar to Vala and GObject) then at the last moment noticed Rust 1.0 had been released, tried to patch on some Rust features, and hit release before they were done.

It's quite deceptive. Rust seems initially hard to learn, but it's a small language, so you arrive at competency faster than you might think. Swift seems initially easy to learn, but is a broad language with lots of edge-cases, so you're never quite as competent as you think you are, or need to be

In this particular case I believe the mountain is largely karst (limestone) and the panels substantially reduced erosion -- particularly of soil -- leading to an increase in fauna that thrive in the shade.

As others have said, it's hardly waste, it's an installation with a 30-year lifespan.