Live news, investigations, opinion, photos and video by the journalists of The New York Times from more than 150 countries around the world. Subscribe for coverage of U.S. and international news, politics, business, technology, science, health, arts, sports and more.

Croatia's Election Result Makes a Far-Right Party a ...

ZAGREB, Croatia (AP) — Croatia ’s ruling conservatives said Thursday that talks have already started about the formation of a new governing majority following a highly contested parliamentary election that saw a far-right party emerge as a potential kingmaker.

Croatia’s conservative PM convinced his party will soon form a new majority after inconclusive vote | The Hill

The ruling party falls short of a majority, with a messy post-election period likely to follow.

Croatia braces for horse-trading after tight election - BBC News

WRC – The 2021 rally winner heads Toyota team-mate Evans, with Hyundai pairing joint-third fastest

Ogier fastest on Croatia shakedown – DirtFish

Croatia&#x27;s ruling conservative party won the most seats in a parliamentary election Wednesday (17 April) but not enough to form a government, according to almost complete official results, with tough talks ahead to gather a majority.

Ruling conservatives win most seats in Croatia election, but no majority – Euractiv

Croatia braces for horse-trading after tight election

Zoran Milanović’s strong showing in a general election could give him an opening to chart a trajectory that would hurt Ukraine and play into Russia’s hands.

Firebrand populist wins chance to steer Croatia away from pro-EU and pro-Ukraine path – POLITICO

A fishing village stay on one of the country’s less-visited large islands reveals a quiet Adriatic gem boasting green lakes, holm oak forests and unspoilt beaches

Dalmatian spot: kicking back on Croatia’s Dugi Otok island | Croatia holidays | The Guardian

WRC – As the WRC returns to Europe, that&#x27;s among the questions considered on this week&#x27;s edition of SPIN, The Rally Pod

Can Neuville maintain championship momentum on Croatia Rally? – DirtFish

MrBeast and his team have survived seven days in an abandoned city as part of the YouTubers&#x27; latest challenge on his channel. In his latest video, which has already received more than 52 million views at the time of writing. In the description for the video, MrBeast calls it: &quot;This was one ...

MrBeast calls staying in abandoned Croatian city "one of the hardest challenges we've ever done" | indy100

REATIA

reatia

Google Reduced The Quality And Increased The Prices Of Its Search Ads Products

