Yes, it is still a quartz watch. The oscillator is still a quartz oscillator. However the mechanism which advances the second hand is replaced with onethat does not need to tick.

The kind of quartz watch is no longer a ticking quartz watch, it is a non-ticking quartz watch.

As for the specific wording of the article, I would assume the authoris not fully versed in partsof quartz watches, and does not know that the oscillator which keeps time is different from the stepping motor which moves the hands.

This invention targets only replacing the stepping motor, not the oscillator.

Thats exactly the proposition. Eliminate tifking quartz watches in favor of non-ticking quartz watches.

Say goodbye to the quartz watches that do tick replace them with ones that do not tick

French innovator aims to consign ticking quartz watches to history

The ‘ticking’ is what is being consigned to history. The article is about an alternative to ‘ticking quartz watches’, a non-ticking quartz watch

Its the ‘ticking’ part of ticking quartz

Yeah! Its a package manager, with its own repos. It needs its own becauseof all those guarentees above. Its designed to be installed on any linux distro, and also has windows, mac, and docker versions.

If you want it to be all nix all the time, thereis also a distro NixOS thats uses nix from front to back.

And, in a confusing failure of naming, the language you use to configure nix is also called nix, just to be cool.

Ok, heres my run down:

Nix is a package manager with the goal of making it so that when you install a package at a version, you always get the same thing.

But isn’t that how all package managers work? Not at all. Most software requires other software to work (dependancies). Those dependencies also have dependencies, and so on. If a version of the dependency changes between installs, your package works differently. So Nix forces the package to specify what version of the dependency to use.

But version numbers are pretty wishy-washy, so nix actually requires git commits. This is good, since it turns out, the compiler and libraries used to build the software are dependencies, too. Building with a different compiler can change the way the package works. So Nix forces the package to specify how to build it also.

So Nix is a package manager where each version of a package is built against a known compiler, and comes bundled with a known set of dependencies.

This allows some cool things, like generations. Change your list of installed packages (or configuratian, it handles that too), nix can save the old config and instantly go back to it. No more bricked linux install (if it can get past the bootloader). Also lets you do os-level per-directory installs. Have two projects that each need a different version of c compiler or postgres? Nix makes that easy. Want to make sure all dev machines in your project have the same python version? Just check in the config.

exactly this. If I need to do development, i’ll use a jetbrains product. If i’m in a pure text editing situation, I want the most powerful thing for manipulating text, and I want it to be available.

Vim can have some IDE-like qualities, if you bolt enough plugins in to it, but by default it affords buttinx text in a file and manipulating it.

I woudn’t classify it as an ide though.

For those curious, this is a fireproofing wrap intended to help save the structure in the event of a forest fire.

Also, remember Human Resources Machine. Its a puzzle game thats actually a progamming language

The one wheel works by having the rider lean in a direction to go that way. The more you lean, the faster it goes. It balances by pushing the rider in that direction. The trick is when you are leaning and going very fast, but then the board loses power and can’t push you anymore. Then the board nose dives and ejects you. Its the physics of the board, so they can warn you it might happen, but not prevent it.

Scare pieces like this are created by people who have no actual understanding of software.

Software is the automation of conceptual tasks. Some of these, like taxes or text editing, were fairly procedural and automated early. Others, like identifying birds or deepfaking celebreties, are dificult and were done later.

Creating software is another conceptual task, and it might be possiple to automate it. But once we have automated creating software, automating any other task becomes trivial as well.

If this ever comes to pass, there are no safe majors.

Both styles have advantages and disadvantages. Fully procedural code actually breaks down in readability after a certain length, some poeple suggest 100 or maybe 200 lines, depending on how much is going on in the function.

Blanket maxims tend to to have large spaces where they don’t apply.

Additionally, the place where the code on the right is more likely to cause bugs and maintainability issues is the mutation of the pizza argument in the functions. Argument mutation is important for execution time and memory performance, but is also a strong source of bugs, and should be considered carefully in each situation. We don’t know what the requirements for this code are, but in general we should recomend against universal use of argument mutation (and mutability in general).

Oh thanks. This is exactly what I was looking for.

The vast majority of wall time for most uses is io. You need someone on your team to care about big o, but for most teams, its not the problem

99% invisible just did an episode on skyscraper conversion. Its farily complicated.

I mean, to be open, I don’t actually see many consequences, so I don’t really do any particular things to protect privacy from like, google. I was sort of hoping someone here would give me one.

Show them the consequeces. You might scare a few people who are already anxious by showing data collected, but most people will be apathetic. Illustrate why its bad. Be systemic about it.

The stunt outlined elsewhere of texting someone with their info is good, but “we all know google isn’t going to threaten us” is the prevailing attitude. Demonstrate what google is going to do and how it hurts people individualy and directly. Until there are personal consequences, peopae won’t really care.

I’ve used privacy for a while now. I became devoted when a card I used at an independant business started being used to pay phone bills in new jersey; privacy auto blocked it. Since then, i’ve used it to kill subscriptions I don’t want by changing to a privacy card and setting the limit to zero. Its good stuff.

I feel like, with this reply, you are willfully glossing over my point. The issue at hand is that open source software is short on the ux design expertise. My claim is that by centering the programing expertise, and in fact by not going out of the way to be inviting to the non-programming expertise, open source projects are self-perpetuating these cycles.

We can find ways to invite good designers in, or we can continue with the “sufficient” design ost projects currently have.

I’m happy if people have ather strategies for overcoming the current problem, but the current aproach is not doing it