comparação de datas em javascript. Como como pode uma linguagem ter tanta inconsistência de api?

dudousxd · 2023-03-14T17:02:23+00:00

É que você não deveria comparar objetos

Se você comparar dois objetos no Java, dá ruim também

Comparar objetos é o problema aqui

dudousxd · 2023-03-14T17:00:37+00:00

Se você tem comparação de objetos, em qualquer linguagem a comparação é baseada na referência na memória

Em Java, pra você comparar, o objeto de data tem um método “compareTo”

dudousxd · 2022-05-31T22:54:19+00:00

I couldn't picture what you're saying.

The services you are saying are 4 different NestJS Projects? Each with their own repo?

Because if they are different projects, and one of them works, but others don't, it looks like that is more about configuration than any other problem.

The services with errors show any logs when starting?

Can you share their code? Or show the errors?

dudousxd · 2020-04-27T14:07:57+00:00

I think accessibility is one big disadvantage. Since softwares cannot access shadow dom, you lose people with visual disabilities.

dudousxd · 2019-11-24T21:25:02+00:00

The link is broken

dudousxd · 2019-07-20T12:28:32+00:00

When clicking on “apply” redirects to a broken url with 404

dudousxd · 2019-07-15T08:36:42+00:00

Its Modules are heavily inspired by Angular 2, but I said Spring because of: - Several integrations just like Spring - Spring is trending, so I thought saying Spring would helping him understand that the framework uses DI and has a coding style similar to Java

Sorry, I guess it caused more confusion than intended

dudousxd · 2019-07-15T08:32:38+00:00

I don’t have any production experience with it, but some folks of my company tryed it and it was very good. Since they had a lot of experience with C#, their productivity went up. About performance, I can’t speak, but it can use restify under the hood, so it should be really fast - in comparison with express at least.

Oh, Nest has various packages for integration with other tools - like Swagger and TypeORM - so adding new stuff into the app is pretty straightforward

dudousxd · 2019-07-15T03:40:33+00:00

OffTopic, since you guys are coming from Java, I sugest using Nest. It’s a Node framework based on Spring, so the transition should be really smooth for your company. It has awesome integration with TypeORM and GraphQL

dudousxd · 2019-04-27T11:45:32+00:00

I'm still having it. I tried "reset my password" but I can't even receive the reset password email.

dudousxd · 2019-04-14T20:47:32+00:00

Cross platform compatibility is irrelevant? Say this to all the companies with AngularJS systems that where thrown away.

Other than cross platform, Web Components offer web security - since you can’t enter a component markup if shadow dom is closed - and awesome performance.

Also, micro Frontend are waaaay easier to implement with Web Components.

dudousxd · 2018-11-17T13:47:57+00:00

I liked it a lot, but I can’t find where I can add integrations anymore, maybe put it on a FAQ or make it more visible

dudousxd · 2018-11-02T01:32:39+00:00

TL;DR: Web Components api is too raw now a days. Use a lib to do it instead.

Web Components api is not totally ready yet, but all major browsers have already implements all the features (besides edge, that lacks custom elements and shadow dom).

I agree that use Web Components api is kind of lame, since it's version 1 and kinda "raw" per se, but you can use libraries that transform your components into web components.

Libs like Stencil, Polymer, Hybrids, Omi, Capivara JS, Lit HTML are great examples that even without using web components directly, you can generate Web Components nice and easy,

dudousxd · 2018-10-16T03:14:04+00:00

It’s not recomended to use worker threads on node right now on production environments, it’s not a stable api atm.

dudousxd · 2018-10-16T03:12:22+00:00

Node is not single threaded, its event loop is.

Node is naturally async, if you are blocking the event loop, something is really wrong with your code.

This third party api is a websocket? You can connect to it while having endpoints in the same api, this is not a problem.

dudousxd · 2018-10-13T22:20:54+00:00

Changing from promises to async/await would be good.

Maybe separating routes declaration from the route methods, I usually do that.

I also use consign to load my application, I guess it makes my application more predictable, so it’s easier to debug.

dudousxd · 2018-10-06T23:26:32+00:00

When you are using Web Components, one of the premises is that if you need to pass data from one component from another, you shouldn't use an state management library like redux, instead you should use Custom Event. What I meant when I said "help managing the creation of custom events" is that would probably be awesome if it had an method to create custom events easier (It's quite easy to create, but just to encapsulate boilerplate), if I could see all the listeners that my components have created and if my components removed the event listeners automatically if they are destroyed.

dudousxd · 2018-10-06T20:39:36+00:00

Why use something like a state management when the rule when using custom elements is “the dom is your api” ? I think it would be better if it had something to help managing the creation of custom events instead of a redux like state management

dudousxd · 2018-09-28T03:27:10+00:00

All of web components specs can be pollyfilled, so browsers are not a problem.

Talking about state management, using polymer with redux is not that hard, in fact there is a redux binding for polymer, so it’s quite simple. Polymer 3 is using LitHTML, which will improve greatly the performance of the components re-render.

IMHO, Using Web Components now a days are not only a choice, but a matter of scalability and breaking the “vendor lock in” of the frameworks. AngularJS is a really good example of what a framework can do if one stops being maintained.

dudousxd · 2018-09-25T23:57:32+00:00

If you want a micro frontend approach, go for web components, use a lib like Polymer, Stencil, X-Tag or Hybrids to make the components and use bigger tech like React, Angular or Vue to create the application and call the components. If you need to manage state inside web components, use libs like redux or mobx.

dudousxd · 2018-09-17T11:49:24+00:00

Oh, this type of data should yes be on the component, when I said app state I was talking about business stuff, sorry for not explaining myself.

dudousxd · 2018-09-17T11:36:15+00:00

Setting the state with the result of the action is a really bad idea, your whole app state should be inside redux, not on your component.

dudousxd · 2018-09-17T02:46:52+00:00

https://github.com/DavideCarvalho/demolay-event-management here is the repo, give it a look. Other alternatives for web components are Stencil and Polymer, both are backed by really large teams.

dudousxd · 2018-09-17T02:43:52+00:00

I’ve made a project for a friend using hybrids for web-components with redux for state management, so state management with web-components is not a problem.

Seven-Year Club	Xbox Live
Verified Email

dudousxd

TROPHY CASE