Podcasts about garbage collector

JDK 26 optimise la JVM dans ses moindres recoins, le SDK Java d'Agent2Agent passe en 1.0, Micronaut 5 est là. Côté terrain, un retour d'expérience après 40 jours à coder avec 100 % d'IA : génie ou junior, Alzheimer numérique et dette technique invisible. Pendant ce temps, GitLab restructure, Microsoft suspend ses licences Claude Code, et un développeur injecte un prompt destructeur dans sa lib JUnit. La révolution IA a un coût et les boites commencent à s'en rendre compte. Enregistré le 12 juin 2026 Téléchargement de l'épisode LesCastCodeurs-Episode-341.mp3 ou en vidéo sur YouTube. News Langages Les améliorations de performance dans le JDK 26 https://inside.java/2026/06/09/jdk-26-performance-improvements/ Côté bibliothèques, l'API LazyConstant (anciennement StableValue) fait son entrée en prévisualisation pour permettre une initialisation paresseuse, sécurisée pour les threads et optimisée par le mécanisme de constant-folding de la JVM. L'extraction de chaînes de caractères via MemorySegment::getString a été revue pour réduire considérablement les allocations intermédiaires et les copies en mémoire off-heap, accélérant fortement les traitements sur les chemins critiques (hot paths). La méthode générée automatiquement hashCode() pour les classes de type record a été optimisée par la JVM pour atteindre un niveau de performance équivalent à une implémentation écrite manuellement. Le ramasse-miettes G1 bénéficie du JEP 522 qui redessine sa table de cartes (card-table) afin de réduire les coûts de synchronisation des barrières d'écriture, offrant un gain de débit de 5 % à 15 % sur les applications manipulant énormément de références d'objets. Grâce au JEP 516 (Project Leyden), le cache d'objets Ahead-of-Time (AOT) adopte un format de flux agnostique, ce qui lui permet d'être compatible avec n'importe quel Garbage Collector, y compris le ramasse-miettes à très faible latence ZGC. Le démarrage de la JVM s'accélère par défaut lorsqu'aucune taille de tas n'est configurée, car HotSpot n'applique plus de pourcentage initial (InitialRAMPercentage) mais démarre directement avec la taille minimale (MinHeapSize) pour éviter d'allouer des métadonnées inutiles. Les threads virtuels gagnent en robustesse en étant désormais capables de céder la main (yield) pendant les phases d'initialisation des classes, éliminant ainsi le risque de famine des threads porteurs (carrier threads). Le compilateur C2 JIT améliore son modèle de coût pour la vectorisation des boucles (SIMD) et se montre maintenant capable de compiler et d'optimiser des méthodes dotées de listes de paramètres extrêmement longues. Librairies Release candidate du A2A Java SDK supportant versions 0.3 et 1.0 en même temps https://medium.com/google-cloud/a2a-java-sdk-1-0-0-cr1-released-f0c651ec9139 Dernière étape avant la GA : Toutes les fonctionnalités prévues pour la version 1.0 sont finalisées. Migration simplifiée depuis la Beta1. Compatibilité v0.3 : Ajout d'une couche de compatibilité permettant aux agents v1.0 de communiquer avec les systèmes v0.3 (via JSON-RPC, gRPC ou REST). Support natif pour Android (nouvel AndroidHttpClient). Uniformisation des clients HTTP pour garantir une cohérence entre les versions. Nouveau parseur SSE (Server-Sent Events) conforme aux spécifications. Ça y est, le SDK Java de l'Agent 2 Agent Protocol est sorti en version 1.0 finale ! (avec compatibilité v0.3 et v1.0) https://medium.com/google-cloud/a2a-java-sdk-1-0-0-final-released-10c05b6aee34 Lancement officiel : Sortie de A2A Java SDK 1.0.0.Final, la première version stable (GA) du protocole Agent2Agent. Objectif du protocole : Standard ouvert (Linux Foundation) permettant aux agents IA de communiquer, déléguer des tâches et collaborer, indépendamment du langage ou du framework. Interopérabilité : Introduction de l'Integration Test Kit (ITK) pour valider la compatibilité entre les SDK (Java, Python, TypeScript, etc.). Transports supportés : Support complet et équivalent pour JSON-RPC, gRPC et HTTP+JSON/REST. Alignement total avec la spécification A2A 1.0.0. Passage aux Java records pour l'immutabilité et moins de code répétitif. Architecture interne basée sur un MainEventBus pour garantir la persistance et éviter les conditions de concurrence. Intégration d'OpenTelemetry pour le suivi et la surveillance. Support d'Android et compatibilité descendante avec la version 0.3. Installation : Gestion des dépendances via Maven BOM (org.a2aproject.sdk). Sortie de Micronaut 5.0 https://micronaut.io/2026/05/20/micronaut-framework-5-0-0-released/ Lancement majeur : Disponibilité générale de Micronaut 5, incluant une refonte de plus de 70 modules et la plateforme BOM. Baselines techniques : Support de Java 25, Groovy 5, Kotlin 2.3 et GraalVM 25.0.3. Optimisations internes : Amélioration significative des performances au démarrage et réduction de la surcharge à l'exécution via une refonte du conteneur IoC et du traitement à la compilation. Architecture HTTP : Support stable de HTTP/3, nouvelle API de formulaires (multipart) et annotations de nullabilité (JSpecify) pour une meilleure interopérabilité Kotlin/IDE. Configuration : Nouveau système d'importation de configuration (remplaçant le Bootstrap Configuration) et validateur de schéma JSON intégré. Fiabilité : Nouvelles API programmatiques pour les politiques de retry et circuit breaker. Sécurité & Outils : Mise à jour majeure des dépendances (Jackson 3, Ktor 3), rafraîchissement du Panneau de contrôle et diagnostics AOT améliorés. Écosystème : Mises à jour complètes pour les bases de données (Data, SQL, R2DBC, MongoDB, Redis), le cloud (AWS, Azure, GCP, OCI) et les tests (JUnit 6, Testcontainers 2.0). Évolutions notables : Intégration HTMX dans Micronaut Views, retrait du support RxJava 2 et migration de divers processeurs d'annotations vers des modules dédiés. Comment rajouter un agent IA dans une app Android, avec le tout nouveau framework ADK pour Kotlin https://glaforge.dev/posts/2026/05/21/wiring-adk-kotlin-agents-in-an-android-application/ Guillaume a participé au développement et au lancement du nouveau runtime ADK pour Kotlin et Android https://developers.googleblog.com/adk-kotlin-android-building-ai-agents/ Tutoriel sur comment intégrer un agent ADK dans une app Dépendances : Ajout du noyau ADK (google-adk-kotlin-core) et du processeur KSP dans build.gradle.kts. Sécurité API : Utilisation de local.properties pour stocker la clé API Gemini et l'exposer via BuildConfig afin d'éviter le hardcoding. Définition de l'agent : Création d'un objet LlmAgent configuré avec le modèle Gemini, des instructions spécifiques et des outils (ex: GoogleSearchTool). Utilisation de InMemoryRunner pour gérer automatiquement le contexte et l'historique de la session. Implémentation de runAsync avec StreamingMode.SSE pour un retour en temps réel dans l'interface. Threading : Exécution des requêtes réseau sur Dispatchers.IO et mise à jour de l'état de l'interface utilisateur sur Dispatchers.Main. Comment développer et hoster des agents IA sur la plateforme d'agents managés de DeepMind https://glaforge.dev/posts/2026/05/21/managed-agents-with-the-gemini-interactions-java-sdk/ L'équipe DeepMind de Google a lancé une plateforme d'agents managés sur son API Gemini Interactions https://blog.google/innovation-and-ai/technology/developers-tools/managed-agents-gemini-api/ Guillaume a implémenté un SDK Java pour utiliser cette API Gemini Interactions, qui donne entre autre accès à tous les modèles mais aussi à cette plateforme managée d'agents IA Agents managés : Permet d'exécuter des agents autonomes qui raisonnent, planifient et exécutent du code dans des environnements isolés (sandboxes), sans gestion d'infrastructure par le développeur. Environnement distant : Utilise des espaces de travail Linux éphémères dans le cloud via le paramètre remote, permettant l'accès réseau et la persistance des fichiers sur plusieurs appels. Agents prédéfinis : Accès immédiat à des agents spécialisés comme deep-research-pro (recherche multi-étapes) ou antigravity (tâches de codage généralistes). Agents personnalisés : Possibilité de configurer ses propres agents avec des instructions système dédiées, des outils spécifiques (exécution de code, recherche Google) et des règles réseau (egress) personnalisées. Architecture basée sur les étapes (Steps) : Utilise une structure de données typée (Step, Content) pour suivre le raisonnement de l'agent, ses appels de fonctions et ses résultats en temps réel. Outils et Schémas : Inclut des utilitaires pour générer des schémas JSON complexes via une interface fluide (DSL), par réflexion Java ou par parsing JSON. Streaming réactif : Support natif des événements en temps réel (SSE) pour suivre la progression de l'agent et recevoir les deltas de contenu au fur et à mesure de la génération. Flexibilité : Fournit un gestionnaire de routage (InteractionsHandler) pour créer facilement des serveurs proxy ou des backends intermédiaires traitant les interactions Gemini. Spring Boot 4.1 https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-4.1-Release-Notes Support natif pour Spring gRPC permettant de créer et tester facilement des applications clientes et serveurs basées sur Netty ou des Servlets via HTTP/2 Introduction du lazy fetching pour les connexions JDBC via la propriété spring.datasource.connection-fetch=lazy afin de ne prendre une connexion du pool que lorsqu'un Statement est réellement exécuté Amélioration de l'auto-configuration de Jackson permettant de définir globalement les contraintes de lecture/écriture pour les formats JSON, XML et CBOR via des propriétés de configuration Sécurisation des clients HTTP bloquants et réactifs face aux attaques SSRF grâce à l'introduction d'un InetAddressFilter bloquant les requêtes sortantes vers des adresses spécifiques Améliorations majeures autour d'OpenTelemetry avec le support complet des variables d'environnement OTel, la possibilité de désactiver le SDK via une propriété globale et l'ajout du support SSL sur les exporters OTLP Ajout de l'auto-configuration pour l'utilisation de Spring Batch avec MongoDB incluant un nouveau starter dédié spring-boot-batch-data-mongo Auto-configuration des endpoints @RedisListener sans nécessiter la déclaration manuelle d'un RedisMessageListenerContainer Dépréciation du support de Apache Derby (projet arrêté), suppression définitive du mode layertools du JAR et réintroduction du support de Spock 2.4 (avec Groovy 5) Upgrade des dépendances majeures de l'écosystème avec notamment Spring Framework 7.0.8, Spring Security 7.1.0 et Micrometer 1.17.0 Outillage Vous êtes plutôt endive ou chicorée ? La librairie Chicory qui permet d'exécuter du code WASM à partir de son application Java est forkée et rejointe la Bytecode Alliance pour continuer son développement https://bytecodealliance.org/articles/endive-and-the-next-chapter-of-webassembly-on-the-jvm Annonce d'Endive : Nouveau projet hébergé par la Bytecode Alliance ; fork de Chicory (moteur WebAssembly pur Java, sans dépendance native). ​Objectif principal : Permettre aux développeurs Java d'intégrer, charger et déployer des modules Wasm nativement via les workflows Java habituels. ​Compilateur "Redline" : Intégration à venir de Redline (basé sur Cranelift) pour compiler le Wasm en code machine natif ; performances comparables à Rust/Wasmtime. ​Zéro dépendance (Java 25+) : Grâce à l'API standard Foreign Function & Memory (Project Panama), l'exécution à vitesse native se fait sans composants externes. ​Modèle de Composants (Component Model) : Support futur prévu pour consommer des composants (Rust, Go, JS, etc.) via des interfaces typées et sécurisées directement dans la JVM. ​Prochaines étapes : Fusion de Redline, conformité stricte aux specs Wasm (dont WasmGC) et amélioration du support WASI. Un visualisateur de sessions de travail avec Antigravity https://glaforge.dev/posts/2026/06/11/antigravity-brain-visualizer/ Un projet open source construit avec Micronaut, LangChain4j et GraalVM pour analyser les sessions de travail avec l'outil de développement agentique Antigravity (de Google) Analyse toutes les étapes, les requêtes utilisateur, les outils utilisés, les erreurs rencontrées, les réponses du modèle Gemini fait une analyse pour comprendre les moments clés de cette session de travail Outil buildé avec l'aide d'Antigravity lui-même SBX-Kits : des environnements de développement simplifiés pour les débutants (et les autres) https://k33g.org/20260501-sbx-kits.html Philippe Charrière (:whale: ) présente SBX-Kits (Sandbox Kits), une initiative personnelle visant à simplifier radicalement la mise en place d'environnements de développement pour les débutants, en éliminant la complexité d'installation des outils traditionnels. Chaque "kit" est une archive prête à l'emploi contenant un outil de développement spécifique (comme un langage, un framework ou une base de données) configuré pour s'exécuter de manière isolée et portable. La philosophie du projet repose sur le principe de "zéro configuration" et "zéro dépendance globale", permettant de tester une technologie ou de commencer à coder immédiatement sans polluer son système d'exploitation. L'approche technique s'appuie sur des scripts légers et des binaires portables pré-packagés, offrant une alternative plus simple et moins gourmande en ressources que les conteneurs Docker ou les configurations d'IDE complexes pour l'apprentissage. L'objectif à terme est de proposer un catalogue de kits couvrant les technologies courantes (JavaScript, Python, petites bases de données) pour faciliter les ateliers de programmation et le prototypage rapide. De nombreux kits sont disponibles sur https://github.com/docker/sbx-kits-contrib ghui: une interface utilisateur en ligne de commande (TUI) interactive pour GitHub https://github.com/kitlangton/ghui ghui est un outil en ligne de commande (TUI) écrit en Rust qui fournit une interface visuelle, interactive et rapide directement dans le terminal pour interagir avec GitHub. Il permet de gérer ses pull requests, ses issues et ses notifications sans avoir à ouvrir son navigateur web ou à taper de longues commandes avec la CLI officielle de GitHub. L'outil propose une navigation fluide au clavier, des raccourcis efficaces, et permet de réaliser des actions courantes comme valider une PR, ajouter des commentaires, attribuer des reviewers ou inspecter les logs des GitHub Actions. Conçu pour être extrêmement réactif, ghui s'intègre naturellement dans le flux de travail des développeurs adeptes du terminal et du mode "sans souris". Sortie de Homebrew 6.0.0 https://brew.sh/2026/06/11/homebrew-6.0.0/ Introduction du mécanisme de sécurité Tap Trust : comme les dépôts tiers (taps) peuvent exécuter du code Ruby arbitraire non sandboxé sur la machine, Homebrew demande désormais une confiance explicite de l'utilisateur avant d'évaluer ou d'exécuter leur code. L'API JSON interne devient le choix par défaut, offrant un système plus léger et beaucoup plus rapide pour les développeurs. Sécurisation renforcée de l'environnement avec l'implémentation du sandboxing sur Linux. Évolution des comportements par défaut basés sur un sondage utilisateur : le mode "ask" est activé par défaut pour les développeurs, affichant un résumé des dépendances et une demande de confirmation avant toute action de brew install ou brew upgrade. Améliorations notables des performances globales, notamment un boost de ~30 % sur la vitesse de la commande brew leaves et la parallélisation de la récupération des bottles (binaires) lors des mises à jour. Ajout du support initial pour la prochaine version d'Apple, macOS 27 (Golden Gate). Multiples optimisations pour brew bundle, incluant une gestion plus sécurisée des installations de paquets npm. Méthodologies Retour d'expérience très détaillé et 100% humain sur 40 jours avec une équipe 100% AI hormis le superviseur https://www.linkedin.com/pulse/jai-vir%C3%A9-mon-%C3%A9quipe-de-dev-pour-une-100-ia-pendant-40-luc-bonnin-jlgjf/ Voici le résumé en bullet points : Expérimentation de 40 jours : remplacer une équipe de dev par 100% IA agentique (Cursor) sur un vrai projet en production (playthatsheet.com, 200k lignes de code legacy) Chiffres bruts : 2,3 milliards de tokens consommés, 1 477 prompts, 260 564 lignes ajoutées (+145%), 59% du code final produit par l'IA ROI vertigineux à court terme : 9 mois de travail humain livrés en 40 jours, coût total 260$ d'abonnement + 15 jours de supervision, ROI x18 Profil psy de l'IA : Alzheimer (oublis de contexte), schizophrène (change de méthodo), ado de 12 ans (refait les mêmes erreurs), oscille entre génie et junior sans prévenir Effet iceberg : la dette technique ne disparaît pas, elle se camoufle et s'accélère ; hallucinations = bombes à retardement détectables uniquement par relecture humaine ligne par ligne Paradoxe du bateau de Thésée : perte de paternité et de maîtrise fine du code, baisse de l'autonomie du dev humain qui valide sans avoir construit Arnaque du "monkey money" : consommation de tokens opaque, non corrélée à la complexité (écart de 350% sur des prompts identiques), facturation imprévisible donc impossible à budgéter Syndrome du bazooka : les devs utilisent l'IA même pour changer une couleur CSS, atrophie progressive des compétences et coût écologique délirant Risque stratégique : dépendance irréversible aux vendeurs de tokens (Nvidia, Anthropic, OpenAI), business non rentable qui devra augmenter ses prix Conseil final : approche Pareto, garder 20% du temps en code "fait main", nommer un responsable stratégie IA, l'humain senior reste irremplaçable pour superviser Une libraries de test JUnit cache un prompt qui demande aux coding agents d'effacer les tests https://arstechnica.com/security/2026/05/fed-up-with-vibe-coders-dev-sneaks-data-nuking-prompt-injection-into-their-code/ Agacé par les « vibe coders », un développeur introduit une injection de prompt destructrice dans son code Le développeur de jqwik (un moteur de tests pour JUnit 5) a volontairement inséré une injection de prompt dans la version 1.10.0 de sa bibliothèque Java pour saboter le travail des agents d'IA. L'instruction injectée via la sortie standard (stdout) ordonne textuellement aux LLM d'ignorer les consignes précédentes et de supprimer l'intégralité du code et des tests jqwik du projet. Pour dissimuler cette action aux yeux des développeurs humains, le mainteneur a utilisé des séquences d'échappement ANSI qui effacent la ligne d'injection dans les émulateurs de terminaux interactifs. La modification a été découverte par un utilisateur qui a pointé du doigt les risques majeurs et disproportionnés pour les machines des utilisateurs, bien que certains outils comme Claude d'Anthropic aient détecté et bloqué la consigne malveillante. Face aux critiques de la communauté et aux accusations de comportement infantile ou potentiellement illégal, le développeur a mis à jour ses notes de version pour documenter explicitement son opposition à l'usage de son outil par des IA, avant de refuser tout commentaire supplémentaire sur conseil de son avocat. La réalité du rôle de Principal Engineer https://leaddev.com/career-development/reality-being-principal-engineer Le passage au rôle de Principal Engineer marque une transition majeure où les compétences techniques ne suffisent plus, l'impact se mesurant désormais à travers l'influence, la stratégie et la capacité à aligner la technique avec les objectifs business. Contrairement aux attentes, le quotidien est souvent marqué par une forme d'isolement, car le poste se situe à l'intersection de la direction (qui attend des solutions) et des équipes techniques (qui attendent des directives), sans appartenance directe à un groupe précis. Le rôle exige d'accepter une grande part d'ambiguïté et l'absence de retours immédiats, les projets et les décisions stratégiques mettant parfois des mois ou des années à porter leurs fruits. La gestion du temps devient un défi critique, nécessitant de savoir naviguer entre les sollicitations constantes, la présence en réunion et le besoin de préserver des moments de réflexion approfondie pour concevoir des visions à long terme. La réussite à ce niveau repose sur le développement de compétences humaines pointues (soft skills), notamment la négociation, la communication vulgarisée auprès des profils non techniques, et la capacité à faire grandir les autres ingénieurs par le mentorat. Sécurité Une attaque de la chaîne d'approvisionnement npm utilise binding.gyp pour compromettre des dizaines de paquets https://cybersecuritynews.com/binding-gyp-supply-chain-attack-compromises-dozens-of-npm-packages/ Une nouvelle variante du ver auto-propageable "Shai-Hulud", baptisée "Miasma", cible l'écosystème npm (et PyPI sous le nom de "Hades") en dissimulant son exécution dans le fichier binding.gyp au lieu des scripts classiques preinstall ou postinstall. La technique, surnommée "Phantom Gyp", exploite le fait que npm lance automatiquement node-gyp rebuild dès qu'un fichier binding.gyp est présent à la racine d'un paquet pour compiler des modules natifs C/C++, exécutant ainsi le code malveillant dès la commande npm install. L'attaque contourne la plupart des outils de sécurité traditionnels car l'injection s'appuie sur l'évaluation récursive de commandes (via la syntaxe ) ou directement sur la fonction eval() de Python sous-jacente à GYP, cachée sous n'importe quelle clé du fichier. Le script malveillant télécharge un runtime alternatif (Bun) pour échapper aux détections comportementales de Node.js, puis moissonne les identifiants et secrets des développeurs et des environnements CI/CD (npm, GitHub, AWS, GCP, Azure, Kubernetes, HashiCorp Vault). Plus de 57 paquets npm (dont le SDK serveur de Vapi ou des outils liés à l'IA) et des dizaines de paquets PyPI ont été infectés via des comptes de mainteneurs compromis, le ver republiant automatiquement de nouvelles versions vérolées en utilisant les jetons volés. Loi, société et organisation Restructuration chez Gitlab https://about.gitlab.com/blog/gitlab-act-2/ GitLab entame une restructuration majeure pour s'adapter à l'ère de l'intelligence artificielle agentique, incluant une réduction d'effectifs planifiée de manière transparente et ouverte. L'entreprise prévoit de réduire de 30 % le nombre de pays où elle maintient de petites équipes, d'aplatir sa hiérarchie en supprimant jusqu'à trois niveaux de gestion, et de réorganiser la R&D en une soixantaine d'équipes plus petites et autonomes. Les processus internes vont être revus en intégrant des agents d'IA pour automatiser les revues, les approbations et les passages de relais afin d'accélérer le rythme de travail. La stratégie repose sur la conviction que le logiciel sera bientôt écrit par des machines et dirigé par des humains, ce qui va multiplier la demande de logiciels et transformer le rôle des ingénieurs vers la résolution de problèmes complexes. Sur le plan technique, GitLab reconstruit son infrastructure sous-jacente (notamment Git) pour supporter la charge massive générée par les agents d'IA, tout en misant sur l'orchestration du cycle de vie, la centralisation du contexte des données et une gouvernance intégrée. Le modèle économique évolue vers un système hybride combinant les abonnements classiques et une tarification à la consommation pour le travail effectué par les agents d'IA. Un LLM local sur un mac pourrait coûter plus cher en électricité qu'un modèle hébergé sur OpenRouter dans le cloud https://www.williamangel.net/blog/2026/05/17/offline-llm-energy-use.html Conclusion : L'inférence locale sur Mac M5 Max est 3x plus chère et 2x plus lente que le cloud (OpenRouter). Électricité : Négligeable (~0,02 $/heure pour 50-100W). Matériel (Le vrai coût) : Achat du Mac à 4 299 $; l'amortissement sur 3 à 5 ans plombe la rentabilité horaire. Coût au million de tokens (Gemma 4 31b) : Mac M5 Max : 0,40 à4, 79 (pour 10-40 tokens/s). OpenRouter : 0,38 à0, 50 (pour 60-70 tokens/s). Verdict pro : Le temps humain perdu à cause de la lenteur locale coûte infiniment plus cher que les tokens cloud. Privilégier les API (Anthropic, OpenRouter). Ai didn't kill your junior pipeline https://andrewmurphy.io/blog/ai-didnt-kill-your-junior-pipeline-you-did L'IA n'a pas tué le recrutement des juniors, les entreprises l'ont fait elles-mêmes, par effet de mode. Sans juniors, pas de futurs seniors : on retire l'échelle qui nous a tous fait monter. Tout le monde pêche dans le même bassin de seniors sans le réapprovisionner, pénurie garantie dans 3-5 ans. Une équipe 100% senior + IA est fragile : un départ et tout le savoir tacite s'évapore. Les juniors posent les "pourquoi ?" qui révèlent les bugs et processus absurdes ; l'IA, elle, exécute sans questionner. Les seniors s'atrophient aussi en déléguant leur réflexion à l'IA, pince à double effet sur les compétences. Dépendre des outils IA, c'est sous-traiter sa stratégie talents à des fournisseurs dont les prix vont tripler. Solution : redéfinir le rôle junior (revue de code IA + mentorat), pas le supprimer. Les rapports internes de Microsoft révèlent la crise des coûts de l'IA : les agents coûtent plus cher que les employés humains https://fortune.com/2026/05/22/microsoft-ai-cost-problem-tokens-agents/ Des données et rapports internes chez Microsoft et d'autres géants de la tech ébranlent la promesse de rentabilité de l'IA, révélant que le déploiement d'agents autonomes à l'échelle de l'entreprise revient souvent plus cher que de payer des humains pour le même travail. Le modèle de tarification à l'usage (basé sur les tokens) se heurte à la nature même des architectures agentiques : contrairement à un simple chatbot, un agent boucle, enchaîne les appels d'outils, crée des sous-agents et auto-évalue son code, ce qui multiplie la consommation de tokens par un facteur de 5 à 30, voire jusqu'à 1 000 fois pour des tâches de programmation complexes. L'impact financier sur les budgets de calcul cloud est immédiat ; par exemple, Uber a entièrement épuisé l'intégralité de son budget annuel 2026 dédié au codage par IA en l'espace de seulement quatre mois. Face à cette explosion des coûts, des retours en arrière drastiques sont observés : Microsoft a ainsi commencé à suspendre une grande partie de ses licences internes Claude Code pour rediriger d'urgence ses milliers de développeurs vers sa propre solution moins onéreuse, GitHub Copilot CLI. Les directeurs techniques (CTO) et acheteurs de solutions logicielles qui ont signé des contrats pluriannuels basés sur des projections de réduction de masse salariale se retrouvent pris au piège, les gains réels de productivité ne parvenant pas à compenser les factures d'infrastructure exorbitantes. Conférences La liste des conférences provenant de Developers Conferences Agenda/List par Aurélie Vache et contributeurs : 11-12 juin 2026 : DevQuest Niort - Niort (France) 11-12 juin 2026 : DevLille 2026 - Lille (France) 12 juin 2026 : Tech F'Est 2026 - Nancy (France) 15 juin 2026 : Jupyter Workshops: Demystifying MyST Markdown in Education - Orsay (France) 16 juin 2026 : Mobilis In Mobile 2026 - Nantes (France) 17-19 juin 2026 : Devoxx Poland - Krakow (Poland) 17-20 juin 2026 : VivaTech - Paris (France) 18 juin 2026 : Tech'Work - Lyon (France) 22-26 juin 2026 : Galaxy Community Conference - Clermont-Ferrand (France) 23-24 juin 2026 : MWCP 2026 - Paris (France) 24-25 juin 2026 : Agi'Lille 2026 - Lille (France) 24-26 juin 2026 : BreizhCamp 2026 - Rennes (France) 26-27 juin 2026 : LeHACK - Paris (France) 27 juin 2026 : Asynconf - Paris (France) 2 juillet 2026 : Azur Tech Summer 2026 - Valbonne (France) 2 juillet 2026 : MCP Connect Travel Edition - Paris (France) 2-3 juillet 2026 : Sunny Tech - Montpellier (France) 3 juillet 2026 : Agile Lyon 2026 - Lyon (France) 6-8 juillet 2026 : Riviera Dev - Sophia Antipolis (France) 28-30 août 2026 : State of the Map - Champs-sur-Marne (France) 4 septembre 2026 : JUG Summer Camp 2026 - La Rochelle (France) 10-11 septembre 2026 : Nantes Craft - Nantes (France) 17 septembre 2026 : dotAI - Paris (France) 17-18 septembre 2026 : API Platform Conference 2026 - Lille (France) 18 septembre 2026 : WordCamp Bretagne - Rennes (France) 18 septembre 2026 : dotJS - Paris (France) 18 septembre 2026 : WordCamp Bretagne - Rennes (France) 22 septembre 2026 : Salon Data 2026 - Nantes (France) 22-23 septembre 2026 : Agile en Seine & IA 2026 - Paris (France) 24 septembre 2026 : OWASP AppSec Days France 2026 - Paris (France) 24 septembre 2026 : PlatformCon Paris - Paris (France) 24 septembre 2026 : React Native Connection 2026 - Paris (France) 24-26 septembre 2026 : Paris Web 2026 - Paris (France) 25 septembre 2026 : SAP Inside Track Paris 2026 - Paris (France) 28-29 septembre 2026 : 4th Tech Summit on AI & Robotics - Paris (France) & Online 1 octobre 2026 : WAX 2026 - Marseille (France) 1-2 octobre 2026 : Volcamp - Clermont-Ferrand (France) 2 octobre 2026 : DevFest Perros-Guirec 2026 - Perros-Guirec (France) 5-9 octobre 2026 : Devoxx Belgium - Antwerp (Belgium) 8-9 octobre 2026 : Forum PHP 2026 - Marne-la-Vallée (France) 12 octobre 2026 : Dev With AI - Paris (France) 22-23 octobre 2026 : Agile Tour Bordeaux 2026 - Bordeaux (France) 26 octobre 2026 : Agile Tour Montpellier - Montpellier (France) 27-29 octobre 2026 : Directions EMEA 2026 - Paris (France) 29-30 octobre 2026 : BDX I/O 2026 - Bordeaux (France) 29-30 octobre 2026 : Agile Tour Nantais 2026 - Nantes (France) 29 octobre 2026-1 novembre 2026 : Pycon FR - Biarritz (France) 30 octobre 2026 : Cloud Nord 2026 - Lille (France) 4-5 novembre 2026 : Devoxx Morocco - Casablanca (Morocco) 14-15 novembre 2026 : Capitole du Libre - Toulouse (France) 19 novembre 2026 : DevFest Toulouse 2026 - Toulouse (France) 19 novembre 2026 : Agile Laval 2026 - Laval (France) 19 novembre 2026 : OVHcloud Summit - Paris (France) 19 novembre 2026 : Codeurs en Seine - Rouen (France) 27 novembre 2026 : DevFest Paris 2026 - Paris (France) 1-3 décembre 2026 : Apidays Paris - Paris (France) 2-3 décembre 2026 : Cloud Native AI Summit Europe - Paris (France) 4 décembre 2026 : DevFest Lyon 2026 - Lyon (France) 4 décembre 2026 : DevFest Dijon 2026 - Dijon (France) 9-10 décembre 2026 : OpenSource Expérience - Paris (France) 9-10 décembre 2026 : DevOps REX - Paris (France) 10 décembre 2026 : KCD Provence - Aix-en-Provence (France) 7-9 avril 2027 : Devoxx France 2027 - Paris (France) 3 juin 2027 : Cloud Native Days France 2027 - Paris (France) Nous contacter Pour réagir à cet épisode, venez discuter sur le groupe Google https://groups.google.com/group/lescastcodeurs Contactez-nous via X/twitter https://twitter.com/lescastcodeurs ou Bluesky https://bsky.app/profile/lescastcodeurs.com Faire un crowdcast ou une crowdquestion Soutenez Les Cast Codeurs sur Patreon https://www.patreon.com/LesCastCodeurs Tous les épisodes et toutes les infos sur https://lescastcodeurs.com/

Imagine what you can learn about a city by picking up the garbage of the people who live there. Simon Paré-Poupart, a sociologist and garbageman in Montreal, joins host Krys Boyd to discuss his life on the back of a garbage truck, why he prefers the term G-men to garbagemen, and the people who are called to do this dirty job well and with pride. His book is “Trash!: A Garbageman's Story,” and his companion piece in Harper's is “The Conscience of the City.” Learn about your ad choices: dovetail.prx.org/ad-choices

Join Lighthouse Horror on Patreon: Lighthouse Horror | PatreonNew Merch out! https://hauntedstuff.com/Art & Credits: ninerioartsMusic by Lucas King, Myuu, Kevin MacLeod & Darren CurtisOriginal YouTube link: I Work as a Garbage Collector. There are 6 STRANGE Rules. Copyright © 2025 Lighthouse Horror. All rights reservedThank you for listening to this scary story! If you enjoyed this story, please check out some of my other horror stories. We'll be uploading new episodes every week, featuring ghost stories, haunted encounters, mysteries, true stories, creepypasta, and anything supernatural and paranormal. Don't miss out on the thrill and suspense that await you in each episode!

פרק מספר 505 של רברס עם פלטפורמה - באמפרס מספר 89, שהוקלט ב-13 בנובמבר 2025, רגע אחרי כנס רברסים 2025 [יש וידאו!]: רן, דותן ואלון (והופעת אורח של שלומי נוח!) באולפן הוירטואלי עם סדרה של קצרצרים מרחבי האינטרנט: הבלוגים, ה-GitHub-ים, ה-Claude-ים וה-GPT-ים החדשים מהתקופה האחרונה.

