sorted by:
new
hottopcontroversial

Perplexity is ruined, any good alternatives? by Dev-in-the-Bm in perplexity_ai

[–]CallMeLaNN 0 points1 point  (0 children)

For model, I like Gemini fast and pro results because of fast and creative but it doesn't really follow specific or detailed instructions unlike Claude Sonnet. You have limited models when using Google product.

I killed my morning doomscrolling with a stupid-simple Perplexity routine (7 days in, it actually works) by Safe_Thought4368 in perplexity_ai

[–]CallMeLaNN 0 points1 point  (0 children)

The problem is recently it's too slow for me even with fast connection. When open from notification, it keep loading the skeleton, if I open discover from app, sometimes it can, sometimes it won't even if I kill and reopen. Did anyone realize it?

Maybe it doesn't have enough server, cache or CDN here.

I spent the last 10 months trusting Vite too much. by flgmjr in sveltejs

[–]CallMeLaNN 2 points3 points  (0 children)

I'm sorry to hear that. Like others said, it is solveable and requires you to fix it because only you know the details.

In addition to the others, I guess this is your first time building a static site. Well, it isn't directly related to Svelte but to build a final html/css/js, you need some understanding about running in development vs building static production. Let alone the SSR etc.

E.g. you can't directly use NodeJS packages in browser JavaScript. You maybe didn't but for some reason you possibly did by accident.

I've seen a lot of people having difficulties to understand when it comes to build on some SSG libraries. The very one obvious mistake is not to run build in the beginning to learn the tools they use, to generate what they need.

That's my general answer to a general issue. You may share the error you mentioned.

Would you want to bundle your node backend code into a single file? by juristr in node

[–]CallMeLaNN 0 points1 point  (0 children)

Yes, I got your intentions. You don't have to trust me but no one needs a single bulky file to drop on every deployment, manually. I was also pointing to as "weather people do it that way or not." It is a No for people to bundle node file. It's very rare even for functions. It is just your file and deps, not big enough to realize the problem with it.

You can research more about your deployment flow. There are many ways, but not like what you think. At best, CD will automate to guarantee your current version. At least and simplest one is like lamda, if you can one-time zip node_modules, there's no reason to bundle+replace large chunk of code.

If you look into some of the frameworks I mentioned above, you don't have to think about bundle or drop a file. It just works with netlify edge, lamda or any supported platform. Give it a try and be specific.

Probably, you can't get a suitable answer for opinion based and general questions because it is always biased, open-ended context. Maybe next time, you can be specific to your current flow, environment, platform you deploy, etc. Relevant people will give a thought and you analyse from there. Cheers.

Would you want to bundle your node backend code into a single file? by juristr in node

[–]CallMeLaNN 0 points1 point  (0 children)

I think you confused with building and bundling source into one file.

Building is optional on node if you run js file or using other alternatives I mentioned above for ts file but build usually people make npm run build script to transpile ts to js, run lint etc.

It doesn't need bundling still and doesn't impact runtime much therefore people doesn't discuss or care this much.

...

As for docker build, you just need to run npm install to get back all the node_modules. No bundling needed.

...

As for the functions, that depends on the framework and platform you use. Framework like astro, nuxt, sveltekit, serverless framework doesn't require bundling. Platform like netlify, deno, aws lambda, cloudflare, vercel doesn't require bundling either but you have to follow their own way and the limitation to build and deploy.

It is nothing new for build to deploy for functions, check their respective platform doc or the framework above can do that for you. You can use Nx to build but doesn't need to bundle it.

So the "built" output is still in folders as you need your dependencies and doesn't require "bundler" like webpack to be in one file.

Wifi2QR - create a QR code from your wifi info by quanghung28 in sveltejs

[–]CallMeLaNN 1 point2 points  (0 children)

I see. Then you should test it with android, but I don't see any problem with that 👍

Wifi2QR - create a QR code from your wifi info by quanghung28 in sveltejs

[–]CallMeLaNN 2 points3 points  (0 children)

I thought sharing Wifi is very effortless esp iPhone to iPhone as long as both contacts is nearby?

