Chrome-Browser blockiert nervende Werbung

heise online Newsticker - 16. Februar 2018 - 12:30
Google schaltet seinen Werbefilter im Chrome-Browser scharf: Er blockiert ab sofort nervige Werbe-Pop-Ups und stoppt plärrende Videos, die automatisch starten. Doch nicht jeder ist davon begeistert.

#heiseshow, live ab 12 Uhr: Der Koalitionsvertrag steht – warum sagt er so wenig zur Digitalisierung?

heise online Newsticker - 16. Februar 2018 - 12:15
Zwar müssen die Mitglieder der Parteien noch zustimmen, aber die Führungen von CDU, SPD und CSU wollen weiter gemeinsam regieren. Einmal mehr behandelt ihr Koalitionsvertrag die Digitalisierung höchst stiefmütterlich. Was das bedeutet, diskutieren wir.

Spiegellose Systemkamera: Fujifilms neues APS-C-Topmodell X-H1 mit kamerainternem Bildstabilisator

heise online Newsticker - 16. Februar 2018 - 11:53
Die Fujifilm X-H1 erbt viele Ausstattungsmerkmale vom bisherigen Flaggschiff X-T2. Neu ist unter anderem ein kamerainterner Bildstabilisator, ein verbesserter Autofokus und ein massiveres Gehäuse, auch Videofilmer sollen auf ihre Kosten kommen.

Südkorea will kein Verbot von Kryptowährungen – Bitcoin legt zu

heise online Newsticker - 16. Februar 2018 - 11:35
Südkoreas Regierung will sich darauf konzentrieren, den Handel mit Kryptowährungen transparenter zu machen, anstatt ihn gänzlich zu ächten.

Dries Buytaert: My POSSE plan for evolving my site

Planet Drupal - 16. Februar 2018 - 11:23

In an effort to reclaim my blog as my thought space and take back control over my data, I want to share how I plan to evolve my website. Given the incredible feedback on my previous blog posts, I want to continue to conversation and ask for feedback.

First, I need to find a way to combine longer blog posts and status updates on one site:

  1. Update my site navigation menu to include sections for "Blog" and "Notes". The "Notes" section would resemble a Twitter or Facebook livestream that catalogs short status updates, replies, interesting links, photos and more. Instead of posting these on third-party social media sites, I want to post them on my site first (POSSE). The "Blog" section would continue to feature longer, more in-depth blog posts. The front page of my website will combine both blog posts and notes in one stream.
  2. Add support for Webmention, a web standard for tracking comments, likes, reposts and other rich interactions across the web. This way, when users retweet a post on Twitter or cite a blog post, mentions are tracked on my own website.
  3. Automatically syndicate to 3rd party services, such as syndicating photo posts to Facebook and Instagram or syndicating quick Drupal updates to Twitter. To start, I can do this manually, but it would be nice to automate this process over time.
  4. Streamline the ability to post updates from my phone. Sharing photos or updates in real-time only becomes a habit if you can publish something in 30 seconds or less. It's why I use Facebook and Twitter often. I'd like to explore building a simple iOS application to remove any friction from posting updates on the go.
  5. Streamline the ability to share other people's content. I'd like to create a browser extension to share interesting links along with some commentary. I'm a small investor in Buffer, a social media management platform, and I use their tool often. Buffer makes it incredibly easy to share interesting articles on social media, without having to actually open any social media sites. I'd like to be able to share articles on my blog that way.

Second, as I begin to introduce a larger variety of content to my site, I'd like to find a way for readers to filter content:

  1. Expand the site navigation so readers can filter by topic. If you want to read about Drupal, click "Drupal". If you just want to see some of my photos, click "Photos".
  2. Allow people to subscribe by interests. Drupal 8 make it easy to offer an RSS feed by topic. However, it doesn't look nearly as easy to allow email subscribers to receive updates by interest. Mailchimp's RSS-to-email feature, my current mailing list solution, doesn't seem to support this and neither do the obvious alternatives.