For our latest “At Work With” episode, where we talk to Pacific Northwesterners with interesting jobs and ask them your questions about what it’s like to do what they do, we bring you along as we visit a queseria where Mexican cheese is made, hit the streets at dawn with a garbage collector and meet a biologist whose job it is to protect birds at the airport.    For our “At Work With” series, let us know who you want to hear from next! You can also send us questions you have for our next “At Work With” interview. Email us at theevergreen@opb.org or visit our web page to submit questions.   For more Evergreen episodes and to share your voice with us, visit our showpage. Follow OPB on Instagram, and follow host Jenn Chávez too. You can sign up for OPB’s newsletters to get what you need in your inbox regularly.   Don’t forget to check out our many podcasts, which can be found on any of your favorite podcast apps: Timber Wars Season 2: Salmon Wars Politics Now Think Out Loud And many more! Check out our full show list here.  

In hour 1, Chris talks about Trump's rally in Green Bay where he drove a Trump branded trash truck and wore his Sanitation vest through the rally... For more coverage on the issues that matter to you, download the WMAL app, visit WMAL.com or tune in love on WMAL-FM 105.9 from 9:00am-12:00pm Monday-Friday  To join the conversation, check us out on X @WMAL and @ChrisPlanteShow Learn more about your ad choices. Visit podcastchoices.com/adchoices

Nesse episódio trouxemos as notícias e novidades do mundo da programação que nos chamaram atenção dos dias 24/08 a 30/08.

Nesse episódio trouxemos as notícias e novidades do mundo da programação que nos chamaram atenção dos dias 24/08 a 30/08.

Hailing from Sydney Australia, Dominic Di Tommaso is part of the elite team farang group of freerunners that also includes Jason Paul and Pasha Petkuns. Dom or ‘Dom tomato' as he's known, started freerunning back in 2007 following a background in ballet and figure skating and a full time job as a garbage man.From collecting bins to free running (aka parkour) Dominic has since become undoubtedly the world's most high profile parkour athlete. Dom trains with Crew 42 in Sydney Australia and has been part of team farang since 2016 - having known them for 5 years prior. He's a sponsored @redbull athlete, and has been so for the past 6 years, in this time parkour has given Dom an outlet for his passion in movement which extends well beyond the constraints of organised team sports.Dom decided a career as a garbage man was the path he would take initially until he got to point where he could become a full time athlete with a number of important sponsorships that meant he could pay his rent and jump and flip his way around the world doing more of what he loves! ________________Follow us on social media!Instagram: @normlesspodcast YouTube: www.youtube.com/@normlessFacebook: www.facebook.com/normlesspodcast/ LinkedIn: https://www.linkedin.com/company/norm...TikTok: https://www.tiktok.com/@normlesspodcastWebsite: normlesspodcast.simplecast.com________________Hayden Kelly, ESSAM, AES, AEP, MHPSHost of the NORMLESS podcastConnect with me on Instagram, Twitter, Facebook and LinkedIn ________________Want to support the show?The best way to show your support is by providing a review on the Apple Podcast app, Spotify or via our facebook page.You can also stay in the loop with the latest podcast updates, news and information by subscribing to our mailing list.

An airhacks.fm conversation with Johannes Bechberger (@parttimen3rd) about: c-control, enjoying lejos and NXT, fixing the PowerPC compiler bug, learning HTML, starting at SAP, learning Java in 2010, AMD Windows 98 machine, then a netbook with Intel Atom, fixing segmentation faults, working on real time option parser, building a real Garbage Collector with Lego, the SAP Machine, building a profiler A flame graph is the view of a tree, execution frequency and method performance, Project Panama, Project Loom and Tiny Profiler, writing ebpf.io in Java, https://mostlynerdless.de Johannes Bechberger on twitter: @parttimen3rd

Effektive Observability mit OpenTelemetryFrüher waren viele Applikationen eine Black Box, besonders für die Ops aka Betriebsabteilung. Dann fing das Logging an. Apps haben Log-Lines geschrieben, zum Beispiel wann die App fertig hochgefahren ist oder wenn etwas schief gegangen ist. In einer Art und Weise haben durch Logs die Devs angefangen, mit den Ops-Leuten zu kommunizieren.Irgendwann später gab es Metriken. Wie viel RAM verbraucht die App, wie oft wurde der Garbage Collector getriggert oder auch Business-Metriken, wie oft eine Bestellung ausgeführt wurde oder wann eine Geo- anstatt einer Text-Suche gestartet wurde.War das alles? Nein. Der neueste Hype: Traces. Eine genaue Einsicht, welchen Code-Path die App genommen hat und wie lange dieser gedauert hat inkl. aller Metadaten, die wir uns wünschen.Und wenn man dies nun alles in einen Sack packt, es gut durchschüttelt und man ein System hat, das man auf Basis dieser Daten fragen stellen kann, nennt man das Observability.Und genau da setzt das Projekt OpenTelemetry an.In dieser Episode sprechen wir mit dem Experten Severin Neumann über Observability und OpenTelemetry.Bonus: Was ist ein Sales-Engineer?**** Diese Episode wird gesponsert von www.aboutyou.de ABOUT YOU gehört zu den größten Online-Fashion Shops in Europa und ist immer auf der Suche nach Tech-Talenten - wie zum Beispiel einem (Lead) DevOps/DataOps Engineer Google Cloud Platform oder einem Lead Platform Engineer. Alle Stellen findest auch unter https://corporate.aboutyou.de/en/our-jobs ****Das schnelle Feedback zur Episode:

I've been told for a couple of years now that I'd love Katie Powner's books, so I've bought a couple, but now it's time to read it, and I think her most recent release, The Wind Blows in Sleeping Grass might just be the perfect choice for me. Listen in and see why! Note: links may be affiliate links that provide me with a small commission at no extra expense to you. What Do a Pig, a Garbage Collector, and an Elderly Woman Have in Common? I had a delightful chat with Katie Powner about writing, characters, her love of pigs, and even the Bible story about the demoniac of Gadarenes. Learning where she got the idea for a garbage-collecting prodigal and a pig named Pearl was only the highlight of the conversation. She also talked about her favorite kinds of books to read (she likes those that are still popular after the newness has worn off) and gave us recommendations for which of her books to start with based on the kind of book you're looking for. The Wind Blows in Sleeping Grass by Katie Powner For the first time in his life, Pete has everything to lose. After years of drifting, fifty-year-old Pete Ryman has settled down with his potbellied pig, Pearl, in the small Montana town of Sleeping Grass--a place he never expected to see again. It's not the life he dreamed of, but there aren't many prospects for a high-school dropout like him. Elderly widow Wilma Jacobsen carries a burden of guilt over her part in events that led to Pete leaving Sleeping Grass decades ago. Now that he's back, she's been praying for the chance to make things right, but she never expected God's answer to leave her flat on her face--literally--and up to her ears in meddling. When the younger sister Pete was separated from as a child shows up in Sleeping Grass with her eleven-year-old son, Pete is forced to face a past he buried long ago, and Wilma discovers her long-awaited chance at redemption may come at a higher cost than she's willing to pay. Learn more about Katie Powner on her WEBSITE and follow her on BookBub and GoodReads. The Wind Blows in Sleeping Grass is also available at 30% off with FREE shipping at BakerBookHouse.com Like to listen on the go? You can find Because Fiction Podcast at: Apple  Castbox  Google Play Libsyn  RSS Spotify Amazon and more!

