Hacker Newsnew | past | comments | ask | show | jobs | submit | Fnoord's commentslogin

OSINT tooling.

Sonoma won't receive updates for long any more. Better off switching to Sequoia. It'll give you 20 months to switch away, instead of 8 months.

Each new macOS version brings new restrictions causing some essential apps to stop working or work in a more complicated way so I keep delaying macOS upgrades as late as possible. macOS used to be an OS that lowered my cognitive complexity but that's no longer true these days due to security overreach.

As a macOS sysadmin I feel this in my bones, and of course I don't know what apps are essential for you, but FWIW Sequoia has been basically identical to Sonoma for me. In fact I had to double check what I was running on this computer before writing this because there's just no functional or aesthetic difference that I know of off the top of my head.

(And yes, I'm holding off on Sonoma for as long as possible because... yuck)


Cracked software has risks attached to it, such as malware.

I bought a license for Pixelmator Pro a couple of years ago. IIRC it cost 30 or 40 EUR. I don't use it much, but it is unlikely you're going to need all of that software.

In that case, may I suggest macOS Tahoe and i(Pad)OS 26?

I hated that UI so much, I'm glad I barely had to use it (that it was slow was due to underperforming hardware, esp. laptops, for which it arguably wasn't meant to run on).

In the meantime, I'll migrate away from anything Apple, for two reasons: 1) I don't want to be dependent on a US company for my OSes, and 2) thank you very much Apple for this design choice making #1 a lot easier. But what I cannot say is 3) it is slow and buggy. I mean, the design itself is bad if you ask me, but the OSes aren't slow. The hardware can deal with it.


The URL and title give it away:

URL starts with 'ai' and the title claims 'is' and 'the new version control.'

I then skimmed through the article, and it mentions it doesn't exist today.

First, it requires an implementation to prove the point, and then it has to defeat the network effect of git. There is zero proof for that argument, only a hypothesis. (Which sums up AI hype pretty well.) Someone's trying to hype AI, just like someone was hyping blockchain. GLHF w/that. Oh, and thank you for ruining the hardware market, assholes.


HyperNormalisation is one of many great documentaries by Adam Curtis, many of which are available on archive.org [1]. Specifically, I can recommend The Century of the Self and The Power of Nightmares. No need for YouTube :) FWIW, these used to be able on Google Video back when that still existed. And via torrents.

[1] https://archive.org/search?query=creator%3A%22Adam+Curtis%22


Learning by mistake isn't painful; it is how you learn best. I keep iterating on that point to my children. But that isn't merely what these guys were doing. They were doing more, since they were documenting their (expensive!) learning process. Documenting your learning process and sharing it freely is allowing others to not make the very same mistakes, but to do better instead. It lowers the barrier of entry for competition, taunting competition who hopefully also share back. Like many talks on 39c3 (esp. the lightning talks), it is an invitation to collaboration.

Sharing the documentation is also an act of compassion, and very much in the spirit of FOSS & OSHW.

This talk was hands down my favourite talk (and not even in a subject I am familiar with!). These two guys shared a lot of info in little time, and were very humble. It was also a presentation which contains a political component (Europe's lack of independence, specifically hardware-wise), but it managed to avoid that discussion. Why, because it is assumed the attending public shares the same value. Instead, it maintains focus on the taking action part. I am not sure everyone here shares said value, but I do, and for whatever it is worth: USA is in a similar boat.


Hey! Talk speaker here, thank you so much for these words.

This is exactly what we wanted to convey: Let's act, our way isnt the best way, but it is the path we're on, and there is little we can do on our own to get to another path.

We don't want to build the european JLCPCB, we don't even know what our company will be in 20 years if it still exists.

What we want is to give knowledge and see more people get into the business of electronics. We also want to give meaningfull jobs to engineers and factory workers which will eventually join us.

We are not going to change the world, I would settle for selling 1 unit of 1 well made product to 1 customer. I would settle for giving one person a job that they love working with cool guys to make electronics. I would settle for the ability to pay my rent from this, from bringing value in the world.


Just curious, is it possible to get some basic production "kit" from China and go from there? I'd assume it's going to be new and cheaper and more "modular", and you only rely them on these basic items. I have never been into electronics manufacturing so not sure if it makes sense.

When they lose a tooth, they just grow a new one. How conveniently cool!

I've been using fish for nearly 10 years.

First, there are some ways to make fish more compatible with bash.

If you want to do some shell scripting in fish, or running other people's shell scripts (or commands) this may aid you since you wouldn't have to port them (or take less time to port them over).

You can achieve this with a plugin system such as 'oh my fish' or 'fisher'. But, as always, it adds complexity (and bloat :P), you'll need it on every fish shell (including remote systems), etc.

It is a bit akin to having nvim with plugins versus being able to use vi. Sometimes, you're going to need to be able to use the latter.

Also, to people who recently adopted fish: fish has been made more and more compatible with bash throughout those years.

FWIW, I use fish with starship these days.


When I'm in fish and I want to run a bash script I just... call it with bash :-)

./script.sh

and script.sh just starts with #/bin/bash

I'm simple


If I use fish, I want to make use of it, and that means I will want to convert scripts, or simply learn to write scripts compatible with fish.

Shell scripts from third parties stick with whatever shell they were written for (ie. /bin/sh or /usr/bin/env bash), and commands copy/pasted from the internet are either quickly executed with bash (one-off) or ported over. Because I like to have such in my history (fish is configured to use atuin), I want to keep using the same shell, so I try to stick with fish. If I cannot convert a command (usually a bunch of commands) to fish, it is PEBCAK and a learning curve/experience.

As for tmux, that is solid advice, because it also allows to stick with a shell which is known to work. I've come to like zellij with alacritty, with zellij the option is default_shell. But now that I use ghostty, I don't use a terminal multiplexer locally any more; only remotely. And there I still use tmux.


This wouldn't work if the script is meant to be sourced (to set environment variables) isn't it?

No, it doesn't.

The way I actually have things setup, in case it helps. I don't change my default shell. I actually default to pretty much working within tmux. So, I kept my default shell to what the OS brings, then in my tmux config, I have,

    # set shell
    set -g default-shell /opt/homebrew/bin/fish
This means, that when I start my terminal, it drops me to zsh (macOS default). Then when I run tmux, it opens fish. The nice thing is that I inherit the environment of zsh.

I have my .zshrc and my .bashrc sourcing a .shellrc file which contains most of my env stuff. This keeps random utilities that write to .bashrc and zshrc working within fish too.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: