redman25

10 ms·

91.
by redman25 2y ago
I agree, class syntax is better. If javascript had been designed today, I imagine that would be the _only_ way to blueprint objects.
92.
by redman25 2y ago
I know that a lot of people advocate for composition over inheritance. Inheritance can add a lot of complexity especially if it is deep or involves a lot of overrides. It can be difficult to find out where a method came from inside the inhe
93.
by redman25 2y ago
Complexity in javascript is probably more like the fact that there are three different ways of constructing classes. Async/await has it's own pitfalls but at least it is adding new functionality.
94.
by redman25 2y ago
If you are trying overly hard to abstract things or work against that language, then yes, things can be difficult to refactor. Here's a few things I've found: - Generics - Too much Send + Sync - Trying too hard to avoid cloning -
95.
by redman25 2y ago
Before switching to neovim, I used a split terminal with vim in one split and the other split for running `rg`, `make`, tests, etc. It's amazing what you can achieve with grep especially if you use something like ctrl+p in vim which ca
96.
Show HN: A prank app created with bevy(github.com)
1 points by redman25 2y ago|0 comments
97.
by redman25 2y ago
Vim land seems much larger than I expected.
98.
by redman25 2y ago
I wonder if the sparse model would perform worse on out of sample test data.
99.
by redman25 2y ago
One solution for performance degradation with soft deletes is to partition the table by some field like `created` monthly. Queries will need to include `created` in the query is the main downside.
100.
by redman25 2y ago
Rust isn’t too bad if you throw clones everywhere. Otherwise, you might as well use a garbage collected language.
101.
by redman25 2y ago
It’s about the amount of value a person can bring as a consumer. Does the consumption of food provide more value to society than the consumption of mega yachts? More equally distributed wealth increases the efficiency of spending (to a poin
102.
by redman25 2y ago
Normally, I’d be equally upset with excess but the fact that this is somewhat of a community building thing is actually refreshing to see from the wealthy (even if by community, it is just friends). It’s mild in comparison to the ultra rich
103.
by redman25 2y ago
> With respect to privacy, we have pledged not to store your codebase [...] It isn't necessarily a strong guarantee to have "pledged", although it is appreciated.
104.
by redman25 2y ago
I've found reliably "turning on" with pmset to be hit or miss. I can't remember the gotcha I ran into if it was that you had to have your laptop lid open or something else...
105.
by redman25 2y ago
Shouldn't all systems be tested end-to-end regardless of if they are microservices or not?
106.
by redman25 2y ago
You can always spin up several services locally or if you have a development cluster run the service you are working on locally against development services.
107.
by redman25 2y ago
Python with types enforced by CI isn’t too bad. Or did you have something else in mind?
108.
Normalizing Security Culture(darkreading.com)
1 points by redman25 2y ago|0 comments
109.
by redman25 2y ago
Seems to me like the value of a threat detection platform would be the detections themselves. With just the platform, and no detections, you have a foundation but the bulk of the work hasn't been started yet. If you're large enoug
110.
by redman25 2y ago
Created a little app for pranking friends and family. Turns a victim’s clicks into confetti. https://github.com/joshvoigts/confetti_desktop
111.
by redman25 2y ago
I've found the Vue community to be a little better at managing complexity than the react community has mainly because Vue was originally touted as a solution to some of react's problems. People are more conscious of the tradeoffs.
112.
by redman25 2y ago
Unless you're building a local first app (i.e. google sheets), the backend for most web apps is the source of truth. SPAs that lazy load tons of data on the frontend are introducing a lot of complexity trying to sync state between the
113.
by redman25 2y ago
Unless you're building an app that holds data locally, for most web apps, you should be pushing state down into the backend. Fat models should be your single source of truth, skinny controllers, and service functions in order to separa
114.
by redman25 2y ago
Isn't that the point that if they couldn't have been fixed that they were problematic in the first place?
115.
by redman25 2y ago
Most GC languages give you limited control over "when" garbage collection or allocation occur. With non-GC'd languages you can at least control them manually based on data structure choice (i.e. arenas), lifetimes, or manual
116.
by redman25 2y ago
Rust can be written simply if you avoid more complicated features of the language. It depends on what you want to get out of it. If you want to develop a library, you might have to dig into more complicated features in order to provide a c
117.
by redman25 2y ago
If you’re ok with sacrificing a small amount of performance for usability, just throw `clone()` everywhere. It will satisfy the compiler. Rust can be written as simply as you want it to be written. Or, you can go crazy with generics or meta
118.
by redman25 2y ago
I love what the author is proposing. I’d be curious how this can work while every library feels like it’s infected by Tokio.
119.
Show HN: Prank app that creates confetti(github.com)
1 points by redman25 2y ago|0 comments
120.
by redman25 2y ago
Shouldn't datetime handling happen in the backend. I cannot imagine why you would trust the client to give you accurate time.

More ›