Waching daily Nov 27 2017

EXID's wish for Christmas is to have Solji be in perfect health

EXIDs wish for Christmas is to have Solji be in perfect health.

  EXID posed for the December issue of 10+ Star.   They were the cover models for the magazine, and the girls had a holiday party for the photoshoot. During the interview, the girls talked about Soljis health.

They said, All the members started taking care of their health, and we started thinking about one another more. Junghwa added, The four of us started doing what she used to, and we grew that much more.

We always feel her empty spot. We all grew so much closer.     When asked what they wanted from Santa, the girls said, We want Solji-unni to be completely healthy again.   Check out the photos above and below.

For more infomation >> EXID's wish for Christmas is to have Solji be in perfect health(News) - Duration: 1:07.

-------------------------------------------

What is PHP? - Duration: 12:28.

Welcome to another video from Yenkna PCs. This time we're gonna look at yet

another website language called PHP. I'm gonna let my A.I. take over. Here you go.

Take it away. PHP is a server-side scripting language designed primarily

for web development but also used as a general-purpose programming language.

Originally created by Rasmus Lerdorf in 1994, the PHP reference implementation

is now produced by The PHP Development Team. PHP originally stood for Personal

Home Page, but it now stands for the recursive acronym PHP: Hypertext

Preprocessor. PHP code may be embedded into HTML or HTML5 markup, or it can be

used in combination with various web template systems,

web content management systems and web frameworks. PHP code is usually processed

by a PHP interpreter implemented as a module in the web server or as a Common

Gateway Interface (CGI) executable. The web server software combines the

results of the interpreted and executed PHP code, which may be any type of data,

including images, with the generated web page. PHP code may also be executed with

command-line interface (CLI) and can be used to implement

standalone graphical applications. The standard PHP interpreter, powered by the

Zend Engine, is free software released under the PHP License.

PHP has been widely ported and can be deployed on most web servers on almost

every operating system and platform, free of charge. The PHP language evolved

without a written formal specification or standard until 2014,

leaving the canonical PHP interpreter as a de facto standard. Since 2014 work has

gone on to create a formal PHP specification. Early History: PHP

development began in 1995 when Rasmus Lerdorf wrote several

Common Gateway Interface (CGI) programs in C, which he used to maintain his

personal homepage. He extended them to work with web forms and to communicate

with databases, and called this implementation "Personal Home Page/Forms

Interpreter" or PHP/FI. PHP/FI could help to build simple, dynamic web

applications. To accelerate bug reporting and to improve the code, Lerdorf

initially announced the release of PHP/FI as "Personal Home Page Tools (PHP

Tools) version 1.0" on the Usenet discussion group comp.infosystems.www.authoring.cgi

on June 8, 1995. This release already had the basic functionality that PHP has

as of 2013. This included Perl-like variables,

form handling, and the ability to embed HTML. The syntax resembled that of Perl but was simpler,

more limited and less consistent. Lerdorf did not intend the early PHP to

become a new programming language, but it grew organically, with Lerdorf noting in

retrospect: "I don't know how to stop it, there was never any intent to write a

programming language I have absolutely no idea how to write a programming

language, I just kept adding the next logical step

on the way." A development team began to form and, after months of work and beta

testing, officially released PHP/FI 2 in November 1997. The fact that PHP

lacked an original overall design but instead developed organically has led to

inconsistent naming of functions and inconsistent ordering of their parameters. In some

cases, the function names were chosen to match the lower-level libraries which PHP was

"wrapping", while in some very early versions of PHP the length of the function names was

used internally as a hash function, so names were chosen

to improve the distribution of hash values. PHP 3 and 4:

PHP 3.0 is the successor of PHP/FI 2.0 . Zeev Suraski and Andi Gutmans rewrote

the parser in 1997 and formed the base of PHP 3, changing the language's name to

the recursive acronym PHP: Hypertext Preprocessor. Afterwards, public testing

of PHP 3 began, and the official launch came in June 1998. Suraski and

Gutmans then started a new rewrite of PHP's core, producing the Zend Engine in

1999. They also founded Zend Technologies in Ramat Gan, Israel. On May 22, 2000, PHP 4,

Zend Engine 1.0, was released. As of August 2008 this branch reached version 4.4.9.

PHP 4 is no longer under development nor will any security

updates be released. PHP 5: On July 13, 2004, PHP 5 was released, powered by the

new Zend Engine II. PHP 5 included new features such as improved support for

object-oriented programming, the PHP Data Objects (PDO) extension (which defines a

lightweight and consistent interface for accessing databases), and numerous

performance enhancements. In 2008 PHP 5 became the only stable version under

under development. Late static binding had been missing

from PHP and was added in version 5.3. Many high-profile open-source projects

ceased to support PHP 4 in new code as of February 5, 2008, because of the

GoPHP5 initiative, provided by a consortium of PHP developers promoting

the transition from PHP 4 to PHP 5. Over time, PHP interpreters became available

