News

Drupal Core News: New community initiative: Frontend bundler

by

Adapted from: https://www.sitback.com.au/insights/article/working-with-javascript-in-d…

As far as I understand it, community initiatives exist because enough people say they’re interested and start working towards the initiative’s goals.

So I thought I would try starting an initiative to solve a problem I see pop up fairly regularly:

Basically: why isn’t there a standard way to install javascript dependencies?

Some modules have tried asset-packagist, but there are myriad problems with that:

I had a whinge about it in #australia-nz: https://drupal.slack.com/archives/C45SW3FLM/p1712295645835869 and took up larowlan’s generous offer to try to get a new initiative this off the ground.

He introduced me to Théodore (@nod_) the frontend framework manager and we three had a short discussion around suitable directions to take. This initiative would not be happening without their help and guidance, thank you so much Lee and Théodore 🙇‍♂️

We explored the idea of using import-maps to let the browser handle module imports and agreed that the cascading downloads would be an unacceptable performance burden on non-admin pages.

The result of that meeting was the idea of trying out publishing Drupal modules on npm, or at least an npm-like repository, since @larowlan mentioned that GitLab can provide one. I got started and wrote some scripts for gathering package names and putting them in a central package.json to be downloaded by npm/yarn/whatever.

Then @larowlan pointed out https://github.com/php-forge/foxy which I had seen, but didn’t really understand the power of. What I didn’t understand was that you could define a package.json file inside a composer package, make a couple of tweaks to composer.json and without publishing any kind of npm package, foxy would find it and treat it like one.

Cue a couple of weeks of messing around with foxy, composer and vite, and I have created a working prototype for compiling multiple Drupal modules (including custom modules if desired) in a project, and routing the library system to the new entry points:

https://github.com/darvanen/drupal-js

It requires a few things:

Any module that wants to opt in:

  • Adds php-forge/foxy to require or require-dev in composer.json.

  • Adds a module-name.foxy.yml file to represent the library state when using foxy.

Site builders:

  • Have one or more modules that use foxy in their project

  • Require and enable drupal/foxy

  • Add a provided vite.config.js to their project (could this be done by the foxy module?)

  • Set up a way to run vite build (or their own implementation):

    • post-install/update commands

    • pipeline?

    • manually?

—

This is where you come in

The prototype is just a starting point. I want us to come together to define a new way of working with JavaScript in Drupal that everyone can and will want to use, similar to how drupal-composer/drupal-project pioneered effective usage of composer and was eventually adopted by core. I intend to keep working on this but I want it to be driven by the community, hence the initiative.

Things you can do right now:

  • Spread the word, recruit more people to the initiative, especially if they maintain a module with JS dependencies.

  • Try out the prototype and give feedback – no change is too big to explore.

  • Join the #frontend-bundler-initiative channel to chat about ways forward – bikeshedding is welcome here, we used to call that brainstorming 😉

  • If you have a module with JS dependencies: speak up to have your module included in the prototype, or make a PR.

  • Contribute to the foxy module to get it to import css/image/asset dependencies from the vite manifest

So what do you say, are you in?- come join me in the channel!

Building a faster, smarter, Chromebook experience with the best of Google technologies

by

ChromeOS will soon be developed on large portions of the Android stack to bring Google AI, innovations, and features faster to users.

Over the last 13 years, we’ve evolved ChromeOS to deliver a secure, fast, and feature-rich Chromebook experience for millions of students and teachers, families, gamers, and businesses all over the world. With our recent announcements around new features powered by Google AI and Gemini, Chromebooks now give us the opportunity to put powerful tools in the hands of more people to help with everyday tasks.

To continue rolling out new Google AI features to users at a faster and even larger scale, we’ll be embracing portions of the Android stack, like the Android Linux kernel and Android frameworks, as part of the foundation of ChromeOS. We already have a strong history of collaboration, with Android apps available on ChromeOS and the start of unifying our Bluetooth stacks as of ChromeOS 122.

Bringing the Android-based tech stack into ChromeOS will allow us to accelerate the pace of AI innovation at the core of ChromeOS, simplify engineering efforts, and help different devices like phones and accessories work better together with Chromebooks. At the same time, we will continue to deliver the unmatched security, consistent look and feel, and extensive management capabilities that ChromeOS users, enterprises, and schools love.

These improvements in the tech stack are starting now but won’t be ready for consumers for quite some time. When they are, we’ll provide a seamless transition to the updated experience. In the meantime, we continue to be extremely excited about our continued progress on ChromeOS without any change to our regular software updates and new innovations.

Chromebooks will continue to deliver a great experience for our millions of customers, users, developers and partners worldwide. We’ve never been more excited about the future of ChromeOS.

Posted by Prajakta Gudadhe, Senior Director, Engineering, ChromeOS & Alexander Kuscher, Senior Director, Product Management, ChromeOS

Chrome OS switching to the Android Linux kernel and related Android subsystems

