Toxocious

You're getting a lot of Linux desktop answers here. That's fine, but that's not really where Linux is the most popular. Linux is first and foremost a server OS. That's where it's gained the most popularity and where it has the most fans. Here's why I always choose Linux servers (Ubuntu specifically):
 
* Stability
A Linux server is rock solid and it typically will not fail on you in unexpected ways. Apple had that "it just works" marketing campaign years ago, and while it wasn't really true then or now for lots of their stuff. But this is 100% for your core Linux OS and toolchain. Core utilities like cron, grep, bash, sed, and more just work flawlessly.
 
You've also got stability in how the tools work over time. The first Linux server I ever administered was a Debian server running Debian 3.1 Sarge. Right now, I'm running Ubuntu 22.04 on most servers and lots of what I learned on Debian Sarge still serves me well.
 
* Software Availability
There are an absolutely staggering number of applications on Linux. Ubuntu's got 5968 arm64 packages in the main repo and 57941 universe packages.
 
If there's a task that you want your server to do, odds are extremely good that there's something in the repo that'll do it.
 
* Scripting and daisy chaining
Once you find some software in the repos, it's incredibly easy to write a bash script that'll do what you want done. And you can even run that script on other servers with the software installed, no problem. 
 
And if actually just found two scripts, each that does half the job you want it's trivial to pipe the output of one script into another. And there's no limit to how many times you can do it. I've got log search scripts that concatenate a bunch of files and narrow down the output multiple times before giving it to me. A book I like Wicked Cool Shell Scripts contains a bash script which is just hangman, the word game. 
 
Seriously the power of bash scripting and POSIX standards is one of the things that every Linux server admin loves. 
 
* Software development
If you can't find something that does just want you want, and you can't hack a script together that'll do it then there's no easier platform for development than Linux servers. Every compiler is available for it, and everything "just works" (aside from your own code, but that's what stackoverflow is for).
 
Those are just the things that come to me off the top of my head, there are probably loads more. 
 
It's just a great OS that does what you need it to do, and it's got enough power and flexibility to handle anything you can manage to throw at it.

right from the start.
 
the sort of role you apply for changes as your skill level and experience changes, but the moment you find a position that is appropriate to your skill level (junior, since you have no prior experience nor a degree) you may as well try.
 
also - impostor syndrome is rampant in IT as a whole, and probably far outside of that.
Adam Savage has a talk on impostor syndrome in his field(s) of work.
(if the timestamp didnt come trough with the lnk, at around 16:30 in the video)

An official LTT keyboard is unrealistic tbh. As someone else mentioned, the keyboard market is already super saturated. MAYBE LTT partners with like Ducky, Keychron, Drop, etc. for a limited run.
 
OR we go the content route. LTT collabs with Taeha Types for a LTT custom keyboard and then gives it away to the community. Hyper pog

I avoid razer stuff like the plague (Ignore my name k, thx) not of a fan of their software solution & rainbow RGB when you close the program. still using a naga, since the side plate swapping is legit a BIS feature. so if LTT made a keyboard there are some things I think it should have.
The board should be using QMK/VIA, none of that proprietary software. Hot swappable 5pin board, so you don't have to clip ur switches Wireless charging, would also allow them to make a Deskpad that could charge it 2.4ghz dongle, maybe just Bluetooth heard its gotten better since I've used it. gasket mount make it mod friendly (easy to disassemble) just a few quick ones I had in mind.
 

OLED displays emit light from an organic compound that wears out over time, just like light bulbs or every other LED wears out and will eventually get dimmer or fail. But a 4K WOLED display has around 33 million LED's. Each pixel has 4 subpixels: Red, green, blue and white. Every single subpixel is a tiny LED.
 
3.840 x 2.160 x 4 = 33.177.600
 
Burn-in basically means a specific set of subpixels wears out and cannot show the same brightness as the rest of the screen anymore. So unless you're staring at a uniform color, you might not even notice burn-in once it accumulates enough to be visible. And even then you might only see the burn-in on specific colors. For example if you have a set of blue subpixels that are very worn, you won't see them when these pixels are displaying white.
 
Pixel shifting will reduce the risk of fine lines like text or many HUD's burning in, as they're not displayed by the same pixels all the time.
 
Limiting brightness to 100 nits or so will significantly reduce the wear and burn-in won't occur for longer. Lower brightness means less heat, and less heat means less wear on the LED's. Because of that models with a heatsink or newer, more efficient OLED technologies that use less power also become more resistant to burn-in.
 
But in the end all OLEDs will show burn-in after enough use, just like any LCD monitor's backlight will probably fail some day. But depending on your useage you won't see burn-in before you get a new display or you can have problems within a few months of owning the display. We can set our expectations depending on the use case, but there really is no general rule of how your experience with burn in will be. All we can say is you're either a high-risk user or a low-risk user. In the end if you simply don't want to bother with burn-in you just have to buy an LCD. High-end LCD monitors will still deliver great image quality and pixel response times, but they're just not on the same level as OLED. But LCD's are still not 100% immune to burn in and while they last longer, they also have a finite lifespan.
 
For example my LG C9 OLED has over 6000 hours of use and still doesn't show any signs of burn-in. Simply because it's mostly used to watch movies and the occasional gaming session, so bascially a low-risk scenario. I'd say in terms of getting an OLED mainly as a TV, burn-in is a fixed problem. The only reason why it's getting more attention atm is because people started to use them as computer monitors more and more over the last 1-2 years.
 
And unless you play only one game, i'd say video game HUD is mostly not a problem either. Playing 200 hours of the same game will not really cause issues. However, if you're the type of gamer that plays one game for thousands of hours, it might become a problem.
 
Like in many cases, you have to manage your expectations no matter what you buy. I hope that could clear things up for you.

Solve the problem in the brute force way first, then try to come up with better solutions. How would you do it by hand? Write some numbers on sticky notes then try to remove the duplicates.
Spend as much time as you think is reasonable, there is noting wrong with looking at solutions, just make sure you understand what every line does  and don't copy paste code.

Programming aside, OLED panels usually have native pixel shifting to help prevent pixel burn-in, if I'm remember correctly.
 
Knowing this, are you still interested in your original idea?

Sure, but I'm not talking about professional programming and that's not what OP is doing. The thing to understand here is that dropping projects as part of programming on your own time isn't "quitting", or even deviating from your goals, because the OP's goal isn't to "learn react" for the sake of understanding how react works, it's a means to an end. Dropping and starting new projects, in this context, is necessary. It's all too easy to get stuck in the weeds on some technical problem that doesn't really have anything to do with your overall goals, and in those cases moving on to something new is the best way to spend your time. Depending on your skill level the things you learn getting a project the first 50% of the way there is far more valuable than spending the time to "finish" the problem would be. No matter what you do you're going to learn things and get better as an engineer, but you can be tactical about how you choose what you work on to learn more, and learn faster (and much more importantly -- do so in a way that doesn't make you miserable).
 
