Then Google Closure Compiler came along which added type safety via JSDOC and TS came along with (TS)JSDoc support and it's own TS syntax.
The community chose native TS and Google Closure compiler slipped away into the background.
So (TS)JSDoc support is a relic from when Microsoft was trying to get market share from Google.
Today in 2025, TS offers so much more than the (TS)JSDoc implementation. Generics, Enums, Utility types, Type Testing in Vitest, typeguards, plus other stuff.
Today I use TS. I also use plain JSDoc for documentation. e.g. @link and @see for docs. Or @deprecated when I'm flagging a method to be removed. @example for a quick look up of how to use a component.
TS and plain JSDoc are both important together. But (TS)JSDoc alone, is a relic of the past.
And this isn't about AI (well, not primarily anyway). It's offshoring, offshoring, offshoring.
IMO, what's taking place now is absolutely transformative and the world economy is in the process of being reshaped. It's not just tech jobs that are being offshored - we're just one of the first/early movers. Many other professional/white-collar jobs (accounting, etc.) are also getting offshored at an accelerating rate. And it's happening all over the western world - it's happening in the US, it's happening in Australia, Canada, the UK, etc.
And unlike previous periods of mass offshoring, I don't think the jobs are ever coming back.
These new tech companies/existing companies were not here for the first wave of offshoring engineers many years ago. basically, the product/service degraded and they brought the product/service back onshore.
It's a cycle that will repeat. Product degrades, there will be public outrage, then they will onshore the product to fix the problems caused from offshoring.
Look up the other gear from ZWO the maker of the seestar.
Deleted Comment
So far there's negative evidence of this. Things are getting more expensive for similar outputs.
Local, in my experience, can’t even pull data from an image without hallucinating (Qwen 2.5 VI in that example). Hopefully local/small models keep getting better and devices get better at running bigger ones
It feels like we do it because we can more than because it makes sense- which I am all for! I just wonder if i’m missing some kind of major use case all around me that justifies chaining together a bunch of mac studios or buying a really great graphics card. Tools like exo are cool and the idea of distributed compute is neat but what edge cases truly need it so badly that it’s worth all the effort?
In large companies this can save quite a bit of money.
Cursor is essentially only the wrapper for running agents. I still do my heavy lifting in Jetbrains products.
It actually works out well because I can let Cursor iterate on a task while I review/tweak code.
Knowing what tools are better for what really helps.
What I found best was
- a standard qwerty keyboard (I didn't want to be restricted to custom keyboards)
- A learning program called Five Finger Typist. https://www.spectronics.com.au/product/five-finger-typist-2-...
Basically I'm hybrid touch typing. Because I cover the whole keyboard as I type the chance for error increases the longer I type. I quickly glance to know where i'm aligned.
In hindsight I should have learnt to use the F and J notches more.
I have extensively remapped my IDE shortcuts to be easier to trigger.