Implementing this plan is going to take me some time, especially because it's hard to prioritize this over other things. Some of the steps I've outlined are easy to implement thanks to the fact that I use Drupal. For example, creating new content types for the "Notes" section, adding new RSS feeds and integrating "Blogs" and "Notes" into one stream on my homepage are all easy – I should be able to get those done my next free evening. Other steps, like building an iPhone application, building a browser extension, or figuring out how to filter email subscriptions by topics are going to take more time. Setting up my POSSE system is a nice personal challenge for 2018. I'll keep you posted on my progress – much of that might happen via short status updates, rather than on the main blog. ;)

GSI Helmholtzzentrum und ESA erforschen gemeinsam Gefahren von Weltraumstrahlung

heise online Newsticker - 16. Februar 2018 - 11:00
Ein Teilchenbeschleuniger am GSI Helmholtzzentrum soll helfen, die Wirkung von Weltraumstrahlung auf Astronauten zu untersuchen. Dazu wurde eine Zusammenarbeit mit der Europäischen Weltraumagentur beschlossen.

Nanoroboter schnüren Krebszellen ab

heise online Newsticker - 16. Februar 2018 - 11:00
Nanoroboter der Arizona State University machen sich im Körper eigenständig auf die Suche nach Krebstumoren und schnüren diesen systematisch die Blutzufuhr ab. An Mäusen bekämpften die Nanobots bereits erfolgreich Tumore und sogar Metastasen.

YouTube-Hit: Die Furbies sind los

heise online Newsticker - 16. Februar 2018 - 10:30
Vor 20 Jahren kamen Furbies, interaktive Plüschspielzeuge, auf den Markt. Ein YouTuber hat 44 von ihnen gesammelt und zu einer Orgel umfunktioniert. Der Klang ist so furchterregend wie das Aussehen.

Welt-Pressefoto des Jahres 2017: Die Nominierungen stehen fest

heise online Newsticker - 16. Februar 2018 - 10:30
Bilder von Krieg und Frieden, Liebe und Hass, Natur und Naturzerstörung – mehr als 4500 Fotografen haben sich am World Press Photo Contest für das beste Pressefoto des Jahres 2017 beteiligt, nun steht die Vorauswahl für die besten Aufnahmen fest.

Marktforscher: Kein Sprachassistent so beschränkt wie Siri auf dem HomePod

heise online Newsticker - 16. Februar 2018 - 10:30
Von knapp 800 Anfragen aus verschiedenen Themenbereichen konnte Siri auf Apples HomePod einer Analyse zufolge nur gut die Hälfte korrekt beantworten – deutlich weniger als die Sprachassistenten der Konkurrenz.

Krypto-Mining statt Werbung: US-Magazin lässt Nutzer mit Adblocker nach Monero schürfen

heise online Newsticker - 16. Februar 2018 - 10:00
Besucher der Website des US-Magazins Salon haben die Wahl: Werbung oder Rechnerleistung. Die PCs der Leser sollen Einnahmen durch Mining erzielen. Damit geht die Nachrichtenseite neue Wege, um ausfallende Werbeeinnahmen durch Adblocker auszugleichen.

Elektroautos: Opel will ab 2020 Elektro-Corsa produzieren

heise online Newsticker - 16. Februar 2018 - 10:00
Der Autohersteller bekräftigt seine Pläne für die Produktion von rein elektrischen Modellen.

Spitzentechnik aus Israel: Lüfterlose Mini-Workstation mit starker Quadro-GPU für sieben 4K-Displays

heise online Newsticker - 16. Februar 2018 - 9:30
Der Compulab Airtop-2 mit Xeon E3, 64 GByte ECC-RAM und Nvidia Quadro P4000 kommt dank Konvektionskühlung ohne Lüfter aus.

Horror-Shooter Dead Space vorübergehend kostenlos bei Origin

heise online Newsticker - 16. Februar 2018 - 9:30
Nutzer von EAs Spieleplattform Origin können sich "für kurze Zeit" kostenlos den Horror-Shooter Dead Space sichern. Das lohnt sich: Dead Space bietet zehn Stunden exzellente Unterhaltung für Spieler mit starken Nerven.

Europäer kombinieren vier Teleskope zur virtuellen Riesensternwarte

heise online Newsticker - 16. Februar 2018 - 8:30
Am Very Large Telescope in Chile sind erstmals alle vier Hauptteleskope zusammengeschaltet worden. Damit betreibt die Europäische Südsternwarte (ESO) heute das größte optische Teleskop der Erde.