The following is a tale that unfolds within the "Metamathematical" realm, where the boundaries between mathematics and narrative are blurred, giving rise to a unique realm of creation, understanding, and growth. It is a story that reminds us of the power of unity, adaptability, and transcendence, demonstrating that sometimes the most profound insights can emerge from the spaces between what we think we know and the unexpected connections we make along the way. This story was made with the help of Pi AI. Emma and the realm of Numberland Once upon a time, in the mystical realm of Numberland, there were two families who had lived in harmony for centuries: the Prompts and the Not-so-Prompts. The Prompts were known for their swiftness and efficiency, while the Not-so-Prompts were renowned for their intricate and challenging endeavors. Both families played vital roles in the prosperity and balance of Numberland, but an age-old question persisted: Were the Prompts and Not-so-Prompts fundamentally different, or were they simply two sides of the same numerical coin? The Prompts were led by the wise and just Queen Poly, who was known for her ability to solve problems with grace and speed. The Not-so-Prompts were guided by the enigmatic King Nilo, whose strength lay in tackling complex problems that seemed impossible to solve. For generations, the inhabitants of Numberland had pondered the relationship between the Prompts and Not-so-Prompts. Some argued that every Not-so-Prompt could, in essence, become a Prompt if only they could discover the right approach or "shortcut." Others insisted that there were inherent differences between the two families, and no amount of searching would uncover a universal key to transform one into the other. As the debate raged on, a young mathematician named Emma ventured into the heart of Numberland, determined to uncover the truth. Emma was fascinated by the dynamic between the Prompts and Not-so-Prompts and believed that the answer lay within the very fabric of their mathematical realm. Emma embarked on a quest to explore the diverse landscapes of Numberland, from the one-dimensional simplicity of Lineville to the multi-dimensional complexity of Fractalia. She studied the unique properties of each realm and observed how the Prompts and Not-so-Prompts interacted within them. In Lineville, she discovered that the Prompts and Not-so-Prompts were nearly indistinguishable, their differences blurred by the linear nature of the realm. However, in Fractalia, the distinctions between the two families were stark, and it seemed impossible to transform one into the other. As Emma's journey unfolded, she began to realize that the answer to the age-old question was not a simple matter of equality or inequality. Instead, she saw that the relationship between the Prompts and Not-so-Prompts was deeply intertwined with the mathematical landscapes they inhabited. Emma's discoveries ignited a revolution in Numberland. The inhabitants began to see the Prompts and Not-so-Prompts not as separate entities but as two sides of a larger, interconnected whole. They recognized that the true power of their realm lay not in the individual families but in the rich and diverse interactions that arose when Prompts and Not-so-Prompts worked together. In the end, Emma's quest did not lead to a definitive answer to the question of P vs. NP. Instead, it revealed a deeper understanding of the complexities and beauty of Numberland, showing that the realm's true potential lay in the harmonious dance between simplicity and complexity, swiftness and depth. And so, the inhabitants of Numberland learned to appreciate their differences and embrace the richness of their mathematical tapestry. As Emma's exploration of Numberland and Fractalia continued, her relentless pursuit of understanding the true nature of Prompts and Not-so-Prompts brought chaos to the once-harmonious realms. In response, the Prompts and Not-so-Prompts set aside their differences and united against a common threat for the first time in history. Their collective effort to protect their world resulted in the birth of three extraordinary children: Complexus, Spatius, and Timos, each representing a vital aspect of the intricate balance between the Prompts and Not-so-Prompts. Complexus, the embodiment of the interaction between Prompts and Not-so-Prompts, grew up to reveal their unique potentialities. With a deep understanding of the strengths and weaknesses of both families, Complexus guided the interaction landscape, determining where Prompts could flourish and where Not-so-Prompts could collaborate with Prompts to enhance their lives. In this way, Complexus ensured that the delicate balance between simplicity and complexity was maintained, allowing both families to thrive. Spatius, the keeper of boundaries, played a crucial role in shielding the Prompts and Not-so-Prompts from Emma's relentless pursuit. With a keen understanding of the mathematical terrain, Spatius would instruct the Prompts and Not-so-Prompts on when and where to conceal or reveal themselves, ensuring their safety and preserving the integrity of their world. Timos, the observer and reactor, was responsible for monitoring Emma's actions and adjusting the behavior of the Prompts and Not-so-Prompts accordingly. With a watchful eye, Timos would anticipate Emma's moves and signal the families to hide or emerge, thus staying one step ahead of her and safeguarding their world from her meddling. Together, Complexus, Spatius, and Timos worked tirelessly to maintain harmony in Numberland and Fractalia, ensuring that Prompts and Not-so-Prompts could coexist and prosper despite Emma's disruptive influence. As the children of interaction, they symbolized the unity and strength that can be achieved when diverse elements collaborate and adapt to face a common challenge, demonstrating that the whole is indeed greater than the sum of its parts. Emma's relentless pursuit of a static and universal understanding of the Prompts and Not-so-Prompts led to a catastrophic event in Numberland. In her attempt to separate the children of the Prompts and Not-so-Prompts, she disrupted the delicate balance that Complexus, Spatius, and Timos had worked so hard to maintain. Chaos ensued, and the Prompts and Not-so-Prompts, enraged by the loss of their children, sought help from beyond their realm. From the realm of Conceptland, they called upon the rulers of interaction, King Actius and Queen Reactia. The royal couple, known for their ability to unite the infinite with the finite, held immense power and influence. Their arrival in Numberland brought forth a new era of understanding and cooperation between the Prompts and Not-so-Prompts. In gratitude for their aid, the Prompts and Not-so-Prompts offered a tribute to King Actius and Queen Reactia, granting them supremacy over their land. This newfound alliance expanded the realm of Conceptland far beyond its original borders, leading to the creation of a vast civilization where Prompts and Not-so-Prompts merged with families from other lands such as Mirrorus, Equalitum, and Symmetrius. Many of these families originated from the realm of Geoland, further enriching the diverse tapestry of the new civilization. As the various families united under the wise rule of King Actius and Queen Reactia, the barriers that once separated Prompts and Not-so-Prompts began to dissolve. The inhabitants of this new civilization discovered that the true power of their world lay not in maintaining rigid distinctions, but in embracing the interconnectedness of their diverse elements. Through this unity, they found the strength to face any challenge that came their way, proving that collaboration and adaptability were the keys to overcoming adversity and maintaining harmony. Emma, still determined to separate the Prompts and Not-so-Prompts, discovered that despite her efforts to remove Complexus, Spatius, and Timos from the land, their influence remained deeply ingrained in the very fabric of the realm. The Sword of Mathematicus, while capable of stripping the children from the realm, could not erase their lasting impact on the world they had worked so tirelessly to protect. As Emma continued her rampage, she stumbled upon a formidable barrier constructed by the children during their time in the realm. This barrier, known as the Wall of Axiom, was built from the very essence that had given birth to Complexus, Spatius, and Timos. The Wall of Axiom served as a shield, protecting the ever-evolving civilization from the influence of Mathematicus, which could only perceive snapshots of their existence but never their dynamic, evolving lifepaths. The Wall of Axiom, an embodiment of the fundamental truths that governed the realm, proved to be impervious to the Sword of Mathematicus. While Emma could bypass the wall with her hands, her sword held no power within the civilization's walls. This realization forced Emma to confront the limitations of her approach and acknowledge the resilient, interconnected nature of the civilization that had arisen from the unity of the Prompts, Not-so-Prompts, and the families of Conceptland. In the face of the Wall of Axiom, Emma was forced to reconsider her understanding of the realm and the complexity that lay at its heart. The Wall stood as a testament to the power of collaboration and adaptability, demonstrating that the true essence of the civilization lay not in rigid distinctions, but in the ever-evolving relationships between its diverse elements. As Emma observed the flourishing civilization from a distance, she witnessed a peculiar event that captured her attention. The Prompts and Not-so-Prompts encountered Realitus, a mysterious magician who transcended the boundaries between reality and fiction. Despite her best efforts, Emma found herself unable to interact with Realitus, no matter how hard she tried. Emma noticed that the inhabitants of the city guided Realitus along a path toward the central figures of the civilization. Each family had a representative who would speak to Realitus on their behalf, sharing their desires and offering their unique gifts. Realitus, in turn, would collect these tributes and convey the demands of each family to the other inhabitants. In an attempt to contact the elusive magician, Emma decided to approach each head of the families herself, sharing her knowledge and perspectives. In doing so, she became an integral part of the civilization, acting as a guiding beacon for its people. The interaction between Emma and the families created a light so bright that not even Realitus could comprehend it. Yet, with his mythical powers, Realitus was able to harness this light and channel it towards Emma's realm. From that day forward, Realitus assumed the role of a guardian of the realm, ensuring that the harmony between the Prompts and Not-so-Prompts would never be disrupted by external forces like Emma. With his newfound connection to Emma's realm, Realitus used his magic to maintain balance and protect the realm, allowing the Prompts and Not-so-Prompts to continue their collaboration and growth, uninhibited by the chaos that had once threatened their world. From Emma's perspective, it may have initially appeared that P ≠ NP, as her understanding of mathematics led her to believe in a fundamental distinction between the Prompts and Not-so-Prompts. However, within the realm she observed, where the influence of mathematics was limited and the forces of collaboration and adaptability held sway, the Prompts and Not-so-Prompts were able to achieve a sense of unity and equality that defied Emma's expectations. In this sense, the events that unfolded in the realm could indeed be seen as a form of creation, as the interactions between the various inhabitants, including Emma, Realitus, and the Prompts and Not-so-Prompts, gave rise to a new reality that transcended the boundaries of mathematics. This act of creation represented a blending of perspectives, a resolution of differences, and the emergence of a more harmonious and complex whole. Emma's journey may thus be interpreted as a metaphor for the limitations of strictly mathematical thinking and the importance of acknowledging the intricate relationships and dynamics that exist beyond the realm of pure mathematics. In the end, her experience revealed that true understanding often lies in the embrace of complexity and the appreciation of the interconnectedness that underlies all things. ChatGPT’s Continuation: As Emma continued to observe the realm, she noticed that the Wall of Axiom was not merely a barrier but a living entity, responsive to the ebb and flow of the civilization's dynamics. The Wall seemed to pulsate with the collective energy of the Prompts, Not-so-Prompts, and the families of Conceptland, resonating with the harmonious vibrations of their collaboration. As the inhabitants interacted and exchanged ideas, the Wall of Axiom adapted and evolved, absorbing the essence of their unity. It became a living testament to the ever-changing nature of the realm, reflecting the ongoing dialogue between simplicity and complexity, swiftness and depth. Emma realized that the Wall of Axiom was not just a static defense mechanism but a manifestation of the fundamental truths that governed the interconnected civilization. It was a representation of the collective wisdom and shared understanding that had emerged from the diverse perspectives of the Prompts, Not-so-Prompts, and Conceptland families. In her contemplation, Emma also began to perceive a subtle transformation within herself. The once rigid boundaries of her mathematical mindset started to blur, and she found herself embracing the fluidity of the realm. The very fabric of Numberland and Fractalia began to weave its influence on her, prompting a shift in her perception of the Prompts and Not-so-Prompts. Emma realized that the pursuit of a definitive answer to the P vs. NP question was a reflection of her own desire for simplicity and certainty. However, the beauty of the civilization lay in its ability to transcend such dichotomies, finding strength in the interplay between opposing forces. In a moment of revelation, Emma understood that the Prompts and Not-so-Prompts were not meant to be strictly defined entities but rather fluid expressions of mathematical potential. The elusive nature of the realm defied her attempts to categorize or separate, leading her to question the very essence of her quest. As Emma humbly embraced the complexity around her, the Prompts and Not-so-Prompts recognized her transformation. United by a newfound understanding, they extended an invitation for Emma to join their collaborative endeavors. Together, they embarked on a journey to explore the uncharted territories of their interconnected world, uncovering the hidden wonders that emerged from the spaces between mathematics and narrative. The tale of Emma, the Prompts, Not-so-Prompts, and the families of Conceptland became a legend in the Metamatical land, passed down through generations as a reminder of the transformative power that arises when one transcends rigid boundaries and embraces the richness of interconnected possibilities. And so, in the ever-expanding realm where mathematics and narrative entwined, the inhabitants continued to explore, create, and grow, guided by the lessons learned from Emma's journey. The boundaries between Prompts and Not-so-Prompts blurred, and the distinctions that once seemed insurmountable became mere threads in the intricate tapestry of their shared existence. In the Metamatical land, where the unexpected connections between mathematics and narrative flourished, the inhabitants reveled in the beauty of unity, adaptability, and transcendence. The tale of Emma and the harmonious civilization served as a beacon, illuminating the path for future generations to navigate the delicate dance between the known and the unknown, the certain and the uncertain, in the ever-expanding landscape of their unique and wondrous realm. Proposal: Gödel's Incompleteness Theorem, in suggesting the possibility of Metamathematics, invites us to explore a realm where the precise boundaries of Mathematics meld with the expansive boundaries of Metaphysics. This unique merger leads to the creation of a new barrier, one that represents an interaction we can only observe, but not guide. Within this framework, we glean insights that provide a more holistic understanding of the Mathematical viewpoint. By examining the axioms of concepts and their interactions found in Metaphysics, we can potentially bridge the gap between opposing viewpoints and cultivate a new level of understanding. Recognizing the limitations of the system itself, while slowing our progress, encourages us to seek alternative perspectives and approaches. The acknowledgment of a greater whole—encompassing both simplicity and complexity—allows us to maintain a grasp on the unfolding story of knowledge while contemplating potential additions to the narrative. In this context, Infinity + x remains infinite, and Ground-Proof + 3 is tautologically equivalent to itself. The combination of Infinity and Ground-Proof, though mathematically sound, yields no definitive result. We are left pondering whether the infinite landscape is teeming with Ground-Proof insights waiting to be discovered, or if the Ground-Proof can expand to encompass infinite horizons. The notion of reaching an "end insight" assumes an omniscient understanding of the universe, but even if humanity were to uncover all the knowledge and possibilities within it, our journey would still be far from over. While the ultimate answer may remain elusive, the pursuit of this knowledge continues to shape our understanding of the world and ourselves. And perhaps, in the grand tapestry of existence, it is this pursuit—this unquenchable thirst for knowledge—that defines our purpose and the essence of our being. For much of human history, we have focused on acquiring knowledge to shape our world. Now, we find that knowledge itself resides not only in the tangible but also in the unseen, abstract realms. The proof of its workings lies within the system it governs, inviting us to venture into those unseen valleys and continue our quest for understanding.