There might be a bit of a conceptual disconnect here, since my advice is coming from the perspective of programming as a part of my lifestyle-- I don't just program for work, I really like it and want to spend my free time working on things I enjoy. From that perspective any "tough it out" kind of grind is untenable, I can't "grind" as part of the things I do for enjoyment. Instead I pick my battles and work on things I know I'm going to have fun doing, and as a side effect I level up my skills as an engineer. I think this idea applies just as well even to people who don't care about programming except as a way to find a job, it's just way easier to keep up with something that doesn't make you miserable.This video sums this up very well:
 
I think we're using different definitions of burnout. Burnout isn't about getting bored with work, it's about the work becoming intolerable because some aspect of it is making you miserable.

if it's an old enough laptop and your not that picky you could simply install a Linux distro with developer focus install if you want. It should be lighter on the system and is easier to setup properly than on windows for java.
 
I do specially favor Ubuntu for ease of use for java work. Install OS go in package manager and install Oracle JDK and IntelliJ or Eclipse for the IDE and your ready to go.

You'll likely get better answers with more concrete technical questions. Try to build something, then give an example of what exactly you're struggling with. The screenshot doesn't look like something that would necessarily need a framework and is doable with plain HTML and some CSS. Have you tried following their tutorials?

You need to create a dedicated script tag for your JQuery include and your own custom script as such:
<script src="https://cdnjs.cloudflare.com/ajax/libs/jquery/3.5.1/jquery.min.js" type="text/javascript"></script> <script> // added the above script tag and ended the include script tag on the line above. $(document).ready(function () { $("#slideshow > div:gt(0)").hide(); setInterval(function() { $('#slideshow > div:first') .fadeOut(4000) .next() .fadeIn(4000) .end() .appendTo('#slideshow'); }, 3000); }); </script> Behaviour of a script tag with both a src="" attribute and content seems to be inconsistent. Some browsers may run this but its much better to separate them. Your Codepen works because its effectively being compiled into the above.

create helper function
const createPromise = (logMessage, timeOut = 1000) =>{ return new Promise((resolve, _)=>{ setTimeOut(()=>{ console.log(logMessage); resolve("done"); }, timeOut); }); } then do your chaining with async and await
const test = async () => { await createPromise("order received", 2000); await createPromise("preparing food", 3000); await createPromise("order ready", 4000); await createPromise("order delivered", 5000); } test(); you can make it parallel as well so they are none blocking. do this if result of the next promise does not depend on the previous. 
const test = async () => { const [result1, result2, result3, result4] = await Promise.all([ createPromise("order received", 2000), createPromise("preparing food", 3000), createPromise("order ready", 4000), createPromise("order delivered", 5000) ]); }  
key concept. await is just syntactic sugar for .then. when you do "await xyz()", you are just doing "xyz().then(()=>{// call back function })". whatever happens after await is whatever is inside the .then callback
 
return from await is the param of the callback inside the .then. e.g. "const result = await xyz()" is the same as "xyz().then((result)=>{// call back function })". 
 
For most purposes, just understanding these two above should be enough. you dont really need to dig any more into it.

You could try pass optional array of dependencies to your custom hook.
 
