throwaway984393

38:28 https://m.youtube.com/watch?v=-zRN7XLCRhc&t=2308s&pp=0gcJCTA...

"A software development kit (SDK) is provided royalty-free,[13][14] though the ability to commission a finished product into a Matter network in the field mandates certification and membership fees,[15][16] entailing both one-time, recurring, and per-product costs.[17] This is enforced using a public key infrastructure (PKI) and so-called device attestation certificates.[15]"

So it's a closed ecosystem that makes money for a cabal of corporations

No. Delete and overwrite are different. You need overwrite protection in addition to delete protection. The solution will vary depending on the storage system and the use case. (The comment in the PR is not an exhaustive description of potential solutions)

It's sad that some distros refuse to package with -o option support anymore

The jobs are available for citizens. But they don't do them. And it's not because of immigration. Think about it for more than 5 seconds. They could just stop immigration for migrant workers and suddenly give citizens jobs. Every politician wants to be known as a job creator. But they don't. Why? There is not enough workers here. Proof? COVID. They stopped letting migrant workers in and farms failed left and right from lack of workers.

We weren't lacking teenagers. We were lacking a dirt cheap seasonal exploitable massive workforce. There are not enough teens even if we conscripted them all. And if you don't, teens don't like doing work. Most teens don't live in the sticks anymore. And (for teens) we care about these stupid things like safety, a minimum wage, and labor laws.

It's not 1950 anymore. The world has changed. The reason we need migrant workers is WalMart. Their demand for ever lower prices creates the need for the lowest priced highest supply scalable labor due to a global supply chain and pricing pressure. You can't put the genie back in the bottle. Want cheap shit? Then you hire migrant workers. Or give up on farms and buy from overseas. Or make robots that can pick fruit. There's no free lunch.

What they've been able to accomplish in such a short time is nothing short of amazing, and I applaud them for their efforts.

That said, I've been using Asahi for a month, and I'm ditching it. Maybe in a year or two it'll be stable, but for now it's got too many bugs and unsupported features. A lot of the problems come down to Wayland and KDE/Gnome, as you literally have to use Wayland. But there's plenty of other buggy or challenging parts that all add up to a very difficult working experience.

One of the biggest challenges I see is support for hardware and 3rd party apps. Not only do all the apps need to support this slightly odd Arm system, but so do hardware driver developers. I never realized before just how much of a Linux system works because most people had an incredibly common platform (x86_64). Even if Linux on Mac became incredibly popular, it would actually take away development focus on x86_64, and we'd see less getting done.

(This kind of problem is totally common among Linux laptops, btw; there's a ton of hardware out there and Linux bugs may exist in each one. Adding a new model doesn't add to the number of developers supporting them all. If anything, the Mac is probably benefited by the fact that it has so few models compared to the x86_64 world. But it's still only got so many devs, and 3rd party devs aren't all going to join the party overnight)

Yep. The times I've been hit by a car while walking it was the car rolling through stop signs, lights and turns.

Please, for the love of god, let it die. WordPress's horrible security, annoying maintenance, and cookie cutter sites have filled the internet with malware and garbage content. It's so annoying to maintain that we have to find these managed hosting places that provide very little value. And despite them, you still need to add a bunch of extra stuff to make a reliable site. Time to create something modern.

Too bad it won't get adopted by existing systems. I know huge companies still doing mandatory frequent password changes despite us telling them it goes against NIST for years.

Office365 is way better. You get native apps, which are obviously better than a web app, you get device integrations for enterprise, you get more advanced tooling, more features. Plus MS has better compliance options. If you're actually running a business, and not just a startup employee who doesn't need to do much, MS is the way.

I find this kind of thing fascinating. In the BDSM rope bondage world there is a lot of ceremony and almost theatrics about safety. But there's actually no real safety, because the participants keep doing things everyone knows is unsafe. The Takate Kote tie is probably responsible for 80% of nerve impingement damage in rope bondage, yet it's wildly popular because people find it pleasing and they keep coming up with new variations on it. Every time you bring up its danger, people like to shout you down like you're over-reacting and they're sick of hearing from you, and then they go give some poor newbie wrist drop.

This is literally designed to make the user's life easier. Regular toaster oven bottom hinges just CLUNK on the table. If you're not very careful when lowering or raising you can skim your hand or grab onto the hot part of the door. This allows you to slowly open it in a controlled manner, which both feels and is more secure, and works with the natural shape and orientation of the hand. Not to mention you can now install it in a raised position (above the table) without worrying about the top flopping down on you.

Oh, great, we'll just move 5 billion people to an elevation nowhere near them, no problem

The most energy efficient solution is what animals have been doing in the desert for millions of years: burrow.

That's low for an electric vehicle fire. An average car takes 500-1000 gallons. Teslas can take up to 30000-40000 gallons. Fwiw, most fire trucks only carry up to like 3000 gallons.

I'm nearing greybeard status, so I have to chime in on the "get off my lawn" aspect.

There is no one general "good engineering". Everything is different. Labels suck because even if you called one thing "microservices", or even "monolith of microservices", I can show you 10 different ways that can end up. So "modular monolith" is just as useless a descriptor; it's too vague.

Outside of the HN echo chamber, good engineering practice has been happening for decades. Take open source for example. Many different projects exist with many different designs. The common thread is that if a project creates some valuable functionality, they tend to expose it both at the application layer and library layer. They know some external app will want to integrate with it, but also they know somebody might want to extend the core functionality.

I personally haven't seen that method used at corporations. If there are libraries, they're almost always completely independent from an application. And because of that, they then become shared across many applications. And then they suddenly discover the thing open source has been dealing with for decades: dependency.