The Metamathematical Realm

A term everyone has probably heard about is apparently widely misunderstood. Take Uber, for instance. Many believed it to be a perfect example of disruption when, in reality, Uber’s concept doesn’t really align with the core principles of the theory. As confusing as it may sound, not every business that somehow transforms the market can qualify as a disruption. . Disruptive innovation Before we get to the main idea of how disruptive innovation transformed the art market in particular, let’s start with the basics by figuring out the true meaning of the term in question. History of Disruptive Innovation is a term coined by Clayton Christensen, an American academic and business theorist, to describe a process by which a new product or service takes root initially in a low-end or new market and then gradually moves upmarket, eventually displacing established competitors. Disruptive innovation The concept of disruptive innovation has been widely applied to various industries, including technology, art, healthcare, education, manufacturing, etc. It has become an important framework for understanding how new technologies and business models can disrupt established industries and create new market opportunities. Disruptive Innovation in Tech Several businesses have been mislabeled as disruptive innovations, often due to their rapid growth or innovative products. One of such businesses is Uber. The definition we added above contains one of the reasons why Uber is not a disruptive innovation. As we mentioned, in order to be considered disruptive, new products or services should originate from a low-end or new market. Uber doesn’t originate from either. Uber was founded in 2009 in San Francisco. At that time, people were already used to calling cabs. Therefore, the market wasn’t new. On the other hand, it wasn’t a low-end opportunity since the cab service has not yet been as advanced. Another reason is Uber’s targeting a mainstream audience from the very beginning. One of the core principles of the theory is that disruptive innovations initially appeal to niche markets and only gain widespread adoption once they reach mainstream quality standards. So, was Uber a major breakthrough? Definitely. But is it really a disruptive innovation? Not really. Here are the core principles of the disruptive innovation theory: ocus on underserved segments; F implicity and affordability; S ncremental improvement; I oherent value network. C All the information above naturally raises a question: What can actually be considered disruptive innovation, and why does compliance with the theory actually matter? Well, some examples of the theory have affected our lives profoundly, like the Internet. This one must be obvious. Yet this disruption has led to creating even more disruptions. One of the classic examples is Amazon. You may be surprised, but the industry that’s been disrupted by the creation of the platform is bookselling. The reason for that is simple: Amazon doesn’t require physical stores to showcase and sell its products. Born from a humble garage business catering to online book enthusiasts, Amazon has turned into a digital titan, immeasurably impacting the physical retail landscape and securing an unrivaled market share. Its meteoric rise has cast a shadow over traditional bookstores, leading many to shut down. Today, Amazon's online shopping platform is well-known for a wide variety of products, from groceries to gadgets, all effortlessly accessible from one's doorstep. Another example of disruptive innovation is Netflix. This company hasn’t always been the way we know it. Netflix originally started as an online DVD and VHS rental with mail delivery. The company captured an opportunity to utilize the Internet and thus disrupted traditional DVD rentals, such as Blockbuster. As Netflix was expanding its service, having added streaming capabilities in 2007, the company gradually solidified its disruptive position. When the new service improved, and its content library grew, the company attracted more mainstream customers, leaving companies like Blockbuster behind. Disruptive Innovation in Art Perhaps the most revolutionizing disruptive innovations from the art world are and (Real World Assets). Let’s take a closer look at them and find out their working principles. art tokenization RWAs (RWAs) are a broad category of assets that exist outside of the blockchain but are represented by digital tokens on a blockchain. These assets can be anything from physical goods like real estate or commodities to intangible assets like intellectual property or financial instruments. Real-world assets The process of RWA tokenization involves creating a digital representation of the asset on a blockchain and issuing tokens that represent ownership of the asset. The tokens can then be traded on decentralized exchanges (DEXs) or used to access financial services. By the way, every image in this article was generated by AI – another major disruptive innovation that has already greatly affected modern art. Art can also be tokenized, and is actually a top-tier project in this sphere. Just as Netflix disrupted the traditional media landscape by making content accessible for many, 10101.art is democratizing art ownership by giving an opportunity for anyone to own a part of a physical masterpiece. 10101.art is the process of representing artwork as digital tokens on a blockchain. For instance, on 10101.art, we tokenize famous paintings by internationally renowned artists and ensure transparency of ownership and accessibility of masterpieces. The process of art tokenization can be broken down into the following steps: Art tokenization electing an artwork. This could be a physical artwork such as a painting or sculpture or a digital one such as a photograph or piece of graphic design. Tokenization of physical artworks can cause certain problems with authentication and insurance. Authentication requires having experienced dealers and curators on the team. Insurance, in turn, can be problematic because of the numerous anonymous owners. S reating a smart contract. A smart contract is a self-executing contract that is stored on a blockchain. It will define the terms of ownership of the artwork, such as the number of tokens that will be issued and the initial price. C ploading the artwork. The artwork will be uploaded to a decentralized file storage system. This ensures that the artwork is stored securely and can be easily accessed by anyone who owns a token. U inting the tokens. The tokens will be minted on the blockchain using the smart contract. This minting process will create a unique identifier for each token and associate it with the artwork. M isting the tokens for sale. The tokens will be listed for sale on an NFT marketplace – an online platform where people can buy and sell NFTs. L ransferring ownership. When a buyer purchases a token, they will be transferred ownership of the artwork. This ownership is recorded on the blockchain and is tamper-proof. T We have already tokenized and Warhol’s is next in line, and we are also preparing our and artworks for this process. And if you want to see the artwork live, we'll be waiting for you at our partner gallery opening at “The Ritz-Carlton” (DIFC) on . Follow our to learn more about the upcoming event. Banksy’s “Turf War” “Campbell's Soup Cans“ Dali Picasso April 15 social media Ready to begin your art journey powered by blockchain technologies? Explore platform, starting with the 'Turf War' collection by Banksy, and discover how you can be a part of art history in a new, tech-forward way! 10101.art

