Echo JS 0.11.0

While this approach enforces strict types (eg renaming exports) i prefer my IDE to import the right thing rather than me importing everything. How I import stuff (in vs code):

- write code
- IDE suggests a symbol
- either use symbol (and auto import is added) or ignore
- if ignore suggested symbol, use the `quick fix` actions to import the correct thing

This really is not a chore, and my build will break if I rename symbols (which isn't the case if using default exports, in which case i need to manually scan my project to rename the import to ensure the name I've given it still makes sense.)

What other benefit are there to using `import * as foo from "...";`? (Genuine question as I do not use this approach.)

Looks good. I used to use mdx files for my blog but it was too much hassle to write content in code so I ended up using a headless cms (strapi). Overview here: https://richardwillis.info/blog/how-i-use-next-js-strapi-and-docker-to-build-my-personal-website

Do others agree with Sindre about not using named exports? My opinion is the exact opposite, to ALWAYS use named exports to provide stricter types. The point about "a chore to import each color manually" is not true when using (for example) TypeScript auto imports.

Please explain how this is related to JS.

I feel like these explicit state machines make the code harder for me to read/parse and will introduce maintenance overhead. Am I alone with this opinion?

I personally have no problem with lamer news. I like that it's simple and I wouldn't suggest changing it. If there are plans to change it, i'd very much like to know as I'm building an app for echojs in my free time and i'm currently working on a TypeScript-Fetch client for LamerNews that i'll use in my app: https://github.com/badsyntax/lamernews-api-client

Is echojs going to stick with Lamer News for the foreseeable future? (I think Lamer News is perfect and don't think the forum software should change, but i'm building some libraries and tools and would like to know if there are plans to move away from it. Hopefully not!)

This seems like a great tool, but the main bottleneck I have is type checking. Sometimes TS is really slow at type checking in my editor. I wish more effort was directed into making type checking faster. I kinda wish the TS team would just stop adding new features and focus on improving type checking performance.

Not a fan of such statements as "Fact: The switch statement is not the best solution for many cases. Another fact:..." I feel this is subjective at best.

getting a 404