Articles

The Technology Stack Needed To Build a Web3 Application

,

The internet ecosystem is currently shifting significantly with the dawn of decentralization. More and more decentralized technologies are becoming mainstream and gaining acceptance by the world at large.

As far as innovation and development is concerned, the startup way of doing things has prevailed. While more prominent companies have tried to get into the space, none of their projects has been groundbreaking regarding their usage. Startups have the upper edge, with many creating successful businesses like opensea.io, Alchemy, and IPFS/filecoin (Protocol Labs).

Source de l’article sur DZONE

/par

Different Test Scopes in Rust

,

I’m still working on learning Rust. Beyond syntax, learning a language requires familiarizing oneself with its idioms and ecosystem. I’m at a point where I want to explore testing in Rust.

The Initial Problem

We have used Dependency Injection a lot – for ages on the JVM. Even if you’re not using a framework, Dependency Injection helps decouple components. Here’s a basic example:

Source de l’article sur DZONE

/par

Adobe Has Acquired You

,

There were mixed reactions on Thursday morning when Adobe announced it had acquired Figma.

Excited press releases extolling the benefits of the “collaboration” followed the news. Dylan Field, founder and CEO of Figma, said: “There is a huge opportunity for us to accelerate the growth and innovation of the Figma platform with access to Adobe’s technology…”

The reaction from the design community has been a little less enthusiastic.

The problem for the design industry is that we’ve been here before. The acquisition of Macromedia followed a period in which Adobe tried to compete, failed to update its legacy code, lost the battle, and purchased the victor. You only need to look at the number of former Macromedia products in Adobe’s stable (zero) to see where Figma’s heading.

Figma has grown faster than any of its rivals in the last eight years. It is, of course, easier to grow when you start at zero. But there’s no denying Figma is a well-managed business and probably a good investment — if not worth the $20bn that Adobe reportedly paid.

Figma’s technology will give Adobe a leg-up in the collaborative design stakes, where it is clearly lacking. And Adobe’s resources will iron out some of the kinks in Figma, especially around typography, which is, if we’re honest, a bit hacky in places.

Adobe will provide a good home (we hope) for the Figma team, who will have the opportunity for career advancement in a much wider pool of development teams.

And, of course, Figma’s annual revenue will begin to trickle into Adobe’s vault — although it may be some time before it makes a dent in that $20bn hole.

But Adobe didn’t buy Figma for its business model, collaborative technology, team, or revenue stream. Adobe bought Figma’s users, all four million of them.

Adobe‘s approach to design software is upselling. It lures you in with free apps, and when you’re engaged, it integrates them with other parts of its ecosystem until suddenly, without meaning to, you’ve agreed to a Creative Cloud subscription.

Adobe was losing customers to a competitor. And more importantly, due to Figma’s free-use approach for individuals, it was losing young customers to a competitor. If it hadn’t bought Figma, Adobe would have needed to invest heavily in its own products while providing them to freelancers for free; that isn’t viable for a company with as many commitments as Adobe.

Yes, it is entirely accurate to say that competition drives innovation, and with fewer competing apps, there is less need for companies like Adobe to build high-quality, reliable products. However, it is also true to say that a lack of competition creates opportunities for new apps.

Somewhere out there, in a dorm room, or a basement, or on a kitchen table, someone is working on Adobe’s next big acquisition. It’s probably an AR design app; we need a few more of those.

For Figma, the next 12 months will be bright as Adobe works to retain the customers it’s bought. Within five years, you’ll probably need an Adobe Fonts subscription and a Photoshop plugin to use Figma. In ten years, it will be stored in a code archive next to Freehand.

Some designers will turn to Sketch; others will turn to Affinity; some will shrug and keep using Figma; others will shrug and keep using XD.

If an app is intrinsic to your design work, it’s probably time to switch apps. Your skills are transferable. I’ve switched apps many times; some I loved, some I just needed. I’ve never encountered an app that improved my work, although plenty have improved my mood while working.

Figma took a great approach and will continue to be great until it isn’t. Tools come and go, Adobe’s acquisitions team, it appears, is eternal.

 

 

Featured image uses photos by Afrika ufundi, Andrea Piacquadio, Andrea Piacquadio, Anna Tarazevich, cottonbro, fauxels, Ketut Subiyanto, Mikhail Nilov, Moose Photos, Pavel Danilyuk, Pavel Danilyuk, Polina Tankilevitch, Tima Miroshnichenko.

Source

The post Adobe Has Acquired You first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

Here Is How To Develop UIs Faster in ReactJS

,

It’s 2022, and React has a huge ecosystem to help developers bring complex UIs to life faster. Furthermore, with the extensive support of ReactJS libraries, there is hardly any case when a developer has to build a component from scratch.

However, not every ReactJS UI developer is aware of the best practices to build UIs faster in ReactJS. Therefore, I’ll be discussing the top five approaches (which I personally use) for building UIs quicker in a ReactJS project. So without further ado, let’s get started:

Source de l’article sur DZONE

/par

Writing Your First Python GitHub Action

,

We wanted to share our findings and experiences from creating our first GitHub Action. In this article, you’ll learn how to write a simple GitHub Action in Python.

Brief Overview of GitHub Actions

In 2019, GitHub released its own CI tool called GitHub Actions. According to GitHub, Actions make it easy for developers to automate tasks within the software development life cycle (SDLC). The native ecosystem integration enables projects to be automated from the moment developers commit code for deployment into production.

Source de l’article sur DZONE

/par

WordPress 6.0 Lives Up To The Hype

,

WordPress 6.0 has been released, and another niche jazz musician will be enjoying extra Spotify royalties next month.

WordPress 6, named for latin-jazz musician Arturo O’Farrill, is the realization of a change of direction the WordPress Foundation adopted several years ago.

All versions of WordPress now power around 42% of the web. That’s approximately 810,000,000 sites. If you looked at each site for a single second, without pausing to blink, it would take you over 25 years to see the home page of each one — of course, if you factor in how long a typical WordPress site takes to load it would take well over a century.

Some people (i.e., me) have been predicting the decline of WordPress for so long that sooner or later, we were bound to be correct. And, despite its astonishing reach, there are some signs that its market share may now be in decline. Even the W3C abandoned it in favor of Craft.

Of the 1,930,000,000 sites that currently make up the web, only around 400,000,000 are active. WordPress’s long-term dominance, coupled with a stalling market share, means that a disproportionate number of abandoned sites are WordPress. With site builders like Wix, Squarespace, and Shopify taking huge chunks of WordPress’ share of new sites, WordPress is facing something of a cliff edge.

What the ill-informed naysayers (i.e., me) hadn’t counted on was that WordPress had already seen the writing on the wall and formulated a plan…

WordPress’s problem has always been its legacy code; supporting out-of-date ideas and a spaghetti-like codebase has meant a great deal of work to do anything new. As a result, the last few releases have seen great ideas stifled by labored implementation. Even the most loyal WordPress user has to admit that Gutenberg, while filled with potential, doesn’t work the way it should. However, with WordPress 6, all the work may be starting to pay off.

With version 6, the block editor in WordPress is starting to feel like a design tool that, if not perfect, is at least usable. Editing content no longer feels like you’re fighting against the UI. Most importantly, the bar for creating a site is much, much lower. WordPress 6 also offers improved performance and accessibility, both areas that have traditionally been lacking. Security is still something of an issue, but that is mainly due to the ROI for hackers that massive market shares generate.

WordPress, it seems, has arrived at two conclusions: its main competition isn’t other CMS but other site builders. To maintain its market dominance, it needs to cater not to professionals but to amateurs.

Don’t get me wrong; the WordPress ecosystem will benefit from WordPress 6, at least reputationally. New sites run by amateurs eventually become established sites run by, if not professionals, then at least knowledgeable amateurs.

OK, so WordPress probably isn’t a good choice for enterprise sites. And there are certainly better options for ecommerce. And as for SEO, well, probably best not mentioned.

But in WordPress 6, we have a free, open-source site builder that lowers the bar for making a new site. It’s a credit to the community that has persevered to produce it.

Source

The post WordPress 6.0 Lives Up To The Hype first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par

Simplify Java Persistence Implementation With Kotlin on Quarkus

,

For decades, developers have struggled with optimizing persistence layer implementation in terms of storing business data, retrieving relevant data quickly, and — most importantly — simplifying data transaction logic regardless of programming languages.

Fortunately, this challenge triggered the invention of Java ecosystems in which developers can implement the Java Persistence API (JPA). For instance, Hibernate Object-Relational Mapper (ORM) with Panache is the standard framework for JPA implementation in the Java ecosystem.

Source de l’article sur DZONE

/par

Using CockroachDB Workloads With Kerberos

,

GSSAPI authentication is becoming increasingly popular as CockroachDB starting to make inroads in Fortune 2000 customer bases and financial services segment. That said, ecosystem coverage for GSS needs to improve for parity with other authN methods. Today, we are providing a workaround and a look at the future. By the way, do you realize this is my 15th article on Kerberos and CockroachDB?

Articles Covering CockroachDB and Kerberos

I find the topic of Kerberos very interesting and my colleagues commonly refer to me for help with this complex topic. I am by no means an expert at Kerberos, I am however familiar enough with it to be dangerous. That said, I’ve written multiple articles on the topic which you may find below:

Source de l’article sur DZONE

/par

How to Prepare for the Immersive Web

,

Websites as we know them are going to change very soon. The days of text, images, and basic interactions in a 2D browser window have served us well, but virtual, augmented, and mixed reality experiences are getting better all the time. Developers and designers need to think beyond the browser window and prepare for an immersive future.

