@12bitfloat no they're specifically being chosen without taking race into account. The post is complaining that they're not white, but the director just chose actors he wanted to work with and envisioned for the roles. Your understanding of the situation is actually backwards.

@12bitfloat

So you want actors selected based on talent... but the point of this post is to complain that they're not white.

Also, I've had this account since 2016, I just forgot about this community. 🙃

If the client didn't make an effort to understand the cost of running the project... idk, that's mostly on them, but developers should make an effort to h the client be aware of the costs of the cloud (and the benefit of not having to maintain that infrastructure).

Because the company didn't "feed you" or your family. You exchanged services for wages. You don't owe them any more than that and likely you could have a lot more to learn somewhere else that would help you grow in your career.

This post is such crybaby snowflake bs and is not appropriate for this community. Go take this crap to Parler 🙄

If we really have to have this stupid conversation: With all the conquest, exploration, and trade routes that went on throughout history there's no way to know what color of folk would be where and when. Unless you don't have a time machine, you just don't know. If you find it awkward, it's because of the imagery you've been provided in the past, but that also has little relevance to the actual historical context. But that's hardly relevant seeing as the film is filled with supernatural events.

@Katakompe @Katakompe ah, okay I thought the app you were building had a political context, sorry about that!

Are you building that Texas abortion snitching website? Because I'd build that like shit on purpose.

@TrevorTheRat I don't see how it couldn't cause more code. You have to define the IoC container (except in languages with package scanning like Java), and then import, and then define your injection. All of that code being out of your control, rather than just importing the service you want and using it. I still haven't really heard the value besides ease of defining mocks for tests, but imo that defeats the rule of "don't add testing code to src," but defining your architecture to support it.

This all being said, I also just kind of hate OOP and feel that it's associated "patterns" are really the ways that you manage the shortcomings of OOP as an architecture.

I agree, but I feel like it would be better than the current default (which I consider CRA to be the default) of no types.

@lbfalvy I would say that's the nice thing about TS in general with building mocks is that you're not going to compile if you claim to implement an interface that you're not implementing. And these days, React + TS work pretty solid out of the box. I do wish they just mandated it though, like Angular. Even if they mandated it with a really light TSConfig that allows you to basically just write JS in a TS file for those who don't want to be forced into it.

@kwilliams I do get the generally accessibility for unit tests because it becomes easier to mock particular dependencies for classes so tha dependant gets exactly what they need.

I'd agree with @ostream because when you're in JavaScript-land, Jest allows you to actually replace import content which is just as useful without the weight/complexity of DI to your application. But I don't see why you couldn't just do a provider like this:

`export const serviceProvider = environment === "mock" ? mockProvider : realProvider;`

Tree shaking cleans the mockProvider from your build and I know you shouldn't add code in src to support testing, but it sounds like that's what DI is doing anyways.

As for @lbfalvy ( don't get why you'd want DI in React (or any framework that doesn't require it to work, like Angular which breaks without it), reads like a lot of extra complexity, adding DI to help you debug problems caused by DI. I'd rather just use context for state and just import services.

Hard agree, CORS implementation is stupid. I also hate that it makes cross origin requests take two actual request. I know preflight is quick but it's just a waste, especially when you can just throw up your own proxy and now that whole form of "security" is entirely circumvented.

@dan-pud those seem to all be full site generators. I was likely going to go with Next for fully static pages. But I wanted to fetch content from a CMS. But because all the data is public I think I'm just going to go the S3 route (or more specifically, Digital Ocean Spaces so that I don't have to give Jeff more money).

@blindXfish if it were a new business I would generally agree. Show up on Google and post on social media platforms.

However, I think a lot of people prefer to contact businesses with an email address, in which case you sort of need a website to distribute imo. You can post an email on social media, but if someone is looking for an email, they're looking for it on a website.

The main thing though, is that my wife is doing a silent takeover with the owner transitioning out over 3 months so I want to maintain the current infrastructure and I want to meet the prior clientele's expectations, seeing as the previous owner has done really well for herself overall.

In the mean time, can we just talk about how absurdly terrible @aws-sdk/s3-client is? Good lord, I can't believe how hard they have to make it to pull the actual data for an object! It's absolute lunacy.

Look at how easy it used to be to pull the data for an object, and look how hard it is in the 2021 update!
https://stackoverflow.com/a/...

@sariel I despise maintaining old tech. It's what I do all day at my job. So for me... it's somewhat of a passion project.

But it's not like customers really "use" this. The business is a bakery and the website is mostly marketing, a blog, and an email blaster (which I'm not sure if anyone has signed up or if the current owner sends out marketing blasts).

Trust me, I get where you're coming from. I reccomend Squarespace and Wix to people all the time as the most appropriate solution, and I get that it could meet this use case. However, I'm going to have to own this possibly for the rest of my life, so I would like to build something that I'm happy with, and hey if I want to switch jobs I'll have a great fullstack example to show off in the process.

But don't worry, I know what I'm doing. I will be working on this in free time and likely won't replace the site for at least 6 months to a year or so.

@fzammetti I legit think that would help

I'm a contractor. This happens to about 50% of the stuff I work on right now. Current client is a big company who doesn't need another dev half as much as they think they do so they just keep sending me into tool exploratory missions.

Solid meme, but every certain of this meme these days forgets the last frame which is just Trump looking so hilariously confident and determined.

Why are we being as specific as Angular and inspecific as both web and JS. Also I just left an Angular job (partially because Angular is terrible) and I've been near impossible to replace. Way I see it, if those jobs want bodies they're going to have to shell out big time.

I read this as an entirely reasonable question, any JS dev should know it. But I also get the issue with asking questions so basic that it trips people up because they might think "this can't be that simple, right?"

I mean no one is stopping you in JS 🤷‍♂️

@lbfalvy yeah that's a structure I agree with. Most apps I've worked with have data that's pretty modular. You have stuff that can be treated as pretty separate; like user-profile is separate from accounts are separate from payments are separate from posts are separate from messages... And so on.

The case can be made for substate if you have a deeply nested GQL model that is the basis of your app but most apps just don't justify that complexity.

The full solution is usually to just not do unit tests.

Github Codespaces?

Honestly. Digital Ocean is my first pick for personal projects because of their cheaper tiers. Plus they seem like a somewhat good company. You want something better for cheaper, you could always run dynamic DNS from your house 🤷‍♂️

I've just kind of given up on Redux. I think Zustand creates a much simpler paradigm while still solving all the same problems. It kind of breaks CQRS because it sort of reccomends multiple stores, but there are plenty of patterns you can adopt to clean that up if you care.

Those folks will never get anyone to visit, as if(job=false) will always return false, meaning don't visit

I learned LocalDate over today. It's pretty alright, but I honestly just wish there weren't so many changes and misconceptions. Java Date class is just like the JavaScript Date object and felt very logical.

>inb4 general Java hate thread