Answer:
Hope this helps pls mark brainiest
Explanation:
<h2> </h2><h2>So we know Student B is gonna get a computer, but its not stated if its A desktop or laptop. hmm,.. So ima do both for the desktop he would what a computer with "Ethernet Storage Fabrics: 25GbE, 50GbE" because If he going to do videos in todays standers it would be in 4k and 8k. he would also need at least 16 of ram if not 32gb. and since he has no cap budget I would personally go for the i9, but he can go for the i7, not much of a fan of the i5 for video productive, for storage he would need a lot for video editing or other stuff so I would go for the main boot (sys) a and for the actually storage for the videos I would go for a with good rpm. For I would go for something with 8-10 or higher.</h2>
Answer:
Hi DancingGrace! The issue with the code is that it is trying to extend multiple classes which is not a feature in Java programming.
Explanation:
The extends keyword allows a class to use the attributes and properties of the base class it is extending and add more features and properties into it's own class. This is useful in programming where different models share similar properties but are slightly different. An example would be designing a class for Car and Bike. Both have some similar properties like wheels, engine, etc, however they are different forms of transport. A useful implementation would be to define a class called Vehicle with similar attributes, and have the Car and Bike extend it.
<h2>Laptops and Tablets are cool, classic, and have a business-y vibe to them but Destop Computers are preferred because they're way more adaptable, have a lot of useful ports USB, SD, etc, and computer monitor vary a lot and anytime you want you can get one with lot's of RAM and Memory so that's very cool, and convenient of you're a businessman.</h2><h2>So what would I choose? I would probably choose A Laptop, but you know, it's business. :)</h2><h3>Good Luck on your Studies!</h3><h3>David Edward.</h3>
This gap between user-designer communications <span>can cause a good project to go bad i</span>f the user is not able to process what is required to be fixed in order for the project to run smoothly. The user may have one way of fixing something while the designer has another. In this case, the designer understands how the project fully works while the user does not and this may end up compromising the whole project.
The law that “designers are not users” and “users are not designers” should always be followed.
