News for hackers. Stuff that matters.
Re:Swift for TensorFlow Shuts Down by simonbarker87 on Friday February 12, 2021 @03:23PM (#26118128)
It doesn’t solve the issue of JS but NestJS feels like a more robust way to make a server in JS - and the docs are great.
Re:Swift for TensorFlow Shuts Down by mrtksn on Friday February 12, 2021 @03:47PM (#26118368)
Thanks, I don't really need large framework for full blown app though.
Re:Swift for TensorFlow Shuts Down by jiofih on Friday February 12, 2021 @04:47PM (#26118932)
Swift and UIKit are already a much larger API than any node framework in existence.
Re:Swift for TensorFlow Shuts Down by mrtksn on Friday February 12, 2021 @05:01PM (#26119055)
They have good defaults and Xcode is a good IDE with full support of these frameworks, Swift is a good language with sensible conventions so you don't really need to learn that much.

When you don't know something you can start typing keywords and see what Xcode autocompletes for and read the explanation about that function from the documentation that is provided to you right there. It's not perfect, sometimes there's no documentation but it's not a big deal as you can look into source files or try it out to see how it behaves.

Re:Swift for TensorFlow Shuts Down by jiofih on Friday February 12, 2021 @07:56PM (#26120460)
You get the same with JavaScript if you use any mainstream editor with TS support (you don’t need to be using TS yourself).
Re:Swift for TensorFlow Shuts Down by mrtksn on Friday February 12, 2021 @08:21PM (#26120580)
I use VSCode, it’s helpful but It’s not remotely the same. With TS it’s better when the devs included documentation.
Re:Swift for TensorFlow Shuts Down by jiofih on Friday February 12, 2021 @09:02PM (#26120786)
It will use typescript type definitions when available, even if you’re writing plain JS. Auto complete works perfectly, what’s not remotely the same?
Re:Swift for TensorFlow Shuts Down by mrtksn on Saturday February 13, 2021 @02:35AM (#26122067)
It's not the same because in JS you usually would use a large number of libraries with varying degree of documentation and different conventions. Also, you would loose autocomplete when you expect to receive something as a parameter instead of defining it in that closure.

The basic language API is not that large, the benefit of autocomplete discovery comes when you have autocomplete on custom types of a specific framework accompanied with proper documentation.

Re:Swift for TensorFlow Shuts Down by jiofih on Saturday February 13, 2021 @04:21PM (#26127055)
I’m sure NestJS, which sparked this thread, has very complete type defs, as does any major framework out there.

You seem intent on dismissing something you obviously haven’t tried in the past couple years; next time I’d suggest a simple “I don’t like it” instead to save us all time.

Re:Swift for TensorFlow Shuts Down by moocowtruck on Friday February 12, 2021 @04:08PM (#26118558)
nestjs is an atrocity that should not have been wrought upon the js/ts community..
Re:Swift for TensorFlow Shuts Down by simonbarker87 on Friday February 12, 2021 @05:14PM (#26119155)
Sorry you feel that way, it feels like angular for the backend to me which is nice, it follows logical patterns, loading modules allows us to configure micro services from a single mono repo, decorators are nice, encourages use of RxJS which is great and it still allows access to the underlying express app if needs be.

Might not be to everyone’s tastes but it feels like a solid tool to me.

Re:Swift for TensorFlow Shuts Down by bartvk on Friday February 12, 2021 @04:22PM (#26118690)
Please check the guidelines via the link at the bottom. What you're doing is called shallow dismissal.