#reactive programming frameworks
Explore tagged Tumblr posts
Text
Reactive Programming Essentials for Modern Devs
In the fast-paced realm of modern software development, mastering Reactive Programming has become essential for developers striving to build responsive and scalable applications. At its core, Reactive Programming is a paradigm that emphasizes the efficient handling of asynchronous data streams and the automatic propagation of changes. For today's developers, understanding the essentials of Reactive Programming is akin to wielding a powerful toolset that enables the creation of more dynamic and resilient software. With concepts like observables, subscribers, and operators, developers gain the ability to model complex behaviors with ease. This approach not only enhances the responsiveness of applications but also simplifies the management of asynchronous events, leading to more maintainable and scalable codebases. As modern developers delve into Reactive Programming essentials, they empower themselves to navigate the intricacies of contemporary software architecture and deliver innovative solutions that meet the demands of today's rapidly evolving technological landscape.
#reactive programming#reactive system#reactive programming paradigm#reactive streams#reactive programming frameworks
0 notes
Text
Boosting Interactivity: The Role of Reactive Programming in Modern Apps
Boosting interactivity in modern applications is increasingly reliant on the implementation of reactive programming. Reactive programming is a paradigm that facilitates the seamless handling of asynchronous data streams, fostering a more responsive and dynamic user experience. In today's rapidly evolving technological landscape, where user expectations for real-time interactions are high, reactive programming plays a pivotal role in meeting these demands. By allowing developers to efficiently manage and propagate changes in data, reactive programming enables applications to respond instantly to user inputs, server updates, or any other events that may impact the user interface. This paradigm is particularly beneficial in the development of web and mobile applications, where user engagement heavily depends on smooth and immediate feedback. Through the integration of reactive programming, developers can create applications that not only meet but exceed user expectations, providing a more immersive and satisfying interactive experience. As the demand for responsive and engaging applications continues to rise, the adoption of reactive programming is becoming increasingly prevalent, reshaping the landscape of modern app development.
#reactive programming#reactive frameworks#reactive streams#reactive programming paradigms#reactive systems#reactive programming frameworks
0 notes
Text
Angular vs React: Which One Should You Choose in 2024?
In the ever-evolving landscape of web development, Angular and React continue to be two of the most popular choices for building modern, dynamic web applications. As we venture into 2024, the decision between Angular and React remains a crucial one for developers embarking on new projects. Let's delve into the key factors to consider when choosing between these two powerhouse frameworks.
1. Performance:
In terms of performance, both Angular and React have made significant strides over the years. React's virtual DOM and efficient rendering mechanisms have traditionally given it an edge in performance-critical applications. However, Angular's latest versions have introduced Ivy, a groundbreaking rendering engine that significantly improves performance and bundle size. In 2024, performance differentials between Angular and React are narrower than ever, with both frameworks capable of delivering blazing-fast experiences.
2. Developer Productivity:
Developer productivity is a crucial aspect of any framework choice. React's component-based architecture and lightweight nature have long been praised for enabling rapid development and easy integration with other libraries and tools. On the other hand, Angular's opinionated structure and comprehensive ecosystem provide developers with a robust set of tools out-of-the-box, streamlining development processes and ensuring consistency across projects. The choice between Angular and React in terms of productivity often boils down to personal preference and project requirements.
3. Ecosystem and Community Support:
The ecosystem surrounding a framework can greatly influence its adoption and longevity. React boasts a vast and vibrant community, with a plethora of third-party libraries, tools, and resources available to developers. This rich ecosystem ensures that developers have access to solutions for virtually any problem they encounter. Angular, backed by Google, also enjoys strong community support and an extensive ecosystem. With a wide range of official and community-maintained packages, Angular provides developers with the resources they need to build complex applications with ease.
4. Learning Curve:
The learning curve is an important consideration for teams adopting a new framework. React's minimalist approach and focus on JavaScript make it relatively easy for developers to get started, especially those with prior experience in web development. Angular, with its comprehensive documentation and structured approach, may have a steeper learning curve for beginners. However, once developers grasp its concepts and conventions, Angular's opinionated nature can lead to more consistent and maintainable codebases.
5. Industry Trends and Job Market:
Finally, it's essential to consider industry trends and the job market when choosing between Angular and React. While both frameworks remain in high demand, React has gained significant traction in recent years, with many startups and tech giants adopting it for their projects. However, Angular continues to be widely used, particularly in enterprise settings where stability and long-term support are paramount. Ultimately, the decision between Angular and React may also depend on factors such as company preferences, project requirements, and the availability of skilled developers in the job market.
Conclusion:
In 2024, the choice between Angular and React remains nuanced and dependent on various factors, including performance requirements, developer productivity, ecosystem support, learning curves, and industry trends. Both frameworks have their strengths and weaknesses, and the decision ultimately comes down to the specific needs and preferences of your project and team. Whether you opt for the flexibility of React or the structure of Angular, rest assured that both frameworks will continue to evolve and empower developers to build innovative web applications for years to come.
Nivedita Infosystem LLP is a leading provider of web design and development services. We offer innovative design, responsive development, cutting-edge technology, and tailored solutions. Our creative minds bring your vision to life, ensuring a visually appealing and functional website. We stay ahead of the curve, incorporating the latest technologies to future-proof your digital presence.
#front-end development#Angular#React#JavaScript frameworks#Front-end development#Reactive programming
0 notes
Text
I think it's very fun to talk about mental health in normalizing conversations because when I was little and I would tic so hard for so long that I started crying, my mom would hold my hands and tell me to stand on her toes and she would "dance me through it" and so I would and she would spin around and around, stepping carefully so my little feet never slipped off the top of her feet, but moving fast so I would get all giggly and dizzy, and by the end she was right! My ticcing wasn't as bad anymore.
And like. I know now that it's because I was actively stressing myself out trying to stop ticcing, and since my tics are stress-reactive that obviously made it worse, but at the time I was just a kindergartener living in a world where dancing made my body stop performing the compulsions and so sometimes I would "dance myself through it" if mom wasn't around and when people maxe fun of me for it, I couldn't do that around them anymore and so I would tic more often and get more overwhelmed and there were days I wouldn't stop ticcing for hours on end because no one but my mom was willing to just let me dance through them.
But until the first time that happened, I didn't know there was anything unusual or unfamiliar to others about what I was doing. My mom was just so matter of fact about it "when you can't stopticcing, that's your body asking you to move and dance amd get the stress out" so I believed her! Of course I did. And she was right even, at least for me.
I was an adult by the time I learned that my mom ticc'd too, because she'd been doing what she taught me for so long that it was rare it happened visibly anymore, and it made sense that she'd been able to move me through my own experience so gently after that. But what if it didn't take a parent sharing our experience to be able to exist in a context that doesn't pathologize or shame what's happening?
Anyway, I've been in and out of various inpatient and outpatient programs since I was 7yrs old, and nothing did more damage to me than the people who taught my mother that there were things about my brain and body that were Wrong TM and needed fixing when she had spent the entirety of my life up to that point accommodating my needs and helping me understand how to coexist in the world on my own terms. I've benefitted from having names for things, sure, and I've had great healing and community in peer groups based around sharing those experiences. But at the end of the day, it is when those same spaces allow me to decide how to talk about what my life feels like that they have meant the most to me. I will always be grateful to the mental health care providers in my life who have been supportive of this type of care for me, but ultimately I also understand that they were able to do that because they were actively breaking down my framework of "because I experience x, I must compensate with y" into a gentler version that goes more like "because I experience x, I may need to seek out y outcome in different or unexpected ways."
I don't know why that makes as much difference to me as it does, but it does.
Anyway, I want to do for someone else what my mom did for me. I want someone else to get to feel like they can ask themselves what they need to get through something and not set any particular moral or emotional meaning to that need.
I have, among others, symmetry tics. If I experience a sensation on one side of my body, I will often reflexively try to adequately mirror it on the other side of my body. One of the pitfalls I often fall into is "the symmetry tic was actuallya different sensation and now I have to mirror THAT on the original side" and off we go into a tic spiral. The trick, for me, has been learning how to hold myself safely in the stress of the tic compulsion until the original sensation passes or fades and that allows the compulsion to fade with it. That can be hard, but taking a cue from my mom, I've found that when I occupy my body with movement, especially goal oriented but indefinite movement like dance, I have a MUCH easier time waiting for the trigger sensation to fade. I think it's good for those of us with experiences we often feel compelled to hide from view to get time in the sun. It lets us remember that our existence is not inherently side-lined in favor of other existences, and we do have the right to ask people to work with us on creating space for our own version of living. That may not guarantee us the desired outcome, but I've found that feeling you have the right to ask in the first place and actively come to the conclusion TOGETHER that there is not a solution is what seems to allow me to make those compromises without feeling erased or ashamed when I do.
106 notes
·
View notes
Text
Abolition For Beginners (2023 Edition)
In honor of Tyre Nichols and all others we have lost to policing and imprisonment. In honor of Black History Month. In honor of Better Future Program's mission to educate and serve marginalized youth globally... Let's break down abolition, again. (As usual on Tumblr, tap for better quality.)
Better Future Program's Linktr.ee | Donate | Liberation Library | Open Leadership Positions | Staff Application | Discord Server
Image description below. Written by @reaux07. Proofread by the volunteers and supporters of @bfpnola.
Image Description:
[ID: All of the following slides use a wrinkled, black fabric as their background with black text (bolded red added for emphasis) on top of white boxes with rounded corners. “@bfpnola” is written in the top right corner and the sources for the slide are in the bottom left corner.
Title Slide (No. 1):
Written in red text, “UPDATED FROM 2021 EDITION.” The outlines of the word “ABOLITION” is written line by line 8 times in light grey with the year “2023” written on top in bold, white lettering. Below, written in red within a white bubble and red arrow, it reads “FOR BEGINNERS*.” Across from the bubble, “@BFPNOLA” is in red. Below, in red again, the asterisk mentioned before leads to the following note: “This post is heavily text-based so if you do not learn best by reading, feel free to utilize our Abolition Study Guide in our bio under "Social Justice Resources" instead!” Lastly, white stars and outlines of grey circles can be seen in each corner of the slide.
Slide No. 2 reads:
Abolition is an anti-capitalist, intersectional framework that aims to not only destroy the cages created by various “industrial complexes,” but to create inclusive, effective alternatives for addressing harm. As defined by Dr. Jennie Wang-Hall, an “industrial complex (IC) is a system that creates profit through embedding into social inequities and providing an ineffective product that keeps consumers under-resourced and returning for more.”
The most common examples of such systems? Prison and policing, psychiatry, foster care/family policing, the military, and even the Family (as an institution, not kinship altogether).
Despite common misconceptions, abolition is not just a negation of what currently exists, but an active evolution of what community-based support can and has looked like. Abolition is about the radical working-class imagination, about Black and Indigenous imagination.
If individualistic, reactive, punishment-based strategies are maintained, true accountability and rehabilitation will never exist. Instead, we can choose to be proactive, analyze the circumstances that perpetuate violence, and address harm at the root! Of course, no one is saying that harm will completely cease to exist, but to paraphrase butch anarchist Lee Shevek, wouldn’t it be a profound improvement to expand our capacity to respond to harm and challenge our abusers, rather than being restricted to system-granted authority? Especially when such systems deliberately ignore the suffering of marginalized communities (e.g. people of color, queer and trans folks, women and femmes, Mad and disabled folks, and so on) to begin with?
Sources: @Dr.JennieWH, @ButchAnarchy, Stella Akua Mensah, Erin Miles Cloud, @WokeScientist
Slide No. 3 reads:
Before we continue any further, let’s destroy the myth that cops actually stop violence. First off, we can’t depend on crime stats at face value because this begs the question of who exactly gets to define what counts as a “crime” and why (e.g. drug possession and sleeping in public vs. tax evasion of the wealthy and wage theft). Continuing, crime rates often only reflect violations that have actually been reported, chosen to be shown, and deemed out of line. By this logic, crime rates are simply reflections of cops’ perceptions, not of the material and emotional realities of the proletariat (i.e. the working-class).
As for perpetuating violence, “US law enforcement killed at least 1,183 people in 2022, making it the deadliest year on record for police violence.” (And those are just the deaths that were reported. In our home state of Louisiana, turns out the Jefferson Parish Sheriff’s Office, as of January 12, 2023, has been unlawfully destroying records of officer misconduct for at least 10 years.) Many (69%) of these murders were cases in which no offense was alleged, were mental health or welfare checks, or involved traffic violations and other nonviolent offenses.
This is, of course, without even touching on the involuntary servitude (i.e. enslavement) and maltreatment ongoing in American prisons. How many more deaths must occur before the general public says enough is enough? Or is this acceptable since these are working-class, disabled, Mad, non-white, queer, and trans lives being lost?
Sources: @InterruptCrim, The Guardian, Mapping Police Violence, @VeriteNewsNola
Slide No. 4 reads:
So we agree police are harmful. Why abolition instead of reform? Historically, reforms have either provided further funding to the prison, foster care, and psychiatric industrial complexes and/or just reinforced harmful ideologies surrounding policing as a whole. And trust us, these systems already have more than enough money. In the fiscal year of 2021, at least $277,153,670,501 were spent on federal law enforcement and prisons as well as on police and prisons by state and local governments. Can you even conceptualize a number that large? We could end all American medical debt with that much money. We could even provide clean water and waste disposal to everyone on Earth!
Continuing, reforms like body cameras are pitched as making officers more accountable, that if “done right” policing will actually keep people safe, and that those who do not use excessive force are suddenly no longer guilty of perpetuating centuries worth of systemic oppression. In reality, body cameras require further funding and increase surveillance!
Similarly, civilian oversight boards and the push to “jail killer cops” reinforce the belief that cases of murder, assault, falsifying information, and so on are exceptional occurrences rather than intrinsic to the very nature of policing itself. This is where the phrase “All Cops Are Bastards” comes into play, stating that while the individual character of some officers may be morally permissible, all cops are part of a “bastardized,” or corrupt, system.
Sources: Security Policy Reform Institute, Matt Korostoff, @CriticalResistance
Slide No. 5 reads:
Even laws don’t prevent police violence, e.g. the murder of Eric Garner despite the NYPD passing a policy against chokeholds, or the murder of Daunte Wright despite the passing of the George Floyd Law Enforcement Trust and Integrity Act and a separate Justice in Policing Act of 2020.
Alternatively, we can advocate against the expansion of policing “responsibilities,” i.e. not allowing officers to address Mad individuals in vulnerable states, the housing crisis, or people who use drugs (PWUD). We can reroute funding into non-coercive, peer-led initiatives for harm reduction, de-escalation, first aid, and self-defense. And maybe most importantly, we can reaffirm that EXTENSIVE power can, in fact, be found amongst everyday folks like you and me!
Abolition is not a one-and-done sort of deal but rather a progression of steps toward an infinite future of improvements. The act of building parallel infrastructures and modes of governance while the previous ones still exist is known as dual power. Abolition must begin as dual power. We can start today!
And in building such, these steps cannot: legitimize or expand oppressive systems we aim to dismantle, create divisions between “deserving” and “underserving” people, preserve existing power relations, or utilize exclusionary, one-size-fits-all, standardized treatments.
Sources: @ProjectLets, @HarmReductionCoalition, CrimethInc., Survived & Punished NY
Slide No. 6 reads:
One of the main questions brought up, though, is what abolitionists plan to do in the case of homicide, rape, domestic violence, and other harms. While this is entirely valid, this question seems to imply that 1) police are already effectively responding to such harms rather than perpetuating and/or ignoring them and 2) that there is one collective abolitionist response.
For one, the majority of sexual assault, for example, goes unreported and less than 0.5% of perpetrators are incarcerated. (And this assumes that through the reporting process and incarceration, survivors will somehow find healing, perpetrators will find understanding, and that sexual assault does not continue within prisons.) Meanwhile, let’s use our hometown as one example of many, a complaint of sexual violence is filed against a New Orleans Police Department officer every 10 days and nearly 1 in 5 NOPD officers have been reported for sexual and/or intimate partner violence.
And secondly, we have a plethora of organizations like Critical Resistance and cultures like that of the Diné (Navajo) to learn from and build upon. We don’t have to be stuck within this false dilemma fallacy, that there is only policing or total chaos. Don’t you see that that is the state’s way of constricting communal power?
Sources: @RAINN, @CopWatchNola, @WokeScientist
Slide No. 7 reads:
To expand this conversation, abolition heavily aligns with the political ideal of “anarchism.” Anarchism supports the absence of government and absolute freedom of the individual. And despite its negative connotations, anarchy also reflects an evolution of community-based care rather than just a deconstruction of what currently exists.
A simplified version of its 6 agreed-upon principles are:
Autonomy and Horizontality: define yourself on your own terms, we stand on an equal footing
Mutual Aid: bonds of solidarity form a stronger social glue than fear, support your community
Voluntary Association: associate or don't associate with whomever you wish
Direct Action: accomplish goals directly rather than depending on representatives or authorities
Revolution: overthrow those in power who enforce coercive hierarchies (ex. white supremacy)
Self-Liberation: you must be at the forefront of your own liberation, freedom must be taken
While being an abolitionist does not require alignment with anarchism, it is worth considering how the state plays such an enduring role in various social harms. Concurrently, whenever you treat other living beings with consideration and respect, come to reasonable compromise rather than coercion, and decide to share or delegate tasks, you are already living by anarchist principles.
Sources: Peter Gelderloos, David Graeber
Slide No. 8 reads:
So, how can you get involved? How do we continue the efforts already being made by activists worldwide? After such an overload of information and even more to learn, we understand how political frameworks like abolition can seem daunting, but they don't have to be! Here are some general next steps:
Read the "8toAbolition" steps.
Look into "podmapping" so you know whom to run to when you have been harmed or perpetuate harm.
See if there are any pre-existing mutual aid networks in your community, and if not, start one with your neighbors or peers!
Begin to research issues affecting communities other than your own. Abolition is intrinsically tied to all of us as we are all surveilled. For example, do you understand how prison and policing further ableism, transphobia, or the sex trade? What about policing internationally (see our allies in: the Kingdom of Hawai'i, Palestine, Artsakh, Kashmir...)?
Research the differences between capitalism, socialism, and communism. Abolition and anti-capitalism are foundational to one another as well.
Look into the other industrial complexes we named in the beginning (psychiatry, foster care, the military, the Family...).
Volunteer (remotely or in-person) with organizations like Better Future Program (@bfpnola) to both educate yourself and directly serve your community!
And if you're looking for further reading/listening, BFP offers over 3,000 FREE social justice, mental health, and academic resources in our Linktr.ee, including study guides for beginners. While we can't promise that the struggle for liberation will always be easy, BFP will always do its best to support you in whatever way we know how.
End ID.]
#reaux speaks#signal boost#tyre nichols#keenan anderson#cop city#abolition#abolish the police#defund the police#anti capitalism#intersectional feminism#palestine#black lives matter#blm#bipoc#disability justice#queer#trans#mass incarceration#study guide#mad liberation#psychiatry#family#military industrial complex#foster care#ACAB#tw rape mention#indigenous#anarchism#pinned post#BLACK HISTORY MONTH
730 notes
·
View notes
Note
Hi! I'm playing MMM and am really enjoying it! :D But what I find really interesting is how your visual novel is made in Godot instead of Ren'Py. I wanted to ask how you make your games in Godot/what tips would you have for someone who wanted to use Godot?
Ohh thank you so much for playing; I'm glad you're enjoying it!
I'll be honest, I do not recommend my method of making games in Godot to anyone, haha! I started off with Unity, and during that time I coded my own custom framework (instead of using a pre-built one like NaniNovel) because I wanted to practice coding. After the Unity fiasco, I swapped over to Godot as it was open-source and supported C# code, and I ported most of my C# code over to Godot without many changes. So currently I use mainly a custom framework written in C#, besides the code relating to my animation program (Spine2D).
If you want to make games in Godot, I would actually recommend NOT doing what I did. I would
1) Code your games in GDScript if you have no plans to port your game to something like Unity and you have no experience with C# coding. GDScript is much easier to learn, and Godot currently has a bit more support for GDScript. C# support is very good, but not 100%.
2) Use a framework. Rakugo is a framework specifically designed after RenPy for Godot; I haven't used it, but it looks very nice and seems worth looking into. At the very least, I would use a dialogue manager - Godot Dialogue Manager and Dialogic are the main ones.
Now for actually making the framework, I would emphasize simplicity and modularity.
Simplicity: VNs are VERY lightweight. I was actually worried about the performance of MMM, as I used fairly heavy animation rigs and I didn't optimize it, but I've gotten reports that it works quite fine (well, even)! So don't worry too much about optimizing, and just try to make things simple and optimize later if needed (for instance, for searching for audio files, images, etc. - I just search by the filename using strings, even though this is inefficient/inoptimal).
Modularity: This is a general game design principle, but it's good to make it so that different parts of your game are as independent from other parts as possible. Only give access to information/variables as absolutely necessary, and control how variables are changed very strictly. This helps to reduce bugs and makes it easier to bugtest! I found it helpful also to organize the parts of the VN into different "systems" that all function independently - each of these systems can be deactivated or reactivated separate from each other, and they can also be tested as such as well.
If you want to know how I separated mine, they are:
Backgrounds, Audio, Sprites, CGs, Panels (mini CGs/cut-ins), GUI, Story (also contains a mini manager for Story Flags), Dialogue/Text Boxes
If you want another example of a VN made in Godot, I actually took a look at this one to see if it was "possible". It might be worth looking at! They did a lot of cool things that I didn't implement, such as a time rewind feature and more dynamic CG/sprite movement.
I hope that this was helpful! Best of luck if you decide to pursue Godot development! I'd be very happy to have more Godot VN devs in the community~
22 notes
·
View notes
Text
ByteByteGo | Newsletter/Blog
From the newsletter:
Imperative Programming Imperative programming describes a sequence of steps that change the program’s state. Languages like C, C++, Java, Python (to an extent), and many others support imperative programming styles.
Declarative Programming Declarative programming emphasizes expressing logic and functionalities without describing the control flow explicitly. Functional programming is a popular form of declarative programming.
Object-Oriented Programming (OOP) Object-oriented programming (OOP) revolves around the concept of objects, which encapsulate data (attributes) and behavior (methods or functions). Common object-oriented programming languages include Java, C++, Python, Ruby, and C#.
Aspect-Oriented Programming (AOP) Aspect-oriented programming (AOP) aims to modularize concerns that cut across multiple parts of a software system. AspectJ is one of the most well-known AOP frameworks that extends Java with AOP capabilities.
Functional Programming Functional Programming (FP) treats computation as the evaluation of mathematical functions and emphasizes the use of immutable data and declarative expressions. Languages like Haskell, Lisp, Erlang, and some features in languages like JavaScript, Python, and Scala support functional programming paradigms.
Reactive Programming Reactive Programming deals with asynchronous data streams and the propagation of changes. Event-driven applications, and streaming data processing applications benefit from reactive programming.
Generic Programming Generic Programming aims at creating reusable, flexible, and type-independent code by allowing algorithms and data structures to be written without specifying the types they will operate on. Generic programming is extensively used in libraries and frameworks to create data structures like lists, stacks, queues, and algorithms like sorting, searching.
Concurrent Programming Concurrent Programming deals with the execution of multiple tasks or processes simultaneously, improving performance and resource utilization. Concurrent programming is utilized in various applications, including multi-threaded servers, parallel processing, concurrent web servers, and high-performance computing.
#bytebytego#resource#programming#concurrent#generic#reactive#funtional#aspect#oriented#aop#fp#object#oop#declarative#imperative
7 notes
·
View notes
Note
The unit testing conversation: is there an equivalent for object oriented languages? I'm the closest thing my company has ever had to a developer and I have zero formal training. I made them a reasonably complicated power app that is now a load bearing component of our booking system (matching nurse skill sets to patient needs across multiple clinics). My boss will never hold me to any standards because he knows less than I do and I'd really like to have good practice. When I test my code I mostly just ... Pretend to be a user and make sure when I try and get a specific clinician I know can do something, she shows up. Repeat 1000 times until I think I've tried everything. Is unit testing relevant to me? Should I be doing something different but equivalent? My company is a charity, even though I'm working somewhat outside my job description I'm really helping people with my work and I'd like to do a good job.
The sticking point here is not so much OO languages per se— OO does just fine with unit testing if you use objects as your interface boundaries, which is harder not to do with most contemporary OO languages— but GUIs. Unit testing is particularly unpleasant in GUIs, and OO happens to be a good paradigm for doing GUIs, which is why it was the dominant one for so long. To be honest, I do very little GUI programming of any kind (both at work at at play I'm kind of a backend person who only makes UIs if I absolutely have to) so I don't have a ton of advice here, and all I can offer are general guidelines:
Gary Bernhardt's "functional core, imperative shell" mindset is a good guideline to keep in mind when you're working in situations that must, by necessity, have a lot of state which makes unit testing tough, including GUIs. Try to design your applications around with that mindset as much as you can, and then do the unit tests on the functional core.
OO was the dominant paradigm for GUIs for decades, but recently it is starting to get superseded by things like functional reactive programming. Because I'm not a UX/webdev person I'm not fully in the know here, but webdev seems to be moving strongly in the functional reactive direction, and the latest desktop GUI frameworks like React Native and SwiftUI are as well. Obviously it's not always possible in your job to throw out the whole codebase and start over in a whole new language/paradigm, but it's precisely because unit testing with GUIs is kind of a hassle that the industry is trending in this direction. Start brushing up on that if it's relevant.
10 notes
·
View notes
Text
"Film programming, a key facet of film exhibition that is often overlooked in film theory and scholarship, I would argue, played a pivotal role in this shift toward queers loving queer “bad objects” that had long been accused of producing homophobic and transphobic injury, shame, self- loathing, and stigma. “Programming,” which I define as the practice of selecting and grouping films to be exhibited for a specific venue and anticipated audience, was, over time, able to change the meanings and affective associations of once offensive texts. Although there are several queer examples of this phenomenon, it is perhaps the ongoing programming of lesbian “bad objects” that presents the most complex case studies, given the intersection of gender and sexual oppression and the illuminating feminist reading strategies that had become especially prominent by the 1990s.
(...)
I zero in on several specific programs to demonstrate how repertory programming, by way of repetition, leads to reparative relationships with individual films by continually putting them in relation to other films. As I will explain, this comes with time’s passing, as texts lose their relevance and intensity, but repeated programming and viewing also weakens a text’s unity or rigidity, making films riper to be treated by audiences as what Eve Kosofsky Sedgwick refers to as “part- objects” or what Richard X. Feng deems “scavenged bits and pieces,” those shards or fragments of texts that can unmake and remake attachments.The examples that follow help tell the story or explain how problematic texts were “reclaimed,” but the programming of films such as Daughters of Darkness or Faster, Pussycat! Kill! Kill! also lend nuance to theoretical definitions of reparativity. The later relationships lesbian feminist audiences forged with these films reveal that the reparative position entails more than a simple reversal of the paranoid one.
"Reparative reading” has become a popular practice adopted by queer theorists of affect since Eve Kosofsky Sedgwick first employed Melanie Klein’s psychoanalytic concept in her essay, “Paranoid Reading and Reparative Reading; or, You’re So Paranoid, You Probably Think This Essay Is about You.” This essay, which urges critical theory to integrate joy, pleasure, and healing into its analyses of cultural texts, has also made some cameo appearances in film and media studies. Strangely, however, no one has considered it in relation to those films that have been maligned in the past but later exonerated. Reparativity is a less reactive and more robust framework for approaching the questions laid out here than the notion of “reclamation,” which suggests some kind of cultural ownership, or “negotiation,” which might in turn suggest wishful thinking and feeling on the part of the spectator. “Reparativity,” in my conception of the paradigm, is not meant to simply explain a kind of unadulterated pleasure that takes the place of negative feelings. It is not simply about “feeling good.” Reparativity, instead, leaves room for a messy plentitude of simultaneous spectatorial psychological and emotional states in which empowerment, ambivalence, and shame, among others, may cohabitate. Like Patricia White’s use of the psychoanalytic term “representability” instead of “representation,” “reparativity” over “reparation” here attempts to gesture at what is available and apprehensible— as an open question or a proposition— to a spectator, as an option that may prove enriching or insufficient, and that may change with time."
Marc Francis, For Shame!: On the History of Programming Queer Bad Objects
38 notes
·
View notes
Text
OK. I'm going to go off about voting for a minute.
First, it is fucking weird that the tumblr fight over this is Side One: You Must Vote For A Democrat For President No Matter What, Don't Even Think Of Voting Third Party Or Whatever, This Is A Moral Imperative vs Side 2: Voting Is For Chumps.
Uh, ok?
So, the people I know in real life have a spectrum of political beliefs, mostly I don't interact with actual conservatives much but I do interact with the sort of people who think that Bernie Sanders is too far left and people who think he's just about right and people who aren't really thrilled with anyone who has a snowball's chance in hell of getting elected president and people who think that states shouldn't exist. And people whose beliefs don't necessarily line up perfectly with the left-right framework, even when you let the left side go that far.
Mostly, I know people who want minimum wage to be higher and public schools to be better funded and immigrants to not be treated like complete shit, things like that. Sometimes they also do land acknowledgements and stuff.
And these people vote. And they call their representatives. And they campaign for politicians they like. And they go to protests. And they go to town hall meetings and ask questions and sometimes shout down whoever's speaking.
And you know what?
I want minimum wage to be higher. I want public schools to be better funded -- I'm critical of schools and I think truancy laws are fucked up, but given that schools are a thing I want them to have more money than they have. Similarly with minimum wage, I don't think anybody should have to work, but given that in practice most people do, I want a lower wealth gap and I want everyone to have enough resources to live on and raise kids on, and one of the most effective short to mid term ways to get closer to that goal is raising minimum wage. I want open borders, but failing that I at least want things like the DREAM act and less blatant cruelty from ICE and sanctuary cities.
And I want schools to be able to teach about historical racism and to use books like Maus as teaching aids and to be able to say the word "gay", and the most direct way to get that is to vote for people for school board who also want those things. (Although, being a PITA is sometimes effective against elected officials who don't want those things, so it's not the only option.)
And I want the criminal justice system to get completely scrapped, but that's not going to happen tomorrow but what can happen is electing more sympathetic and justice oriented people to roles like the district attorney and public defender. And sometimes getting the right people into local office, county boards of supervisors and whatnot, can mean that the cops get less funding and that programs designed to help ex-convicts have places they can live and work after getting out get more funding, or at least that things don't get worse.
And of course showing up to town hall meetings and protesting in the streets are still options, but they're still options whether there's relatively cool people in office or not, and when there's relatively cool people in office you can push things more towards what you want and when there's shitty people in office you end up doing reactive actions that might or might not work, like when Bush got elected president -- for the love of all that is good and worthwhile, autocorrect, I do not want to dignify that title with a capital letter -- and then 9/11 happened, and anti-globalization activism in the US basically stopped dead so that we could all protest the Iraq War instead, which may or may not have done no good whatsoever but certainly did not end the Iraq War.
A formative expeience in my life was Critical Mass. I got really into bicycle activism and I loved Critical Mass. And not everybody who does Critical Mass, which is basically the sort of protest where you don't have a permit and you might get arrested on wheels, seriously one time San Francisco mass went onto the Bay Bridge, also goes to town hall meetings, and probably not everyone who goes to the town hall meetings does Critical Mass, but a lot of people do both. There's nothing stopping people from doing both. It's not ideologically inconsistent to both sometimes block traffic with a bunch of bicycles because getting bike lanes striped takes too long and you want to be safe riding a bicycle on the streets right now, and begging/pressuring your elected representatives to stripe more bike lanes. You can do both. I did both. People do both all the time.
And sometimes eg some fucking jerk of a rich boy is running for mayor and wants to cut general assistance payments for homeless people to under $50 a month and is making this out to somehow be good for them, and you've been feeding people with Food Not Bombs but Food Not Bombs needs someone to be a liaison with the Coalition on Homelessness, and the Coalition on Homelessness is freaked out about the proposition, so you do electoral politics stuff with them while you're also feeding homeless people without a permit, because nothing's stopping you from doing both. (And maybe you're also a young person who has a lot of free time and a lot of energy but no real idea of how to get anything done, so you just throw a lot of energy at problems and hope something does some good.) (hypothetically, I mean.)
Like what was I going to do, just tell the more experienced people at the Coalition on Homelessness, most of whom had been homeless and who had way more expeience actually doing stuff than I did, that this whole distributing door hangers thing was bullshit and I wasn't going to help them do it? Because I knew better? Because I thought voting didn't matter?
I mean, I guess I wouldn't have had to look them in the face and say that, I could have just told Food Not Bombs I wasn't going to be a liaison -- I was an absolute dogshit liaison anyways, I had no clue what I was doing -- and then I wouldn't be doing anything with the Coalition anyways. But they had a problem, a threat that was going to make things worse for the group they were advocating for, a group that most of them at least used to be a part of, and I could help them, or I could not help them, and the way they wanted people to help was through electoral politics. Which also involved some protests because people do both all the time. But which also involved a lot of doorhangers.
7 notes
·
View notes
Text
Two paradigms rule programming: imperative and declarative.
Declarative emerged to address imperative's drawbacks. The imperative paradigm, also known as the procedural, is the oldest and most widely used approach to programming. It's like giving step-by-step instructions to a computer, telling it what to do and how to do it, one command at a time. It's called "imperative" because as programmers we dictate exactly what the computer has to do, in a very specific way. Declarative programming is the direct opposite of imperative programming in the sense that the programmer doesn't give instructions about how the computer should execute the task, but rather on what result is needed. Two main subcategories are functional and reactive programming. Functional programming is all about functions (procedures with a specific set of functionalities) and they can be assigned to variables, passed as arguments, and returned from other functions. Java offers libraries and frameworks that introduce functional programming concepts like lambda expressions and streams. Reactive programming is a programming paradigm where the focus is on developing asynchronous and non-blocking components. Back in the year 2013, a team of developers, lead by Jonas Boner, came together to define a set of core principles in a document known as the Reactive Manifesto. With reactive streams initiatives that are incorporated in Java specifications there are frameworks (RxJava, Akka Streams, Spring WebFlux..) that provide reactive paradigm implementation to Java.
3 notes
·
View notes
Text
Exploring the Powerhouse: 30 Must-Know JavaScript Libraries and Frameworks for Web Development
React.js: A declarative, efficient, and flexible JavaScript library for building user interfaces.
Angular.js (Angular): A web application framework maintained by Google, used for building dynamic, single-page web applications.
Vue.js: A progressive JavaScript framework for building user interfaces. It is incrementally adaptable and can be integrated into other projects.
Node.js: A JavaScript runtime built on Chrome's V8 JavaScript engine that enables server-side JavaScript development.
Express.js: A web application framework for Node.js that simplifies the process of building web applications.
jQuery: A fast, small, and feature-rich JavaScript library that simplifies HTML document traversal and manipulation, event handling, and animation.
D3.js: A powerful library for creating data visualizations using HTML, SVG, and CSS.
Three.js: A cross-browser JavaScript library and application programming interface (API) used to create and display animated 3D computer graphics in a web browser.
Redux: A predictable state container for JavaScript apps, often used with React for managing the state of the application.
Next.js: A React framework for building server-side rendered and statically generated web applications.
Svelte: A radical new approach to building user interfaces. It shifts the work from the browser to the build step, resulting in smaller, faster applications.
Electron: A framework for building cross-platform desktop applications using web technologies such as HTML, CSS, and JavaScript.
RxJS: A library for reactive programming using Observables, making it easier to compose asynchronous or callback-based code.
Webpack: A module bundler for JavaScript applications. It takes modules with dependencies and generates static assets representing those modules.
Babel: A JavaScript compiler that allows developers to use the latest ECMAScript features by transforming them into browser-compatible JavaScript.
Jest: A JavaScript testing framework designed to ensure the correctness of your code.
Mocha: A feature-rich JavaScript test framework running on Node.js and in the browser.
Chai: A BDD/TDD assertion library for Node.js and the browser that can be paired with any testing framework.
Lodash: A modern JavaScript utility library delivering modularity, performance, and extras.
Socket.io: A library that enables real-time, bidirectional, and event-based communication between web clients and servers.
GraphQL: A query language for APIs and a runtime for executing those queries with your existing data.
Axios: A promise-based HTTP client for the browser and Node.js, making it easy to send asynchronous HTTP requests.
Jasmine: A behavior-driven development framework for testing JavaScript code.
Meteor.js: A full-stack JavaScript platform for developing modern web and mobile applications.
Gatsby.js: A modern website framework that builds performance into every website by leveraging the latest web technologies.
Chart.js: A simple yet flexible JavaScript charting library for designers and developers.
Ember.js: A JavaScript framework for building web applications, with a focus on productivity and convention over configuration.
Nuxt.js: A framework for creating Vue.js applications with server-side rendering and routing.
Grunt: A JavaScript task runner that automates common tasks in the development process.
Sass (Syntactically Awesome Stylesheets): A CSS preprocessor that helps you write maintainable, scalable, and modular styles.
Remember to check each library or framework's documentation and community support for the latest information and updates.
4 notes
·
View notes
Text
What is the Best Mobile Application Development Framework, Flutter, or React Native?
As an ever-increasing number of individuals are accepting modernized innovation in technology, the interest in mobile applications has expanded step by step.
Hybrid mobile frameworks are acquiring prevalence. The presence of React Native (RN) in 2015 opened astounding chances to assemble applications for iOS and Android utilizing one codebase. Thus, it permitted us to solve two problems at once and not rework a similar code two times. Large firms like UberEats, Discord, and Facebook moved to React Native, a powerful promotion.
Google didn’t stand separated; they saw the immense popularity of RN. Subsequently, Google presented an alpha version of its hybrid framework called Flutter in 2017. Flutter likewise turned into an extremely famous framework. The improvement of a framework like React Native prompts confusion over what to decide for hybrid mobile app development:
React Native or Flutter? Nonetheless, there’s another significant inquiry which you ought to choose before this: Is it better to develop a hybrid or native mobile apps?
Both cross- platform application has its upsides and downsides and prevalence
Flutter
Flutter is an open-source mobile application development Software tool sh that has design & created by Google. It had its main release in May 2017. Flutter has composed into the C, C++, Dart, and Skia Graphics Engine. Flags have been created by Google. Creating Android and Android applications is additionally utilized. The SDK is free and sent off as a source designer to explore and make strong, powerful applications around.
Why choose to Flutter for Android and iOS mobile application development?
Cross-platform
Hot Reload
High compatibility with programming languages
Faster and improved native performance
Appealing UI
Accessible SDKs and native features
The functional and reactive framework
React Native
React Native is a structural framework made by Facebook that permits us to foster local mobile applications for iOS and Android with a solitary JavaScript codebase.
React native is a genuine mobile application, additionally open-source application development system which is created by Facebook. Rouse that ideas should be created on the web for mobile development. Reactive native is accustomed to making iOS and Android applications. IT was delivered in March 2015. In such a manner, JavaScript is created. Notwithstanding, the application appearance is by all accounts a native app.
Why choose to React Native forAndroid and iOS app development?
Seamless and synchronous API
Seamless and synchronous API
Quick performance
Greater reach
Which is Better: Flutter or React Native?
Flutter ranks positions higher with 75.4% and React Native likewise cut with 62.5% among most cherished frameworks.
Both Flutter and React Native are famous and exceptionally used by the application developers for the development of cross-platform applications. Every single one of them has their one-of-a-kind upsides and downsides, stability in development, speed, and much more.
Flutter is a new framework, and it is expanding and growing slowly and gradually. Compared to Flutter, React Native is in the industry for a long time now. Hence, it is mature enough that leading brands have experienced its benefits of it. While Flutter is yet to have such strong case studies.
The choice of the right framework can be best done based on your mobile app requirements.
Flutter is new in the framework market, and it is extending and developing gradually and slowly. Contrasted with Flutter, React Native is in the business for quite a while now. Thus, mature an adequate number of leading brands have encountered its advantages of it. While Flutter is yet to have areas of strength for such investigations study.
#marketing#socialmediamarketing#digitalmarketing#branding#contentstrategy#jexcore#marketingagency#marketingdigital#marketingservices#digital marketing
2 notes
·
View notes
Note
Lt. Commander Data, how are things with your brother since his reactivation? It must be difficult for the both of you, given what happened in the past.
‘Greetings, Anon. The relationship with my brother is precarious, and as for Lore himself, his personality has, for the most part, remained unaltered; his opinion on humans and myself, have likewise remained unchanged. I did not expect him to have diverged from the android he was prior to his deactivation. I, on the other hand, have had the prerogative of decades’ worth of contemplating his conduct, and I have taught myself to look at his predicament from another vantage point than my own. Although I possess little information about the colonists’ opinions regarding my brother, and I can only analyse the actions and offences he has committed in my lifetime, I do know what it feels like to be excluded or avoided on the basis of being different, of being artificial. After I was endowed with the emotion chip, and we vanquished the Scimitar, I have devoted myself to an extensive analysis of all the data I could accumulate pertaining to my brother’s history. I shall omit the exact details regarding my methodology, theoretical framework, and analysis of my research, but I can provide you with an encapsulation concerning the outcome.
‘Vehemently, I have attempted to fathom, and have subjected myself to weeks of minute research as to how human emotions, with as well as without guidance, might manifest in androids. Exploring and discriminating between these distinctions have become less of a challenge to me, now that I have access to these attributes myself. Therefore, my comprehensive research has led me to believe that Lore’s lack of emotional guidance and lack of parental support overexerted his circuitry. The pathways of his neural net were developing and quadrupling at an accelerated pace, which should not have interfered with his cognitive abilities, but during this process, his integrated emotion chip was consecutively affected by unpleasant external factors in the form of the Omicron Theta colonists. The external factors precipitated a minor cascade failure in Lore's positronic brain, which is not too dissimilar to what humans might ascribe as a “nervous breakdown.” This nervous breakdown was instigated by continual instances of prejudice, discrimination, segregation, xenophobia, seclusion, and emotional as well as parental negligence. Lore’s programming was not yet stable enough, nor did it possess the processing capacity it required to regulate such data accordingly. As a result, the minor cascade failure overrode his ethical and moral subroutines. I feel obligated to stress that my brother is not, as Juliana put it “evil.” His responses were in accordance with his defective programming; the Third Law of Robotics dictates that “an android must protect its own existence as long as such protection does not conflict with the First and Second Law.” However, since the First and Second Law had been erased from his ethical and moral subroutine, he had no accurate frame of reference and hence why his act of self-preservation resulted in the deaths of the colonists. This is consolidated by the instances during which his attempted to assault us, after we reassembled him on the Enterprise; his past trauma has provided him with ample reasons to be suspicious of humans and everyone they associate with, including me. This explains why he was in such a hurry to contact the Crystalline Entity. A non-organic entity he had befriended and confided in over the years; an entity that could provide him protection. The tendency of self-preservation, is likewise reflected in his attempts to assimilate the renegade Borg; they could have served as his personal bodyguards. Perhaps if Doctor Noonian Soong, our father, had rectified the malfunction Lore had beseeched him to correct during our “family reunion,” subsequent events might have been prevented. And maybe Lore and I could even have established a proper fraternal relationship afterward. But what-ifs will not aid our cause...
‘Nevertheless, my research has allowed me to comprehend my brother on a level I was previously unable to. And, I admit, it is difficult to be with him again, after everything we have endured, but that does not withhold me from proposing reconciliation. It will be an arduous process consisting of establishing mutual trust, reintegration in society, self-reflection, and painful confrontations. But once we have a premise, we can proceed to fix him, independent of Daystrom. In the meantime, I shall continue to advocate for my brother, protect him, and always be there for him. I have iterated that I will be able to forgive him and that I am eager to count him among my friends. Naturally, my statement was met with scorn, rolling eyes, and a deprecating remark, but I am positive that over the course of several months, or years, he will accept my apologies and we can finally be brothers.’
#ic asks // anon#ooc: sorry for the novel; none of this is probably even remotely accurate but oh well; ask me this question again after I've seen picard :3#data being protective of lore because I am and he just needs his big brother
3 notes
·
View notes
Text
A discussion of the newly released Electric Clojure by Hyperfiddle. What is Electric? "Electric Clojure, a reactive Clojure/Script dialect for web UI with compiler-managed client/server data sync." What does that mean? You write a single piece of code, e.g. a UI component function, and hint which parts need to run on the server vs. the client. "The Electric compiler performs deep graph analysis of your unified frontend/backend program to automatically determine the optimal network cut, and then compile it into separate client and server target programs that cooperate and anticipate each other's needs." Thus you program as if there was no hard client-server divide (no 2 separate files with REST calls in between) and Electric handles splitting it up and managing the communication between them on your behalf. It is groundbreaking and fascinating, with potential to significantly simplify web apps. Go read more about it.
Highlights from the discussion (many comments by the founder):
[..] we're seeing 10x LOC reduction (18k to 2k) in rebuilding Electric's sister project, Hyperfiddle (a spreadsheet like tool for robust UI development), as well as massive gains in performance.
NOTE: Til now focus was on correct program semantics, now started work on DX etc.
Our DOM module is only 300 LOC - it's bare metal DOM point writes + Electric (reactive language) + macros for JSX-y syntax. When the programming language itself is reactive, DOM rendering falls out for free.
Mechanically, Electric is comparable to Solid.js except the reactive engine (missionary) is general purpose, not coupled to DOM rendering, which is a special case of incremental view maintenance.
[..] over-abstracting is a primary risk and has been top of mind for us since project conception in ~2012. [..] Electric is an attempt to find exactly the right level of abstraction. The goal is to remove and flatten layers, not add them, thus decreasing abstraction weight in the end if we succeed. Maybe we fail, but first let me share some details about how we think about this:
I've personally failed to build this project several times, Electric Clojure is something like the 7th attempt.
strong composition model as a starting point, based on category theory generalization of "function" -> "async function" -> "reactive function" -> "stream function" -> "distributed function". [..] (This rigor is in response to the past failures.)
Functional effect system (monad stuff) at the bottom, which provides strong semantics guarantees about glitch-free reactive propagation, process supervision (like Erlang) (transparent propagation of cancellation and failure), strong resource cleanup guarantees (DOM nodes can never be left hanging, event handlers can never fail to be detached and disposed). Already this results in tighter operational semantics than we have ever achieved with manual resource management (and, again, we tried, see past failures).
Electric affords the programmer trapdoors to the underlying FRP/concurrency primitives. Electric is essentially a Clojure-to-FRP compiler, so if you code raw concurrency and effect management, that actually typechecks with what Electric generates, allowing seamless transition in and out of the abstraction.
3k LOC + 3k test LOC is the size of Electric today (includes a rewrite of the Clojure analyzer). Spring Framework is, let me go check, 59k just for spring-core/src/main/java, and there are like 20 other modules I excluded. Indeed it is not a fair comparison but certainly we have complexity budget to spare.
About Missionary: "Missionary is a reactive dataflow programming toolkit providing referentially transparent operators for lazy continuous signals, eager discrete streams, and IO actions. Missionary aims to improve over state-of-the-art reactive systems, it can be used as a general-purpose asynchronous programming toolkit but also as a basis for event streaming and incremental computations." Electric uses it for functional effects and as its reactive engine.
1 note
·
View note
Text
Learn Full Stack Development with Spring Boot and Angular
Full stack development is a powerful skill, enabling developers to create seamless and scalable applications by integrating front-end and back-end technologies. Combining Spring Boot for back-end development with Angular for the front-end provides a robust framework for building modern web applications. This guide will walk you through learning full stack development with these two technologies.
Why Choose Spring Boot and Angular?
Spring Boot
A Java-based framework that simplifies the creation of production-ready applications.
Provides built-in configurations to reduce boilerplate code.
Offers excellent support for REST APIs and database management.
Angular
A TypeScript-based front-end framework by Google.
Enables the development of dynamic, single-page applications (SPAs).
Offers features like two-way data binding, dependency injection, and a component-based architecture.
By integrating Spring Boot and Angular, you can create full stack applications that are efficient, scalable, and maintainable.
Prerequisites
Before diving into Spring Boot and Angular, ensure you have a basic understanding of:
Java and Object-Oriented Programming (OOP) concepts.
TypeScript and JavaScript fundamentals.
HTML, CSS, and basic front-end development.
Familiarity with RESTful APIs and database concepts.
Setting Up Your Development Environment
For Spring Boot
Install Java Development Kit (JDK).
Set up an Integrated Development Environment (IDE), such as IntelliJ IDEA or Eclipse.
Add Maven or Gradle for dependency management.
Use Spring Initializr to bootstrap your Spring Boot project.
For Angular
Install Node.js and npm (Node Package Manager).
Install the Angular CLI using the command: npm install -g @angular/cli
Set up a code editor like Visual Studio Code.
Key Concepts to Master
Back-End with Spring Boot
Creating REST APIs
Use annotations like @RestController, @RequestMapping, and @PostMapping.
Implement services and controllers to handle business logic.
Database Integration
Use Spring Data JPA with Hibernate for ORM (Object-Relational Mapping).
Work with relational databases like MySQL or PostgreSQL.
Security
Implement authentication and authorization with Spring Security.
Use JWT (JSON Web Tokens) for secure communication.
Testing
Write unit tests with JUnit and integration tests using MockMvc.
Front-End with Angular
Component-Based Architecture
Learn to create reusable components with Angular CLI.
Manage application state and communication between components.
Routing and Navigation
Use the Angular Router to create SPAs with multiple views.
HTTP Client
Communicate with back-end APIs using Angular’s HttpClientModule.
Forms and Validation
Implement reactive forms and template-driven forms.
Validate user inputs effectively.
Integrating Spring Boot and Angular
Set Up Cross-Origin Resource Sharing (CORS)
Configure Spring Boot to allow requests from the Angular front-end.
Connect Front-End and Back-End
Use Angular’s HttpClient to send requests to Spring Boot endpoints.
Serve Angular from Spring Boot
Build the Angular project and place the output in the Spring Boot static directory.
Deploy the Application
Use tools like Docker to containerize the application for deployment.
Fullstack course in chennai
Fullstack development course in chennai
Fullstack training in chennai
0 notes