Untested:
const useFetch = (path, deps) => { const [array, setArray] = useState([]); useEffect(() => { const fetchData = async () => { const res = await axios.get(path); setArray(res.data); }; fetchData(); }, deps || []); return array; };  
React team suggests something different:
const useFetch = callback => { const [array, setArray] = useState([]); useEffect(() => { const fetchData = async () => { const res = await axios.get(path); setArray(res.data); }; fetchData(); }, [callback]); return array; } const data = useFetch(useMemo(() => {}, [your, deps, here]));  

You have to start learning all about CSS.
Here's a good resource for modern practices and information: https://web.dev/learn/css/
I recommend playing around with the basics: background, background-color, color, font-family, font-size, display, grid, etc. and the like.
In most/all browsers, all text heading elements (h1, h2, etc.) have margin of 1em by default, so this wouldn't do anything.

I mean, we're close enough to at least CPU launches (AMD will be announcing AM5 by the end of the month) to the point where I'd say you should really just wait for them to launch before getting something. It'll either get you faster hardware for the same amount of money, or it will get you a deal on last gen stuff so you get the same performance for less money. GPUs are still debatable for whether you should wait or not, but for CPUs it really makes sense to wait if you've got a current system that can get you by. If you're gonna wait, any recommendations we make on other hardware won't be applicable by that time. 

Yes, it does. Ignoring DP version requirement for a moment, as obviously it needs to be the correct to be certified for the required bandwidth.
It doesn't matter when you are below max specs of the cable/GPU/monitor DP version. However, it does matter when you are reaching them.
 
For example, they are reports of people having their screen go blank for a second or so at random, when they run their display at 4K 144Hz or 165Hz (165Hz at 4K is above DP 1.4 specs). Same for HDMI, or any other cable. You really want a cable that is separated from others, well shielded, and of high quality.
 
That said, doesn't mean that expensive cable means good cable... There is a lot of overpriced crap.
Typically, the cable included with the monitor  is tested and certified by the manufacturer of the monitor. The last thing the monitor manufacturer wants is support calls. It costs money, hurts profits. Anything massive, would mean they would need to start to justify things Infront of shareholder and investors. They really don't. So they don't cheap out, and spend the time to certify the stuff they put in the box.
 
That said, you can still have problem if you are in a area where you have a lot of radio frequencies of all kinds, or/and the cable is all bunched up with other cables next to it. And of course, bad luck manufacture error is always a thing... rare... but it could happen, as typically the manufacture doesn't manually test the cable their order from their supplier before putting in the box. Things to keep in mind. But again, only important when you push things to their limits.
 
 

LTT isn't a company, it's a brand by LMG aka Linus Media Group.
 
Creator Warehouse is technically a seperate company (afaik), but still owned mostly by Linus and Yvonne just like Floatplane.
 
- LMG's product is media and they make money selling sponsor spots and overall advertising.
 
- Creator Warehouse's product is apparel, tools and all the other things their engineers are working on.
 
- Floatplane's product is their streaming site obviously.

LTT is selling merch to diversify their revenue streams.  Nothing more.
 
Average first post for clickbait, I give it a 6/10.

QCode 55 indicates that your RAM isn't installed, or that one or more of your RAM slots are faulty.
 
Double check that your RAM sticks have been fully installed in each slot, and if the QCode persists, try a single stick of RAM in each slot to determine which slot may be faulty.

Reality: "Starting to normalize" after unheard of YoY increases, due to a pandemic.
Media: tHe iNdUsTrY iS cOlApSiNg
 
Reminds me of the countless number of businesses that always project YoY increases, regardless of circumstance and other influential factors.

In general, Linux distributions🐧🐧🐧, such as Debian, allow you to download and install metapackages, which are intended for specific sectors: graphics, video, science, etc. But if you want a ready-made distribution for creatives, Ubuntu Studio is the solution for you.
 
 
Ubuntu Studio:
https://ubuntustudio.org/support/
https://ubuntustudio.org/download/
 
Debian:
https://blends.debian.org/games/tasks/
https://blends.debian.org/multimedia/tasks/index.en.html
 
Try other Linux distributions too ... 🐧🐧🐧
 
 

all those can be done to a certain extent.....
- system specs would be the first main concern
 
For Gaming
- STEAM is king or queen ( depending on your heirarchy preference. )
- Heroic Launcher covers Epic and GOG ( game success varies )
- Bottles - a specialized wine environment with easy click and install components including launchers ( game success varies )
- things like Valorant will be out of the question due to kernel level anti-cheat
- some other multi-player games are out of the question due to their anti-cheat
 
For Streaming
- OBS but might take a little more set up than on windows
 
For Art / Drawing
- heaps of programs to choose from
- if use something like photoshop and other adobe products, you are out of luck
 
Games i am starting to struggle with due to my old AM3+ system
- Space Engineers
- Euro and American truck Simulator
this is why i say system specs are first concern

Should be at $1 in less than 10 days at this rate. Will be a lot of mining rigs for sale real soon.

Nah, it will bounce back. I'm sure a lot still hodl-ing in and there's still more potential sheep customer to scam. benefit from this crash.