Articles

The need for data engineers and analysts to run interactive, ad hoc analytics on large amounts of data continues to grow explosively. Data platform teams are increasingly using the federated SQL query engine PrestoDB to run such analytics for a variety of use cases across a wide range of data lakes and databases in-place, without the need to move data. PrestoDB is hosted by the Linux Foundation’s Presto Foundation and is the same project running at massive scale at Facebook, Uber and Twitter.

Let’s look at some important characteristics of Presto that account for its growing adoption.  

Source de l’article sur DZONE

BERLIN – SAP SE (NYSE : SAP) annonce que son fonds d’investissement, SAP.iO Fund, a soutenu Jina AI, une entreprise berlinoise fournissant une solution de recherche basée sur les réseaux de neurones, en open source.

Jina AI combine les récentes avancées en matière de Machine Learning en traitement du langage naturel, vision et reconnaissance vocale dans une nouvelle plate-forme de recherche, afin d’offrir une plus grande précision, flexibilité et adaptabilité aux entrées de recherche.

Le projet principal de Jina AI, Jina on GitHub, permet aux utilisateurs de créer une solution de recherche native dans le cloud, fonctionnant sur la base du Deep Learning. Jina permet de réduire de plusieurs mois à quelques minutes le temps nécessaire à la construction d’un réseau de neurones prêt pour la production et adapté aux environnements commerciaux ; qui exigent un cycle de développement rapide. Depuis la sortie de On GitHub en mai 2020, ce projet a déjà attiré plus de 2 000 engagements de la part de 48 contributeurs du monde entier. Dès maintenant, Jina prend en charge la recherche de texte, d’image, de vidéo, d’audio et de données multimodales. D’autres types de données seront pris en charge à l’avenir.

« Alors que les entreprises accélèrent leurs transformations numériques, un besoin est apparu pour une recherche d’entreprise plus efficace et précise » a déclaré Ram Jambunathan, vice-président senior de SAP et directeur général de SAP.iO. « Nous sommes enthousiasmés par le potentiel de Jina AI à fournir une solution de recherche précise aux clients de SAP. »

Jina AI a été fondée par le Dr Han Xiao, qui est connu pour le développement de l’infrastructure de recherche de nouvelle génération pour l’application de messagerie de Tencent, WeChat. Il est également connu pour son leadership au sein du bureau du programme Open Source de Tencent, où il a encouragé la culture open source et de développement de la société. Xiao a été membre du conseil d’administration de la Linux Foundation AI en 2019 et est fondateur et président de l’association germano-chinoise de l’IA.

 

The post Le fonds SAP.iO investit dans Jina AI, société de recherche basée sur les réseaux de neurones appeared first on SAP France News.

Source de l’article sur sap.com

In AWS, we have several ways to deploy Django (and not Django applications) with Docker. We can use ECS or EKS clusters. If we don’t have one ECS or Kubernetes cluster up and running, maybe it can be complex. Today, I want to show how deploy a Django application in production mode within a EC2 host. Let’s start.

The idea is create one EC2 instance (one simple Amazon Linux AMI AWS-supported image). This host doesn’t initially have Docker installed. We need to install it. When we launch one instance, when we’re configuring the instance, we can specify user data to configure an instance or run a configuration script during launch.

Source de l’article sur DZONE

We are gathered here today….

Today I write in memory of Adobe Flash (née Macromedia), something that a bunch of people are actually too young to remember. I write this with love, longing, and a palpable sense of relief that it’s all over. I have come to praise Flash, to curse it, and finally to bury it.

We’ve been hearing about the death of Flash for a long time. We know it’s coming. December 2020 has been announced as the official timeframe for removal, but let’s be real about this: it’s dead. It’s super-dead. It’s people-are-selling-Flash-game-archives-on-Steam dead.

That last bit actually makes me happy, because Flash games were a huge part of my childhood, and the archives must be preserved. Before I’d ever heard of video cards, frames per second, and “git gud”, I was whiling away many an hour on disney.com, cartoonnetwork.com, MiniClip, Kongregate, and other sites, looking for games.

I think we’ve established in my previous work that even as a missionary kid, I did not have a social life.

The Internet itself gave me a way to reach out and see beyond my house, my city, and my world, and it was wonderful. Flash was a part of that era when the Internet felt new, fresh, and loaded with potential. Flash never sent anyone abuse, or death threats. Flash was for silly animations, and games that my parent’s computer could just barely handle, after half an hour of downloading.

I even built my first animated navigation menus in Flash, because I didn’t know any better. At all. But those menus looked exactly like the ones I’d designed in Photoshop, so that’s what mattered to me, young as I was.

That was a part of Flash’s charm, really.

What Flash Got Right

Flash Brought Online Multimedia into the Mainstream

Funny story, JavaScript was only about a year old when Flash was released. While HTML5 and JS are the de-facto technologies for getting things done now, Flash was, for many, the better option at launch. JS had inconsistent support across browsers, and didn’t come with a handy application that would let you draw and animate whatever you wanted.

It was (in part) Flash that opened up a world of online business possibilities, that made people realize the Internet had potential rivalling that of television. It brought a wave of financial and social investment that wouldn’t be seen again until the advent of mainstream social networks like MySpace.

The Internet was already big business, but Flash design became an industry unto itself.

Flash Was Responsive

Yeah, Flash websites could be reliably responsive (and still fancy!) before purely HTML-based sites pulled it off. Of course, it was called by other names back then, names like “Liquid Design”, or “Flex Design”. But you could reliably build a website in Flash, and you knew it would look good on everything from 800×600 monitors, to the devastatingly huge 1024×768 screens.

