TheFuzzball

Imagine building a brand new component library to replace your already quite successful component library and still making it React-only.

It's annoying, sure, but it's not worth disabling SIP.

Why?

But this is my point — it would take hundreds, or even thousands of years for aliens to get here. To do that they'd need some sort of abundant fuel source.

Let's say they have had thousands of years of Nuclear Fusion, for example, it wouldn't surprise me if they could produce any elements they need by fusing hydrogen.

But let's say they didn't, and they do in fact see Earth as a rare jewel full of precious materials... the logistics of taking our natural resources just seems like a joke. Surely the juice isn't worth the hundreds of years of planning and logistics squeeze.

I used to buy this dark forest idea, because it's scary and exciting, but I think the biggest mistake is projecting our behaviours onto extra-terrestrials.

If they wanted to destroy Earth they'd just slightly nudge a big asteroid in our direction and be done with it.

/ sorry for the ADHD rant

We're like a paranoid child terrified that anyone that enters our room is going to steal our Lego, so we must be left alone!

Nobody wants our Lego.

To flip it, why would I use unbound without pi-hole? What's the win I haven't seen (or even looked at or considered?)

In my experience, the fewer moving parts the better.

I run Unbound on my OPNsense router, and it uses the same blocklists as Pi-hole and the stats page (blocked domains, DNS requests, etc) are the same afaict.

I'm curious why you'd use pi-hole in combination with Unbound instead of using blocklists and stats that Unbound has built in?

What is multiplication if not adding over time?

I have been looking into Desktop Linux recently because macOS has taken a bit of a quality dip. GNOME - I'm never going to pronounce it guh-nome, please stop, it's embarrassing - seems to have a strong alignment with the old macOS philosophy. It's opinionated.

It also clearly copies macOS: Epiphany and the Settings app being prime examples.

I installed NixOS on an old T2 MacBook Pro, and it's... awful. Things just don't work, or don't work properly. It actually reminds me of running macOS on PCs back in the day (osx86, etc). GNOME 49 is headed in the right direction I think, but Desktop Linux is still in an absolute state.

Coming from Logseq... this looks ideal for me.

It could also be that there is a dirth of high quality CSS training data in comparison to JavaScript et al.

I wouldn't be surprised if the negative developer sentiment toward CSS is reflected in training datasets.

Two other use cases spring to mind:

- "GitHub: Let me know when this PR is merged" - "Store: Let me know when this item is in stock"

Unfortunately I think it's only useful if it works everywhere, so we can't rely on every website implementing it themselves.

Just hope that Herbie doesn't go bananas again

Correct, and it's Linux-only and more hardcore FOSS (i .e. they don't have any blessed way to use non-free software).

I'm not sure why it's being sold as an alternative to Nix/NixOS

Our brain works on a couple of bananas

What a fantastic non sequitur

Absolutely agree.

When my boomer dad complains about the Pakistani family he went to sell something to having 2 BMWs it's definitely racist.

But the racism is inflamed by poor economic conditions, and the rationale is "how come these people that aren't even from here have a better life than me?"

Sadly, people seeking power know this and use the racism to get power and don't fix the underlying cause, which was never immigration — it was wealth inequality.

You're confusing language that causes a strong emotional response within you, with language that was written by a person experiencing strong emotion.

It's colourful language for sure, but gimme a break.

I am so tired of the AI doomer argument.

The entire thing is little more than a thought experiment.

Look at how fast AI has advanced, it you just project that trend out, we'll have human-level agents by the end of the decade.

No. We won't. Scale up transformers as big as you like, this won't happen without massive advances in architecture and hardware.

I believe it is possible, but the idea it'll happen any day now, and by accident is bullshit.

This is one step from Pascal's Wager, but being presented as fact by otherwise smart people.

The UK is going to simply be cut off from many social media services.

Oh no! Anyway...

If it was USB-C powered people would be complaining about the size of the external power supply.

They will, just in time for everyone to have switched to pytorch!

The default shell on macOS has been zsh for over 4 years now, and they keep it up-to-date.

The UI elements on iPadOS are necessarily larger to accommodate touch.

It's just a lot less information dense than macOS, and making it the same scale will make using it as a touch device harder.

> A builder implementation using OCI instead of custom sandboxing code.

Hermetic builds require some sandboxing; Using OCI containers seems like an obvious choice, but didn't exist when Nix was first created.

Presumably this would make this implementation Linux-only, since OCI isn't natively supported outside of Linux?

Sonos would like a word.

Window management in macOS has gotten worse over time.

There are at least 3 ways to do everything now (e.g. Classic windowing, fullscreen splits, Spaces, Stage Manager), and they're all a bit crap.

Apple needs to implement a proper window management API that lets you replace Dock.app (which controls a lot of window management suff IIRC) so that we can do it ourselves and not rely on accessibility API hacks or disabling SIP.

In a word? GPLv3.

I think you'd have to write a facade package with a consistent API that mapped to the node/deno/bun equivalents, since they're each quite different.

Best bet is to use the Node fs package and rely on the deno/bun compatibility layer.

More generally, Deno pushes for Web Platform APIs, and as more are proposed and implemented the runtime-specific APIs will become fewer and fewer.

A toxic article full of untruths and generalisations.

You have to teach React developers the difference between the <Link> and <a> tag, and how <a> doesn't swap nor replace your page content, it loads an entirely new page.

This is more of a complaint about JavaScript than "frameworks". Any default browser behaviour can be prevented, so when you click an `<a>` and it does the same thing as a `<button>`, a lot of devs will think "I'm done here". They need to be educated on accessibility and why it matters.

Sometimes the economics of a project make spending the time to make your advertising microsite that'll be live for 3 months not really worth making WGAC 3.0 compliant, sorry, welcome to the real world.

But, and it's a tough pill to swallow for many… WordPress. It gets you from 0 to 97% in an instant, and the last remaining 3% is offered by some plugin, or a minimum amount of code knowledge.

facepalm

Bear in mind that Apple and Adobe have a very long and close history - Apple did not kill Flash to spite Adobe, they did it because 1. Flash was plagued with security problems, and 2. Flash was plagued with performance problems and the iPhone was a very low performance device.