by
Surprisingly quietly, in the middle of Apple’s WWDC, Google’s ChromeOS team has made a rather massive announcement that seems to be staying a bit under the radar. Google is announcing today that it is replacing many of ChromeOS’ current relatively standard Linux-based subsystems with the comparable subsystems from Android. To continue rolling out new Google AI features to users at a faster and even larger scale, we’ll be embracing portions of the Android stack, like the Android Linux kernel and Android frameworks, as part of the foundation of ChromeOS. We already have a strong history of collaboration, with Android apps available on ChromeOS and the start of unifying our Bluetooth stacks as of ChromeOS 122. ↫ Prajakta Gudadhe and Alexander Kuscher on the Chromium blog The benefits to Google here are obvious: instead of developing and maintaining two variants of the Linux kernel and various related subsystems, they now only have to focus on one, saving money and time. It will also make it easier for both platforms to benefit from new features and bugfixes, which should benefit users of both platforms quite a bit. As mentioned in the snippet, the first major subsystem in ChromeOS to be replaced by its Android counterpart is Bluetooth. ChromeOS was using the BlueZ Bluetooth stack, the same one used by most (all?) Linux distributions today, which was initially developed by Qualcomm, but has now switched over to using Fluoride, the one from Android. According to Google, Fluoride has a number of benefits over BlueZ. It runs almost entirely in userspace, as opposed to BlueZ, where more than 50% of the code resides in the kernel. In addition, Fluoride is written in Rust, and Google claims it has a simpler architecture, making it easier to perform testing. Google also highlights that Fluoride has a far larger userbase – i.e., all Android users – which also presents a number of benefits. Google performed internal tests to measure the improvements as a result from switching ChromeOS from BlueZ to Fluoride, and the test results speak for themselves – pairing is faster, pairing fails less often, and reconnecting an already paired device fails less often. With Bluetooth being a rather problematic technology to use, any improvements to the user experience are welcome. At the end of Google’s detailed blog post about the switch to Fluoride, the company notes that it intends for the project as whole – which is called Project Floss – to be a standalone open source project, capable of running on any Linux distribution. ↫ Russ Lindsay, Abhishek Pandit-Subedi, Alain Michaud, and Loic Wei Yu Neng on the chromeOS dev website We aspire to position Project Floss as a standalone open source project that can reach beyond the walls of Google’s own operating system in a way where we can maximize the overall value and agility of the larger Bluetooth ecosystem. We also intend to support the Linux community as a whole with the goal that Floss can easily run on most Linux distributions. If Fluoride can indeed deliver tangible, measurable benefits in Bluetooth performance on Linux desktops, I have no doubt quite a few distributions will be more than willing to switch over. Bluetooth is used a lot, and if Fedora, Ubuntu, Arch, and so on, can improve the Bluetooth experience by switching over, I’m pretty sure they will, or at least consider doing so.

ESP – ARHC Robotics Podcast Aethon 002

by
Affiliate Disclosure: Some of the links below are affiliate links, which means that at no additional cost to you, I will earn a commission if you click through and make a purchase.

Aquí está el comunicado de prensa original de Aethon:
https://aethon.com/st-engineering-aethon-launches-zena-rx/

¡La tienda de National Geographic en Amazon es perfecta para regalos educativos!
https://amzn.to/45bWgSm

Hola, soy August Lizárraga Jr.

Planeo investigar y presentar personalmente la mejor información disponible sobre robótica de atención médica de asistencia y rehabilitación a toda mi audiencia en inglés, español, portugués, alemán, francés y holandés.

¡Robots que ayudan a limpiar! Visita la tienda iRobot en Amazon.
https://amzn.to/3yPiAFn

¿Interesado en la robótica? Consulte las principales tiendas de robótica en Amazon:
https://amzn.to/3RiuZaZ

Arduino: Su fuente de referencia para kits de microcontroladores y más.
https://amzn.to/3x9G2MT
HiLetgo: Encuentra todos los componentes electrónicos para tus proyectos de bricolaje.
https://amzn.to/3x45zHo
DFRobot: Obtenga los componentes básicos para una variedad de proyectos electrónicos.
https://amzn.to/45czY2F

Copyright © 2024 by August Lizarraga Jr.

All rights reserved. No part of this publication may be reproduced in any form or by any electronic or mechanical means, including information storage and retrieval systems, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted by copyright law. Please purchase only authorized electronic editions and do not participate in or encourage electronic piracy of copyrighted materials. Your support of the author’s rights is appreciated. Any member of educational institutions wishing to photocopy part or all of the work for classroom use, should send inquiries to augustprofessional35@gmail.com.

Any use of this publication to train generative artificial intelligence (“AI”) technologies is expressly prohibited. The author and publisher reserve all rights to license usage of this work for generative AI training and development of machine learning language models.

Sattva Green Groves Is Located In Prime Location Of Bangalore

by
https://appsumo.com/profile/sattvagreeng/
https://mdbootstrap.com/user/greengroves/
https://paste.toolforge.org/view/3782ce0b
https://bodyspace.bodybuilding.com/about-me/sattvagreeng
https://forum.index.hu/User/UserDescription?u=2001348
https://coggle.it/diagram/ZmkI3CxbA21zSyGU/t/-/da7a3f27c4da5585a417eb565bca42140555c67f2608819825c721168d43fb20
https://www.colourlovers.com/lover/sattvagrovespro
https://zbrush.dpi.upv.es/wordpress/artistas-2/sattvagreenplan/profile/
https://rutube.ru/video/ed3dc078a6f45fac82b1178f52f50599/
https://workdrive.zohopublic.in/file/oa9b75cc97a49b96a40dca4fbae16d9c2ea27
https://community.amd.com/t5/user/viewprofilepage/user-id/422854
https://www.pinterest.ca/csiliconcity/
https://issuu.com/siliconcityplan/docs/century_silicon_city.pptx
https://www.pinterest.com.au/csiliconcity/