Code quality is actually quite distinct from an applications feature set. Something that was vibe coded in a week can have similar features to something that took 2 years for a dev team to bring to maturity, however the actual code base will be on a completely different level. Not all applications care about all of these things: Security, scalability, stability, performance, low resource consumption, test coverage, readability, effort to customize and extend.
If you are creating a dating app or a device driver you will naturally have different preferences for the code base.
The end users opinion is secondary to the opinion of the company or person who owns the software. The software is an asset that the company uses to run its business. If pissing off 50% of your user base is acceptable business strategy, then they may opt to cut corners in places which will result in dissatisfied users.
The real question is what is the goal of the company. Most companies main goal is profit, but in some cases like nationalized government services, non profit organizations, providing a core service offering is the main goal. In the latter case it may be acceptable to have shitty UI and some broken parts of the application as long as the important functionality works.
Then there is the tradeoff between investment (good developers are usually not free) and essential vs nice to have features. Maintaining a minimum viable product is non negotiable while assessing experimental features for market desire will have a reduced budget and have more tracking for return on investment.
I think excellence is something that becomes incredibly difficult to maintain the more staff you have. You will start edging towards the average which is not excellent by definition.
The error is stating that the code is trying to run in an iframe and the content security policy of the frame source (your code?) doesn't allow the parent site to embed the iframe
Code quality is actually quite distinct from an applications feature set. Something that was vibe coded in a week can have similar features to something that took 2 years for a dev team to bring to maturity, however the actual code base will be on a completely different level. Not all applications care about all of these things: Security, scalability, stability, performance, low resource consumption, test coverage, readability, effort to customize and extend.
If you are creating a dating app or a device driver you will naturally have different preferences for the code base.
The end users opinion is secondary to the opinion of the company or person who owns the software. The software is an asset that the company uses to run its business. If pissing off 50% of your user base is acceptable business strategy, then they may opt to cut corners in places which will result in dissatisfied users.
The real question is what is the goal of the company. Most companies main goal is profit, but in some cases like nationalized government services, non profit organizations, providing a core service offering is the main goal. In the latter case it may be acceptable to have shitty UI and some broken parts of the application as long as the important functionality works.
Then there is the tradeoff between investment (good developers are usually not free) and essential vs nice to have features. Maintaining a minimum viable product is non negotiable while assessing experimental features for market desire will have a reduced budget and have more tracking for return on investment.
I like this kind of thing where there is no accurate translation without losing context or information.
I've heard some like neovim but I haven't tried.
Thank you!
OH LORD HE COMIN
Mozilla is just Google with a trench coat on. They fund it as protection against antitrust.
What would you recommend? Bazzite?
Just look at that plumage!
I think excellence is something that becomes incredibly difficult to maintain the more staff you have. You will start edging towards the average which is not excellent by definition.
Manul
It's laggy from my country otherwise I'd use it.
What a beautiful cat and tree
Wow nice work!
Here we all chat together friend
In my house Netflix is called the Star Trek machine
The error is stating that the code is trying to run in an iframe and the content security policy of the frame source (your code?) doesn't allow the parent site to embed the iframe
This turd keeps in the public sphere by negative posts like this. Better to just not post and let him fade into obscurity.
I'm guessing that they used more than just compression but also a linked list type database like graphQL which is what Google uses.
Definitely one of the best.
The names of these things sound like they were invented by 20-something-year-olds