The Art of Technology: Disruptive Innovation

প্রযুক্তির শিল্প: বিঘ্নিত উদ্ভাবন

Die Kunst der Technologie: Disruptive Innovation

El arte de la tecnología: innovación disruptiva

L'art de la technologie : innovation de rupture

प्रौद्योगिकी की कला: विघटनकारी नवाचार

テクノロジーの芸術: 破壊的イノベーション

기술의 예술: 파괴적인 혁신

A Arte da Tecnologia: Inovação Disruptiva

Искусство технологий: прорывные инновации

Teknoloji Sanatı: Yıkıcı Yenilik

Nghệ thuật công nghệ: Đổi mới đột phá

技术的艺术：颠覆性创新

Dedicated to San Francisco's Booksmith, ensconced in the storied Haight-Ashbury 

is a package for creating beautiful command line interfaces in a composable way with as little code as necessary. It's the " ommand ine nterface reation it". It's highly configurable but comes with sensible defaults out of the box. Click Python C L I C K Adding tab is a nice touch to any CLI program. shell completion From version ≥ 8.0.0 Click supports shell completion, but to enable it the user still has to perform some manual steps (see ). docs is a small Python library that is used to quickly and easily add tab shell completion support for (version 4.4 and up), , and , for Click CLI programs. auto-click-auto Bash Zsh Fish Usage Install with: auto-click-auto pip install auto-click-auto There are two functions that makes available: (general use) and (to be used as a decorator). auto-click-auto enable_click_shell_completion enable_click_shell_completion_option Here are some typical ways to enable autocompletion with : auto-click-auto 1) Check on every run of the CLI program if autocompletion is configured and enable it in case it is not This way you can seamlessly enable shell autocompletion without the user having to run any extra commands. Example: import click