Microsoft findet Sicherheitspatch für Skype zu aufwendig

heise online Newsticker - 16. Februar 2018 - 8:30
Angreifer könnten an einer Schwachstelle in Skype ansetzen, um sich Systemrechte unter Windows anzueignen. Ein Patch ist derzeit nicht in Sicht. Standard-Installationen sind aber nicht gefährdet.

Valentinstags-Installation: Riesenlinse aus dem 3D-Drucker

heise online Newsticker - 16. Februar 2018 - 8:00
Seit 10 Jahren gibt es auf dem New Yorker Times Square eine Kunst-Installation zum Valentinstag. Dieses Jahr ziert die weltgrößte Linse den Anlaufpunkt für Touristen. Ausgedruckt haben sie 50 3D-Drucker von Formlabs.

Gizra.com: Travis - The Need for Speed

Planet Drupal - 16. Februar 2018 - 8:00

Chances are that you already use Travis or another cool CI to execute your tests, and everyone politely waits for the CI checks before even thinking about merging, right? More likely, waiting your turn becomes a pain and you click on the merge: it’s a trivial change and you need it now. If this happens often, then it’s the responsibility of those who worked on those scripts that Travis crunches to make some changes. There are some trivial and not so trivial options to make the team always be willing to wait for the completion.

This blog post is for you if you have a project with Travis integration, and you’d like to maintain and optimize it, or just curious what’s possible. Users of other CI tools, keep reading, many areas may apply in your case too.

Unlike other performance optimization areas, doing before-after benchmarks is not so crucial, as Travis mostly collects the data, you just have to make sure to do the math and present the numbers proudly.

Caching

To start, if your .travis.yml lacks the cache: directive, then you might start in the easiest place: caching dependencies. For a Drupal-based project, it’s a good idea to think about caching all the modules and libraries that must be downloaded to build the project (it uses a buildsystem, doesn’t it?). So even a variant of:

cache: directories: - $HOME/.composer/cache/files

or for Drush

cache: directories: - $HOME/.drush/cache

It’s explained well in the verbose documentation at Travis-ci.com. Before your script is executed, Travis populates the cache directories automatically from a successful previous build. If your project has only a few packages, it won’t help much, and actually it can make things even slower. What’s critical is that we need to cache slow-to-generate, easy-to-download materials. Caching a large ZIP file would not make sense for example, caching many small ones from multiple origin servers would be more beneficial.

From this point, you could just read the standard documentation instead of this blog post, but we also have icing on the cake for you. A Drupal installation can take several minutes, initializing all the modules, executing the logic of the install profile and so on. Travis is kind enough to provide a bird’s-eye view on what eats up build time:

Execution speed measurements built in the log

Mind the bottleneck when making a decision on what to cache and how.

For us, it means cache of the installed, initialized Drupal database and the full document root. Cache invalidation is hard, we can’t change that, but it turned out to be a good compromise between complexity and execution speed gain, check our examples:

Do your homework and cache what’s the most resource-consuming to generate, SQL database, built source code or compiled binary, Travis is here to assist with that.

Software Versions

There are two reasons to pay attention to software versions.

Use Pre-installed Versions

Travis uses containers of different distributions, let’s say you use trusty, the default one these days, then if you choose PHP 7.0.7, it’s pre-installled, in case of 7.1, it’s needed to fetch separately and that takes time for every single build. When you have production constraints, that’s almost certainly more important to match, but in some cases, using the pre-installed version can speed things up.

And moreover, let’s say you prefer MariaDB over MySQL, then do not sudo and start to install it with the package manager, as there is the add-on system to make it available. The same goes for Google Chrome, and so on. Stick to what’s inside the image already if you can. Exploit that possibility of what Travis can fetch via the YML definition!

Use the Latest and (or) Greatest

If you ever read an article about the performance gain from migrating to PHP 7, you sense the importance of selecting the versions carefully. If your build is PHP-execution heavy, fetching PHP 7.2 (it’s another leap, but mind the backward incompatibilities) could totally make sense and it’s as easy as can be after making your code compatible:

language: php php: - '7.2'

Almost certainly, a similar thing could be written about Node.js, or relational databases, etc. If you know what’s the bottleneck in your build and find the best performing versions – newer or older – it will improve your speed. Does that conflict with the previous point about pre-installed versions? Not really, just measure which one helps your build the most!

