roydivision

More and more article titles follow this click bait pattern. The article itself is fine, interesting, albeit a bit short. But I totally agree, and it irks me too, that the implied promise of the title is not honored.

You can easily host and manage your own package repository. My point is that this apparent limitation is not in itself a strong enough reason to embark on NIX.

Go fill your boots if you want to use NIX, power to you, but be honest about why if you're going to write a piece about it.

It seems from my own upload that you are limited to one / email address. So yes you could just use a bunch of aliases, but I guess they're banking on most people only having access to a few addresses.

> More importantly, Docker containers themselves aren’t reproducible—running apt-get update or pip install requests at different times can yield different results, even with the same Dockerfile.

apt-get install <package name>=<version>

> And frankly, no one really needs Kubernetes, they just have it because everyone and their grandma has it. I digress, that’s a topic for another day.

Oh grow up, ffs.

The Mastodon instance I'm on.

The article specifically states that this light is NOT visible to humans:

> UPE, also known as biophoton emission, is a spontaneous release of extremely low-intensity light that is invisible to the human eye and falls within the spectral range of 200–1,000 nm.

Some nice explanations of f and t:

https://stackoverflow.com/questions/12495442/what-do-the-f-a...

Paul Fischer's book, 'A Kim Jong-Il Production' is well worth a read, not only for the story of these kidnappings, but of life in North Korea and its history.

I choose browser plugins instead for a more consistent experience, at home or anywhere.

I switched about two months ago, paid for a year. It's such a relief, it's like having search of ten years ago back again. It just works, and no useless crap. Options that make sense to ME, not to the profit line.

I'm now paying for:

- Search

- Email

- News

- Backups

Of course I'd rather not spend the money, but ALL these services are leagues ahead of the ad-supported alternatives. This is how the Internet should work.

(Edit - formatting)

A flawed solution looking for a problem.

Guitar player here. App looks great, but shame it's only for piano. I used a different app that does pretty much the same thing and really benefited from it, the improvement was noticeable after each session.

If you add guitar support it will be an immediate download for me.

I have no idea how Apple prioritise their bug fixing, but it really looks to me like bugs only get fixed when adding new features, if at all.

This is such a trivial big win as well, create a software dev team to focus on the outstanding bugs. Head it with one or two senior developers, make it the first step in onboarding new developers. What a great way to learn, and make a difference.

This is not rocket surgery, and Apple really do have a bad reputation here, even with the muggles.

Mainly The Guardian and Mastodon

Other sites include 404Media, Wired, The Newyorker, BBC News.

I couldn't agree more. However the reason we have a Popcorn option on the microwave is because it makes the difference at the point of sale, not at the point of use. Most people when presented with two devices that essentially do the same thing, but one has more options will chose the one with more options because they have been lead to believe it's better.

Design is so often polluted by marketing. The direction of progress from concept to design to marketing to sale should be one way only.

I personally wouldn't go anywhere near sideloading applications that haven't been through Apple's verification processes, or advise anyone in my family to do so.

I also think that it is very hard to argue _against_ allowing sideloading.

These two opinions can co-exist.

Make it optional, make sure the user knows what they are doing, and has acknowledged multiple times that they understand the risks, and that they acknowledge support for any problems at all with the phone will be compromised as a result.

Realistically, 99% of iPhone users don't need to sideload, nor understand what it means, and would be worse off doing it on their phones.

Yeah yeah Apple the big corp walled garden big evil boo. Yes they make mistakes, yes they make a ton of money. But, their stuff works better than anything else on the market for the vast majority of people, and their decisions are almost always thoroughly thought through in favor of the customer experience, accessibility, security and safety.

$ <some long command I will probably need later> # <some memorable name>

Later, search for <some memorable name>

I thought this would be comparing Rust to Ada Lovelace's code...

And I've coded in Ada...

Eggs? In this economy?

A slight tangent - does anyone have advice on anonymous blogs? I would accept an email address as being the sole contact, but nothing else.

Looks gorgeous! Respect to Jax.

I think you are in a minority, you WANT to learn.

Yes, the downside is that we aren't really learning anything, just solving problems supported by machines that tell us the solutions. Any schmuck can do that.

This stands to reason. If you need the answer to a question, and you can either get it directly, or spend time researching the answer, you're going to learn much more with the latter approach than the former. You may be disciplined enough to do more research if the answer is directly presented to you, but most people will not do that, and most companies are not interested in that, they want quick 'efficient', 'competitive' solutions. They aren't considering the long term downside to this.

I've worked as a sysadmin for most of my professional career, around 25 years. Sure I've screwed up, but I've learned each time. Covering everything in bubble wrap to shield you from consequences of mistakes is counter-productive. All that happens is that you learn that there are safety nets and not to think twice about what you're doing. Also these tools are non-standard, so you'll expect them everywhere. Don't do this.

Cached self hosted with Bitwarden as upstream master.

(Edited - added 'upstream')

I've been wondering for some time if it would be possible to create a formal way of describing board game rules. Although there is much variety in board gaming, mostly they consist of some sort of state machine, with events that change that state, and usually a clear end game state.

Does anyone know if this has been researched?

I can't be the only person here, other that the OP, who is excited by this?

(Thanks Mikhael! Ordered :-) )

Thanks!

Really like the

Don't <thing>

Why not?

When should you?

format of the Postgres Don't Do This page.