TehPers

When you tariff them by over 100% of their value, they tend to cost more to import.

My whole comment was on the tariffs specifically, and there is a 100% chance they affect sales in the US. Even with cost reductions in manufacturing over the total lifetime of the console, there’s no chance they cut costs enough to keep up with the tariffs, and there is no chance they planned for the tariffs to be this high in their planning.

Outside the US? These tariffs aren’t applied, but raising the prices globally limits the impact of them on one of their largest markets since they can amortize the cost across all their markets instead of just one.

If you are new to something and want to learn, seek resources and educate yourself with them. Learning takes time, and there are no shortcuts.

A hot DB should not run on HDDs. Slap some nvme storage into that server if you can. If you can’t, consider getting a new server and migrating to it.

SQL server can generate execution plans for you. For your queries, generate those, and see if you’re doing any operations that involve iterating the entire table. You should avoid scanning an entire table with a huge number of rows when possible, at least during requests.

If you want to do some kind of dupe protection, let the DB do it for you. Create an index and a table constraint on the relevant columns. If the data is too complex for that, find a way to do it, like generating and storing hashes, sorting lists/dicts, etc just so that the DB can do the work for you. The DB is better at enforcing constraints than you are (when it can do so).

For read-heavy workflows, consider whether caches or read replicas will benefit you.

And finally back to my first point: read. Learn. There are no shortcuts. You cannot get better at something if you don’t take the time to educate yourself on it.

Sure you can. Actions taken in the right direction are still going in the right direction regardless of who makes them.

This would be like saying that a member of a capitalist society can’t criticize their society. It reeks of “yet you participate in society”.

This depends on the markets. For example, if prices in the US raised 50% due to Tariffs, then they might lose one of their largest markets, but if they can raise them 10% globally, then they can potentially limit that loss and still have a chance (as much as possible anyway) in all of their markets.

Either way, they need to raise prices because their costs have gone up. It’s a question of where that money is coming from, and how they can reduce its impact on them as much as possible.

There are ad docs in the dotnet copilot.

For your second part:

A lot of open source projects exist to make people’s lives easier at work. The people developing these projects are often also people who have jobs as devs and have a use for the projects. It just so happens that it’s easier to use these libraries at work and share them with others when they’re more permissively licensed, and there are community benefits when people all contribute back to it.

There’s nothing wrong with wanting to go the AGPL route and forcing everyone into open source, but that makes it much harder to use these tools at work, which often kills the motivation behind building them in the first place.

I tend to be of the opinion that community tools should be GPL/AGPL, while libraries can be anything. It works as a compromise for both - so devs can have an easier time at work while also forcing contributions back to community-developed tools.

Edit: I should also mention dual licensed AGPL/paid commercial. That model is probably my favorite, but unfortunately uncommon.

The two-sentence ruling offered no explanation for why the judges were overruling the trial court; it also didn’t name the judges who made the decision. And it came despite the judges hearing no oral arguments on the case.

Clearly it’s because Chewbacca lives on Endor, but that makes no sense.

This seems to me more like a complaint about JS’s functional methods on arrays being eager rather than a complaint about loops. All of this is solved in languages with iterators (or async iterators for a potentially better solution).

For example, in C#, .Where does nothing immediately on enumerable types, and on IAsyncEnumerable, you can go as far as streaming/chunking results from a DB into the enumerable and filtering off the DB asynchronously just by passing the enumerable into an await foreach. In Rust, you get the same options (though more verbose) using streams from futures.

Edit: the rest of the article doesn’t really have much to do with loops, but these are all solved problems in C#, Rust, and I assume other languages too. Even Python has iterables, and you can configure your thread pools however you want to for concurrency.

It also tends to spray under low pressure, which is unfortunately both at the start and end. Mid-piss, it’s generally fine from my experience.

If you’re asking if I sound before pissing, no. If you’re asking if I go out of my way to piss on myself, also no.

Don’t claim your piss shoots out like a laser pointer. Nobody will believe you lol.

Edit: I think I misunderstood you. I’m in the US, and we tend to have this strange phenomenon when we’re born where the doctor likes to practice their surgical skills on our junk right out of the womb. So I think your question might be irrelevant to me basically.

I appreciate improvements, but I don’t think this will solve the problem of pee shooting out in random directions (occasionally vertically down) before setting on a gentle spray in all directions at once. It’s not even like we’re free-handed firehosing the stream or anything - even carefully aimed, it can decide to just fuck off to the right for no damn reason.

Anyway, all this to say the floors will still be sticky, but hopefully less so.

There should really be a different term for Instagram/TikTok/FB/etc style social media sites (I call them “push-style” social media, though “algorithmic” is probably a better term) and websites like public forums, chatting platforms, etc. The former is what I think this article is talking about. The latter seems both fine and necessary these days, even in some cases among children.

For your goals, I would stick with Python unless you want to learn another language. There’s not much value to switch away when all the tools you need are primarily designed for Python.

As far as functional programming goes, with AI stuff, my experience is that you generally are more interested in orchestrating services than FP. For example, run input through model #1, then based on the output, run one of these other 3 models (or multiple of them in parallel), then eventually pass it all back into another service/function to aggregate and format the outputs. You can think of each of these as being “functions”, but they’re much higher level than what you’d traditionally consider functions in FP and more along the lines of microservices.

Space, apparently.

Have you considered doing it in Rust instead? You can even do the frontend in Rust for extra internet points.

Some of these key findings seem a bit overblown. The number of domains persistently connected to shouldn’t really matter - one is enough. Update checks are standard for software. Unique IDs/device fingerprinting are so common that browsers build in ways to try to prevent it at scale. JWTs are standard authentication tools - who’s the security concern for? ByteDance? Or are you saying the JWTs are from the local machine? And MessagePack isn’t exactly a secret format either.

The TL;DR of this seems to be that ByteDance’s AI IDE collects a crazy amount of data and offers free AI services in exchange. I’m not really sure why you’d want those services, especially at the cost of all your code potentially being stolen or other data being collected, but it should be obvious that nothing in this world is truly free.

I would say run Doom, but I’m not confident in that. At the very least, Skyrim hasn’t been rereleased on it yet.

An alternative could be to use something like postgres with the pgvector extension to do semantic searches instead of just text-based searches. You can generate embeddings for the text content of the story, then do the same for “sci-fi” or something, and see if searching that way gets you most of the way there.

Generating embeddings locally might take some time though if you don’t have hardware suitable for it.

SQL is designed for querying (it’s a query language lol). If the stories are huge, you can save them to individual files and store the filepath in the database, but otherwise it can hold columns with a fair amount of data if needed.

You can probably get away with using sqlite. A more traditional database would be postgres, but it sounds like you just need the database available locally.

Can’t speak for everywhere, but in the US, if your first questions are about salary, they’re going to be left wondering if you’re even qualified for the job and if money is all you care about. Even if it is (which is fine most of the time), that’s not really the impression you should give if your goal is to be hired.

Asking about salary later on is usually a much better idea. You know whether you actually are interested in working there, the interviewer knows if they are interested in you, and wanting money it isn’t the first impression you give.

As for Python - leetcode style interviews are common, but almost always worthless. The only real value the company gets from something like that is to check that you actually can write code. They’re pointless beyond that, and a company doing leetcode interviews should be a red flag.