OpenTelemetry: What’s New With the Second-Biggest CNCF Project? - Related to angular, design, svelte, frameworks:, tool

Svelte 5 And The Future Of Frameworks: A Chat With Rich Harris

Svelte 5 And The Future Of Frameworks: A Chat With Rich Harris.

After months of anticipation, debate, and even a bit of apprehension, Svelte 5 arrived earlier this year. Frederick O’Brien caught up with its creator, Rich Harris, to talk about the path that brought him and his team here and what lies ahead. After months of anticipation, debate, and even a bit of apprehension, Svelte 5 arrived earlier this year. Frederick O’Brien caught up with its creator, Rich Harris, to talk about the path that brought him and his team here and what lies ahead.

Svelte occupies a curious space within the web development world. It’s been around in one form or another for eight years now, and despite being used by the likes of Apple, Spotify, IKEA, and the New York Times, it still feels like something of an upstart, maybe even a black sheep. As creator Rich Harris lately put it,.

“If React is Taylor Swift, we’re more of a Phoebe Bridges. She’s critically acclaimed, and you’ve heard of her, but you probably can’t name that many of her songs.”.

This may be why the release of Svelte 5 in October this year felt like such a big deal. It tries to square the circle of convention and innovation. Can it remain one of the best-loved frameworks on the web while shaking off suspicions that it can’t quite rub shoulders with React, Vue, and others when it comes to scalability? Whisper it, but they might just have pulled it off. The post-launch reaction has been largely glowing, with weekly npm downloads doubling compared to six months ago.

Still, I’m not in the predictions game. The coming months and years will be the ultimate measure of Svelte 5. And why speculate on the most pressing questions when I can just ask Rich Harris myself? He kindly took some time to chat with me about Svelte and the future of web development.

Svelte 5 is a ground-up rewrite. I don’t want to get into the weeds here — key changes are covered nicely in the migration guide — but suffice it to say the big one where day-to-day individuals are concerned is runes. At times, magic feeling $ has given way to the more explicit $state , $derived , and $effect .

A lot of the talk around Svelte 5 included the sentiment that it marks the ‘maturation’ of the framework. To Harris and the Svelte team, it feels like a culmination, with lessons learned combined with aspirations to form something fresh yet familiar.

“This does sort of feel like a new chapter. I’m trying to build something that you don’t feel like you need to get a degree in it before you can be productive in it. And that seems to have been carried through with Svelte 5.”.

Although raw usage numbers aren’t everything, seeing the uptick in installations has been a welcome signal for Harris and the Svelte team.

“For us, success is definitely not based around adoption, though seeing the number go up and to the right gives us reassurance that we’re doing the right thing and we’re on the right track. Even if it’s not the goal, it is a useful indication. But success is really people building their apps with this framework and building higher quality, more resilient, more accessible apps.”.

The tenets of a Svelte philosophy outlined by Harris earlier this year reinforce the point:

The web matters. Optimise for vibes. Don’t optimise for adoption. HTML, The Mother Language. Embrace progress. Numbers lie. Magical, not magic. Dream big. No one cares. Design by consensus.

Rich Harris – North Star, JSNation US 2024.

Frameworks are a means to that end, and Harris sees plenty of work to be done there.

Every milestone is a cause for celebration. It’s also a natural pause in which to ask, “Now what?” For the Svelte team, the sights seem firmly set on shoring up the quality of the web.

“A conclusion that we reached over the course of a recent discussion is that most software in the world is kind of terrible. Things are not good. Half the stuff on my phone just doesn’t work. It fails at basic tasks. And the same is true for a lot of websites. The number of times I’ve had to open DevTools to remove the disabled attribute from a button so that I can submit a form, or been unclear on whether a payment went through or not.”.

This certainly meshes with my experience and, doubtless, countless others. Between enshittification, manipulative algorithms, and the seemingly endless influx of AI-generated slop, it’s hard to shake the feeling that the web is becoming increasingly decadent and depraved.

“So many pieces of software that we use are just terrible. They’re just bad software. And it’s not because software engineers are idiots. Our main priority as toolmakers should be to enable people to build software that isn’t broken. As a baseline, people should be able to build software that works.”.

This sense of responsibility for the creation and maintenance of good software speaks to the Svelte team’s holistic outlook and also looks to influence priorities going forward.

Part of Svelte 5 feels like a new chapter in the sense of fresh foundations. Anyone who’s worked in software development or web design will tell you how much of a headache ground-up rewrites are. Rebuilding the foundations is something to celebrate when you pull it off, but it also begs the question: What are the foundations for?

Harris has his eyes on the wider ecosystem around frameworks.

“I don’t think there’s a lot more to do to solve the problem of taking some changing application state and turning it into DOM, but I think there’s a huge amount to be done around the ancillary problems. How do we load the data that we put in those components? Where does that data live? How do we deploy our applications?”.