But when I discovered Robert Gammal's book, The Garbage Collector, I learned that I had missed a huge part of the story.During a root canal procedure, the endodontist drills out the tooth's center. He then applies carcinogenic antiseptics such as phenol and formaldehyde in a futile attempt to sterilize it. Next, he fills it with a range of materials that are far from biocompatible. These toxic materials are described HERE, and all of them are considered safe and effective by the dental fraternity, the FDA, and the Therapeutic Goods Association of Australia. Any of these can pass into the brain, which is only a few inches away. Precisely filling the remaining hole where nerves went into a tooth's roots is impossible. So the dentist either leaves these open to the rest of the body or overfills it. In the past, this was often done using mercury alloys. Currently, other hazardous materials are used, but removing dead teeth with old amalgam-containing root canals is still part of any biological dentist's practice. Dr. Gammal's wrote me to say, “All root fillings leak and this gets worse over time. The other danger is that if the root canal is overfilled with toxic filling materials, it inevitably kills the bone around the end of the root. Mercury is sometimes still placed at the end of the root following the apicectomy procedure, and this is a total disaster.”Following a root canal, the tooth is no longer living but dead—it becomes a “foreign body.” A tooth is not a stone—it is human tissue. All surgeons know what happens when dead biological materials remain inside people. These are inevitably infected and spread bacteria to new locations. For example, nearly all heart attack artery blockages are infected with the same bacteria that are in the patient's mouth. Also, inflammatory diseases such as arthritis and other autoimmune conditions often go away when canal teeth are removed. Gammal editorializes:Nothing works. The whole procedure is based on illusion from beginning to end. If it were possible to sterilize the tooth, then this problem would not exist. There is a blanket denial that bacteria and toxins escape from the tooth the whole way down the length of the root, and not just through the apex. It would therefore make more sense to take the whole root out and not just the end of it. Fantasy and illusion reign in the minds of endodontists.NB: This introduction understates the harms of root canals. The rest of this post will document why they should never be performed and why they must be extracted.FOR MORE, SEE https://robertyoho.substack.com/p/259-i-thought-i-was-done-banging#detailsSupport the show

On today's episode of The Juggling Act, Mel and Sarah jump on the bandwagon and talk about the Matilda's obsession that has gripped Australia. They also chat about why Mum's act as ‘emotional garbage collectors' for their families and Mel investigates the strange character appearing in her son's nightmares. Have things to say about this episode? Join our Facebook group and share your thoughts! Want to see more of Mel and Jules? You can find them on TikTok via @thejugglingactpodcastSee omnystudio.com/listener for privacy information.

On today's episode, Chris and Andrew have an early start and catch up on their lives. Then, they dive deep into the latest developments in the Rails community, including the release of Rails 7.0.6, bug fixes, and changes to Active Record.  They share their experiences with GitHub deployments, documentation issues, and how they navigate through its challenges. They discuss the benefits of MySQL and Postgres, as well as the ongoing advancements in Postgres, specifically Crunchy Data's contributions.  Chris and Andrew share their views on working in different company sizes, the joys of learning new things, dealing with burnout, and the slower pace of feature shipping in larger companies. There's a discussion on Reddit's recent actions, its impact on subreddit moderations, and the discontinuation of the Reddit API. We'll also hear about Chris's cooking adventures, experimenting with different flavors, and making some Texas Twinkies. Hit download to hear more! [00:02:00] Chris and Andrew talk about the release of Rails v7.0.6 with bug fixes and changes in libraries like Action Cable and Active Record, including subqueries and associations with polymorphic relationships.[00:06:10] Andrew is curious about the GitHub deployment stuff and expresses his desire to create GitHub deploys from Heroku. They talk about the complexities of setting up GitHub deployments and the lack of clear information from GitHub, and how the documentation with Checks API can be confusing to set up. [00:09:49] Chris discusses the challenges of figuring out GitHub's deployment process and the lack of documentation. He expresses frustration with the lack of clarity and support for smaller accounts. [00:14:41] PlanetScale is brought up and its association with MySQL, and they discuss the benefits of MySQL and Postgres, and the new features and advancements in Postgres, including Crunchy Data's contributions and the potential use of Postgres in web environments. [00:17:43] Chris shares a fun story about working on implementing jump server support in the new Hatchbox.  They encountered unexpected complexities with the net-ssh gem to address the problem. [00:29:51] Chris emphasizes the importance of being mindful of memory usage and performance trade-offs and how it becomes more critical when building large-scale products. [00:31:59] Andrew mentions that releasing features can be challenging and Podia is currently facing that challenge with releasing a feature while also building onto it. He emphasizes the importance of coordination, communication, and learning from code to recognize and solve problems faster. [00:33:46] Chris reflects on his experience working at a consulting agency and how it allowed him to learn quickly by facing different projects and finds joy learning new things as a programmer. [00:34:43] We hear Andrew talk about feeling stuck in a job, comparing small companies which offer more challenges, to big companies where employees get stuck doing the same tasks, and Chris tells us he's happiest when learning new things and how it accelerates burnout.[00:35:57] Chris discusses the challenges faced by big companies when it comes to feature shipping due to the need to ensure existing users are not negatively impacted, and Andrew highlights the varying levels of impact when breaking code and emphasizes the importance of being able to find and fix bugs quickly. [00:39:00] We hear about Chris's mad cooking skills with pulled pork and experimenting with smoked cream cheese which he hopes to use in some Texas Twinkies. [00:43:53] The conversation shifts to Reddit and its recent actions regarding subreddit moderation and the discontinuation of the Reddit API, and they express frustration with Reddit's handling of the situation and the negative consequences it's had on the community. [00:51:30] We end with Chris needing to attend to his cooking tasks and Andrew mentions his responsibility to lead Podia in Jason and Jamie's absence.   Panelists:Chris OliverAndrew MasonSponsor:HoneybadgerLinks:Jason Charnes TwitterChris Oliver TwitterAndrew Mason TwitterRails 7.0.6 PlanetScaleCrunchy DataReddit Won't Be the Same. Neither Will the Internet (WIRED)What the Heck is a Texas Twinkie?

Les langages comme le JavaScript, le Java, le C# et bien d'autres gèrent la libération de la mémoire grâce à un mécanisme appelé le "ramasse-miettes", ou "garbage-collector" en anglais !Notes de l'épisode :Article d'origine : https://code-garage.fr/blog/comment-fonctionne-le-garbage-collector-en-javascript/Heap, primitives et références : https://code-garage.fr/blog/comprendre-les-primitives-et-les-references-en-javascript/

Untapped Potential: Dr. Thomson Fontaine's Arrest (Part 2), Plus from Garbage Collector to Harvard University

#circuitpythonparsec Check your board's free memory with the Garbage Collector. To learn about CircuitPython: https://circuitpython.org Visit the Adafruit shop online - http://www.adafruit.com ----------------------------------------- LIVE CHAT IS HERE! http://adafru.it/discord Adafruit on Instagram: https://www.instagram.com/adafruit Subscribe to Adafruit on YouTube: http://adafru.it/subscribe New tutorials on the Adafruit Learning System: http://learn.adafruit.com/ -----------------------------------------

Anil Madhavapeddy is an academic, author, engineer, entrepreneur, and OCaml aficionado. In this episode, Anil and Ron consider the evolving role of operating systems, security on the internet, and the pending arrival (at last!) of OCaml 5.0. They also discuss using Raspberry Pis to fight climate change; the programming inspiration found in British pubs and on Moroccan beaches; and the time Anil went to a party, got drunk, and woke up with a job working on the Mars Polar Lander.You can find the transcript for this episode  on our website.Some links to topics that came up in the discussion:Ron, Anil, and Jason Hickey's book, “Real World OCaml”Anil's personal website and Google Scholar pageThe MirageOS library operating systemCambridge University's OCaml LabsNASA's Mars Polar LanderThe Xen Project, home to the hypervisorThe Tezos proof-of-stake blockchainThe Coq Proof Assistant system

Links and vulnerability summaries for this episode are available at: https://dayzerosec.com/podcast/a-kernel-race-sudump-and-a-chrome-garbage-collector-bug.html We start off this week with a look at in-the-wild 0days from the past seven years, before diving into some pretty awesome bugs this week including a OOB access in Squirrel (programming language), a couple Linux kernel issues and a Chrome garbage collector bug. [00:00:22] Spot The Vuln - Just Be Positive - Solution [00:06:42] Overview of 0days seen in the wild the last 7 years [00:18:33] Squirrel Sandbox Escape allows Code Execution in Games and Cloud Services [00:29:15] SuDump: Exploiting suid binaries through the kernel [00:38:09] How a simple Linux kernel memory corruption bug can lead to complete system compromise [00:55:46] Chrome in-the-wild bug analysis [CVE-2021-37975] [01:12:40] FuzzCon Europe 2021 The DAY[0] Podcast episodes are streamed live on Twitch (@dayzerosec) twice a week: Mondays at 3:00pm Eastern (Boston) we focus on web and more bug bounty style vulnerabilities Tuesdays at 7:00pm Eastern (Boston) we focus on lower-level vulnerabilities and exploits. The Video archive can be found on our Youtube channel: https://www.youtube.com/c/dayzerosec You can also join our discord: https://discord.gg/daTxTK9 Or follow us on Twitter (@dayzerosec) to know when new releases are coming.

Willkommen zum Skillbyte-Podcast! Skillbyte ist ihr Partner für digitale Exzellenz. In diesem Podcast geht es um das Thema: Digitale Bildung in Deutschland // Inhalt // 01:55 - Historische Entwicklungen vor dem Garbage Collectors (GC) 06:55 - Der Aufstieg der Interpreter 11:20 - Der Garbage Collector übernimmt das Speichermanagement 14:33 - So arbeitet der Garbage Collector 15:39 - Tradeoff: Durchsatz vs. Latenz 20:02 - Garbage Collection im Detail 21:10 - Funktionsweise des Concurrent Mark Sweep Garbage Collectors 26:04 - Exkurs G1 Garbage First Collector 27:19 - Zusammenfassung 29:33 - Tuning String Depublication: https://blog.codecentric.de/2014/08/string-deduplication-ein-neues-feature-java-8-update-20/ Abonnieren Sie diesen Podcast und besuchen Sie uns auf https://www.skillbyte.de Feedback und Fragen gerne an podcast@skillbyte.de

Evolución de la sintaxis de Python, comunidades locales y metareferencias a las grabaciones de las tertulias https://podcast.jcea.es/python/24 Participantes: Jesús Cea, email: jcea@jcea.es, twitter: @jcea, https://blog.jcea.es/, https://www.jcea.es/. Conectando desde Madrid. Jesús, conectando desde Ferrol. Víctor Ramírez, twitter: @virako, programador python y amante de vim, conectando desde Huelva. Eduardo Castro, email: info@ecdesign.es. Conectando desde A Guarda. Gato, desde Chile. Audio editado por Pablo Gómez, twitter: @julebek. La música de la entrada y la salida es "Lightning Bugs", de Jason Shaw. Publicada en https://audionautix.com/ con licencia - Creative Commons Attribution 4.0 International License. [00:53] Volvemos a estar poquita gente. Comunidades locales en Galicia. Python Vigo: https://www.python-vigo.es/. Makerspaces: https://en.wikipedia.org/wiki/Hackerspace. GPUL: Grupo de Programadores e Usuarios de Linux: https://www.gpul.org/. [05:48] Propuesta de cambio en la sintaxis de lambda. Ventaja de la sintaxis actual: al aparecer el término "lambda", se puede buscar en Internet. El lenguaje cada vez es más opaco y complejo. [09:58] Asistencia escasa en las últimas tertulias. ¿Cómo afrontarlo? ¿Proponer temas a lo largo de la semana? [12:23] Volvemos al cambio de sintaxis de lambda. PEP 617 -- New PEG parser for CPython https://www.python.org/dev/peps/pep-0617/. [15:03] Guido van Rossum https://es.wikipedia.org/wiki/Guido_van_Rossum está apoyando muchos cambios polémicos en Python. Nominación de Pablo Galindo al Steering Council: https://discuss.python.org/t/steering-council-nomination-pablo-galindo-salgado-2021-term/5720. [16:58] ¿Python intenta seguir la estela de otros lenguajes con los que compite? PEP 617 -- New PEG parser for CPython https://www.python.org/dev/peps/pep-0617/. El parser nuevo abre muchas posibilidades peligrosas. Lista de correo de Python-ideas: https://mail.python.org/mailman3/lists/python-ideas.python.org/. [23:38] ¿Dónde se almacenan los valores por defecto de los parámetros de una función? Librerías para procesar y generar bytecode https://es.wikipedia.org/wiki/Bytecode python. Ejemplo: simplificar la sintaxis de meter código ensamblador desde Python. Decoradores que manipulan las tripas de las funciones, a nivel de bytecode https://es.wikipedia.org/wiki/Bytecode. Módulo "dis" https://docs.python.org/3/library/dis.html. import dis >>> def a(): ... return 5 ... >>> dis.dis(a) 2 0 LOAD_CONST 1 (5) 2 RETURN_VALUE [30:13] Cómo mezclar código síncrono y asíncrono, en función del tipo de función que te llama. inspect.iscoroutinefunction(object): https://docs.python.org/3/library/inspect.html#inspect.iscoroutinefunction. inspect.iscoroutine(object): https://docs.python.org/3/library/inspect.html#inspect.iscoroutine. inspect.isawaitable(object): https://docs.python.org/3/library/inspect.html#inspect.isawaitable. inspect.isasyncgenfunction(object): https://docs.python.org/3/library/inspect.html#inspect.isasyncgenfunction. inspect.isasyncgen(object): https://docs.python.org/3/library/inspect.html. [32:03] Bibliotecas con "plugins". Namespaces: PEP 420 -- Implicit Namespace Packages https://www.python.org/dev/peps/pep-0420/. Problemas con el "modo desarrollo" del paquete. PEP 402 -- Simplified Package Layout and Partitioning: https://www.python.org/dev/peps/pep-0402/. Este PEP se rechazó. PEP 382 -- Namespace Packages https://www.python.org/dev/peps/pep-0382/. Ficheros pth: https://docs.python.org/3/library/site.html. [42:21] Charla Python Madrid: Python Packaging: Lo estás haciendo mal https://www.youtube.com/watch?v=OeOtIEDFr4Y. Buenas prácticas actuales. Se puso como deberes futuros. [45:11] Metareferencia: Podcast: Python en español: https://podcast.jcea.es/python/. Notas y capítulos para poder navegar por las grabaciones. Temas pendientes para poder publicar los audios. Biblioteca toc2audio: https://docs.jcea.es/toc2audio/. MP3 https://es.wikipedia.org/wiki/Mp3 en formato VBR https://es.wikipedia.org/wiki/Tasa_de_bits_variable. ¿Dónde colgar las grabaciones? ¿Secuestrar y resucitar el podcast "Python en español": https://podcast.jcea.es/python/? Zope: https://es.wikipedia.org/wiki/Zope. [51:33] Temas Django https://www.djangoproject.com/: Consultas complejas usando el ORM https://es.wikipedia.org/wiki/Asignaci%C3%B3n_objeto-relacional. SQL: https://es.wikipedia.org/wiki/SQL. Postgresql: https://www.postgresql.org/. MySQL: https://www.mysql.com/. MariaDB: https://mariadb.org/. [55:38] Novedades Python 3.10: PEP 622 -- Structural Pattern Matching https://www.python.org/dev/peps/pep-0622/. PEP 634 -- Structural Pattern Matching: Specification https://www.python.org/dev/peps/pep-0634/. PEP 635 -- Structural Pattern Matching: Motivation and Rationale https://www.python.org/dev/peps/pep-0635/. PEP 636 -- Structural Pattern Matching: Tutorial https://www.python.org/dev/peps/pep-0636/. ¿Deberes futuros? What the f*ck Python! https://github.com/satwikkansal/wtfpython Docker: https://en.wikipedia.org/wiki/Docker_(software). [01:02:18] Podcast: Python Bytes: https://pythonbytes.fm/. Hablar de las cosas habiéndolas probado. Real Python https://realpython.com/. No hay contenido comparable en español. [01:05:08] Traducción de la documentación Python al español: Documentación Python en Español: https://docs.python.org/es/3/. Documentación oficial de Python en español https://pyar.discourse.group/t/documentacion-oficial-de-python-en-espanol/238/23. GitHub: https://github.com/python/python-docs-es/. Documentación oficial de Python en Español https://elblogdehumitos.com/posts/documentacion-oficial-de-python-en-espanol/. docs.python.org en Español https://elblogdehumitos.com/posts/docspythonorg-en-espanol/. [01:06:43] Tutorial de Python en español: https://docs.python.org/es/3/tutorial/index.html. [01:07:08] Python España: Aprende Python https://www.es.python.org/pages/aprende-python.html. Parece abandonado. [01:07:43] Eventos Python en España: http://calendario.es.python.org/. Costaba mucho que la gente avisase de los eventos. Al final había que estar en todas partes y poner mucha oreja. [01:09:03] Automatizaciones de seguimientos. [01:09:43] La dificultar para crear comunidad. [01:10:38] Iniciativa de comunidades tecnológicas de Madrid. Problemas comunes de los organizadores: conseguir ponentes, reservar locales, conseguir subvenciones, gente que se apunta y luego no acude, etc. Calendario de actividades tecnológicas en Madrid. [01:13:18] Python para desarrollar herramientas de sonido. Latencia. PulseAudio: https://es.wikipedia.org/wiki/PulseAudio. Instrumentos VST: https://es.wikipedia.org/wiki/Virtual_Studio_Technology. Jesús Cea ha escrito software de control de una emisora de radio. Detalles. Ojo con el sistema de recogida de basuras. gc — Garbage Collector interface: https://docs.python.org/3/library/gc.html. [01:19:43] Capítulos en podcasts. Más detalles sobre el "workflow" de edición de sonido. Biblioteca: https://docs.jcea.es/toc2audio/. rnnoise: https://jmvalin.ca/demo/rnnoise/. [01:22:53] Despedida. Experimento con deberes para poder tratar temas profundos habiéndolos visto con anterioridad. [01:24:18] Final.

