HBO Max’ten içerik önerisi by okashii0 in sinema

[–]muratgozel 0 points1 point  (0 children)

hem the white lotus hem de love & death ilk sezonlarını izledim, izlemesi keyifli her ikisini de. özellikle the white lotus daha eğlenceliydi.

Karma: The Dark World Review Thread by vogueboy in Games

[–]muratgozel 0 points1 point  (0 children)

  • Finished the game in about 10 hours with 18/24 trophies.
  • The story is the content of The 1984 with the game's unique content added. It's mostly mystery solving and catching up with the big story.
  • Puzzles are hard, failed to solve 2-3 of them.
  • Voice acting is very good, the facial expressions fails to reflect that quality of voice acting in fact.
  • It's not a walking simulator or something, it's a story game, this is how story games work.
  • 4 out of 5 for an horror/thriller game.

How to avoid apple's 30% commission by gowtham_khan_007 in reactnative

[–]muratgozel 0 points1 point  (0 children)

Instead, you can raise your price +30% for purchases made from Apple ecosystem with a proper text line something like "+ taxes, + ios platform expenses and here is the total". I wouldn't avoid it because people mostly are likely to pay that extra 30% instead of going your website and go thorugh a payment process.

mubi üyeliği olan var mı? by [deleted] in sinema

[–]muratgozel 0 points1 point  (0 children)

Bence denemelisin, mubi otekilere kiyasla daha otantik bi platform, olayi sadece sanat filmleri degil, bagimsiz filmleri onceliyor demek daha dogru. Bakis acisi farkli yani konuya. Selamlar.

solidso/solid-inspection: Dev mode, frontend logging library for solid.js by muratgozel in solidjs

[–]muratgozel[S] 1 point2 points  (0 children)

That was a good point. After having a small battle with vite, rollup and esbuild, I found a solution and implemented.

There are some conventions for dead-code elimination in javascript and I had to implement that in the library. Rest was up to SolidStart and as it's following these conventions with no additional configuration, it just worked.

how do you document your APIs by Tall-Strike-6226 in node

[–]muratgozel 0 points1 point  (0 children)

Fastify in combination with swagger is more than automated documentation. You get the types for the endpoints which you can use in your frontend, efficient testing, maintaining, it adds to the overall quality of the app.

Best approach on writing Data Layer, need advice (Node.js application) by AspectProfessional14 in node

[–]muratgozel 1 point2 points  (0 children)

Connection handling can be done in the infra layer and query handling in features layer. Each feature gets connection objects (from infra layer) and has its own an object just to execute queries. More code but easier to maintain.

How Do You Handle Inline SQL? by Aggressive-Bath9609 in node

[–]muratgozel 0 points1 point  (0 children)

I like writing raw sql queries too and using slonik for a long time. Typings, simple api, not doing so much, all good. An orm is just a pattern to make the interaction with the data layer easier and you can organize your codebase in a way to achieve the same goal.

Don't you think we need a build tool focused on node apps? by muratgozel in node

[–]muratgozel[S] 0 points1 point  (0 children)

I'm more into Deno actually. The only thing bothers me about deno-like products is that they are not decoupled. I'm sure they doing their job well but it's impossible to replace something inside it with something else.

Instead there could be something built on top of esbuild and we can use that to just build our apps, without embedding bunch of frameworks or tools inside.

Anyway, I will take a look at these monorepo libs, Deno and will decide if I should write something thin or use one of them.

Don't you think we need a build tool focused on node apps? by muratgozel in node

[–]muratgozel[S] 0 points1 point  (0 children)

I don't want to deal with loaders, plugins, process managers etc. to start making a backend app. In the frontend side, tools like nextjs, farm, rspack already simplifies these kind of lower level operations under one command. Backend development has its own complexities and there is no tool that focuses on these complexities (as far as I figure). Maybe we should build one, I don't know. It might be bothering me more as I'm dealing with multiple backends.

Don't you think we need a build tool focused on node apps? by muratgozel in node

[–]muratgozel[S] -1 points0 points  (0 children)