If you aren't aware, there is an entire universe out there of people working solely on managing dependencies so that you, a developer or user, can "just" install software into your computer and have it magically work. It is fucking hard and complicated and necessary. If you've never done packaging for a distro or a language (and I mean 250+ hours of it), you won't understand how much work it is or how it will affect your own projects.

So yes, there are modular moniliths, and unmodular monoliths, and microservices, and libraries, and a whole lot of varied designs and use cases. Don't just learn about these by reading trendy blog posts on HN. Go find some open source code and examine it. Package some annoying ass complex software. Patch a bug and release an update. These are practical lessons you can take with you when you design for a corporation.

CLI renaissance, or new dark age? The advent of the Web as the modern application platform of choice destroyed the advancement of graphical user interfaces. We now live in a bizarre world of CLIs when we should be using GUIs.

Before the Web, and during its rise, there was a vast array of productivity tools designed to allow users to do more work, faster, and better, through graphical interfaces. It would have been ridiculous to release a program to users with only a command line interface. We left the dark ages of terminals behind, and pushed into new territory, advancing what users could do with computers.

But once the Web began to develop the capabilities of browsers further, Web programming began to teach young programmers that the web was the only place that needed a graphical interface, because the web was a "universal" graphical application interface (lol, if you don't count the browser wars)

This delighted programmers, as they never really liked making graphical interfaces. Logic and functions were more fun to write than user interfaces (which only made the users - not developers - happier).

This was then hammered home when Markdown was widely adopted for its simplicity, inspiring a sort of text-based Stockholm-syndrome. People started to claim bizarre things, like that the command line and Markdown were preferable (or even superior) to GUIs and WYSIWYGs in almost all cases. More languages were adopted that had no inherent graphics capabilities, and the devs moved ever further towards text.

So the web has unintentionally set back computer science and user productivity by decades. Until browsers lose the spotlight, this will probably continue, and non-web GUIs will continue to be that ugly thing you only write if you have to. Users will continue to languish in these half baked solutions, slaves to the solutions that are presented to them. And devs will continue to create text interfaces that only they enjoy.

Rather than rethinking old ideas and creating new ones, we are simply doubling down on the past.

It's pretty trivial for an embedded device to trim down the series of startup tasks to only what's required, and then just write a C program that does those steps. I certainly wouldn't pick up such a gigantic, complex and potentially insecure package as systemd for an embedded project. I want less moving parts, not more

K8s is a fantastic development tool. You can't ask for a better self-service tool to enable developers to ramp up on a platform and develop or test their apps across teams and orgs in a standard, portable, safe way. Its biggest problem arguably is that it's too configurable, and doesn't have enough abstractions to hide the complexity.

Not only excess power draw, but excess heat, which then needs more power for the AC to cool the home

No matter how old the machine/distro, screen is packaged. Tmux is only packaged for recent distro versions.

Don't start your company as open source. It will attract the wrong customers (the ones who don't give you money but sure like to complain) and detract from building your product. If you can build a successful product, open source it afterwards to give you a competitive advantage without being a drag.

It's well established that sexual assault is under-reported in the US general population

Don't send an alert at all unless it is actionable. Yes, I get it, you want alerts for everything. Do you have a runbook that can explain to a complete novice what is going on and how to fix the problem? No? Then don't alert on it.

The only way to make on-call less stressful is to do the boring work of preparing for incidents, and the boring work of cleaning up after incidents. No magic software will do it for you.

Lol wut? It causes cancer, it doesn't kill you within days.

A steel oval auto locking keylock 38kN carabiner. (https://www.amazon.com/PETZL-OXAN-Carabiner-Black-Triact-Loc...) Very strong, fails gradually, optimal loading and alignment, secure, doesn't catch on things, wide enough for most uses.

Not a fan of shoving more functionality into a tool, that doesn't officially support it, to solve a problem that the tool isn't meant to solve.

I like that it forces users to read the docs to find the functionality. Users don't read the docs, and then they wander around the internet looking for a random blog post with a snippet for one problem, and they don't ever really learn how to use the program.

Users are a bit like high school students just skimming books for an answer to fill in on a test. They need to be forced to learn.

Not to mention using Cloudfront in front of S3 can lower cost, due to caching.

Tribal organization is different than hierarchy. Hierarchy is actually fairly recent; forms of it existed in terms of social class structure and rule for a few thousand years, but today's hierarchy was invented by the modern Christian church.

Humans are social animals, so we absolutely need some form of social structure to function. But how that structure must work isn't rigidly defined. What is clear, though, is that since we aren't innately rational creatures, we do need a simplistic form of governance (typically a power structure of leaders).

I'm sure that makes the medicine go down easier, but we're not powerless at all. We choose to have no say. We choose not to run our own campaigns and get grassroots approval. Less than half of us vote. The rest accept the status quo, despite the fact that they don't have to. We give away our power.

All of the methods by which a dark horse can run and win are there. The state will not remove your votes or intimidate voters not to vote for you. You will not be poisoned by radioactive toxins to prevent you from running. You will not be kidnapped, or your family threatened, or a bomb set off in polling locations. This isn't in any way like so many other actually repressive regimes. All you have to do is go and run.

We have more power in this society than anyone in any other. So why do we claim we're powerless? Because it makes us feel better that we're so lazy. I could run for office, but that might restrict my time watching The Office. Better to just say that running is pointless, so I don't have to make the change I want to see.

And even if you don't want to run, you can vote for independents, you can complain to your representatives, you can organize your friends and neighbors to petition local government for local reforms and participate in larger state and federal efforts. Individually we may be a drop in the bucket, but collectively we are a wave. You can't say that isn't powerful.