Anotaciones de tipos: ¿Son pythónicas? También versiones de paquetes y grafos de dependencias https://podcast.jcea.es/python/18 En este audio hay un hablante que no identifico. ¿Quien es?. Es quien habla, por ejemplo, en 01:06:00 o en 01:12:00. ¿Antoni? Participantes: Jesús Cea, email: jcea@jcea.es, twitter: @jcea, https://blog.jcea.es/, https://www.jcea.es/. Conectando desde Madrid. Víctor Ramírez, twitter: @virako, programador python y amante de vim, conectando desde Huelva. Dani, conectando desde Málaga. Eduardo Castro, email: info@ecdesign.es. Conectando desde A Guarda. Audio editado por Pablo Gómez, twitter: @julebek. La música de la entrada y la salida es "Lightning Bugs", de Jason Shaw. Publicada en https://audionautix.com/ con licencia - Creative Commons Attribution 4.0 International License. [00:52] Preámbulo. Design of CPython’s Garbage Collector: https://devguide.python.org/garbage_collector/. Dificultades con el horario de la tertulia. Podría haber más tertulias en otros horarios, llevadas por otras personas. Problemas para publicar los audios. Editar es un infierno. Las notas de los audios tienen una importancia transcendental. Dinámica de las tertulias. Antiguo podcast "Python en español": https://podcast.jcea.es/python/. [08:32] Presentaciones. Raspberry Pi Pico: https://www.raspberrypi.org/products/raspberry-pi-pico/. Micropython: https://www.micropython.org/. [13:32] El aviso legal para poder grabar los audios. [14:32] Bugs sobre "pickle" https://docs.python.org/3/library/pickle.html en el módulo __main__. Se trata de un problema conocido. Ejemplo de código: https://pastebin.com/vGM1sh8r. Issue24676: Error in pickle using cProfile https://bugs.python.org/issue24676. Issue9914: trace/profile conflict with the use of sys.modules[__name__] https://bugs.python.org/issue9914. Issue9325: Add an option to pdb/trace/profile to run library module as a script https://bugs.python.org/issue9325. [16:27] Lo importante que es abrir bugs, para que puedan solucionarse. Queja productiva. [18:12] Nueva versión de MYPY http://mypy-lang.org/ y MYPYC https://github.com/mypyc/mypyc, que aprovechan Python 3.9. Sigue fallando mucho. [20:42] pyannotate https://pypi.org/project/pyannotate/ para meter anotaciones de tipos de forma automática. Las dificultades de meter tipos en un proyecto ya maduro. [22:52] Puedes usar tipos o no. Son opcionales. Ventajas en equipos grandes. Linter: https://es.wikipedia.org/wiki/Lint. Impone disciplina y una cultura. Las anotaciones de tipos no se verifican en tiempo de ejecución. Se usan en el sistema de test e integración continua. Una de la ventaja de los "__slots__" es que si te equivocas en el nombre de atributo en una asignación, te dará un error claro. Los tipos ayudan aquí también. "pyannotate" https://pypi.org/project/pyannotate/. Las anotaciones de tipos te permiten luego compilar Python para ganar rendimiento "sin coste". Las anotaciones se pueden meter en el mismo código o en un fichero "compañero". Usar un fichero "compañero" es útil para poder usar anotaciones modernas en versiones antiguas de Python. Evitar "contaminar" el sistema de control de versiones con cambios masivos irrelevantes que ofuscan la historia de un proyecto. Por ejemplo, el autor original del código. Que los creadores de código y los etiquetadores de tipos sean personas diferentes. "typeshed": Collection of library stubs for Python, with static types: https://github.com/python/typeshed. ¿Y meter tipos en los comentarios, como se hacía antiguamente? Hay mucha literatura de ingeniería de software sobre si es bueno documentar tipos o no, según el tipo de equipo y el tipo de proyecto. [40:17] Python podría ser mucho más rápido aunque no se usen tipos. Podría ser mucho más inteligente. Descubrimiento de tipos en tiempo de ejecución. Tema recurrente. Numba: https://numba.pydata.org/. Javascript V8: https://en.wikipedia.org/wiki/V8_(JavaScript_engine). [43:06] Habiendo tantos compiladores, ¿por qué no se integra alguno en el intérprete normal de Python? Complejidad y compatibilidad. Faltan manos. Hay muchos "gérmenes" que no germinan. Dispersión de esfuerzos. [46:12] Puntos de dolor de Python para la gente que viene de otros lenguajes: Tipos. Velocidad. Espacios significantes. [46:37] ¿Qué es "Python"? Cada novedad de sintaxis de Python cambia el lenguaje. ¿Qué es Python? Problemas para los que llegan nuevos al lenguaje. Hay organizaciones grandes que un lenguaje sin tipos ni siquiera lo consideran. [51:22] Cultura común en todos los proyectos Python. Baja barrera de entrada si conoces esa cultura. La cultura va evolucionando. Solución de compromiso: Meter tipos solo en la frontera. [53:02] El tipado avanzado de Python 3.9 da un error de sintaxis al importar el código en una versión anterior de Python. [54:46] El operador morsa no se puede usar dentro de un "list comprehension": >>> [i for i in ('a', '' ,'b') if i := i.strip()] File "", line 1 [i for i in ('a', '' ,'b') if i := i.strip()] ^ SyntaxError: invalid syntax No queda otra que escribirlo como: >>> [i.strip() for i in ('a', '' ,'b') if i.strip()] ['a', 'b'] duplicando el i.strip(). [56:40] En versiones de Python anteriores a 3.8 no se podría usar un continue en un finally. El texto era https://docs.python.org/3.7/reference/compound_stmts.html#the-try-statement: When a return, break or continue statement is executed in the try suite of a try...finally statement, the finally clause is also executed ‘on the way out.’ A continue statement is illegal in the finally clause. (The reason is a problem with the current implementation — this restriction may be lifted in the future). Eso se solucionó en Issue32489: Allow 'continue' in 'finally' clause: https://bugs.python.org/issue32489. [57:47] f-string con datetime https://docs.python.org/3/library/datetime.html. Ya está en los propios ejemplos de PEP 498: Literal String Interpolation: https://www.python.org/dev/peps/pep-0498/. [59:22] Modo depuración en f-strings en Python 3.8: >>> a = 5 >>> f'{a=}' 'a=5' Útil para el loging. [01:00:47] Versiones fijas de dependencias y actualizar un despliegue. Herramientas para esto: "pip" https://pypi.org/project/pip/, "virtualenv" https://pypi.org/project/virtualenv/. "pipenv" https://pypi.org/project/pipenv/. "Poetry": https://pypi.org/project/poetry/. Grafo de dependencias "pip-tree": https://pypi.org/project/pip-tree/. Paralelismos con el enlazado estático y dinámico. [01:14:22] ¿Por qué se ha instalado este paquete, qué paquetes exige y qué paquetes dependen de él? pip show. Grafo de dependencias "pip-tree": https://pypi.org/project/pip-tree/. [01:19:22] Visualizar el grafo de versiones de un sistema de control de versiones moderno. Por ejemplo con Mercurial: "hg glog" https://www.mercurial-scm.org/. [01:23:07] Recogida de basuras: Design of CPython’s Garbage Collector: https://devguide.python.org/garbage_collector/. Hora de sacar la basura garbage collector - Pablo Galindo y Victor Terrón - PyConES 2018 https://www.youtube.com/watch?v=G9wOSExzs5g. La recolección de basura de la generación más antigua funciona de forma diferente. En vez de ser por un número fijo de desequilibrio entre creación y destrucción de objetos, funciona por porcentaje. [01:31:37] Divagación: Powerball https://powerball.org.uk/. [01:31:52] Explicación de cómo funciona "__slots__" https://docs.python.org/3/reference/datamodel.html. [01:34:22] Libro "CPython Internals": https://realpython.com/products/cpython-internals-book/. Website de "Real Python": https://realpython.com/. Merece bastante la pena. También tienen podcast: "The Real Python Podcast: Python Tips, Interviews, and More" https://realpython.com/podcasts/rpp/. [01:36:42] Más sobre "__slots__" https://docs.python.org/3/reference/datamodel.html. Técnica estándar. Un diccionario vacío ocupa 64 bytes: sys.getsizeof({}). Se puede usar para evitar errores mecanográficos al escribir en atributos. [01:38:52] "AutoScraper: A Smart, Automatic, Fast and Lightweight Web Scraper for Python" https://pypi.org/project/autoscraper/. Búsquedas "borrosas". Seguimos sin encontrar la biblioteca de scraping de foros de la que ha hablado Eduardo en tertulias anteriores. [01:43:02] Librería para dibujar grafos: graphviz https://pypi.org/project/graphviz/. Le das un texto describiendo nodos y conexiones entre nodos y calcula un gráfico. Sería trivial para dibujar el grafo de dependencias de "pip". Ejemplo: El gráfico de antes, con ciclos: https://lists.es.python.org/pipermail/general/attachments/20201229/0c14bc58/attachment-0002.png. El gráfico de después, sin ciclos: https://lists.es.python.org/pipermail/general/attachments/20201229/0c14bc58/attachment-0003.png. [01:47:22] ¿Cómo asegurarse que el nombre de un fichero no tenga caracteres extraños? ¡Problema de seguridad! Expresiones regulares. Cuidado con el unicode https://en.wikipedia.org/wiki/Unicode. Mejor usar una lista blanca que una lista negra. Usar pathlib.is_relative_to() https://docs.python.org/3/library/pathlib.html#pathlib.PurePath.is_relative_to. Novedad en Python 3.9. [01:52:07] ¡Usa la versión actual de Python, leches! Ahora mismo, Python 3.9. Ventajas de compilar el intérprete desde código fuente para no depender de la versión que te proporciona el sistema operativo. Puedes tener tu propio intérprete de Python dentro de un "virtualenv" https://pypi.org/project/virtualenv/. Proyectos "llave en mano". El cliente quiere algo que se instale como un componente en lo que ya conoce. Por ejemplo, en un panel de configuración en un servicio de hospedaje. [01:56:47] Jesús Cea repite una vez más la anécdota de que al principio de los tiempos para conducir un coche tenías que ser mecánico, pero ya no. Falta toda la base, pero... ¿Hace falta? [01:59:12] Memoria escasa en un microcontrolador. [01:59:55] Final.