on most existing 32-bit and 64-bit operating systems, either by building

them from the PHP source code, or by using pre-built

binaries. For the PHP versions 5.3 and 5.4, the only available Microsoft Windows

binary distributions were 32-bit x86 builds, requiring Windows 32-bit

compatibility mode while using Internet Information Services (IIS) on a 64-bit

Windows platform. PHP version 5.5 made the 64-bit x86-64

builds available for Microsoft Windows. PHP 6 and Unicode: PHP has received

criticism due to lacking native Unicode support at the core language level,

instead only supporting byte strings. In 2005, a project headed by Andrei Zmievski

was initiated to bring native Unicode support throughout PHP, by embedding the

International Components for Unicode (ICU) library, and representing text

strings as UTF-16 internally. Since this would cause major changes both to the

internals of the language and to user code, it was planned to release this as

version 6.0 of the language, along with other major features then in development.

However, a shortage of developers who understood the necessary changes, and

performance problems arising from conversion to and from UTF-16, which is

rarely used in a web context, led to delays in the project. As a result,

a PHP 5.3 release was created in 2009, with many non-Unicode features back-ported

from PHP 6, notably namespaces. In March 2010, the project in its current

form was officially abandoned, and a PHP 5.4 release was prepared containing most

remaining non-Unicode features from PHP 6, such as traits and closure re-binding.

Initial hopes were that a new plan would be formed for Unicode integration, but as

of 2014 none had been adopted. PHP 7: During 2014 and 2015, a new major

PHP version was developed, which was numbered PHP 7. The numbering of

this version involved some debate. While the PHP 6 Unicode experiment had never been

released, several articles and book titles referenced the PHP 6 name, which

might have caused confusion if a new release were to reuse the name. After a

vote, the name PHP 7 was chosen. The foundation of PHP 7 is

a PHP branch that was originally dubbed PHP next generation (phpng).

It was authored by Dmitry Stogov, Xinchen Hui and Nikita Popov, and aimed to

optimize PHP performance by refactoring the Zend Engine to use more compact data

structures with improved cache locality while retaining near-complete language

compatibility. As of 14 July 2014, WordPress-based benchmarks, which served

as the main benchmark suite for the phpng project, showed an almost 100%

increase in performance. Changes from phpng are also expected to make it easier

to improve performance in the future, as more compact data structures and other

changes are seen as better suited for a successful migration to a

just-in-time (JIT) compiler. Because of the significant changes, the reworked Zend Engine

is called Zend Engine 3, succeeding Zend Engine 2 used in PHP

5. Because of major internal changes in phpng, it must receive a new major

version number of PHP, rather than a minor PHP 5 release, according to

PHP's release process. Major versions of PHP are allowed to break backward-

compatibility of code and therefore PHP 7 presented an opportunity for other

improvements beyond phpng that require backward-compatibility breaks, including

wider use of exceptions, reworking variable syntax to be more consistent

and complete, and the deprecation or removal of various legacy features. PHP 7

also introduced new language features, including return type

declarations for functions, which complement the existing parameter type declarations, and

support for the scalar types (integer, float, string, and boolean) in parameter

and return type declarations. Beginning on June 28, 2011, the PHP Group

implemented a timeline for the release of new versions of PHP. Under this system,

at least one release should occur every month. Once per year, a minor release

should occur which may include new features. Every minor release should at

least be supported for two years with security and bug fixes, followed by at

least one year of only security fixes, for a total of a three-year release

process for every minor release. No new features,

unless small and self-contained, are to be introduced into a minor release

during the three-year release process. Thank you, A.I. I hope you found this video

educational about PHP. Please, hit that like button. If you haven't subscribed,

please subscribe. And, catch you later.

For more infomation >> What is PHP? - Duration: 12:28.

-------------------------------------------

UQXBUSLEAD1xBUSL1_039 What is the difference between knowledge and wisdom - Duration: 8:55.

BERNARD MCKENNA: Oh, a very big difference.

[LAUGHS] The people who brought us the global financial crisis in Wall Street were very

knowledgeable people.

So knowledge alone is simply not enough.

It's interesting that when we look in philosophy, and in literature, we can often find useful

things that can guide us.

And in 1934, T.S.

Elliott in a poem called, The Rock, said this - Where is the life we have lost in living?

Where is the wisdom we have lost in knowledge?

Where is the knowledge we have lost in information?

And then, about 50 years later, Russell Ackoff, who was an academic at Wharton Business School,

and also a business analyst, came up with the notion of data, information, knowledge,

and wisdom.

Clearly, a distinction between those four elements.

Now, we all know that we have more information than we can possibly deal with-- more data

than we can possibly deal with.

We've now developed the notion of a zeta-byte-- which I think is 10 to the 21 bits of information.

Remember when we used to think that terabytes were pretty darn big?

Well, now we've got zeta-bytes.

So the human mind obviously cannot possibly comprehend that amount of data.