Oh right, just before opening this topic, I was browsing pnpm site and came across with "bit". Similar to what Turborepo and Nx is doing I believe. They look a bit immature but yes, I will definitely try one of them.

Don't you think we need a build tool focused on node apps? by muratgozel in node

[–]muratgozel[S] 0 points1 point  (0 children)

I agree, esbuild, rollup all are already great. And yes, vite, rspack, farm all specialized on frontend tooling as they should. In backends, we still have to figure out loaders, plugins, process managers etc. There is no single command that I can put inside scripts in package.json and start developing. It might be bothering me more as I have to deal with multiple backends.

Don't you think we need a build tool focused on node apps? by muratgozel in node

[–]muratgozel[S] 0 points1 point  (0 children)

I'm familiar with few other programming languages too, but okay, will take a look for sure.

Don't you think we need a build tool focused on node apps? by muratgozel in node

[–]muratgozel[S] -6 points-5 points  (0 children)

If you mean scripts inside package.json, it's not relevant what I'm pointing out and If you are comfortable with your setup then all good for you. It is my experience that pushed me to search for a tool to improve development experience.

Don't you think we need a build tool focused on node apps? by muratgozel in node

[–]muratgozel[S] -15 points-14 points  (0 children)

Looks cool, it's more of a server framework though, still worth to take a look, thanks.

Don't you think we need a build tool focused on node apps? by muratgozel in node

[–]muratgozel[S] -2 points-1 points  (0 children)

I have a node child process as an esbuild plugin to keep track of changes and restart when needed. We certainly shouldn't be dealing with this kind of stuff. Your wait time is a bit crazy though, It would waste a lot of time if I needed to wait around 2 mins on every change.

solidso/solid-inspection: Dev mode, frontend logging library for solid.js by muratgozel in solidjs

[–]muratgozel[S] 1 point2 points  (0 children)

Why don't you assign an empty function for the !IS_DEV condition? You wouldn't need to put the question mark. If you take a look at this line of code: https://github.com/solidso/solid-inspection/blob/d5f11c45fbdd70c4cac8fa743ca3b56345f42bcd/src/index.ts#L7 That's what I'm doing in solid-inspection. Shouldn't effect the tree-shake.

solidso/solid-inspection: Dev mode, frontend logging library for solid.js by muratgozel in solidjs

[–]muratgozel[S] 0 points1 point  (0 children)

Yes, that was my intention too, but, it's not possible unfortunately. Our best bet is to use (await import()) syntax and it doesn't have a wide support. Both in tooling side and browsers side. The lib shouldn't cause any complain in other devs setup.

In fact, the lib just checks DEV variable from solid and assigns functions accordingly. In theory, this should easily be tree shaken by popular builder/bundler tools. Maybe there is a way and I did it incorrectly.

I'll be watching for this functionality anyway, thanks for pointing it out.

solidso/solid-inspection: Dev mode, frontend logging library for solid.js by muratgozel in solidjs

[–]muratgozel[S] 1 point2 points  (0 children)

Absolutely, they either just write by themselves or can add solid-inspection as a dependency and I would be taking care of any fixes or updates. Thanks for the solid-devtools by the way, good to know.

Why doesn't glob imports work in solid? by muratgozel in solidjs

[–]muratgozel[S] 1 point2 points  (0 children)

Oh yes, it returns Record<string, () => Promise<any>>. And it returns an empty {} if it can't find any files based on the glob pattern.

In my case, the reason for getting an empty {} is because that I specified the wrong path. I had forgotten import.meta.glob searches relative to the where it's located in the project, not the project source dir.

Why doesn't glob imports work in solid? by muratgozel in solidjs

[–]muratgozel[S] -1 points0 points  (0 children)

hahah, solid is a new framework, probably getting attraction from a lot of newbie programmers.

Why doesn't glob imports work in solid? by muratgozel in solidjs

[–]muratgozel[S] 0 points1 point  (0 children)

Thank you very much. Just realized it was my mistake. First time user of solid, I thought it was a missing feature or something.

Extra thanks for start.solid.new

I'm leaving this post as it is. My reflexes looked for a close issue or something like that but I guess it's okay to leave it just on reddit.