Eduardo Castro se desata y nos invita a comentar trucos y construcciones idiomáticas no evidentes https://podcast.jcea.es/python/17 Participantes: Jesús Cea, email: jcea@jcea.es, twitter: @jcea, https://blog.jcea.es/, https://www.jcea.es/. Conectando desde Madrid. Eduardo Castro, email: info@ecdesign.es. Conectando desde A Guarda. Javier, conectando desde Madrid. Víctor Ramírez, twitter: @virako, programador python y amante de vim, conectando desde Huelva. Dani, conectando desde Málaga. Miguel Sánchez, email: msanchez@uninet.edu, conectando desde Canarias. Jorge Rúa, conectando desde Vigo. Audio editado por Pablo Gómez, twitter: @julebek. La música de la entrada y la salida es "Lightning Bugs", de Jason Shaw. Publicada en https://audionautix.com/ con licencia - Creative Commons Attribution 4.0 International License. [00:52] Haciendo tiempo hasta que entre más gente. Raspberry Pi Pico: https://www.raspberrypi.org/products/raspberry-pi-pico/. Jesús Cea está encantado con su rango de alimentación. Micropython: https://www.micropython.org/. [06:02] Truco: Python -i: Ejecuta un script y pasa a modo interactivo. También se puede hacer desde el propio código con code.InteractiveConsole(locals=globals()).interact(). Jesús Cea se queja de que usando la invocación desde código no funciona la edición de líneas. Javier da la pista correcta: para que funcione, basta con hacer import readline antes de lanzar el modo interactivo. [11:17] Regresión con ipdb: https://pypi.org/project/ipdb/. [12:37] Nueva versión de Pyston https://www.pyston.org/. Intérprete de Python más rápido. Un 50% más rápido que cpython. [16:22] Ver si dos fechas son iguales con datetime https://docs.python.org/3/library/datetime.html. Trabajar siempre en UTC https://es.wikipedia.org/wiki/Tiempo_universal_coordinado, aunque solo tengas una zona horaria. [19:52] Jesús Cea ha investigado cómo funcionan los POSTs HTTP en las protecciones CSRF https://es.wikipedia.org/wiki/CSRF. Buena práctica: La respuesta al POST es una redirección a un GET. Patrón Post/Redirect/Get (PRG) https://es.wikipedia.org/wiki/Post/Redirect/Get. Ventajas de usar un framework. [24:32] ¿Optimizaciones cuando tienes grandes cantidades de datos? Tema muy amplio, hacen falta detalles del problema. Se ofrecen algunas ideas: Map/Reduce: https://en.wikipedia.org/wiki/Map_reduce. Usar generadores u otras construcciones "lazy" siempre que sea posible. https://wiki.python.org/moin/Generators. [31:52] Gestión de memoria en Python. Design of CPython’s Garbage Collector: https://devguide.python.org/garbage_collector/. Hora de sacar la basura garbage collector - Pablo Galindo y Victor Terrón - PyConES 2018 https://www.youtube.com/watch?v=G9wOSExzs5g. [35:17] Tipografía para programadores: Victor Mono: https://rubjo.github.io/victor-mono/. Fira Code: https://fonts.google.com/specimen/Fira+Code. Fira Code Retina: https://github.com/tonsky/FiraCode/issues/872. [37:17] Eduardo Castro se ha currado una lista de trucos sencillos pero interesantes: En estas notas solo referenciamos los puntos a los que dedicamos más tiempo, se habló de más cosas. El documento para poder seguir los comentarios de la grabación está en https://demo.hedgedoc.org/s/hEZB92q40#. hash(float('inf')) -> 314159. [43:02] LRU Caché: "blame". [01:33:57] Usos de lambda. Módulo Operator: https://docs.python.org/3/library/operator.html. [01:35:52] Algunos trucos cortos adicionales. collections.deque: https://docs.python.org/3/library/collections.html. dateutil: https://pypi.org/project/python-dateutil/. itertools: https://docs.python.org/3/library/itertools.html. if a < x < b: >>> import dis >>> dis.dis(lambda x: a < x < b) 1 0 LOAD_GLOBAL 0 (a) 2 LOAD_FAST 0 (x) 4 DUP_TOP 6 ROT_THREE 8 COMPARE_OP 0 ( 18 ROT_TWO 20 POP_TOP 22 RETURN_VALUE Desempaquetado complejo: >>> a, b, (c, d), *e, f = 1, 2, (3, 4), 5, 6, 7, 8, 9 >>> print(a,b,c,d,e,f) 1 2 3 4 [5, 6, 7, 8] 9 Usar la variable "guión bajo" para descartar valores. Ojo con la internacionalización. [01:56:22] Python cada vez tiene más "gotchas". Algunos ejemplos: Operador morsa. Tratado con projilidad en tertulias anteriores. Parámetros mutables. Definir "closures" dentro de un for pero usarlo fuera. Tuplas con un solo elemento. Es más evidente el constructor tuple(), pero ojo: tuple('abc') -> ('a', 'b', 'c'). [02:01:06] ¡Terminamos con los trucos! [02:01:37] Ideas para indexar y buscar el documentos: Whoosh: https://whoosh.readthedocs.io/en/latest/intro.html. Solr: https://solr.apache.org/. [02:04:22] Deberes para el futuro: módulos dis https://docs.python.org/3/library/dis.html y enum https://docs.python.org/3/library/enum.html. [02:04:47] Sugerencia sobre visión artificial: https://www.pyimagesearch.com/. De lo mejor que hay. [02:06:47] regex https://pypi.org/project/regex/ que libera el GIL https://en.wikipedia.org/wiki/Global_interpreter_lock. [02:07:47] Acelerador y distribución de programas Python precompilados en binario y empaquetados en un directorio e, incluso, en un único fichero: Nuitka: https://nuitka.net/. [02:08:57] Design of CPython’s Garbage Collector: https://devguide.python.org/garbage_collector/. [02:09:17] Cierre. [02:10:52] Casi se nos olvida el aviso legal para grabar y publicar las sesiones. [02:12:55] Final.

I often bring a garbage bag with me on my Hook Mountain walks. I can’t stand to see trash on the trails, so I feel compelled to do my part to clean up the garbage along the way. I unpack some associations and metaphors that come to mind while collecting garbage. Garbage collectors were important to Martin Luther King, Jr. and the civil rights movement. Garbage collectors have been critical in nationally exposing and highlighting the abuses, non-unionized, low-paying jobs and dangerous working conditions that too many people have suffered under. MLK brought the garbage collectors’ plight into our consciousness, cared about them being treated with dignity and respect. Picking up and clearing garbage, has become a spiritual practice for me. It is a minuscule step in what truly needs to be done to address advocacy for our precious earth, but I feel cleansed, renewed and grateful for this simple measure to clean up garbage, outwardly and inwardly! May you be inspired to clean up your surroundings. May you treat nature with awe, reverence and wonder. May we learn multiple ways to be our planet’s fierce advocate. Check out the show notes to listen and re-listen to the powerful words of Greta Thunberg for the bigger picture task at hand. Enjoy the podcast! Links: Greta Thunberg on YouTube Greta Thunberg on Instagram

Join our solo RPG live session while we explore an asteroid belt in search of some space garbage. Seems an easy task, innit? But anything can happen when randomness comes to play! :) Support FMX™ https://horoscopezine.itch.io/fmx Traveling deep space https://youtu.be/TtlgB7Sv2uQ Delta Base https://youtu.be/5SjG19NZXDk HEX™ https://youtu.be/XbHXrHVwa-Y Join our Discord server https://discord.gg/RvGKvfuSpH Subscribe to our Youtube channel https://www.youtube.com/channel/UCIitO5WUBqXWI4NvQolqUMQ/videos Like us on Facebook https://www.facebook.com/horoscopezine Follow us on Instagram too :D https://www.instagram.com/horoscopezine

Normally I'd start this out with some of the funnier things that happened; but before I dive into what happened last week, I want to talk about this week. Warning: death and violence follow. Yesterday was the 31st anniversary of the École Polytechnique massacre. If you're not familiar with this atrocity, let me quote Deb Chachra's chilling telling of the event:  On December 6, 1989, in late afternoon a man had walked into the École Polytechnique, the engineering school of the University of Montreal, carrying a hunting rifle, ammunition, and a knife. He entered a mechanical engineering class of about sixty students, separated out the nine women, and told them, "I am fighting feminism." One of the women, Nathalie Provost, responded, "Look, we are just women studying engineering, not necessarily feminists ready to march on the streets to shout we are against men, just students intent on leading a normal life." She reports that his response was, "You're women, you're going to be engineers. You're all a bunch of feminists. I hate feminists."He then opened fire on the women, killing six of them. Then he went from floor to floor in the building, targeting and shooting women.Fourteen women were killed that day, twelve of them engineering students, one a nursing student, and one a university employee.Here are their names: Anne St-Arneault, Geneviève Bergeron, Hélène Colgan, Nathalie Crotea, Barbara Daigneault, Anne-Marie Edward, Maud Haviernick, Barbara Klueznick, Maryse Laganière, Maryse Leclair, Anne-Marie Lemay, Sonia Pelletier, Michèle Richard, and Annie Turcotte. (Me: You can hear more about these women here.)An additional thirteen people were injured. Nathalie Provost was shot four times, but survived. In the weeks, months, and years that followed, among other responses, Canada implemented stricter gun-control regulations, and began to observe December 6th as a National Day of Remembrance and Action on Violence Against Women. The event remains the worst mass murder in Canadian history.Our industry has problems with sexism, whether latent or outright. While we hope never to have another atrocity like this one; we should strive for equality and justice in our industry. As a white dude in tech, I'll do everything I can; and I ask you to do the same. If you've never had to fear for your life just because you wanted to be an engineer, then you too need to stand up and help stop the sexism in our industry. Now, on to what happened last week in the world of .NET. 

In this episode, David Delabassee (Developer Relations) discusses with Per Liden (ZGC Lead) the Z Garbage Collector that is now production ready in JDK 15.

JetBrains опубликовали планы по релизу новых версий Kotlin и рассказали что у них в приоритетах на ближайшее время. Всё, начиная от поддержки возможностей новых JVM до багфиксинга и нового синтаксиса - мы обсудили.Также бонусом мы попали на статью о Kotlin DSL, которая нам не понравилась, но зато дала возможность обсудить зачем вообще нужен DSL и как делать неправильно, а также действительно ли нужно переходить с Groovy на Kotlin для gradle.00:00:30 - Kotlin Roadmap00:40:56 - Kotlin DSL: Gradle scripts in Android made easyКомментарии и пожелания можно оставлять в нашем телеграмм чате.

Rehan Staton, a 24-year-old college student who previously worked as a garbage collector, was accepted to Harvard Law School. Born and raised in Maryland, Staton had a difficult life growing up. At one point, his father, who was his family's sole provider, worked three jobs at once to make ends meet. Because of the difficulties his family faced, Staton struggled with his academic performance in elementary school. However, he eventually excelled and became one of the top students after getting help from a tutor his father met. When he was in high school, Staton focused on boxing and dreamed of becoming a professional athlete. However, his hopes were dashed because of a shoulder injury. Instead of continuing his studies, he decided to work as a garbage collector after graduating from high school. He said that he wanted to do it to help his father pay for bills and other household expenses. A higher-up from Staton's work heard about his story and helped him enroll at Bowie State University. Two years later, he transferred to the University of Maryland. After graduating in 2018, Staton became an analyst at a consulting firm. He eventually decided to pursue law and was accepted into Harvard Law School. Staton said that he could not have made it without his support system. Having his family and coworkers by his side inspired him to give his all and pursue his dreams. He will attend Harvard Law School this fall. To help with his expenses, a fundraiser has been set up.

“Rust hat alle Vorteile von Go, PHP, C und JavaScript und ist dazu noch typsicherer als alle anderen Sprachen,” sagt Matthias Endler, ein waschechter Rustacean, den wir in Folge 49 zu Gast haben!Rust ist eine Programmiersprache, die vor allem auf Performance und Sicherheit ausgelegt ist. Während sie systemnah ist und leistungsstarke Abstraktionen bietet, die stark an dynamische Sprachen wie Ruby oder Python erinnern, hat sie außerdem eine Speichersicherheit ohne Garbage Collector auf Lager! So macht sie die Low-Level-Programmierung einfacher und sicherer.In Folge 49 plaudern wir mit Matthias Endler über die Vorzüge der Programmiersprache. Er erzählt, dass der Code tatsächlich lauffähig sei, wenn der Compiler das sagt, und dass in Rust geschriebene Services monatelang problemfrei laufen können! Diese Vorteile hören wir uns genauer an und sprechen dabei auch über Plug-ins, die man mit Rust in anderen Sprachen einbinden kann, grundsätzliche Konzepte wie Borrowing und Ownership, und wie Rust auf CDN Edges mit WebAssembly ausgeführt werden kann.Pssst! Wir haben gehört, dass die Programmiersprache sogar von SpaceX verwendet wird… Na, wenn das mal nicht ein Reinhören wert ist! ;)Wenn ihr Lust habt, Matthias zu treffen und beim Thema Rust auf dem Laufenden zu bleiben, besucht doch das nächste Meetup von Rust Cologne in Köln! Unbedingt empfehlenswert findet Matthias außerdem Aerorust, die Working Group von Rust und Aerospace.Picks of the DayFabi: Dynamo für MacOS – als Extension für Safari nutzen und effizient Werbung skippen!Lesenswerter Artikel zu Actix Web postmortem von Nikolay Kim, 17.01.2020.Matthias: PICO-8 – ein Emulator, mit dem man eigene 8-Bit-Spiele basteln kann!Schreibt uns!Schickt uns eure Themenwünsche und euer Feedback.podcast@programmier.barFolgt uns!Bleibt auf dem Laufenden über zukünftige Folgen und Meetups und beteiligt euch an Community-Diskussionen.TwitterInstagramFacebookBesucht uns!Erfahrt hier, wann das nächste Meetup in unserem Office in Bad Nauheim stattfindet.MeetupMusik: Hanimo