You know, before those darned kids with their “wide screens” took over. Even then, Flash still looked good, even if a bunch of people suddenly had to stop making their sites with a square-ish aspect ratio.

Flash Was Browser-Agnostic

On top of being pseudo-responsive, the plugin-based Flash player was almost guaranteed to work the same in every major browser. Back in a time when Netscape and Internet Explorer didn’t have anything that remotely resembled feature parity, the ability to guarantee a consistent website experience was to be treasured. When FireFox and Chrome came out, with IE lagging further behind, that didn’t change.

While the CSS Working Group and others fought long and hard for the web to become something usable, Flash skated by on its sheer convenience. If your site was built in Flash, you didn’t have to care which browsers supported the <marquee> tag, or whatever other ill-conceived gimmick was new and trendy.

Flash Popularized Streaming Video

Remember when YouTube had a Flash-based video player? Long before YouTube, pretty much every site with video was using Flash to play videos online. It started with some sites I probably shouldn’t mention around the kids, and then everyone was doing it.

Some of my fondest memories are of watching cartoon clips as a teenager. I’d never gotten to watch Gargoyles or Batman: The Animated Series as a young kid, those experience came via the Internet, and yes… Flash. Flash video players brought me Avatar: The Last Airbender, which never ever had a live action adaptation.

Anyway, my point: Flash made online video streaming happen. If you’ve ever loved a Netflix or Prime original show (bring back The Tick!), you can thank Macromedia.

What Flash Got Wrong

Obviously, not everything was rosy and golden. If it was, we’d have never moved on to bigger, better things. Flash had problems that ultimately killed it, giving me the chance, nay, the responsibility of eulogizing one of the Internet’s most important formative technologies.

Firstly, it was buggy and insecure: This is not necessarily a deal-breaker in the tech world, and Microsoft is doing just fine, thank you. Still, as Flash matured and the code-base expanded, the bugs became more pronounced. The fact that it was prone to myriad security issues made it a hard sell to any company that wanted to make money.

Which is, you know, all of them.

Secondly, it was SEO-unfriendly: Here was a more serious problem, sales-wise. While we’re mostly past the era when everyone and their dog was running a shady SEO company, search engines are still the lifeblood of most online businesses. Having a site that Google can’t index is just a no-go. By the time Google had managed to index SWF files, it was already too late.

Thirdly, its performance steadily got worse: With an expanding set of features and code, the Flash plugin just took more and more resources to run. Pair it with Chrome during that browser’s worst RAM-devouring days, and you have a problem.

Then, while desktops were getting more and more powerful just (I assume) to keep up with Flash, Apple went and introduced the iPhone. Flash. Sucked. On. Mobile. Even the vendors that went out of their way to include a Flash implementation on their smartphones almost never did it well.

It was so much of a hassle that when Apple officially dropped Flash support, the entire world said, “Okay, yeah, that’s fair.”

Side note: Flash always sucked on Linux. I’m just saying.

Ashes to Ashes…

Flash was, for its time, a good thing for the Internet as a whole. We’ve outgrown it now, but it would be reckless of us to ignore the good things it brought to the world. Like the creativity of a million amateur animators, and especially that one cartoon called “End of Ze World”.

Goodbye Flash, you sucked. And you were great. Rest in peace. Rest in pieces. Good riddance. I’ll miss you.

 

 

Featured image via Fabio Ballasina and Daniel Korpai.

Source


Source de l’article sur Webdesignerdepot

This is the tutorial I wish I had around some years ago when I first tried to learn how to use Vim. If you’re just beginning to know this amazing text editor, please keep reading; I am writing this tutorial right for you!

Whether you prefer to code in a simple steps editor or in a full-fledged IDE, the fact remains that a console-based text mode editor can be an invaluable tool for many purposes, from coding to remote system administration. VIM (Vi IMproved) is the most common version of a classic UNIX text editor named vi, which is currently available on almost any platform. It’s one of the most useful and complex console tools you can find, and also one you can make use right away, no matter what you do for a living (everyone needs to write something, right?).

Source de l’article sur DZONE

Learn more about Linux runlevels — the right way!

You can think of Linux runlevels as different "modes" that the operating system runs in. Each of these modes, or runlevels, has its own list of processes and services that are either turned on or off. From the time Linux boots up, it’s always in some runlevel.

This runlevel may change as you continue to use your computer, depending on what kind of services the operating system needs access to.

Source de l’article sur DZONE

Create a new App Service Plan. If you have already created then skip this step. An app service is like one container or a VM machine. In a single Azure app service, you can host N number of web apps. Based on load, you can split your apps to separate app services if required.

To create a new app service, you’ll first need to set a resource group name; if you already have created it, you can use the same or else can create new. Next, fill the app service name, select Linux as your OS, select a pricing plan based on your needs, and hit create.

Source de l’article sur DZONE

GitLab Pages is a way to create websites for projects and groups in order to publish documentation, wikis, or any static content. Sometimes, for resource limitation, decreasing the load on the main GitLab instance (if self-hosted), to increase security, or for separating docs and wikis from code, we need to host our GitLab Pages in a separate server. To achieve this, we should have two GitLab instance on two distinct machines: one of them is our main GitLab (a normal GitLab installation) and the other one is an instance only for publishing GitLab Pages.

This is a tutorial and provides some technical information and configurations, We assume you are familiar with GitLab installation and GitLab Pages, and already have one GitLab self-managed instance (on-premises or in the cloud) in use.

Source de l’article sur DZONE