Make it Parallel

When a Travis job is running, 2 cores and 4 GBytes of RAM is available – that’s something to rely on! Downloading packages should happen in parallel. drush make, gulp and other tools like that might use it out of the box: check your parameters and configfiles. However, on the higher level, let’s say you’d like to execute a unit test and a browser-based test, as well. You can ask Travis to spin up two (or more) containers concurrently. In the first, you can install the unit testing dependencies and execute it; then the second one can take care of only the functional test. We have a fine-grained example of this approach in our Drupal-Elm Starter, where 7 containers are used for various testing and linting. In addition to the great execution speed reduction, the benefit is that the result is also more fine-grained, instead of having a single boolean value, just by checking the build, you have an overview what can be broken.

All in all, it’s a warm fuzzy feeling that Travis is happy to create so many containers for your humble project:

If it's independent, no need to serialize the execution Utilize RAM

The available memory is currently between 4 and 7.5 GBytes , depending on the configuration, and it should be used as much as possible. One example could be to move the database main working directory to a memory-based filesystem. For many simpler projects, that’s absolutely doable and at least for Drupal, a solid speedup. Needless to say, we have an example and on client projects, we saw 15-30% improvement at SimpleTest execution. For traditional RMDBS, you can give it a try. If your DB cannot fit in memory, you can still ask InnoDB to fill memory.

Think about your use case – even moving the whole document root there could be legitimate. Also if you need to compile a source code, doing it there makes sense as well.

Build Your Own Docker Image

If your project is really exotic or a legacy one, it potentially makes sense to maintain your own Docker image and then download and execute it in Travis. We did it in the past and then converted. Maintaining your image means recurring effort, fighting with outdated versions, unavailable dependencies, that’s what to expect. Still, even it could be a type of performance optimization if you have lots of software dependencies that are hard to install on the current Travis container images.

+1 - Debug with Ease

To work on various improvements in the Travis integration for your projects, it’s a must to spot issues quickly. What worked on localhost, might or might not work on Travis – and you should know the root cause quickly.

In the past, we propagated video recording, now I’d recommend something else. You have a web application, for all the backend errors, there’s a tool to access the logs, at Drupal, you can use Drush. But what about the frontend? Headless Chrome is neat, it has built-in debugging capability, the best of which is that you can break out of the box using Ngrok. Without any X11 forwarding (which is not available) or a local hack to try to mimic Travis, you can play with your app running in the Travis environment. All you need to do is to execute a Debug build, execute the installation part (travis_run_before_install, travis_run_install, travis_run_before_script), start Headless Chrome (google-chrome --headless --remote-debugging-port=9222), download Ngrok, start a tunnel (ngrok http 9222), visit the exposed URL from your local Chrome and have fun with inspection, debugger console, and more.

Takeaway

Working on such improvements has benefits of many kinds. The entire development team can enjoy the shorter queues and faster merges, and you can go ahead and apply part of the enhancements to your local environment, especially if you dig deep into database performance optimization and make the things parallel. And even more, clients love to hear that you are going to speed up their sites, as this mindset should be also used at production.

Continue reading…

Bericht: Nächster Nvidia-Grafikchip heißt Turing und soll noch im März erscheinen

heise online Newsticker - 16. Februar 2018 - 7:30
Nvidia plant laut einem Reuters-Bericht, im März einen neuen Grafikchip unter dem Codenamen Turing zu veröffentlichen. Laut Reuters soll es sich um einen Gaming-Chip handeln.

Agiledrop.com Blog: AGILEDROP: Time to move forward?

Planet Drupal - 16. Februar 2018 - 2:10
When is the right time to let it go and move forward? Yes, we are talking about migrating to Drupal 8 version. Drupal 8 was released in November 2015, so it has been more than two years now. No matter what kind of website you have, whether you have an online shop, small brochure website or an extensive and complex website, if its build on Drupal 6, it's almost urgent you move forward and upgrade it to Drupal 8. Why? The Drupal community no longer (officially) supports Drupal 6 since three months after Drupal 8 came out. That means that bugs are no longer getting fixed. Drupal 6 is simply long… READ MORE