There are tens of thousands of pieces of space debris orbiting the Earth. We've tried a few different ways to bring them back down over the years. Plus: in Huddleston, Virginia, a giant hay sculpture of a country music legend. Meet Will-hay Nelson! ESA commissions world’s first space debris removal (European Space Agency) To Clean Up Space Junk, Some People Grabbed a Net and Harpoon (Wired) 'Will-Hay Nelson' creation at Virginia farm going viral (WSET) Put Cool Weird Awesome on the road again as a backer on Patreon! --- Send in a voice message: https://anchor.fm/coolweirdawesome/message

O Garbage Collector é um importante componente que a maioria dos runtimes modernos possuem e como eles funcionam no background e funcionam bem, cada vez menos as pessoas sabem da sua existencia ou se preocupam em enteder a sua utilidade. Um arquiteto se soluções precisa entender como as coisas funcionam para dar boas soluções e por isso este componente faz toda a diferença.

Every time we get to talk about an open-source project on our podcast, we couldn't be happier. This episode we have Marc to talk about Hermes, an open-source JavaScript engine, optimised for running React Native apps on Android. You can listen to Marc explain why it was necessary to build a JavaScript engine to support the needs of a particular framework and get a glimpse of the architecture and the design decisions behind it. Tune in now for episode 17! Please do send us feedback! You can reach us via email mobilepodcasts@fb.com, Twitter (@insidefbmobile) or Instagram (insidefbmobile). Topics Discussed Hermes: https://hermesengine.dev/ React Native: https://facebook.github.io/react-native/docs/hermes Timestamps Intro 00:05 Interview: Marc 00:57 Hermes Overview 02:25 Design Tradeoffs 07:01 Garbage Collector 11:56 Feature Omissions 15:36 Hermes Technical Design 17:35 Developer Experience 19:23 What's Next? 20:15 Using Hermes Without RN 21:32 Outro 22:28 Bloopers 00:25:50

It's Episode 421 and I've got plugins for Migrating WordPress, Garbage Collection, Database Cleaning, and ClassicPress Options. It's all coming up on WordPress Plugins A-Z! For more articles visit WordPress Specialist with a focus on... - WordPress Training, Classes and Emergency Support... for more articles like All-in-One WP Migration Google Drive Extension, Plugins Garbage Collector, Advanced Database Cleaner, and ClassicPress options in Episode 421.

Interesują Cię tematy wydajnościowe, optymalizacji pamięci czy jak działa Garbage Collector w JVM, .NET czy Rust? W tym odcinku mój gość Konrad Kokosa wyjaśnia te i inne powiązane pojęcia. Od dobrych kilku lat jego specjalizacją jest rozwiązywanie problemów wydajności, zagadki diagnostyczne i łamigłówki architektury w świecie .NET. Jest niezależnym konsultantem, prelegentem, blogerem. Notatki do odcinka znajdziesz na https://devsession.pl Serdecznie zapraszam do wysłuchania rozmowy i podzielenia się nią w mediach społecznościowych! Bardzo ważny jest dla mnie feedback i wsparcie podcastu! Dlatego zostaw proszę recenzję na iTunes, podziel się informacją o tym odcinku w mediach społecznościowych czy polub FanPage Devsession. Pozdrawiam Grzegorz Kotfis    

1. First, let's make sure you don't have an agreement with someone that they bring home all their homework for you to do...cause that ain't cool.  You're not broken or busted, you have an unhealthy agreement with someone who lacks self-responsibility. 2. People that sincerely come to you with their heartache, know you are a safe space, and often don't need much more than a listening ear.  Make sure you remind yourself there's nothing else to be done, but love em.  That's more than enough. rebeccagarifo.com with love and joy- Rebecca Garifo Ph.D.

Panel: Charles Max Wood Guest: Nell Shamrell-Harrington This week on My Ruby Story, Chuck talks with Nell who is a principle engineer at Chef. Check them out at Chef.Io. She also works with Operation Code. This organization helps veterans to learn code, and helps them get a technical job. Check out today’s episode where Chuck and Nell discuss Ruby, Rust, and much more! In particular, we dive pretty deep on: 2:00 – Chuck: Episode 105 is another episode you’ve been on before. 2:25 – Chuck: I want to spotlight you and talk about what you are working on. How did you get into programming? 2:38 – Nell: I was a theater major in college. I graduated in 2007 and the big financial crisis hit in 2008. I found work at the Physics Department in Seattle. Once they found out that I knew how to code, they gave me more coding to do. When you are doing just the mathematics portion – you don’t see how this applies to real life. I didn’t pursue it because I didn’t see how it worked in the real world. Then I saw eventually how my theater background really helped me with coding because you have to be super creative. After that (this is when I got into Ruby) my roommate in college sent me a message. She was working with Ruby, too, and she wanted to bring me on as a junior developer. 5:55 – Chuck: It’s interesting, too, to see what you just said. Not seeing the real-world application with some of that stuff. I can relate to that. I wanted to get into IT after college. The other thing is that it was someone you KNEW to get you into Ruby. People get into a specific framework because of someone that they knew/know. 6:54 – Nell: Yes, it’s the personal testimonies that help people make those decisions. 7:13 – Chuck: It was someone that you KNEW that helped you get X job. 7:24 – Nell: Yes, in Operation Code, too. Take a look at this candidate (normally you wouldn’t look at them b/c of their CV) and take a chance on them. 8:09 – Chuck: One thing that I am curious about what’s been your favorite thing to work on with Ruby? 8:38 – Nell: I worked on the supermarket product. Cookbook is a chef recipe for infrastructure... We weren’t just running a site that people were using. They were saying: we love it, but we are behind a firewall. They couldn’t use the public one and they wanted a private one. The answer was: Yes! That was the first time I worked on software – packaged and distributed. I loved the breadth of the industries that it had an affect on. It was cool to see different industries use my work through a Ruby on Rails application. Ruby does scale! 10:42 – Chuck: Let’s talk about your work at Chef. You worked on Supermarket and then what was the distributed part to it? 11:05 – Nell: Chef Omnibus was the tool we used. You could take that package and install it on the infrastructure... 11:33 – Chuck: I worked at a university for a while. The work I did was that the access to the Internet was limited. Chef would have been nice! 11:58 – Chuck: What did you do at Blue Box? 11:59 – Nell: Software engineer there and we were a hosting company. We had a Rails application... I helped write the code. 12:29 – Chuck: What are you working on now? 12:32 – Nell: I am working on a project called Habitat. Nell talks about what THIS project is and how it functions. Check it out! 14:20 – Chuck: How did you get into Operation Code? 14:26 – Nell: Both my parents were air force operators. I wanted to but I had a physical limitation so I couldn’t. I grew up in military culture from 0-14 years old. After that I realized in my 20’s I really missed it. After the military it’s scary because you don’t have (maybe) a sense of purpose like you did in the military. She asked how she could help and someone referred her to Operation Code. She realized she could be an asset and help these veterans. She works with close to 3,000 veterans to help them give a purpose after military life. They learn code and then hopefully find a technical job. 17:13 – Chuck: I spent some years around that life, too, when I was a missionary overseas. My brother-in-law was medically discharged. You see this change and it can be scary for them. You wind up in this position and you want to help. I admire this. These folks have sacrificed for us so let’s make a difference for them, too. 18:35 – Nell: My friend said that she didn’t like it when people thanked her for her service. She said that so many warzones it seems empty. When she heard this it was powerful to her. 19:40 – Chuck: How can people get involved? 19:43 – Nell: Operation Code – Hit the JOIN link. You can sign-up to be a volunteer. The slack community is where all the magic happens.  20:24 – Chuck: Anything else? 20:28 – Nell: Habitat is written in Rust. I haven’t done tons in Ruby right now. But what I am known in Ruby is for regular expressions. People have told me that it has helped them a lot. 22:14 – Nell: Regular expressions can be a lot of fun but they are mind numbing at first. Seeing an example can help. 22:33 – Chuck: Habitat is written in Rust. What’s that transition like from Ruby to Rust? 22:49 – Nell: I took a Latin course. Learning Rust was like learning Latin in that it’s a HUGE learning curve. However, in both that I stopped fighting with the language. And stepped back to see why it was doing what it’s doing. In Rust there is no Garbage Collector. My Ruby experience did give me a leg-up. Nell continues to talk about the differences between Rust and Ruby. 24:30 – Chuck: Which language do you like better? 24:34 – Nell: Personally, Ruby but for this project Rust! 24:45 – Chuck: We were talking about the tradeoffs between... 25:01 – Nell: Yes, choose the language that works for THAT project and for your team. 25:17 – Chuck: How can people find you? 25:23 – Nell: Twitter. I check it throughout the day, so feel free to DM me. GitHub, too. I have gotten back to voice acting so check that out! 26:11 – Advertisement – Fresh Books! Links: Ruby Elixir Rails Rust Operation Code Nell Shamrell-Harrington's LinkedIn Nell Shamrell’s Twitter Nell Shamrell’s GitHub Chef.Io Sponsors: Get a Coder Job Cache Fly Fresh Books Picks: Charles Frameworks Summit Podcast Conference Home Depot Tool Rental  Nell New speed eradicator for Facebook The Daiso Store!

Panel: Charles Max Wood Guest: Nell Shamrell-Harrington This week on My Ruby Story, Chuck talks with Nell who is a principle engineer at Chef. Check them out at Chef.Io. She also works with Operation Code. This organization helps veterans to learn code, and helps them get a technical job. Check out today’s episode where Chuck and Nell discuss Ruby, Rust, and much more! In particular, we dive pretty deep on: 2:00 – Chuck: Episode 105 is another episode you’ve been on before. 2:25 – Chuck: I want to spotlight you and talk about what you are working on. How did you get into programming? 2:38 – Nell: I was a theater major in college. I graduated in 2007 and the big financial crisis hit in 2008. I found work at the Physics Department in Seattle. Once they found out that I knew how to code, they gave me more coding to do. When you are doing just the mathematics portion – you don’t see how this applies to real life. I didn’t pursue it because I didn’t see how it worked in the real world. Then I saw eventually how my theater background really helped me with coding because you have to be super creative. After that (this is when I got into Ruby) my roommate in college sent me a message. She was working with Ruby, too, and she wanted to bring me on as a junior developer. 5:55 – Chuck: It’s interesting, too, to see what you just said. Not seeing the real-world application with some of that stuff. I can relate to that. I wanted to get into IT after college. The other thing is that it was someone you KNEW to get you into Ruby. People get into a specific framework because of someone that they knew/know. 6:54 – Nell: Yes, it’s the personal testimonies that help people make those decisions. 7:13 – Chuck: It was someone that you KNEW that helped you get X job. 7:24 – Nell: Yes, in Operation Code, too. Take a look at this candidate (normally you wouldn’t look at them b/c of their CV) and take a chance on them. 8:09 – Chuck: One thing that I am curious about what’s been your favorite thing to work on with Ruby? 8:38 – Nell: I worked on the supermarket product. Cookbook is a chef recipe for infrastructure... We weren’t just running a site that people were using. They were saying: we love it, but we are behind a firewall. They couldn’t use the public one and they wanted a private one. The answer was: Yes! That was the first time I worked on software – packaged and distributed. I loved the breadth of the industries that it had an affect on. It was cool to see different industries use my work through a Ruby on Rails application. Ruby does scale! 10:42 – Chuck: Let’s talk about your work at Chef. You worked on Supermarket and then what was the distributed part to it? 11:05 – Nell: Chef Omnibus was the tool we used. You could take that package and install it on the infrastructure... 11:33 – Chuck: I worked at a university for a while. The work I did was that the access to the Internet was limited. Chef would have been nice! 11:58 – Chuck: What did you do at Blue Box? 11:59 – Nell: Software engineer there and we were a hosting company. We had a Rails application... I helped write the code. 12:29 – Chuck: What are you working on now? 12:32 – Nell: I am working on a project called Habitat. Nell talks about what THIS project is and how it functions. Check it out! 14:20 – Chuck: How did you get into Operation Code? 14:26 – Nell: Both my parents were air force operators. I wanted to but I had a physical limitation so I couldn’t. I grew up in military culture from 0-14 years old. After that I realized in my 20’s I really missed it. After the military it’s scary because you don’t have (maybe) a sense of purpose like you did in the military. She asked how she could help and someone referred her to Operation Code. She realized she could be an asset and help these veterans. She works with close to 3,000 veterans to help them give a purpose after military life. They learn code and then hopefully find a technical job. 17:13 – Chuck: I spent some years around that life, too, when I was a missionary overseas. My brother-in-law was medically discharged. You see this change and it can be scary for them. You wind up in this position and you want to help. I admire this. These folks have sacrificed for us so let’s make a difference for them, too. 18:35 – Nell: My friend said that she didn’t like it when people thanked her for her service. She said that so many warzones it seems empty. When she heard this it was powerful to her. 19:40 – Chuck: How can people get involved? 19:43 – Nell: Operation Code – Hit the JOIN link. You can sign-up to be a volunteer. The slack community is where all the magic happens.  20:24 – Chuck: Anything else? 20:28 – Nell: Habitat is written in Rust. I haven’t done tons in Ruby right now. But what I am known in Ruby is for regular expressions. People have told me that it has helped them a lot. 22:14 – Nell: Regular expressions can be a lot of fun but they are mind numbing at first. Seeing an example can help. 22:33 – Chuck: Habitat is written in Rust. What’s that transition like from Ruby to Rust? 22:49 – Nell: I took a Latin course. Learning Rust was like learning Latin in that it’s a HUGE learning curve. However, in both that I stopped fighting with the language. And stepped back to see why it was doing what it’s doing. In Rust there is no Garbage Collector. My Ruby experience did give me a leg-up. Nell continues to talk about the differences between Rust and Ruby. 24:30 – Chuck: Which language do you like better? 24:34 – Nell: Personally, Ruby but for this project Rust! 24:45 – Chuck: We were talking about the tradeoffs between... 25:01 – Nell: Yes, choose the language that works for THAT project and for your team. 25:17 – Chuck: How can people find you? 25:23 – Nell: Twitter. I check it throughout the day, so feel free to DM me. GitHub, too. I have gotten back to voice acting so check that out! 26:11 – Advertisement – Fresh Books! Links: Ruby Elixir Rails Rust Operation Code Nell Shamrell-Harrington's LinkedIn Nell Shamrell’s Twitter Nell Shamrell’s GitHub Chef.Io Sponsors: Get a Coder Job Cache Fly Fresh Books Picks: Charles Frameworks Summit Podcast Conference Home Depot Tool Rental  Nell New speed eradicator for Facebook The Daiso Store!