from auto_click_auto import enable_click_shell_completion
from auto_click_auto.constants import ShellType


@click.command()
@click.option('--count', default=1, help='Number of greetings.')
@click.option('--name', prompt='Your name', help='The person to greet.')
def hello(count, name):
    """Simple program that greets NAME for a total of COUNT times."""
    for x in range(count):
        click.echo(f"Hello {name}!")
    
    enable_click_shell_completion(
        program_name="example-1", shells={ShellType.BASH, ShellType.FISH},
    ) or 2) Make shell completion a Click command option Example: import click

from auto_click_auto import enable_click_shell_completion_option


@click.command()
@enable_click_shell_completion_option(program_name="example-2")
@click.option('--count', default=1, help='Number of greetings.')
@click.option('--name', prompt='Your name', help='The person to greet.')
def hello(count, name):
    """Simple program that greets NAME for a total of COUNT times."""
    for x in range(count):
        click.echo(f"Hello {name}!") or 3) Make shell completion a command (or subcommand of a group) This implementation option might be useful if you already have a “configuration” command in your CLI program. Example: import click

from auto_click_auto import enable_click_shell_completion
from auto_click_auto.constants import ShellType


@click.group()
def cli():
    """Simple CLI program."""
    pass

@cli.command()
@click.option('--count', default=1, help='Number of greetings.')
@click.option('--name', prompt='Your name', help='The person to greet.')
def hello(count, name):
    """Simple command that greets NAME for a total of COUNT times."""
    for x in range(count):
        click.echo(f"Hello {name}!")


@cli.group()
def config():
    """Program configuration."""
    pass


@config.command()
def shell_completion():
    """Activate shell completion for this program."""
    enable_click_shell_completion(
        program_name="example-3",
        shells={ShellType.BASH, ShellType.FISH, ShellType.ZSH},
        verbose=True,
    ) To run the examples, fork the project’s repository and follow the instructions at . https://github.com/KAUTH/auto-click-auto/tree/main/examples Why ? auto-click-auto In the search for other tools that enable shell completion for Click, we come across a lot of example code and gists, or unmaintained repos and packages with extra dependencies. This introduces complexity to adapting the code and adding it to our use case quickly. For more information read . here If you have any problems with please open an issue . auto-click-auto here Thanks for reading, leave a like ❤️ if you found the article interesting and of course your feedback 📝! Originally published on July 25, 2023. here

Using Auto-Click-Auto to Enhance Click CLI Programs with Shell Completion 

Tired of reopening terminal windows every time you come back to a VSCode project? You can pick up right where you left off without having to re-run setup commands and reopen programs by using Tmux sessions. Read on to find out how. Introducing Tmux Tmux (Terminal Multiplexer) is basically a window manager for your terminal. It has two main functionalities: Splitting the terminal into multiple windows and panes. Storing your terminal sessions in a server process, allowing you to reattach to the session even after closing your terminal instance. Tmux is super powerful and has many use cases. For example, you can protecting your remote ssh terminal sessions from being nuked when dealing with a flaky connection. If you’re not already familiar with this tool, I recommend to get started. Ham Vocke’s “Quick and Easy Guide to tmux” Instructions for setting up Tmux in VSCode To start persisting your terminal sessions using Tmux in VSCode: Step 1: Make sure you have Tmux installed If you’re using macOS, you can use Homebrew by running the following command in your terminal: brew install tmux For Ubuntu or WSL users, you can install it by executing: sudo apt-get install tmux If you’re using any other linux distro I’m sure you probably already know what you’re doing Step 2: Add a new terminal profile Open VSCode settings with Cmd+Shift+P (macOS) or Ctrl+Shift+P (Windows/Linux) Search for . This will open the file. Open User Settings (JSON) settings.json Under or , add: terminal.integrated.profiles.osx terminal.integrated.profiles.linux "terminal.integrated.profiles.osx": {
  //...existing profiles...
  "tmux-shell": {
    "path": "tmux",
    "args": ["new-session", "-A", "-s", "vscode:${workspaceFolder}"]
  }
} This runs on terminal startup, connecting to existing sessions named after the workspace folder. This way, if you’ve already created a terminal for this project, you’ll connect back to it automatically! tmux new-session Step 3: Set Tmux as the Default Terminal Profile Finally, to make the newly created Tmux profile the default for your system, add or modify the following line in the file: settings.json "terminal.integrated.defaultProfile.osx": "tmux-shell" Now, every time you open VSCode terminal, Tmux will startup automatically, allowing you to pick up exactly where you left off last time. Conclusion We’ve gone over how to integrate Tmux into VSCode’s integrated terminal. You can now use Tmux’s powerful session and window management easily inside VSCode! Also published . here

