12 ms·
> backend only Lol, not even close pal > tsc cold starts in terminal ??? Why would it be only possible to cold start in the terminal and hot start in the IDE
by nawgz 5y ago
> backend only
Lol, not even close pal
> tsc cold starts in terminal
??? Why would it be only possible to cold start in the terminal and hot start in the IDE?
> you update the code, the IDE tells you the error
Well, we’re making ridiculous assumptions about each other, do you only code in a single TS file? How on earth do you never impact a call site that isn’t the one you’re looking at immediately? The IDE is useless in this case. Option click to open offending lines is way more valuable than red highlighting that may or may not be stale
> why isn’t the browser updated 2sec after
But it clearly is? Maybe you have some bad use of tsc watch or something. I suggest you revisit your dev command…
- nsonha 5y agocould you maybe chill, no need to "pal"... lol? > Why would it be only possible to cold start in the terminal why do you ask me, do you know the command to start tsc "hot"? Please tell me? > How on earth do you never impact a call site that isn’t the one you’re looking at immediately? The IDE is useless in this case even if you've never used an IDE before, the whole idea is that it understands the concept of a project and does static check project-wide. I would call what you said a "ridiculous assumption", because of course IDE shows errors project-wide. Actually speaking of which, good luck with project-wide errors that overflow your terminal buffer. > I suggest you revisit your dev command… the 2 secs is just an example, I don't do that stuff anymore, like you I'm just engaging in the conversation to project my opinions. I would like to add that making a tsc alternative is a massive job & not proven possible so far, so the only room left for performance improvements is making alternative "transpilers". That's probably the answer to why these tools started as babel alternatives and not tsc alternatives