voidpointer

To implement groove packing digitally, you don't need to put that process in the signal chain, do you? You can digitize the master, analyze it, and determine the required spacing at various points on the record. You then feed that information back to the machine to control the cutting processes, as the analog signal is transferred directly to the record. No digital buffer in the signal path.

I think this is just the way the decision tree works in safety-sensitive areas where many human lives are at stake. The catch-all in the decision tree, if there is no exact solution, is always the "get to safety at all costs" option. There will be some window of trying to resolve an issue (here: telling everyone to shut down devices) and when that does not resolve the issue, the catch-all kicks in. That's just the pattern and in an environment like an airplane, where margin for error is slim to non-existant, there is no deviation from that pattern.

In general and long-term I agree with what you are saying. I assume this was a new/unknown situation. (On the other hand, the article links to other similar stories, so maybe I am cutting them too much slack). If "electronic device names" are of concern, there should be an established protocol to deal with them. Especially if this keeps happening.

Was any of this a good idea? No, probably not, but people need to calm down.

I can understand the safety concern - and I think the decision to turn around was ultimately the right call. Especially given that they had called for people turning off BT for some time.

The fact that the device was not turned off suggests to me that the owner did not know they were the cause of this. If they had done this by intent and were set on going through with it even after the turnaround was initiated, they would have also had the sense to drop the device into some other seat or leave it in the lavatory...

If it turns out they did this with full intent, there should be some _appropriate_ consequence

So, how did it eventually show up? Owner's phone goes off/airplane-mode, watch starts advertising; someone else wants to connect their BT headphones and sees the name of the watch?

According to the article, it was a Fitbit device belonging to a teenager... Chances are, the kid selected that nickname for the device a long while ago and forgot about it, and was probably unaware that the device was using Bluetooth at all, and that they should turn off their fitness tracker when the announcement came through...

At the same time, some people in the comments under the article are more or less calling for the death penalty for the kid...

Maybe you have a point there. An optimistic outlook would be that AI allows people to create content that can compete with the polished, mass-produced, standardized stuff without the prohibitive budget requirements. The pessimistic view is that it leads to more isolation, where everyone only "creates" for themselves.

Isn't the scenario you are describing the ultimate collapse of art and culture as we know it? If everyone sits at home and creates the content that they want, what do we talk about? How do we engage in shared culture if there is nothing to experience together?

Why is this relevant for understanding how the IP works or even tweaking it? Whatever is relevant for that matter will most certainly not be a modification to the Linux kernel that the android system is running. It will not fall under the GPL that the kernel is licensed under. Can someone explain why this dispute is worth having beyond a theoretical legal debate on whether they should hand out the particular source tree from which their kernel was built (if they even built it)?

Probably a silly question, but if you take this all the way and treat everything as a DB that is synchronized in the background, how do you manage access control where not every user/client is supposed to have access to every object represented in the DB? Where does that logic go? If you do it on the document level like figma or canvas, every document is a DB and you sync the changes that happen to the document but first you need access to the document/DB. But doesn't this whole idea break apart if you need to do access control on individual parts of what you treat as the DB because you would need to have that logic on the client which could never be secure...

The relative ease with which called-IDs can be spoofed seems to be one of the major "tools" with which scammers can gain the trust of their victims (or trick other systems into believing that they are the victim). Most of the non-technical folks I know will also more or less blindly trust a caller-ID. Fortunately, many scammers (at least here in Europe) are still calling you claiming they are interpol following up on your Paypal account being breached whilst a +233... number shows on your phone.

Absolutely but that tradeoff should be for the customer to make.

Reading speed at that age will vary greatly. Reading subtitles while also having to follow the picture takes away focus and that makes it hard much harder for an inexperienced reader. My daughter, who picked up reading very naturally would have been able to follow sub-titles at age 7 without much trouble. My younger, 7-yo son on the other hand, who is more average in reading ability wouldn't be able to keep up with subtitles yet. Average reading speeds at age 7 seem to be 60-100 words per minute where subtitles are more at the 100-150 words per minute range. So for above-average readers, it will be possible but for the average, they won't be able to keep up consistently.

I did experience the issue with an FIIO headphone DAC too. Basically, when connecting the device, the balance slider in audio settings would get initialized to what seemed to be a random value. I am using several other audio interfaces (both USB and Thunderbolt) as well for music production/recording and I have never seen that issue with any of those devices. I suppose it is an interoperability problem between the USB audio class driver and core audio that only manifests for certain types of devices. Still, if it is common enough for people publishing apps to fix it, Apple should get it sorted out.

Texture-wise it should be very different due to how the gluten will develop. Taste-wise you are probably right. It’s mostly a substrate for the butter and syrup.

In order to get close to how these might have tasted in Locke's time, one shouldn't be using modern white flour which is a 19th century development. Using (stone-milled) whole wheat might come closer to how things were in the 17th century. (Also better for your glucose levels)

The cover-band analogy isn't so great; the issue where a specific solution becomes a proxy for solving some problems that no one bothered to fully understand is real though. Describing problems and doing thorough discovery is hard and silver bullets are attractive. The cargo-cult analogy is quite fitting for a lot of hyped-up topics.

When you go to a car dealer and tell them your problem is getting from A to B, guess what their solution is going to be...

What I'm not getting: If Project Gutenberg is US based, how can they be dragged in front of a German court at all? How could a German court enforce anything on a US based entity? So couldn'd PG's response just have been to ignore the case? What would have happened then?

Thanks. drinks-another-coffee

This is going to be a dumb question I fear... If, as the article says, photons can't travel through a vacuum how are we able t see the stars (let alone distant galaxies)? Is it just because space isn't enough of full vacuum, or what am I missing?

If it's just about having a usable safe, it's an easy decision. They just need to decide whether the cost for the locksmith is worth it for them to have a usable safe...

If it's about what might be in there... shouldn't it be fairly easy to drill a small hole (given the right type of drill) and use a miniature/endoscopic camera to take a look?

You don't need many books on it. There's Petzold.

Somehow, the examples all sound more like a quality and/or testing issue. The workflow seems prone to people rebasing to a buggy state and at that point, in a non-trivial system, all bets are basically off. Basically I need to be able to have a "JTB" about a pull request having undergone enough review and testing before being merged on the master that it doesn't introduce such glaring regressions as cited in the examples. If that cannot be ensured, I'm setting myself up for one goose chase after the other...

Feb. 2016?

The interesting thing here is that the common response here is: "Hey that's a great theory, but in real life, I just paid off my mortgage with my proceeds from bitcoin."

Mortgages have been payed off with lottery wins. That doesn't make lottery tickets a good investment.

Unfortunately, it cannot power the dock. That was a bit of a letdown for me

passing 0 to f returns infinity (IEEE 754)

Not arguing the point here. It's just a terrible example.

Just out of curiosity... What is the point in testing all 2^24 possible color values?

Because freelancers get paid sick days?

Not sure how this is designed in this game, but if you want to make the game only show a certain portion of the map to clients at a given time, you need to make sure that things that the player should not see are never sent to the client. Otherwise, you are always opening the system up for this sort of "cheating". With the game being open-source, it is easier to do but also with closed-source games, this is what things like "wallhacks" etc are based off: making information that is available to the client visible to the user.