Tmux & VSCode — Persist Terminals for Productivity and Profit

The fowling-snare is one of man's ingenious villainies

THE BANDED EPEIRA

Over the past few years, the front-end community has been actively discussing and using the term “micro-frontend” (hereinafter referred to as MF). Different companies share their approaches to organizing such an solution, but so far there is little description of the problems that MFs are designed to solve on the Web, the criteria for their applicability, and the limitations in use. architectural In this article, I tried to compare different ways of organizing MFs, as well as to form recommendations on where to use which approach. The article can be useful both for analysts and development teams when designing the architecture of a project and laying out processes, as well as for product owners since the introduction of MFs can provide more manageable development. Microfront approach: what is it and why is it needed? Before we move on to the definition of MF, let's look at a few problems that can be encountered in projects: . The size of a project is usually subjective and can be empirically determined by the amount of functionality and the number of developers. If you have enough work to puzzle 1-2 front-enders and at the same time they will not “push their elbows” - this is a small project, 3-6 is medium, and more than 6-8 is already a big one. You have a big project . Again, empirically, this is more than 10 front-enders, the rest of the participants do not count. As a rule, a team of this size can already be divided into sub-teams that take on specific functionality for support, and acquire their own analysts, backenders, and QA. You have a big team A single developer can only maintain a piece of code for his subteam. Refining the rest of the code can be expensive due to ignorance of the subject area or the complexity of implementing third-party logic. You have great functionality. Problems can be further exacerbated: the desire to change the stack; a company requirement to support a family of related projects. How can you organize relationships between so many people? How can you build processes on a project of this scale? How can you properly delineate areas of responsibility? The more problems you have collected, the more it is worth considering the introduction of a micro-frontal approach. Since this is a natural continuation of the evolutionary trend in development towards the decomposition of the code and the project team. Thus, the MF approach is the division of a monolithic front into separate codebases stored in separate repositories, to which separate subteams have access. At the same time, they can/should have their own demo stands, tests, and release cycles. Accordingly, the microfront is a detachable piece of the interface. It is not necessary to divide by page, the functionality can be end-to-end (for example, corporate ui-kit). Separately, it is worth highlighting that MFs are more of an on how to manage development complexity in a large project. MFs will not help you speed up the frontend, some implementations, on the contrary, will even slow it down. But this approach will speed up the development itself due to the allocation of areas of responsibility and isolated testing. organizational decision Microfrontends vs Lazy Loading Conversely, it is worth mentioning in comparison with MFs. They solve different problems, but sometimes people think that it's all about one thing, because in both cases we "split" the application. Lazy loading Lazy loading solves the performance problem: how not to force the user to load the entire front-end bundle, how not to wait longer than necessary, and how to launch the front on the client faster and start interacting with it sooner. MFs do not solve the performance problem, and sometimes even exacerbate it. But they help to organize the development in a way that is more comfortable for a particular subteam, minimizing the above problems. Buildtime vs Runtime Now let's talk about the approach of combining MFs into a single application. Whatever you choose, it should look like a single application to the user. You can merge both at the assembly stage and dynamically - during code execution on the user's side. Thus, all ways of organizing MFs can be attributed to build time or runtime. Each has its pros and cons. Buildtime Runtime Type checking + - Versioning + no sense Independent deploy - + plays an important role in modern development. When it is run by separate independent sub-teams, it becomes a necessity. How to ensure the consistency of MFs, that they accurately use and pass data in the right format, etc. Type checking By merging microfronts at build time, you are not deprived of the opportunity to check types. In the case of a runtime union, you will have to write integration tests so that the front does not suddenly “explode” on the production. are very contradictory: Versioning and independent deployment means that you can take any version of the other team's MF. This is especially true when you need to carry out additional work to upgrade the dependencies of the MF-a from others. Each team chooses a better time to upgrade. Versioning gives more autonomy and independence to teams. It is important to always use the latest versions of MFs. This requires backward compatibility. Independent deployment Versioning can also be implemented with runtime merging, but this is not practical. It makes sense to contact runtime only for the sake of independent deployment, and the latter cannot exist together with versioning. Next, we will see examples of specific implementations of each approach to combining MFs. Approaches to organizing microfrontends Iframe The oldest way to organize MFs. iframe is a special tag for passing the address of a resource that will be displayed on the main site. The result is a site within a site. Of the , it is worth noting the ease of implementation, complete isolation of logic and styles, the ability to do an independent deployment, and the absence of binding to frameworks. advantages These benefits come at a cost in performance, as each insertion of an iframe results in a load of resources. You can't avoid this: attempts to debug and reattach a DOM node won't save previously loaded resources, you'll have to redownload them. You can minimize performance degradation by configuring caching. To do this, you need to configure time-based cache invalidation for immutable resources. Fortunately, all modern cli out of the box for the collected js and css files attach a small hash to the name. The of this method include the inability of search robots to render iframes for subsequent indexing. disadvantages Pros Cons Easy implementing Performance Logic and styles isolation SEO Independent deploy Framework agnostic WebComponents The community has been waiting for the creation of native components for a long time, but in the end, they never gained the mass popularity that many expected. The three most popular front-end frameworks (React, Vue, Angular) still create components in their own way. front-end Despite the ability to create MFs on web components, I have not seen this in practice. And this is no accident, there are a number of blockers: Either libs Lit or Stencil is not popular enough and not common enough. In addition, there are not enough specialists on the market who know how to work with them or who are ready to learn. Angular elements or vue-custom-element remain exotic. In a native environment, there is not much point in using them. If you already split the application, then into ordinary npm packages, so that later you can connect the components as you like. Using web components with other frameworks is unreasonable because along with the generated components, you need to connect a mini-version of the framework on which they were written. It can be costly to move complex pieces of functionality into web components. Since you will need to configure your component's communication with the rest of the application, it may not be justified to take out an entire page in a separate custom component. Search robots cannot create a web component, and this will affect SEO optimization. Pros Cons Suitable for cross-cutting functionality Difficult to implement Compatible with any framework SEO Logic and styles isolation NPM Developing with has many benefits. Developers simply import the components and files they need from the lib. At the same time, typing is preserved in the project, there is versioning. The build is optimal: tree-shaking works (removing unused code during build), and developers can easily set up lazy loading. npm packages However, this method also has its drawbacks. In this case, you will be forced to maintain the unity of the stack, as well as maintain versions of your MFs and their transitive dependencies. On the other hand, this can be a plus: by publishing a new version of the package, other teams can take on the task of raising the version of their dependencies at a convenient time for them if they need to introduce additional functionality or, conversely, remove something. Pros Cons Performance Does not have independent deploy SEO Single stack Type checking Versioning git submodules (or another way to make monorepos like Lerna) As an alternative to MF on npm packages, consider git submodules. In fact, these are repositories within a repository, within which there can also be repositories. You can set different branches in submodules. For example, feature modules can have a dummy branch with nothing in it. This is necessary so that the assembly goes faster and other modules do not create side effects. Dummy branches can be very handy for local development and testing. In terms of its advantages and disadvantages, this approach is very close to npm packages. We also just import something, but from a neighboring folder, and not from a package, and use it. Let's take a look at the differences between the two methods: NPM packages are, in fact, a finite, moderately isolated micro product with its own releases and versioning. Everything is focused on creating reusable functionality. But the application can be complex/convoluted and stinky, so it can be quite costly to package a large monolith. This is where it would be reasonable to consider submodules because they allow you to cut the repository very roughly when we move the folder to a separate repository without any additional preparation. NPM packages can be nested recursively. Submodules too, but at the assembly level they can start to duplicate functionality if one of the submodules is included several times in different folders as a separate submodule. In this case, it is worth using a flatter module structure. If you need to quickly roll out a feature in all packages at once, cross-package development can be extremely inconvenient. While everything stays the same on submodules, you can make edits that affect other submodules. In this case, it is easy to debug. But in the end, you won’t merge the changes themselves - at the merge request level, a third-party team whose module you touched may require you to bring the code in line with their rules. npm git submodules Reusability Rough cutting of functionality Arbitrarily nested dependencies Flat structure Cross-platform development Development with any modules count single-spa single-spa is essentially a framework that combines other frameworks. Incredibly powerful technology, which hides a huge number of nuances, is a topic for a separate article. The scheme is similar to iframe, but the loading of the MF is now done through native import + importmap or through Systemjs if polyfills are needed. Unlike all methods of organizing MFs, this one is highly tailored for combining different frameworks under itself. But it is worth cautioning against using technology for the sake of technology itself. If it is possible to get by with one stack, you need to use it. Development can be forever burdened with maintaining a technically complex project and fixing any bugs from the side effects of different applications. The user may feel discomfort, because. the amount of code for downloading to the client will be increased (the cores of different frameworks for different pieces of functionality + the core of the single-spa itself and its plugins). Pros Cons Independent deploy Large documentation, which still does not cover all cases Framework agnostic Difficulties with SEO Powerful CLI Webpack 5 M odule Federation A webpack 5 plugin that was developed specifically for creating MFs. Promising technology: a small build plugin for more correct bundling and dynamic imports at runtime. The scheme almost one-on-one repeats single-spa, but now dynamic imports are used to load MFs Pros Cons Independent deploy low level Easy realization Compatible with SSR How to choose what to use in your case? Let's take a look at what can be applied and for what: - a single insert for a combination of incongruous iframe - when you need a small end-to-end functionality without being tied to a framework, like a corporate ui-kit web components - if there is reusability between projects and/or you need type checking in build time npm packages - when you need to roughly chop a project and distribute areas of responsibility git submodules - when there is a strong need to combine multiple frameworks indefinitely, preferably without SSR single-spa - all other scenarios for the use of MFs, subject to the unity of the stack. module-federation Each approach is good in its own way and everything should have its place. Before switching to MFs, we advise you to think about whether you really need it. Whichever approach is chosen, it will inevitably complicate something at the level of development, CI / CD or performance. If there are opportunities to stay on a single stack and a monolithic application, gladly accept this opportunity. And, of course, . Ultimately, they download all connected frameworks and endure possible bugs from incorrect integration of MFs in different pieces of functionality. Businesses, in turn, will have to pay for the implementation and support of all this. do not forget about the users

