rezonant

27 ms·

451.
by rezonant 3y ago
It either indicates Apple isn't sure it can catch up or that they simultaneously realize they need to provide these AI features but don't think AI as a marketing component will have the staying power to make the investment worth i
452.
by rezonant 3y ago
While not immediately, ultimately Android was very explicitly a hedge against Apple, not Microsoft. Seems this became clear at Google near instantly after the iPhone announcement. Google actively shifted it's Android development toward
453.
by rezonant 3y ago
> I believe there's no point on discussing this with particularly you since you have been commenting all around trying to just confirm your view instead of just comprehend that this is not sustainable for new developers I don't
454.
by rezonant 3y ago
I've been in the open source community for about 25 years so I doubt it. For what it's worth I would say a model should be fully reproducible to be open source, but that's not a decided consensus -- and AI models are sufficie
455.
by rezonant 3y ago
No you don't, but if you wanted to host it from your gigabit office IP, you probably would want to.
456.
by rezonant 3y ago
I'd bet Hugging Face would be happy to have hosted these canonically too, so not sure why that doesn't happen more.
457.
by rezonant 3y ago
> No git would be impossible. I’ve never seen a repo even a few GB in size, if you are uploading non code files you really should not be using git It's not actually a limitation in git itself, especially if you use Git LFS. People u
458.
by rezonant 3y ago
Others have pointed out that GitHub doesn't allow that, but > Torrents can unfortunately die after a period of time if no one continues seeding it or if they don't use a permanent web based seeder, which doesn't appear to
459.
by rezonant 3y ago
Well what constitutes an "open source" model is still controversial and debatable-- lots of people on both sides of that argument.
460.
by rezonant 3y ago
I'm sure just like in X's algorithms, @elon tweets are weighted heavily.
461.
by rezonant 3y ago
> The point of the post was to point out (maybe I did it wrongly) that those things you have described are pretty impossible given the ecosystem we have nowadays in Javascript (as a whole!). That's the thing, nothing you have assert
462.
by rezonant 3y ago
Yes I think you are right when NPM first introduced it, which was in NPM 5 [1]. At that time package locks were new. Node 16 shipped with NPM 8, and by then this was not the behavior any more. I don't remember exactly when, but I belie
463.
by rezonant 3y ago
Ninja'd, see my edit. Fine to log and die if needed of course
464.
by rezonant 3y ago
Handling uncaughtException and unhandledPromiseRejection is a common mistake. You should not do it unless you have a good reason. Your program should die for science, and you should fix the place where you didn't handle that exception
465.
by rezonant 3y ago
Well, strictness actually is optional in Kotlin too, since you can lateinit things and !! your way through nullability like in any language. And of course if you are consuming Java stuff this is more likely, since Kotlin exposes nullable ty
466.
by rezonant 3y ago
No, "npm install" doesn't actually do that. In the situation you are talking about, "npm install" and "npm ci" behave the same. It makes sense that they behave the same here right? What is the point of a p
467.
by rezonant 3y ago
> if the package.json is using relative version number What do you mean by this? You can specify dependency versions using "^" which means "I accept new minor and patch versions" or "~" which says "I ac
468.
by rezonant 3y ago
Fun, all the power to ya on that. I've done a bunch of Kotlin for Android and although I initially didn't like a lot of how it does syntax, it has grown on me a lot. It is definitely a language that is focused on correctness and c
469.
by rezonant 3y ago
Sounds like you are talking about frontend development. In that case you are trading off speed for accuracy. Some dev server tooling has this issue. Most systems built on Vite though do check across files, so likely that's just a bug
470.
by rezonant 3y ago
Exactly, and since this is AWS SDK for S3 we're taking about, and I depend on that same SDK in my own projects and they aren't broken (including using some of the more advanced streaming parts of it), I'm guessing there was a
471.
by rezonant 3y ago
"npm ci" omits dev dependencies by default. However, "npm install" also adheres to your package-lock.json, and does not update things on you. npm ci is just npm install with a few tweaks that make it better to use for CI
472.
by rezonant 3y ago
Patch or major is always a judgement call. Making all changes a major jump is a bad idea, because it means that dependent packages are less likely to adopt important functionality or security fixes. NPM already gives you a way to control wh
473.
by rezonant 3y ago
NPM uses your package-lock.json for normal installs as well. "npm ci" behaves nearly identical to npm install except for a few things, detailed here: https://docs.npmjs.com/cli/v8/commands/npm-ci No
474.
by rezonant 3y ago
This is not the default for NPM, Yarn, or PNPM. The "package-lock.json" is what does the pinning, and it's exact version. If you listen to very bad advice though, half of the Q&A answers on the Internet suggest all proble
475.
by rezonant 3y ago
Now enjoy using gdb to debug it
476.
by rezonant 3y ago
Friends don't let friends write raw JavaScript. Typescript nearly eliminates the problem you bring up, when used correctly.
477.
by rezonant 3y ago
In the interest of keeping you in discussion, there was another submission with further conversation: https://news.ycombinator.com/item?id=39732106#39732221
478.
by rezonant 3y ago
There is no downvote for submissions, only flag.
479.
by rezonant 3y ago
When you are not experienced on the platform you are building on, all debugging is heroic. It's really strange that they would invest all this time as if they are keen to understand the cause of why it happened, but then be satisfied w
480.
by rezonant 3y ago
This sounds like a team ignoring a huge amount of best practices for JavaScript development. Some combination of the following were not observed: - Use Typescript. - Practice version locking on your dependencies and make sure it works corre

More ›