In the short to medium term, this will likely translate into some love for SvelteKit, the web application framework built around Svelte. The framework might start having opinions about authentication and databases, an official component library perhaps, and dev tools in the spirit of the Astro dev toolbar. And all these could be precursors to even bigger explorations.

“I want there to be a Rails or a Laravel for JavaScript. In fact, I want there to be multiple such things. And I think that at least part of Svelte’s long-term goal is to be part of that. There are too many things that you need to learn in order to build a full stack application today using JavaScript.”.

Although Svelte has been ticking along happily for years, the release of version 5 has felt like a new lease of life for the ecosystem around it. Every day brings new and exciting projects to the front page of the /r/sveltejs subreddit, while this year’s Advent of Svelte has kept up a sense of momentum following the stable release.

Below are just a handful of the Svelte-based projects that have caught my eye:

Despite the turbulence and inescapable sense of existential dread surrounding much tech, this feels like an exciting time for web development. The conditions are ripe for lovely new things to emerge.

And as for Svelte 5 itself, what does Rich Harris say to those who might be on the fence?

“I would say you have nothing to lose but an afternoon if you try it. We have a tutorial that will take you from knowing nothing about Svelte or even existing frameworks. You can go from that to being able to build applications using Svelte in three or four hours. If you just want to learn Svelte basics, then that’s an hour. Try it.”.

Hi, let's get started with our install. Download the ISO and boot it however you want.

You know about Baseline, right? And you may have heard that the Chrome team made a web component for it.

Open source has long driven innovation and the adoption of cutting-edge technologies, from web interfaces to cloud-native computing. The same is true ......

OpenTelemetry: What’s New With the Second-Biggest CNCF Project?

This is part two of a Makers series on the state of observability. Part one featured Christine Yen , CEO and co-founder of [website].

Morgan McLean, a former employee at Microsoft and Google who’s now at Splunk, has long wrestled with solving the challenges of observability in large-scale systems.

As a product manager early in his career, he would sometimes write internal tools. “One of my biggest points of frustration was always, when we were working on large, high-scale services, being able to actually debug them when things went wrong,” expressed McLean, co-founder of OpenTelemetry and senior director of product management at Splunk, a Cisco enterprise, in this episode of The New Stack Makers.

In those days, he stated, “when we were on call or when we were pushing out rollouts, if there was any risk of instability, it would take a nontrivial amount of time to chase down what went wrong, and that was just due to our tools.”.

In this episode, McLean talked to Alex Williams, TNS founder and publisher, about the past, present and future of OpenTelemetry, the open source framework that helps software engineers collect and analyze data about how their systems and applications are performing.

OpenTelemetry was created from the merger of two projects in 2019: OpenTracing and OpenCensus. It’s a Cloud Native Computing Foundation incubating project, and it’s been rapidly adopted as a part of many organizations’ observability strategies.

OTel, McLean mentioned, emerged to solve the problems of scale that emerged as organizations began to embrace Kubernetes. “It meant now we had to spend a lot of time extracting data from end-clients’ applications in order to make those tools work. It sounds relatively trivial, right? You’re just switching platforms. What’s the big deal?

But, he added, “because things like OpenTelemetry didn’t exist, it’s actually a heck of a lot of work to be able to get distributed traces, to get application metrics, to get various other types of data out of end-individuals’ environments. Because it means you need to integrate with every language runtime, every framework that end-individuals use, and every database that they’re using.”.

Integrating with all of them, he concluded, is “untenable for any one person, organization, whatever, to go and maintain that.” A new set of standards was called for. Hence the subsequent creation of OpenTracing (begun with contributions by LightStep and Uber) and OpenCensus (started at Google) — and eventually, OpenTelemetry.

Alleviating ‘Points of Frustration’ With OTel.

OpenTelemetry is now the second most active open source project‚ after Kubernetes, in the CNCF, McLean told the Makers audience, with more than 1,200 developers checking in code to OTel repos per month.

“It’s very obvious to me now, several years in, the impact that this has on the industry,” he expressed. “People can use these tools. Developers everywhere can gain these deep insights into their applications and their infrastructure as a result.”.

But plenty of work needs to be done. For instance, documentation could be improved, McLean stated. “Open source project management — in terms of how the organization is structured and who’s working on what and things like that — is not really radically different than running a project in a enterprise or really in any kind of environment. It’s all just human project management.”.

OTel innovations loom on the horizon. For instance, McLean spoke to TNS at KubeCon + CloudNativeCon North America last November about profiling signals, slated to move into general availability in 2025.

Profiling, he expressed, is the fourth major observability signal — alongside logs, tracing and metrics.