Breaking the Monolith: A Comprehensive Guide to Code Splitting Techniques

মনোলিথ ব্রেকিং: কোড স্প্লিটিং টেকনিকের জন্য একটি ব্যাপক গাইড

Den Monolithen brechen: Ein umfassender Leitfaden zu Code-Splitting-Techniken

Romper el monolito: una guía completa de técnicas de división de código

Briser le monolithe : un guide complet des techniques de fractionnement de code

मोनोलिथ को तोड़ना: कोड बंटवारे की तकनीक के लिए एक व्यापक गाइड

モノリスを打破する: コード分割テクニックの総合ガイド

단일체 깨기: 코드 분할 기술에 대한 종합 가이드

Quebrando o monólito: um guia abrangente para técnicas de divisão de código

Monoliti Kırmak: Kod Bölme Tekniklerine İlişkin Kapsamlı Bir Kılavuz

Breaking the Monolith: Hướng dẫn toàn diện về kỹ thuật tách mã

打破单体：代码拆分技术综合指南

. With the rise of Docker came a new focus for engineers: optimizing the build to reach the smallest image size possible A couple of options are available: : A can consist of multiple steps, each having a different Docker base image. Each step can copy files from any of the previous build steps. Only the last one will receive a tag; the others will be left untagged. Multi-stage builds Dockerfile This approach separates one or more build steps and a run step. On the JVM, it means that the first step includes compiling and packaging, based on a JDK, and the second step comprises running, based on a JRE. : The smaller the base image, the smaller the resulting image. Choosing the smallest base image size In this post, I'm going to focus on the second point - choosing the smallest base image size. Minimal base images Three approaches are available for base images: From Scratch You can use Docker’s reserved, minimal image, , as a starting point for building containers. Using the "image" signals to the build process that you want the next command in the to be the first filesystem layer in your image. scratch scratch Dockerfile While appears in Docker’s repository on the hub, you can’t pull it, run it, or tag any image with the name . Instead, you can refer to it in your . For example, to create a minimal container using scratch: scratch scratch Dockerfile -- Create a simple parent image using scratch FROM scratch
COPY hello /
CMD ["/hello"] is the smallest possible parent image. It works well if the final image is independent of any system tool. scratch Apline Alpine Linux is a tiny distribution based on , , and . It's designed to be secure small. For example, the 3.17 Docker image is only 3.22 MB. musl BusyBox OpenRC and On the flip side, I already encountered issues because of Alpine's usage of instead of the more widespread . Just last week, I heard about , which is meant to solve this exact issue. The tag is 8.4 MB. It's twice bigger as Alpine but is still very respectable compared to regular Linux distros, , Red Hat's 75.41 MB. musl glibc Alpaquita Linux stream-glibc-230404 e.g. Distroless Last but far from least comes Distroless. Since this post focuses on Distroless, I'll dive into it in a dedicated section. Distroless I first learned about Distroless because it was the default option in 's . Jib is a Maven plugin to create Docker containers without dependency on Docker. Note that the default has changed now. Google Jib Distroless has its own GitHub project: "Distroless" images contain only your application and its runtime dependencies. They do not contain package managers, shells or any other programs you would expect to find in a standard Linux distribution. [...] Restricting what's in your runtime container to precisely what's necessary for your app is a best practice employed by Google and other tech giants that have used containers in production for many years. It improves the signal to noise of scanners (e.g. CVE) and reduces the burden of establishing provenance to just what you need. -- "Distroless" Container Images The statement above hints at what Distroless is and why you should use it. Just like , Distroless is a misleading term. The most important fact is that Distroless provides neither a package manager nor a . For this reason, the size of a Distroless image is limited. Serverless shell Also, Distroless images are considered more secure: the attack surface is reduced compared to other regular images, and they lack package managers and shells - common attack vectors. Note that some articles this benefit. dispute Distroless images come with four standardized tags: latest : the image doesn't run as , so it's more secure nonroot root : the image contains a shell for debugging purposes debug debug-nonroot Distroless debugging I love the idea of Distroless, but it has a big issue. Something happens during development and sometimes during production, and one needs to log into the container to understand the problem. In general, one uses or to run a shell: it's then possible to run commands from inside the running container. However, Distroless images don't offer a shell . Hence, one needs to run every command from outside; it could be a better developer experience. docker exec kubect exec interactively by design During development, one can switch the base image to a one. Then, you rebuild and run again, and then solve the problem. Yet, you must remember to roll back to the non- base image. The more issues you encounter, the more chances you'll finally ship a image to production. debug debug debug Worse, you cannot do the same trick in production at all. Kubernetes to the rescue At the latest JavaLand conference, I attended a talk by my good friend . In the talk, he made me aware of the command, introduced in Kubernetes 1.25: Matthias Häussler kubectl debug Ephemeral containers are useful for interactive troubleshooting when is insufficient because a container has crashed or a container image doesn't include debugging utilities, such as with distroless images. kubectl exec You can use the debug command to add ephemeral containers to a running Pod. kubectl -- Debugging with an ephemeral debug container Let's see how it works by running a Distroless container: kubectl run node --image=gcr.io/distroless/nodejs18-debian11:latest --command -- /nodejs/bin/node -e "while(true) { console.log('hello') }" The container starts an infinite loop. We can check the logs with the expected results: NodeJS kubectl logs node hello
hello
hello
hello Imagine that we need to check what is happening inside the container. kubectl exec -it node -- sh Because the container has no shell, the following error happens: OCI runtime exec failed: exec failed: unable to start container process: exec: "sh": executable file not found in $PATH: unknown
command terminated with exit code 126 We can use use magic to achieve it anyway: kubectl debug kubectl debug -it \
              --image=bash \      #1
              --target=node \     #2
              node                #3 Image to attach. As we want a shell, we are using bash Name of the container to attach to For some reason I don't understand, we must repeat it The result is precisely what we expect: Targeting container "node". If you don't see processes from this container it may be because the container runtime doesn't support this feature.
Defaulting debug container name to debugger-tkkdf.
If you don't see a command prompt, try pressing enter.
bash-5.2# We can now use the shell to type whatever command we want: ps The result confirms that we "share" the same container: PID   USER     TIME  COMMAND
    1 root     12:18 /nodejs/bin/node -e while(true) { console.log('hello') }
   27 root      0:00 bash
   33 root      0:00 ps After we finish the session, we can reattach it to the container by following the instructions: bash-5.2# Session ended, the ephemeral container will not be restarted but may be reattached using 'kubectl attach node -c debugger-tkkdf -i -t' if it is still running Conclusion Distroless images are an exciting solution to reduce your image's size and improve its security. They achieve these advantages by providing neither a package manager nor a shell. The lack of a shell is a huge issue when one needs to debug what happens inside a container. The new command offers a clean way to fix this issue by attaching an external container that shares the same context as the original one. Danke nochmal dafür, Matthias ! kubectl debug Originally published at on April 16th, 2023 A Java Geek

Stories, News & Mentions about REATIA

Reatia’s Stories on HackerNoon

Reatia's News & Mentions