Indeed, forming that data into information sets is also enormously difficult.

The other factor that we have to take into account is what Herb Simon called bounded

rationality.

And by that, we mean that people are not necessarily the sort of rational beings that we would

like to think that they are, in two ways.

First of all, when we make decisions, we now know that we make decisions not just on what

we would call reasoning processes, but we do bring into account elements of intuition,

elements of experience, we draw on various bits of knowledge that we have from the past--

and emotions.

So we don't make purely rational decisions, anyway-- we know that that's incorrect.

The second point about bounded rationality is that the human brain simply cannot deal

with more than, say, the general accepted point is around about seven bits of information.

And once we get beyond that, the brain starts to go whoa, I can't handle this anymore.

So we have bounded rationality.

Now, a lot of the evidence now shows that what people really do, what leaders really

do when they make a decision, is that they make a call, which is what we would call intuitive.

But it doesn't just mean a gut feeling.

Anyone can have a gut feeling-- we all have gut feelings.

But a leader has a gut feeling of intuition that is based on huge amounts of experience

and knowledge, but also it's based on the reflexivity.

That is, they've made a call some time, it went belly up, and they go, goodness me, that

didn't go so well.

What went wrong there?

So they need reflexivity, as well.

So when I say gut feel, or intuition, I don't just mean that people say, oh, I think this

is the way we'll go.

They have an intuitive understanding that this is the right way to go.

And having made that decision, what we now know is that people are then able to what

I call backfill with rationality.

They can then go, I now have the answer, now I'm going to look at the building blocks that

lead to that answer.

And that's the way, generally, people work.

Now, the point about having that sort of intuitive judgment, and the difference between knowledge

and wisdom, is that that intuitive judgment must be characterized by a number of things.

Obviously, experience, but of course, a wise person crucially has to have the characteristic

of a moral being.

They have to be virtuous in the sense that they are not doing this for their own benefit,

and not just thinking only of the firm's profit line, or whatever.

They're thinking of the general benefit.

So again, it gets back to that disposition element that I was talking about.

People who make these calls, if they have the right disposition, if they continue to

think and reflect on what they've done, and how those things turned out, then those sort

of intuitive judgments will generally turn out to be pretty good ones.

PAUL HOLLAND: Tricky, isn't it?

I tell people that there aren't too many diagrams in management science they need to remember,

but the DIKY [sic] [DIKW] pyramid or triangle is one of them.

Because it needs to remind us how important that stuff is, particularly that little layer

between data and information where you have to analyze stuff.

But anyway, we're not talking about that.

But certainly, the knowledge component where effectively, whatever information you're taking,

you take it in through your lenses, and you turn it into something personal for you.

And it becomes knowledge.

And of course, I suppose, in a simple way, simple model, you've got explicit knowledge,

and you've got tacit knowledge.

Explicit stuff you can spit back out again pretty easily.

And most organizations that think they're doing knowledge management, are just collecting

terabytes on the servers, and that's good stuff.

Really good stuff.

But that's simply explicit knowledge turned back into information.

Tacit stuffs the gold, and even the platinum in organizations, the stuff that you know

but you can't say-- the deep stuff.

And sometimes it's what you can do.

Thats all very well to have people full of that stuff, but then they're going to be able

to apply it.

And to me the difference is that wisdom provides you with the context in which to use your

knowledge, to direct your knowledge appropriately.

You know, I know a lot of knowledgeable people I wouldn't send to the shop to buy a bottle

of milk, probably go to the wrong shop and come back with something else.

To be wise-- and again, its an ancient concept, isn't it?

The wise person of the village.

They've got a lot of knowledge, but they know when and where to apply it.

You can find very knowledgeable people-- it can be any real all the day, seven days a

week, 24 hours a day, and they just become a nuisance.

Or they're sharing their knowledge with you at inappropriate times, or the wrong sort

of knowledge.

You know, stuff thats outdated, or it's not right for that particular moment.

Only a wise person knows when and where and how to share their knowledge to get results

of some form-- whether its purely to aid in the growth of that particular person, over

a period of time, or whether its to solve a problem that they're facing at that particular

time.

And that sort of wisdom can come from a mentor, a person who is a knowledgeable person in

your life who was there for the long-run, but is relatively passive.

You can go and ask them things, and they can 'like the old guru' when they say, well, son in this

situation.

I believe that this is what you should be considering.

But they can be a coach, as well, someone who's more actively involved in your life,

helping you create a plan.

And they can help direct that plan through using their knowledge appropriately with you,

sharing that knowledge appropriately with you.

And maybe just in the form of questions back to you, or challenges, rather than telling

you to do something.

So to me, knowledge is that very personal filtering and storing of the information of

the world, mixed in with your own predilections, and your beliefs, and your experiences.

So you cook up this brew of stuff inside you, some of which can come out pretty easily,

and some of which can't-- and thats your knowledge.

But a wise person knows how to apply that, when and where, and how to apply it.