“With profiling, you’re actually getting insight into the performance a level deeper into the application itself, and the actual functions or methods inside of that application. You can see their memory consumption. You can see how they call each other. You can see their CPU consumption.”.

McLean also told the Makers audience about efforts made over the past couple of years, both at Splunk and within the OTel community, on the OTel operator and other efforts to create components to make adoption easier for the end user.

“As you see more and more improvements get made to open telemetry that just make it automatic, or as it gets built into more platforms and run times just out of the box, you’re going to see — I mean, it’s already rapid adoption — but you will see that accelerate even further. The few points of frustration that people may have had with it evaporate.”.

Check out the full episode to learn more about what’s new and what’s ahead for OpenTelemetry.

OpenAI has launched Deep Research, a new agent within ChatGPT designed to conduct in-depth, multi-step investigations across the web. Initially availa......

I’ve been a software engineer for a little over a decade now, and I like to think I’m a pretty organized person. I have a system for everything, and t......

New Tool Generates Angular Components From Design

Coding to Figma UI design specifications can be time-consuming for frontend developers. A new artificial intelligence tool called AutoCode from WaveMaker is designed to simplify the process by generating web and mobile components. The code can then be exported to Angular for the web and React Native for mobile.

“This handoff process between the design team and the frontend engineering teams takes up time because of the number of iterations it goes through to get the fit and finish perfectly implemented,” mentioned Prashant Reddy, WaveMaker’s senior director of product. “With AutoCode, what we are trying to do is to make that handoff between a designer and the frontend engineering team as pixel perfect, as precise as we can, so that we can reduce the number of iterations that the teams go through in order for them to deliver the end product.”.

WaveMaker is a low-code platform, but it’s primarily used by professional frontend developers at financial institutions, large product companies and independent software vendors, -founder and CTO Deepak Anupalli. Often these companies are building and delivering hundreds of screens as part of their product modernization journey.

“Even before LLMs (large language models), we were generating code in Angular and React Native, and we were actually giving the code to the developer so that they can build their application on top,” he noted. “That is how we were able to convince our developers to adopt the product. They are actually seeing real code, they own it and they customize it.”.

AutoCode translates Material 3-based Figma designs to production-ready code for UI elements, app navigation and interactions.

Material 3 is Google’s open source design system. Figma uses a Material 3 Design Kit, which includes pre-designed components, styles, and guidelines. This makes it possible for designers to easily create prototypes and mockups that adhere to Material 3 principles.

While WaveMaker AutoCode works out of the box for Figma designs using the Material 3 design system, it can be enabled to work with client-proprietary design systems. AutoCode identifies design elements such as forms, lists and cards and maps them to corresponding widgets within WaveMaker studio. It supports Figma variables, modes and design tokens to maintain the integrity of the original design through the development process.

Generated code can also be customized to add business logic within WaveMaker’s studio environment.

WaveMaker currently has more than 90 components, including buttons, text fields, forms, multi-step forms, tables and charts. It also offers mobile app components that are commonly used, including bottom navigation.

“There are patterns that emerge, that that we see as common across web and mobile app, and then we componentize that and add that into the product,” Reddy presented.

AutoCode can recognize individual components such as a text box or a button, but it also can group them and recognize that together, they create a long form or a registration form.

“That abstraction is very critical because then the programming model shifts to ‘Where do you want the data that is coming out of this form to go to?’” Reddy stated. “Our AI model recognizes all the components that are in the design, and then groups the components in the design into logical, higher order abstractions — like forms, table grids, list of cards — whether they are vertical or horizontal.”.

It recognizes higher order abstractions, also.

“From a program point of view, when you see a list of cards, you think of them as an array in your data,” he noted. “It’s very essential for the programmer to not see the five cards that are in the Figma design as individual cards but as a list. So our AI model does all of that.”.

AutoCode is a machine learning-based (ML) tool, but not generative AI. Rather than training an LLM, it relies on metadata from the Figma design. This solves the issue of hallucination, Reddy and Anupalli expressed.

“Our implementation is based on ML techniques that don’t use LLM, and so that’s one part of the solution architecture that makes it predictable and consistent every time you run,” he mentioned. “We generate the design tokens, then the components that use them and then the page. These are all architectural guardrails that make sure that the translation quality is accurate, and you can verify that at each layer.”.

WaveMaker also offers a WaveMaker CoPilot, an AI-powered assistant within WaveMaker’s developer studio that can provide prompt-based UI customization for WaveMaker AutoCode generated UIs.

Editor’s Note: Updated Feb. 5, 10:28 [website] to correct the spelling of Deepak Anupalli.

If you've ever needed some random data for testing or just wanted to add a bit of fun to your p......

Most of the e-commerce applications are zero-tolerant of any downtime. Any impact on application resources can impact the overall availability metrics......

A while ago, I explored Neo4j, a powerful graph database, earlier for the implementation of the.