Highlights this week include: OneLake catalog: The trusted catalog for organizations worldwide - Microsoft's OneLake catalog provides a central hub for discovering, managing, governing, and securing data across the Fabric platform, now adopted by over 230,000 organizations worldwide. Supercharge AI, BI, and data engineering with Semantic Link (GA) - Ruixin Xu - Semantic Link reaches general availability in Microsoft Fabric, unifying AI, BI, and data engineering through a shared semantic layer that streamlines workflows across data science, reporting, and automation. Enrich Power BI reports with machine learning in Microsoft Fabric - Ruixin Xu - A walkthrough of an end-to-end pattern for adding ML predictions such as churn scoring to Power BI reports, using Fabric's unified semantic models, notebooks, and scoring endpoints.
VS Code becomes multi-agent command center for developers - VS Code v1.109 lets developers orchestrate GitHub Copilot, Anthropic Claude, and OpenAI Codex agents side by side, transforming the editor into a unified multi-agent development hub. Choosing the Right Model in GitHub Copilot: A Practical Guide for Developers - A practical guide to selecting the right AI model in GitHub Copilot for different tasks, from fast lightweight models for quick edits to deep reasoning models for complex debugging and agentic workflows. Azure Databricks Supervisor Agent (GA) - Databricks Agent Bricks Supervisor Agent is now generally available, offering a managed orchestration layer that coordinates multiple AI agents and tools from a single entry point, governed by Unity Catalog.
Finally, What is Retrieval-Augmented Generation (RAG)? - An explainer on RAG uses a retail example - analysing customer reviews about delivery, the technique of retrieving relevant information and injecting it into an LLM's context to ground responses in domain-specific data and reduce hallucinations.
If you're interested in all things Microsoft Fabric - don't forget to sign up for our new newsletter - Fabric Weekly - which we'll start publishing in the next month or so. We'll be moving all Fabric content over from Azure Weekly to Fabric Weekly, just as we did with Power BI Weekly 7 years ago.
Overview of the shift from instructor-led courses to agent-first, context-driven learning with AI as a collaborative build partner. Key mindsets: start with vision, think out loud, insist on mutual pushback, and use AI as a mirror for refining ideas. Practical tactics: create handoff documents, paste exact errors or code into prompts, use AI to craft prompts for other models, preserve session context, and prefer voice over typing for faster iteration.
EasyBuild.ShipIt 1.0.0 is out! Automate your release chores. ShipIt parses your Conventional Commits to calculate versions, generate changelogs, and auto-open Release PRs! Auto Release PRs Monorepo readyStart shipping: https://github.com/easybuild-org/EasyBuild.ShipIt#dotnet #fsharp
Something truly monumental happened in the world of software development in 2025. Safari shipped a
reasonable implementation of text-wrap: pretty:
https://webkit.org/blog/16547/better-typography-with-text-wrap-pretty/. We are getting
closer and closer to the cutting-edge XV-century technology. Beautiful paragraphs!
We are not quite there yet, hence the present bug report.
A naive way to break text into lines to form a paragraph of a given width is greediness: add the
next word to the current line if it fits, otherwise start a new line. The result is unlikely to be
pretty โ sometimes it makes sense to try to squeeze one more word on a line to make the lines more
balanced overall. Johannes Gutenberg did this sort of thing manually, to produce a beautiful page
above. In 1981, Knuth and Plass figured out a way to teach computer to do this, using dynamic
programming, for line breaking in TeX.
Inexplicably, until 2025, browsers stuck with the naive greedy algorithm, subjecting generations of
web users to ugly typography. To be fair, the problem in a browser is harder version than the one
solved by Gutenberg, Plass, and Knuth. In print, the size of the page is fixed, so you can compute
optimal line breaking once, offline. In the web context, the window width is arbitrary and even
changes dynamically, so the line-breaking has to be โonlineโ. On the other hand, XXI century
browsers have a bit more compute resources than we had in 1980 or even 1450!
Making lines approximately equal in terms of number of characters is only half-way through towards a
beautiful paragraph. No matter how you try, the length wonโt be exactly the same, so, if you want
both the left and the right edges of the page to be aligned, you also need to fudge the spaces
between the words a bit. In CSS,
text-wrap: pretty
asks the browser to select line breaks in an intelligent way to make lines roughly equal, and
text-align: justify
adjusts whitespace to make them equal exactly.
Although Safari is the first browser to ship a non-joke implementation of text-wrap, the
combination with text-align looks ugly, as you can see in this very blog post. To pin the ugliness
down, the whitespace between the words is blown out of proportion. Hereโs the same justified
paragraph with and without text-wrap: pretty:
The paragraph happens to look ok with greedy line-breaking. But the โsmartโ algorithm decides to add
an entire line to it, which requires inflating all the white space proportionally. By itself, either
of
p { text-wrap: pretty;text-align: justify;}
looks alright. Itโs just the combination of the two that is broken.
This behavior is a natural consequence of implementation. My understanding is that the dynamic
programming scoring function aims to get each line close to the target width, and is penalized for
deviations. Crucially, the actual max width of a paragraph is fixed: while a line can be arbitrary
shorter, it canโt be any longer, otherwise itโll overflow. For this reason, the dynamic programming
sets the target width to be a touch narrower than the paragraph. That way, itโs possible to both
under and overshoot, leading to better balance overall. As per
original article:
The browser aims to wrap each line sooner than the maximum limit of the text box. It wraps
within the range, definitely after the magenta line, and definitely before the red line.
But if you subsequently justify all the way to the red line, the systematic overshoot will manifest
itself as too wide inter-word space!
WebKit devs, you are awesome for shipping this feature ahead of everyone else, please fix this small
wrinkle such that I can make my blog look the way I had intended all along ;-)
Save the date and tune in for Aspire Conf on March 23! A free livestream event. Discover Aspire and learn how it can transform the way you build and deploy your distributed apps and agents.
Welcome to IoT Coffee Talk, where hype comes to die a terrible death. We have a fireside chat about all things #IoT over a cup of coffee or two with some of the industry's leading business minds, thought leaders and technologists in a totally unscripted, organic format.
This week Rob, Rick, Mark, Alistair, David, Bill, Anthony, Wienke, Oliver, Tom, Debbie, Pete, and Leonard jump on Web3 for a discussion about:
๐ถ ๐๏ธ BAD KARAOKE! ๐ธ ๐ฅ "Jessica", The Allman Brothers Band" ๐ฃ IoT Coffee Talk celebrates 300 episodes and 6 years of uninterrupted ridiculousness!! ๐ฃ What makes our show so amazing? ๐ฃ Will AI be around longer than other tech fads? ๐ฃ How much do we not care about our privacy? Is it a good thing or bad? ๐ฃ What happens when you realize that AI doesn't forget? ๐ฃ What is the risk of an AI hallucinating (lying or misrepresenting) YOU? ๐ฃ Is SaaS dead? Is the developer dead thanks to AI? ๐ฃ How do you leverage AI responsibly for coding and software development? ๐ฃ Who will be liable for crap vibe code? ๐ฃ If you don't catch the hallucination in your vibe code, should you get fired or Claude? ๐ฃ The new philosopher of our time, Mediocrates, The Lazy and Mindless. ๐ฃ Was Qualcomm's takeover of Arduino a good thing or bad? Why? ๐ฃ Europe may force everyone to be responsible with IoT and AI. Find out how.
It's a great episode. Grab an extraordinarily expensive latte at your local coffee shop and check out the whole thing. You will get all you need to survive another week in the world of IoT and greater tech!
Tune in! Like! Share! Comment and share your thoughts on IoT Coffee Talk, the greatest weekly assembly of Onalytica and CBT tech and IoT influencers on the planet!!
If you are interested in sponsoring an episode, please contact Stephanie Atkinson at Elevate Communities. Just make a minimally required donation to www.elevatecommunities.org and you can jump on and hang with the gang and amplify your brand on one of the top IoT/Tech podcasts in the known metaverse!!!
Take IoT Coffee Talk on the road with you on your favorite podcast platform. Go to IoT Coffee Talk on Buzzsprout, like, subscribe, and share: https://lnkd.in/gyuhNZ62
Log in
Automate your release chores. ShipIt parses your Conventional Commits to calculate versions, generate changelogs, and auto-open Release PRs!
Auto Release PRs
https://github.com/easybuild-org/EasyBuild.ShipIt#dotnet #fsharp