Many have been very skeptical about VR and AR in the past because despite grand promises about what they would achieve, they’ve mostly failed to deliver on the scale that the industry hoped for.

But it’s different this time: industry leaders like Meta, Apple, and Microsoft are pursuing a range of different mixed reality projects; they see the opportunity and are dropping hints about what’s next.

In a survey from Perkins Coie LLP and the XR Association, nearly 9 in 10 respondents said that by the year 2025, immersive technologies—including augmented reality, virtual reality, and mixed reality — will be as ubiquitous as mobile devices.

That’s a bold prediction, but it could be our new reality.

Use Cases

VR and AR aren’t a logical fit for every website, and that’s fine. There’s no need to force an immersive experience on something better suited to a standard viewing experience.

But when they’re done right, 3D experiences can add a lot to your website. Check out the demo experience from Mozilla, the 3D tours from Matterport, and the immersive storytelling from Within.

Here are a few areas where these technologies shine:

  • Retail – VR can be used to provide a virtual showroom where customers browse through products. AR can even bring the products into your home by showing you how a piece of furniture will fit in your room, what a painting will look like on your wall, or in Apple’s case, how a product will look on your desk.
  • News – Coverage of events can be enriched by providing a 360-degree view and placing viewers in the center of the story.
  • Training – AR can generate virtual overlays over physical equipment so employees can have hands-on training that’s more effective.

Define Your Platform

Adding immersive experiences to your website will require various skills based on what you’re trying to create. Whether you’re new to web development or are a seasoned developer with many years of experience, the main difference from classic web development is that you’re switching from a 2D to a 3D experience. Development in VR/AR is much closer to developing 3D video games than creating web applications.

First of all, you need to decide on the hardware that you’re building for. Are your viewers mainly using computers, smartphones, or a headset like the Oculus Quest? Each hardware category offers a different set of capabilities for what’s possible.

Next, when we look at 3D engines and frameworks on the market, some big names like Unity, Unreal Engine, and CRYENGINE stand out. Most of these engines were spun out of game development and are based on programming languages like C, C++, or C#. While very powerful, they’re overkill for anyone trying to create a basic immersive web experience.

The good news for web developers is that the WebXR Device API is an open standard specified by the W3C with a JavaScript API that makes immersive experiences possible in the browser. So if you already have a background in web development, you can use your knowledge of JavaScript to get started.

There are some useful frameworks and platforms that make working with WebXR more convenient:

  • A-Frame – A web framework for building 3D experiences.
  • React 360 – A framework for the creation of interactive 360-degree experiences that run in the web browser. As the name already suggests, it builds on React and reuses the concepts you already know.
  • Amazon Sumerian – A managed service that lets you create and run 3D, AR, and VR applications. Since it’s integrated into the AWS ecosystem, it’s also possible to add AI-enabled elements into your generated world.

Create Your Content

No one wants to read long blocks of text in 3D. Since we’re talking about visual experiences, it’s logical that the emphasis should be on creating content that is pleasing to the eye and interesting to look at. What works on a normal website probably isn’t going to feel natural in a 3D environment, so you need to decide what visuals you should create to suit the format.

What high-resolution images and assets do you need? Can you add videos? How about 360-degree videos? Will viewers just be looking at something, or will they be able to interact with it?

You also can’t forget about sound because it’s a critical part of immersive experiences. What music and sounds should you create to make the content come alive?

Not everyone is going to have the latest and greatest device or 5G coverage. The requirements for bandwidth and transmission quality are much higher with 3D content. A few milliseconds of latency can go unnoticed on a typical website, but in a VR/AR setting, it can make the experience laggy or unusable.

Try to optimize your content to be the highest quality it can be within a reasonable file size. If the experience starts to suffer from too many assets downloading at the same time, it’s better to create a more streamlined experience that maintains a high performance rate.

It’s important to consider your hosting infrastructure, as well. This shouldn’t be a big problem, but it is worth mentioning that you need to add new content types to your configurations, and your CDN needs to support these new types, too.

Make Your Content Flexible

When we’re talking about getting your website ready for immersive experiences, we’re not just talking about having people scroll through your regular website in VR. That isn’t compelling for your audience.

The idea is to take some content that’s already on your website and separate it from the presentation layer so you can use it in a 3D environment or any other platform that you want. Classic content management takes place in silos, which means you cannot easily reuse the content from your website.

This separation can be achieved by using a classic database, but if you want developers and content teams to collaborate, a headless CMS is front-end agnostic and more user friendly.

Start Experimenting Today

Building 3D content experiences may seem intimidating, but as we’ve seen, you likely already have the web development skills necessary to get started and try out some different ideas.

What you build today will prepare you for the 3D future of tomorrow.

 

Featured image via Pexels.

Source

The post How to Prepare for the Immersive Web first appeared on Webdesigner Depot.

Source de l’article sur Webdesignerdepot

/par