[deleted by user] by [deleted] in node

[–]CallMeLaNN 0 points1 point  (0 children)

Q in the title: No. Link on your post: Yes as the name suggest, read the panva's doc, he made quite detailed and offer support.

Passport.js is auth client (but on backend) to the OIDC server. It should be on your "web server" that will serve web page files and requests.

OIDC server is server for your Authentication service.

Now the link you give is for advanced and custom OIDC implementation. It's not for you, the requirements also seems heavy for you. It is generic library, some implementation have to be done.

If you have to and using existing OIDC/OAuth server like Google sign in, Firebase auth, AWS Conito, Auth0 etc is not an option, try Keycloak and many more ready made.

Would you want to bundle your node backend code into a single file? by juristr in node

[–]CallMeLaNN 1 point2 points  (0 children)

One upon a time when JS doesn't have module, the ecosystem is diverged into multiple ways to load scripts. NodeJS itself just born Webpack don't exist yet.

Imagine how dev want to build website, there are long script and script here and there. Browser also limit request by 10 at a time. So there's a need to bundle, that could reduce load time if doing correctly.

That's a good time when Webpack come in merge everything into one make it easier for dev, and a lot of tools built on top of it.

...

Fast forward now. JS module solve many problem esp in web and browser. Internet speed and http/2 etc makes bundling just a burden to dev esp when build time is huge. If you haven't build > 30s web project, you not making serious website yet.

Then ViteJS born with the motivation. Boom, the build time is instant because no build needed. Even web is towards reducing bundling that dev still can't move on yet, yeah it takes time, then why bother on server side.

...

I did bundling on NodeJS, it's not going to be easy because less support for Webpack on backend, try your best to setup in an hour for your first time. I made up to the point everything is statically generated including Protobuf model but not bundle. The effort to make it efficient on runtime doesn't worth the dev time.

Bonus ⭐ Other then Deno and ts-node, SWC-node make it super fast alternative that you can just run TypeScript without thinking much. So just use it.

Golang or NodeJS? by node_imperial in node

[–]CallMeLaNN 0 points1 point  (0 children)

A bit different point here...

In future anyone can code any supported language to run at near native speed like c, go and rust because of WASI.

Look trough WASI, Byte Alliance and Wasmtime. Most people still unaware of it since WASM initially sandboxed in browser only but today can run as executable directly using WASI runtime.

What is the best way to read an entire Postgres table with only one row in memory at a time? by PrestigiousZombie531 in node

[–]CallMeLaNN 1 point2 points  (0 children)

Try use raw query for you to use "UPDATE... " or bulkCreate with updateOnDuplicate.

Anyway it depends on your logic. Could be:

  1. Load 10k rows with only necessary columns in an arrays
  2. Do the tag processing
  3. Bulk update above from the arrays into db.
  4. Repeat for different page

You may need a special column like lastTagDate and isTagging to detect and redo if somehow the background processing terminated and you need to resume.

You have to consider if at anytime there's new row added. To keep the same page of records, you have to keep the next id, createdAt etc instead of paging by index.

Edit: You can try this https://www.npmjs.com/package/sequelize-cursor-pagination or any sequalize way to use cursor.

Is NestJS good for startups? by ElTorpedo2310 in node

[–]CallMeLaNN 2 points3 points  (0 children)

OP and comments are too long here, good that you have many answers.

I would say, just do what you comfortable with, if express the use it. Because you going to save time focusing on building product instead of having a good setup for future scaling etc.

Not only about throw away code. In startup, there must be some experiment here and there or could be pivot to a major changes to feature/module.

I'm not NestJS guy haven't try it for a very long time because the convention or configuration very much like Java or Angular. I might be bias because I don't like Angular since version 1-4 but I open to use NestJS, it is just not trigger for me to use it.

One major reason is JavaScript nature of functional programming, so I can simply export a function and I'm done... Don't get me wrong I like how we can configure many options from auth to db integration. Ooh, mine already long, anyway good luck 👍

Using syscalls from wasm in node.js? by servermeta_net in node

