Hacker News new | past | comments | ask | show | jobs | submit | mircerlancerous's comments login

Sounds like the presenters are assuming that everyone must be using JS in the same way they are. As someone who prefers to work in VanillaJS, I'm already frustrated by all the language changes being forced upon me. So maybe I agree with them that fewer changes should be made, but for completely different reasons. I'd rather them work on API improvements so that web apps get closer to parity with native apps. All this other talk is pointless while web apps remain second class IMO

What do you mean forced upon you? There is no requirement for you to use new features. If you do, it’s because you or your team thinks it’s more convenient — and it really is! map, filter, arrow functions, scope improvements with const/let, etc. are major language improvements. So is null coalescing and optional chaining. You don’t have to use them, but they do make JS more straightforward to work with.

I think "forced upon" could also read as:

- at work they expect me to write code with the latest features

- my colleagues write code with the latest features and I have to review/extend/build upon using the same style

- the community, books, copilots, LLMs, libraries, tooling are "forcing" all that new stuff upon me

- etc.


As a dabbler in JS, it jumps out to me that a lot of tools are trying to force ESM, despite the fact that they lack many essential features that other module systems have.

I think the proposal is actually good for people like you.

You can choose to just work with the core and maybe a minimal sugar library. Which will probably be faster and don't include "all the language features that were forced upon you".


This is not what happened in C vs C++.

This is pretty neat. It was pretty simple to get started, and the updates in the preview are nice and fast. For me I can see myself using this for prototyping. I do wish though that there was a way to use it anonymously. You've already got the service worker part, so why not allow the user to save their work to a service worker cache?


Thanks for the feedback !

Would add your suggestion to our roadmap! I had that in mind before, but quickly scraped it, as synchronization would be a pain and slow down the MVP.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: