## python – What’s the future for abbreviations names in libraries?

When writing a library, we encounter a dilemma in naming functions, the function names need to follow naming conventions. Recently, I encountered python panda library (released 2008), and I needed to use iloc() and loc() functions. However, those two functions made me look up for their documentations unnecessarily. In fact, I wouldn’t have looked it up if they were named properly, location() and indexLocation() for examples. Panda library is not as old as c standard library, I can’t find excuse for it to be honest. Are name abbreviations going to continue?

## What is the future of Language Design?

What is the future design of Programming Languages?
I have heard that compilers is going to become more integrated with editors and Browsers?
Are we moving to a future with less code in Language Design?

## mathematics – Predict future position of a moving body in Phaser arcade physics

I am looking for an equation for predicting the future position of a moving arcade physics body in Phaser 3. The body has drag applied and isDamping set to true. Phaser applies the drag using the following run on each update (showing x axis only but same applies to y).

//  Damping based deceleration
dragX = Math.pow(dragX, delta);

velocityX *= dragX;

Given the above, how would I write a kinetic equation to predict the future position?

I am currently using the method below, where I am iterating over frames to calculate the position accumulatively. But this is inefficient and inelegant so would prefer a solution which estimates the position without any looping.

public futurePosition(timeInSeconds: number): Phaser.Math.Vector2 {
const DELTA = 1 / 60; // Assume we are running at 60fps
const DRAG = 0.3; // Drag value
const position = this.position.clone(); // Current position of body
const velocity = this.body.velocity.clone(); // Current velocity

// Inefficiently looping through frames
for (let i = 0; i < timeInSeconds / (DELTA * 1000); i++) {
velocity.x *= Math.pow(DRAG, DELTA);
velocity.y *= Math.pow(DRAG, DELTA);
position.x += velocity.x * DELTA;
position.y += velocity.y * DELTA;
}

return position;
}

Any help appreciated. Thanks.

## mathematics – Predict future position of a moving body in Phaser’s arcade physics

I am looking for an equation for predicting the future position of a moving arcade physics body in Phaser 3. The body has drag applied and isDamping set to true. Phaser applies the drag using the following run on each update (showing x axis only but same applies to y).

//  Damping based deceleration
dragX = Math.pow(dragX, delta);

velocityX *= dragX;

Given the above, how would I write a kinetic equation to predict the future position?

I am currently using the method below, where I am iterating over frames to calculate the position accumulatively. But this is inefficient and inelegant so would prefer a solution which estimates the position without any looping.

public futurePosition(timeInSeconds: number): Phaser.Math.Vector2 {
const DELTA = 1 / 60; // Assume we are running at 60fps
const DRAG = 0.3; // Drag value
const position = this.position.clone(); // Current position of body
const velocity = this.body.velocity.clone(); // Current velocity

// Inefficiently looping through frames
for (let i = 0; i < timeInSeconds / (DELTA * 1000); i++) {
velocity.x *= Math.pow(DRAG, DELTA);
velocity.y *= Math.pow(DRAG, DELTA);
position.x += velocity.x * DELTA;
position.y += velocity.y * DELTA;
}

return position;
}

Any help appreciated. Thanks.

## litecoin – What is the future of Bitcoin and Cryptocurency in the next 1 – 5 years?

litecoin – What is the future of Bitcoin and Cryptocurency in the next 1 – 5 years? – Bitcoin Stack Exchange

## cryptography – Future strength of encryption today

I see that in several training quizzes the “correct” answer is to store encrypted data where somebody could copy it and save it, when it can be done so that the encrypted data is only in RAM and then (hopefully) deleted after it is no longer used. In this example it was sensitive data used to bootstrap an EC2 instance. The recommendation was to store the data with the image. Who knows how easy it will be after 20 years or 50 years to break that encryption? If someone has the encrypted file and after a long time technology will be quite difficult to withstand any new code breaking technology, similar to how easy it is today to break the DES from 1970s.

## The future of webhosting

What do you think is going to happen to our industry in the next 10 years?… | Read the rest of https://www.webhostingtalk.com/showthread.php?t=1842168&goto=newpost

## flutter – How do I resolve a Future, transform it to Thing, and ensure it’s available before it’s accessed?

My apologies for what I assume is rather basic question, but I’m struggling to understand this.

I’m attempting to use FileOutput in the Logger package to log to device storage. This requires a File object as a parameter.

To obtain the correct path I’m using getApplicationDocumentsDirectory() from the path_provider package. This returns a Future which I can manipulate to a Future in an async function with await.

I’m unclear though how to extract a File from this and how to make sure that these objects are available to the logger before they are needed. Does this need to be done before I call runApp()? I assume I don’t need to and shouldn’t push async up to the main()?

This is where I am. x2() is a test function I can call successfully out of main() after invoking runApp() and gives me the correct results.

Future<String> get _localPath async {
final directory = await getApplicationDocumentsDirectory();
print("directory: \$directory");

return directory.path;
}

Future<File> get _localFile async {
final path = await _localPath;
print("path: \$path");

return File('\$path/logger.out');
}

var logger2 = Logger(
output: MultiOutput((
ConsoleOutput(),
FileOutput(
file: _localFile,
overrideExisting: true,
),
)),
printer: PrettyPrinter(
printBox: false,
printTime: true,
),
filter: ProductionFilter(),
);

void x2() async {
var f = await _localFile;
print("_localFile: \$f");
}