reactstrap VS Spring Boot

After the app creation process completes, navigate into the app directory and install Bootstrap, cookie support for React, React Router, and Reactstrap.

3 months is not a long time to learn web development! I made my first web site in 1995 and I've been doing it ever since. On a bad day I still get flustered with React and CSS. How much of a skilled trade like plumbing or carpentry or welding or being an electrician could your learn in 3 months?

The "ultimate" web developer has a wide range of skills that almost nobody has. For instance, the ultimate web developer knows some systems programming (will need it when things go terribly wrong) but also is a talented artist that can not only draw images but can also make systems of images, colors, fonts and other assets that combine as required, create 2d- and 3d- animations, etc. (Thank God people decided it isn't cool for web sites to play sounds or you might have to be a musician and/or sound engineer too!)

There is a level of skill in graphic design that is less than that where you understand how to pick colors, pick fonts, make harmonious layouts. It's a subject I am still learning: from time to time I have a rather serious "graphics" hobby like printing a series of decorative cards, photography projects, etc. I learned a huge amount when I had to to an accessibility overhaul for the site I work on, not only in terms of accessibility standards but how to think about graphic design. (e.g. when you pick colors, the first thing to think about is how bright or dark they are, any design that makes sense in color makes sense in black and white. I am a fan of Ansel Adam's writings on photography for this reason. In fact I learned a lot about composition when I picked up a book on portrait photography the other day.)

CSS is hard. It has that graphic design knowledge as a background, yet few graphic designers have the discipline of programming that CSS really demands. You can get hung up on the details of selectors, inheritance, padding, borders, margin collapsing, all that. You won't really be in control until you know how to look up anything in the official docs, but those docs are sprawling

https://www.w3.org/TR/css-2022/#module-classification

I count at least 50 documents that are "normative references" right there! (Clearly not something you can master in 3 months)

On top of that there is the complexity of "CSS frameworks" built on top of CSS. All of them have additional concepts to learn but they don't absolve you from having a complete understanding of what lies beneath.

To pause for a sec, note that web devs usually work in teams -- so you don't have to go it alone. A designer might make you comps in Photoshop and it is your job to write HTML and CSS to make it look like that. Hopefully you have a tester, sysadmin, marketing people, etc. If I had my way somebody would plan how CSS is used systematically to help multiple designers and devs do the right thing.

Then, React. I feel completely in control with components I write myself, but the sheer number of third-party components that you might choose or that you might encounter in React code somebody else wrote.

You'd image a widget set like

https://reactstrap.github.io/?path=/story/home-installation-...

or

https://mui.com/material-ui/

would let you largely ignore HTML and CSS and you might really make some apps where the "XML" looks like a desktop application but marketing some day will require you to customize these radically or you will encounter some application that mixes three widget sets and seven other third-party components and you need to understand all of that stuff to be in control.

Sometimes you are more in control, sometimes you aren't. When you're not in control you appear to make rapid progress sometimes but you also get stuck and things that you'd think would be quick take a long time and you know... That's what is.

But... We are not in perfect control and many businesses make many minor and major mistakes in their infrastructure, still make money, still pay coders.

I'd say though that there is something wrong with React. I like how React can draw any application I imagine, particularly with

https://docs.pmnd.rs/react-three-fiber/getting-started/examp...

but it does not have a real plan for how information flows in your application. I like the way props flow downwards, but those components that pass context are a disaster. React provides you with tools you can use to implement your own plan... Or maybe barrel ahead without a plan which won't be bad if you are lucky and your app is small, otherwise things may get worse and worse and things the boss thinks look easy are really very very hard and you'd better get control!

So your 3 mo bootcamp is just the beginning of learning the trade. You can get a job in the industry already but if you do you may find it is SNAFU in many places, it is not unusual for a developer to take several weeks to be able to put together a dev workstation, build and run the system. Ideally you get in with people who model good behavior but even then you will have times you are feeling unproductive because you are not productive because of situations not entirely in your control.

Other than that you can do side, personal, family and friends projects. Find some answers to the above problems that let you make the kind of app that you want to make, try to spend as little time as possible learning frameworks and languages and instead focus on a small toolbox where you can pound out little projects where you feel in control and that will build your confidence and skills until you are ready to swim with the sharks.

Great, we were finally able to make use of the plethora of reactstrap components like Spinner, Button, Layout and a host of others. There are more to it as this is just a tip of the iceberg. I recommend you go through reactstrap official documentation to get a feel of the numerous other UIs that they provide.

Reactstrap has 10.1K stars, 1.2K forks, 231K users, and 239 contributors. According to npmjs.com, it has 374,493 weekly downloads.

I tried with reactstrap, and yes has bootstrap css classes as components (e.g ) but you have to includes all bootstrap styles:

I've followed https://reactstrap.github.io/ and got it working. But bootstrap is now applied to all the site, because I have this

I start developing a React app with reactstrap. I followed the Get Started running the following commands :

I do a lot of enterprise application development in a very small team. It's important for us to create applications that work on any device with a modern web browser that is connected to the Internet and not just a LAN or VPN. The apps must authenticate thru single-sign on that is federated with the company Active Directory. The apps need to rely on commonly available libraries like React and Bootstrap albeit through ReactStrap, and they must be spartan and similar. That is to say that users need to be able log onto all of the various apps the same way, and the apps need to do simply what they need to do with no bells or whistles. Furthermore, one app should look and feel like the others. We don't want to confuse users by making them feel like they need to learn a whole new system for every new application.

I'm new to Material UI and ReactJS. I've been playing around with Create-React-App (CRA) and reactstrap. My question is, can I use Material UI and CRA together to build an app?

- Usually manually wired and configured vs the spring boot "starter" pattern of having libraries that automatically do some of the manual setup work for you: https://github.com/spring-projects/spring-boot/blob/main/spr...

I wish more client library sets had the feature-matrix that the pulsar one does, because in practice most end up being the same: Java supports everything because it's either built in the same codebase or is the most used client and gets the most support, while the dotnet client codebase has many feature-requests or performance improvement issues, often leading to a "third-party client" being created.

https://github.com/spring-projects/spring-boot/pull/39754/co...

If you’re currently running with an earlier version of Spring Boot, I recommend that you upgrade to Spring Boot 2.7 before migrating to Spring Boot 3.0. It minimizes compatibility issues as much as possible.

Okay, we need to build the game? No problem, we will use Spring Boot and Swing!

It's weird that some people including you directly attack my competence. As a power user you should have plenty of experience getting something to work that is not properly document, does not work how the documentation promised it to, or has weird problems on top of it. Look at idiotic things like this:

https://github.com/spring-projects/spring-boot/issues/33044

Take any similar issue and you'll see a bunch of people who try to find a solution for them because they just aren't repeatable at all. The underlying issue is the auto configuration doing things you can't follow quite properly. It's like it wasn't mean to be understood. Issues like the one I linked above also show me that the spring dev crowd also doesn't understand the ecosystem anymore. The problem is complexity and automagic.

An interested reader can decide for themselves:

https://github.com/spring-projects/spring-boot/tree/main/spr...

Explicitly decoding URL query parameters occurs less often because many frameworks, including Spring Boot, handle decoding automatically.

https://aws.amazon.com/lambda/ https://aws.amazon.com/api-gateway/ https://aws.amazon.com/serverless/sam/ https://aws.amazon.com/cloudformation/ https://aws.amazon.com/s3/ https://spring.io/projects/spring-boot https://start.spring.io