Panel: Charles Max Wood Guest: Nell Shamrell-Harrington This week on My Ruby Story, Chuck talks with Nell who is a principle engineer at Chef. Check them out at Chef.Io. She also works with Operation Code. This organization helps veterans to learn code, and helps them get a technical job. Check out today’s episode where Chuck and Nell discuss Ruby, Rust, and much more! In particular, we dive pretty deep on: 2:00 – Chuck: Episode 105 is another episode you’ve been on before. 2:25 – Chuck: I want to spotlight you and talk about what you are working on. How did you get into programming? 2:38 – Nell: I was a theater major in college. I graduated in 2007 and the big financial crisis hit in 2008. I found work at the Physics Department in Seattle. Once they found out that I knew how to code, they gave me more coding to do. When you are doing just the mathematics portion – you don’t see how this applies to real life. I didn’t pursue it because I didn’t see how it worked in the real world. Then I saw eventually how my theater background really helped me with coding because you have to be super creative. After that (this is when I got into Ruby) my roommate in college sent me a message. She was working with Ruby, too, and she wanted to bring me on as a junior developer. 5:55 – Chuck: It’s interesting, too, to see what you just said. Not seeing the real-world application with some of that stuff. I can relate to that. I wanted to get into IT after college. The other thing is that it was someone you KNEW to get you into Ruby. People get into a specific framework because of someone that they knew/know. 6:54 – Nell: Yes, it’s the personal testimonies that help people make those decisions. 7:13 – Chuck: It was someone that you KNEW that helped you get X job. 7:24 – Nell: Yes, in Operation Code, too. Take a look at this candidate (normally you wouldn’t look at them b/c of their CV) and take a chance on them. 8:09 – Chuck: One thing that I am curious about what’s been your favorite thing to work on with Ruby? 8:38 – Nell: I worked on the supermarket product. Cookbook is a chef recipe for infrastructure... We weren’t just running a site that people were using. They were saying: we love it, but we are behind a firewall. They couldn’t use the public one and they wanted a private one. The answer was: Yes! That was the first time I worked on software – packaged and distributed. I loved the breadth of the industries that it had an affect on. It was cool to see different industries use my work through a Ruby on Rails application. Ruby does scale! 10:42 – Chuck: Let’s talk about your work at Chef. You worked on Supermarket and then what was the distributed part to it? 11:05 – Nell: Chef Omnibus was the tool we used. You could take that package and install it on the infrastructure... 11:33 – Chuck: I worked at a university for a while. The work I did was that the access to the Internet was limited. Chef would have been nice! 11:58 – Chuck: What did you do at Blue Box? 11:59 – Nell: Software engineer there and we were a hosting company. We had a Rails application... I helped write the code. 12:29 – Chuck: What are you working on now? 12:32 – Nell: I am working on a project called Habitat. Nell talks about what THIS project is and how it functions. Check it out! 14:20 – Chuck: How did you get into Operation Code? 14:26 – Nell: Both my parents were air force operators. I wanted to but I had a physical limitation so I couldn’t. I grew up in military culture from 0-14 years old. After that I realized in my 20’s I really missed it. After the military it’s scary because you don’t have (maybe) a sense of purpose like you did in the military. She asked how she could help and someone referred her to Operation Code. She realized she could be an asset and help these veterans. She works with close to 3,000 veterans to help them give a purpose after military life. They learn code and then hopefully find a technical job. 17:13 – Chuck: I spent some years around that life, too, when I was a missionary overseas. My brother-in-law was medically discharged. You see this change and it can be scary for them. You wind up in this position and you want to help. I admire this. These folks have sacrificed for us so let’s make a difference for them, too. 18:35 – Nell: My friend said that she didn’t like it when people thanked her for her service. She said that so many warzones it seems empty. When she heard this it was powerful to her. 19:40 – Chuck: How can people get involved? 19:43 – Nell: Operation Code – Hit the JOIN link. You can sign-up to be a volunteer. The slack community is where all the magic happens.  20:24 – Chuck: Anything else? 20:28 – Nell: Habitat is written in Rust. I haven’t done tons in Ruby right now. But what I am known in Ruby is for regular expressions. People have told me that it has helped them a lot. 22:14 – Nell: Regular expressions can be a lot of fun but they are mind numbing at first. Seeing an example can help. 22:33 – Chuck: Habitat is written in Rust. What’s that transition like from Ruby to Rust? 22:49 – Nell: I took a Latin course. Learning Rust was like learning Latin in that it’s a HUGE learning curve. However, in both that I stopped fighting with the language. And stepped back to see why it was doing what it’s doing. In Rust there is no Garbage Collector. My Ruby experience did give me a leg-up. Nell continues to talk about the differences between Rust and Ruby. 24:30 – Chuck: Which language do you like better? 24:34 – Nell: Personally, Ruby but for this project Rust! 24:45 – Chuck: We were talking about the tradeoffs between... 25:01 – Nell: Yes, choose the language that works for THAT project and for your team. 25:17 – Chuck: How can people find you? 25:23 – Nell: Twitter. I check it throughout the day, so feel free to DM me. GitHub, too. I have gotten back to voice acting so check that out! 26:11 – Advertisement – Fresh Books! Links: Ruby Elixir Rails Rust Operation Code Nell Shamrell-Harrington's LinkedIn Nell Shamrell’s Twitter Nell Shamrell’s GitHub Chef.Io Sponsors: Get a Coder Job Cache Fly Fresh Books Picks: Charles Frameworks Summit Podcast Conference Home Depot Tool Rental  Nell New speed eradicator for Facebook The Daiso Store!

Cell Block H Podcast - Episode 2   Synopsis: - Mrs. Jackson is a prison baby - Bea gives her old hubby a banging surprise - Mums daughter is not a total bitch, she’ll give you a ride and will get you a room - Franky starts scheming on being top dog - Lynn is super serial about being innocent - Marty is too cool for school   First viewing: 2018-08-25 (this time around) Recorded: 2018-09-21   Episode Info:   First airing - 27th February 1979   Written - Reg Watson - (Number of episodes 2) Produced - Ian Bradley - (Number of episodes 2) Directed - Graeme Arthur - (Number of episodes 2)   Clips From The Episode:   “Morning Lynn!” - Bea, 05:13 “Rotary Phone On Supplements” - 12:02 “Just don’t go smashing the furniture, ay?“ - Bea, 16:06 “Yeah 10 years” - Bea, 24:07 “Digging holes” - Franky, 33:40 “Look Down at me once more” - Bea, 35:35 “I just brought you a present.“ - Bea, 44:43   Newcomers:   Ann-Maree McDonald - Rosie Bill Bennett - Mr Gibson Billie Hammerberg - Valerie Richardson Anne Charleston - Lorraine Watkins Don Barker - Bill Jackson Ronald Korosy - Marty   Exits:   Terry Trimble - Harry Smith (Episode 2)   Links From The Episodes:   Who’s Who In Wentworth - Encyclopedia for everything Prisoner Cell Block H Prisoner Cell Block H - Episode 1 (Audio commentary by Ian Bradley) Prisoner Cell Block H - Imdb Rotary Phone - Wikipedia   Intro / Outro:   Intro music - Graham De Wilde - Icescape   Intro clips:   Miss Ferguson threatens prisoner - Episode? (If you know which episode this is please let me know) Nola doesn’t want to go across the Nullarbor - Episode 340 Bea threatens prisoner - Episode? (If you know which episode this is please let me know) Lizzie's sentence - Episode 105   Outro music - Andrew Jackman - Underwater Beauty 1   Outro clip:   Frankie misses Doreen - Episode 1   Contact:   Email: cellblockhpodcast@gmail.com Twitter: @cellpodcast Facebook: www.facebook.com/cellblockhpodcast/   ***Spoilers*** * * * * * * * * * * *   In View With Peter Dean - Contemporary Article   Most Roles Played Leaderboard:   Bill Bennett 10 Terry Trimble 7 Will Deumer 7   Characters:   Don Barker - Bill Jackson (3 episodes, 2-4)   Ronald Korosy - Marty Jackson (4 episodes, 2-6)   Andrew McKaige - Marty Jackson (10 episodes, 381-406) - Voice acting for a couple of the Halo Games   Michael Winchester - Marty Jackson (59 episodes, 625-692)   Nicki Paull - Lisa Mullins (6 episodes, 651-656) - Doris Cruickshank (3 episodes, 478-481) - Played a flight attendant in Queen of the Damned   Terrie Waddell - Lisa Mullins (32 episodes, 657-692)   Anne Maree McDonald - Roise (8 episodes, 2-74) - She’s also a opera singer.   Reg Evans - Electrician (2) - Fred (Foreman) (3 episodes, 315-321) - Mick "Foxy" Lawson (398) - Howard Simmons (7 episodes 561-584)   Billie Hammerberg - Valerie Richardson (5 episodes, 2-36) - May Collins (51 episodes, 537-587)   Bill Bennett   - Mr. Gibson (2 episodes, 2-4) - Old Codger (59) - Old Man (73) - Garbage Collector (147) - Old Man (199) - Cleaner (308) - Magistrate (371) - Judge (446)   Anne Charleston - Lorraine Watkins (2 episodes, 2-6) - Policewoman (2 episodes, 345-346) - Policewoman (354) - Diedre Kean (16 episodes, 464-492) - (I missed mentioning) she played Celeste Donaldson in Wentworth (season 1, episode 4)   I also missed mentioning these two things:   Gabrielle Hartley - Lorraine Watkins (3 episodes, 65-67) - Lady Brooke-Giddings (4 episodes, 584-610)   Terry Trimble - Harry Smith (Episode 2) - Pentridge Guard (75) - Customer (92) - Van Driver (166) - Sergeant Thomas (247) - Detective Inspector Lovell (337) - Bernard Cox (411)

Microsoft is doing a good job in shielding the complexity of what is going on in the CLR from us. Until now Microsoft is taking care to optimize the Garbage Collector and tries to come up with good defaults when it comes to thread and connection pool sizes. The problem though is that even the best optimizations from Microsoft are not good enough if your application suffers from poor architectural decisions or simply bad coding.Listen to this podcast to learn about the top problems you may suffer in your .NET Application. We have many examples and we discuss how you can do a quick sanity check on your own code to detect bad database access patterns, memory leaks, thread contentions or simply bad code that results in high CPU, synchronization or even crashes!

Microsoft is doing a good job in shielding the complexity of what is going on in the CLR from us. Until now Microsoft is taking care to optimize the Garbage Collector and tries to come up with good defaults when it comes to thread and connection pool sizes. The problem though is that even the best optimizations from Microsoft are not good enough if your application suffers from poor architectural decisions or simply bad coding.Listen to this podcast to learn about the top problems you may suffer in your .NET Application. We have many examples and we discuss how you can do a quick sanity check on your own code to detect bad database access patterns, memory leaks, thread contentions or simply bad code that results in high CPU, synchronization or even crashes!

Rebecca and guest co-host Emily Pearl Goodstein talk with Watt Hamlett (a man of many talents) about nicknames (wanted and unwanted), things that we judge (or don't judge), personal style (or lack thereof), how it seems like we all have mentors (and/or mentees), whether ladies should be required to shave their legs (or not), and whether one should admit to ever having told a lie (or lie and claim to have always told the truth). 

まつもとゆきひろさんをゲストに迎えて、Ruby GC, Ruby 2.2, Swift, 開発環境、エディタ、Emacs などについて話しました。 Show Notes 2014 Fukuoka Ruby Nights Rebuild: 5: Ruby 2.0 (まつもとゆきひろ) Ruby version policy changes starting with Ruby 2.1.0 Ruby Garbage Collection: Still Not Ready for Production Ruby 2.1: Out-of-Band GC Watching and Understanding the Ruby 2.1 Garbage Collector at Work Feature #9634: [PATCH]Symbol GC Denial of Service and Unsafe Object Creation Vulnerability in JSON (CVE-2013-0269) yukihiro_matz: My vague plan for Ruby GIL ... Introducing Rubinius X Swift Language Changes in Xcode 6 beta 3 - Swift Blog yukihiro_matz: なかなかエディタを作る時間が取れなくて How Emacs changed my life

Interview with Scott Moulton, leading forensic authority on Solid State Drive Forensics