1 karma · joined June 24, 2020
A full-stack developer is not a 10x ninja developer in every language/technology in the "stack". A full-stack developer is a developer that has good enough understanding of a stack of technologies (say Django for the backend and Vue for the frontend, maybe Swagger in the middle, and PSQL for the database) to help the team fix integration issues between each layer of the stack.
You're a programmer, not a court reporter. You don't need +200 WPM. You need to think before/during/after writing each one of the characters you type. And more often than not, you actually spend +5min of 20 lines of code, so your +200 WPM ability doesn't matter at all.
Let me give you the simplest possible example. A form with multi-dependant inputs: you select an option from a dropdown, and depending of the choice you made, you see another dropdown with some options, or maybe an entire new set of inputs. Maybe there is a button that will open a popup with another form, dynamically generated based on what you choose. Or maybe there is data you must dynamically fetch from the server, based on some combination of actions that the user did.
You can play the ".show()" and ".hide()" game with plain JS, but if you have more than 5 inputs, I promise you, you'll be really sorry for choosing that method.
You can also "inject" somehow any SPA just into that particular view in your project, but then you'll be already dealing with the cons of both SPA and SSR. It doesn't pay off.
I have been doing all types of FE and BE development, and what has given me the best results is making the BE a REST API and doing the rendering on the frontend.
Just my 2 cents.
The only thing I do see as an advantage is the reduced size in the distributable. But, imho, size really doesn't matter these days.
You can't have a graphical, user-oriented, server and tell the user to "hey, just use a shell script and a control binary, and then hook a hotkey into your window manager and make it run that script". That's just not how user friendliness works.
Try to find a common ground between Wayland being secure and Wayland being practical.
That said, I have no idea whatsoever about video codecs; I'm just saying what I understood from the link I was provided with.
* both x264 and x265 take less time to encode and the produce smaller files (lossless compression)
* AV1 takes 160x-190x more time than x264 (lossless compression)
* AV1 can't take advantage of multi-threading the same way x264 and x265 can. Neither for encoding nor for decoding.
* AV1 requires 3.5x-6x more CPU power to decode than x264
I just fail to see how AV1 is "all around better". Can you share another link? Maybe this time more specific so I can read the data you used to get to that conclusion.
Unpopular opinion: I just switched them again, this time to Mac. 0 support calls since then.
I'm still really not sure how/why VSCode feels so responsive and performant compared to Atom, which, according to Atom's devs lengthy blog posts, went through a pile of refactoring, focused exclusively on performance.
Edit: Also, staying with Atom isn't really viable at this point, since development was pretty much halted, in favor of X-Ray (aka Atom 2.0?). The only significant changes that are being made are the GitHub-integration related features.