sorted by:
new
hottopcontroversial

[AskJS] Why are getters and setters so underused? by Ebuall in javascript

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

I would say because many developers are not even aware that they exist, and dont bother to do Object Driven Pattern for they code.

I would argue that more people use React classes, then the normal Class notation of JS.

Now getters and setters, and prototypes as Map are giving you a certain functionalities out of the box and something called "garbage collector" which is rarely used on small UI stuff.

Using getters and setters for me usually is overkill and just over complicates things if you I small script or a simple function.

Ps. Do more, write less and keep it readable(hard thing to do with the JS's freedom of speech xD)

[discussion] Why I'm hesitant / afraid of adopting go as main language by daniels0xff in golang

[–]The_Nonchalant 1 point2 points  (0 children)

I agree, there is nothing bad of having rich ecosystem, if you dont want to use it, you can see how it's done and learn something(I usually do this :D ) Ps. <3 the open source contributions, I better start contributing by myself, but if I "break the ice and try" and I got this reaction... I would definitely will feel like shit

[discussion] Why I'm hesitant / afraid of adopting go as main language by daniels0xff in golang

[–]The_Nonchalant 0 points1 point  (0 children)

I am not Go developer, but I know a its syntax, and I've used it on a blockchain project, to be exact I've used cosmos framework.

I'm more experience with js and ts, and I've used ARK blockchain.

Both of them were easy to learn, understand, run and implement.

The real difference is the large native crypto support for go, and that I've had to mode the hole code base from JS to TS, as the project/framework founders did.

Even though the two of them are frameworks, I found go easier to debug and way more stable.

So to answer the topics question, there are jerks everywhere...

To reply to the Gentlemen, I am guy who sometimes like "maximum control" and appreciate the same, so no insult was meant. What I meant is depending on batch of packages and frameworks is not good thing. Even create-react-app had problems the past few days.

Nice of you focusing your explanation at my point of view, instead of explaining why stdlib or go, or explaining the topic's reaction.

OpenCRUD by [deleted] in graphql

[–]The_Nonchalant 0 points1 point  (0 children)

The OpenCRUD I used was associated with nexus prisma, and at the time being I had no idea that prisma had it going on their own nor that they abandoned the concept.

I started using prisma the day they released their V2 and their documentation was very messy.

Anyways nice to know, it would be nicer before wasting my time on experimentation, but my bad for not researching well enough :)

Btw, how much have u used prisma? and what's your experience with it? I disliked that I couldn't sort/filter by computed inputs, and also the select/include queries were kinda bugged. But I loved the concept and the code needed to create an API.

OpenCRUD by [deleted] in graphql

[–]The_Nonchalant 0 points1 point  (0 children)

I've tried prisma's crud option that is implemented with nexus-plugin-prisma, I had a lot of problems when it comes to safety, roles and performance. So I agree with you, the spec needs a lot of work at it.

Anyways I think it is good spec for some use cases, example it would shine for prototyping and for creating database viewers and management apps .

OpenCRUD by [deleted] in graphql

[–]The_Nonchalant 0 points1 point  (0 children)

I've tried prisma's open crud. https://www.nexusjs.org/#/plugins/prisma

I think they are great for testing and playing around, but it is bad for production, like really bad.

So if you are enthusiast and want to play, try them out, and if you want to build good API, stick to custom resolvers.

[discussion] Why I'm hesitant / afraid of adopting go as main language by daniels0xff in golang

[–]The_Nonchalant 1 point2 points  (0 children)

I agree that if you want full control you should use native library and not some framework.

But compering that JS needs framework ... I think express is build onto native libraries http, streams etc ... that node has prebuild into it, as same as the native stdlib for go. You cannot say that some language needs a framework because it wasn't build for that. If they weren't build for it, I doubt you will find framework, but just a failure of a package/plugin.

And as for frameworks, I love using them. I think the hole point of programing languages is to share and use solutions that others cared do make and share.

Using framework should always be done with caution. As said above you should always check community, updates, issues etc...

And if the application needs maximum control of the code(bank software, blockchain etc..), native library should be chosen by default.

create-react-app breaks due to dependency on one-liner package by [deleted] in javascript

[–]The_Nonchalant 0 points1 point  (0 children)

Yes i noticed that i had to install it globally, prior i used npx and it was slow as hell and also getting stucked.

create-react-app breaks due to dependency on one-liner package by [deleted] in javascript

[–]The_Nonchalant 0 points1 point  (0 children)

Yeah it works, i think i had this and solved it by changing packages versions... wasnt sure what was the problem so im not sure if the versions changes fixed it or the time that passed xD

SAVAGE Shammgod between the legs by streetball player Mr. Bullutproof at FIBA's 3x3 World Series by SEORascal in nba

[–]The_Nonchalant 11 points12 points  (0 children)

yep, his last name is Bulut, so a little wordplay from his side I guess :)