spartanatreyu

This seems a little meh, people shouldn't be getting taught react or nextjs if they're not proficient enough with JS first.

That just teaches people to reach for frameworks when what they're trying to do could likely be solved in a few lines of code.

Theo had a great video on this, and went through why jquery is still important for the internet (besides the older and/or inexperienced who use it):

https://www.youtube.com/watch?v=1bZYmpOOC8U

1 hour of planning can save 10 hours of work.

1 hour of research can save 10 hours of planning.

Some small nits to fix:

1. C has it's own undefined behavior.

2. JS has confusing behavior, not undefined behavior. Its specs are well defined and backwards compatible to a fault, making some things unintuitive and harder to learn if you don't learn the history of the language.

3. Problems with both should be avoided by learning and using standard practices. (Don't pretend C is object oriented, always use === instead of == in js, etc...)

In complete agreement:

1. Result types are awesome, all future languages should be designed around them.

Your question:

what things did the LHC discover that have real practical applications right now other than validating some hypothesis

Is really multiple questions:

1. Is doing fundamental research with no application in mind useful?

2. Has the LHC led to practical applications usable today

The answer to question 1 is yes.

There's different types of research programs made to target different goals. Some aim for short or medium term applications, and others are just pure fundamental research.

Just because pure research doesn't have an application in mind, doesn't mean it's not useful. The application isn't the goal, the expansion of our knowledge base is. Everyone who ever thought up of an application for something did so based on their own knowledge base. If the knowledge base never expands, then we run out of applications to think up. This is why pure research is useful.

And all of history supports this:

• The discovers of rays shooting off cathode-ray-tubes in the 1800s were just doing pure research and had no idea it would lead to TVs
• particle accelerator research lead to invention of cat scans
• chemists trying to research heavier elements leading to the discovery of nuclear fission, leading to nuclear power
• electrolysis research lead to the invention of lead (and rechargeable) batteries
• etc...

The answer to question 2 is also yes:

The obvious ones are:

• improved manufacturing processes
• improved supercooled superconductors
• improved large scale vacuum chambers
• Improved data processing
• Trained a new cohort of experienced scientists/engineers/workers/etc (who can now work on new projects outside of the LHC)

you have to fix the indentation because if not then the document won’t work or mean something completely different

Whitespace has no meaning in json. You can indent however you want, or not at all.

I'm assuming you're running into issues because you're writing json in a yaml file which does care about indentation, and you're only writing json in yaml to get access to comments.

In which case it circles back around to: why not use toml? Whitespace formatting doesn't corrupt the file, and it has built in comments.

If you read the - as "dash":

docker compose up
docker system prune -a
docker compose up

Cut and paste problem?

If you're reaching for yaml, why not use toml?

How would you mark a flag in your json settings file as deprecated?

That doesn't really work when you need two comments at the same level, since they'd both have the same key

Where do you put your comments in JSON files?