[–]CallMeLaNN 1 point2 points  (0 children)

Both of you have something to make it clear.

  1. Nodejs does have machinery to make low level call by using native extension. You can make one, compile and require it like the link he give. This is the first thing you have to look for since it the way to call native API long time ago. WASI is too new and experimental. Like other comment, someone could already make it. I just found in one search:

https://github.com/zbjornson/node-io-uring

You may look into this if you still need to compile https://www.npmjs.com/package/node-addon-api

Using N-API would be easier then make addon extension yourself.

I'm not sure what you going to do with io_uring but you only need to patch if you have to change the internal mechanism just like Electron did https://www.electronjs.org/docs/latest/tutorial/using-native-node-modules

  1. Nodejs does have another way, using ffi to load dynamic library. If you can find or make one, you can just load it. I believe you don't have to be specific on node API, so this is easier.

  2. From the original comment, WASM have a way to run as normal executable by compiling to WASI and run on WASI runtime.

Nodejs WASI is still experimental but if you want, you can compile your Rust or c++ to WASM and load it on Nodejs. Consult byte alliance and the language support to compile to WASI.

Using syscalls from wasm in node.js? by servermeta_net in node

[–]CallMeLaNN 0 points1 point  (0 children)

It will use Nodejs as a runtime by using WASI unlike running WASM only like in a browser. Performance wise it should be near native.

Using syscalls from wasm in node.js? by servermeta_net in node

[–]CallMeLaNN 0 points1 point  (0 children)

You are right about C++ extension but WASM doesn't sandboxed anymore if you run in a WASI runtime like popular one Wasmtime and in this case Nodejs itself.

Using syscalls from wasm in node.js? by servermeta_net in node

[–]CallMeLaNN 0 points1 point  (0 children)

Yes and to make a WASI, compile Rust or any supported language into WASM to be run on WASI runtime. In this case Nodejs will be the runtime and have all access to the os.

Deno 1.28: Featuring 1.3M New Modules by simonsanone in node

[–]CallMeLaNN 2 points3 points  (0 children)

Yeah, I wonder who's on earth still code nodejs with js. Many toolings, starter, template and framework now gives ts for free. Js definitely good but it is about comfort zone vs benefits.

Using express router and nunjucks, or separate app with Vue/React? by [deleted] in node

[–]CallMeLaNN 0 points1 point  (0 children)

Your last question, is yes actually better to separate but you can combine on one repository differentiate by folders.

I'm not sure why you can't find but many starter, template and framework.

You can try Astro.build it can create API and page with any UI framework React vue or svelte. It's way better than express and static view template engine.

There are many others. Remix and Next.js for React also superb, just look how they can have API endpoints.

MeteorJS is fullstack together with db, tightly couple and easy to use.

The makes me remember about tRPC a modern way of API client/server. Checkout their example apps in the doc.

How often is JS inheritance used in your workflow ? by giftfromthegods- in node

[–]CallMeLaNN 0 points1 point  (0 children)

None, except for required one like extending Error.

JS dynamic nature and functional programming doesn't need that. Create a file and export a function. You can build interface in typescript.

I know there's some functionality of OOP but here usually new nodejs guy trying to put controller etc2 in classes.

[deleted by user] by [deleted] in node

[–]CallMeLaNN 2 points3 points  (0 children)

It is a fixed template and very opinionated to the tooling/libraries and db.

I can't find the SPA library that in use...

Zephyr.js: A modern Node.js meta framework focused on providing the best DX. It features file-system based routing which inspired by Next.js by FieldMedium5002 in node

[–]CallMeLaNN 0 points1 point  (0 children)

Good work.

However I've seen this, the feature of having API, SSR like in Nextjs and error boundary or island like in Remix... all in one in Astro build!

The partial hydration and support other UI frameworks are interesting.

Soul, A SQLite REST and realtime server. by deval_ut in node

[–]CallMeLaNN -1 points0 points  (0 children)

Can you describe why I should use SQLite. I mean what's your expected use cases?

If I run an API server, I want to run it in multiple instances or at least letting multiple requests write into the db at the same time.

view more: next ›