TehPers

I’ll be honest, I’m not really sure what you’re trying to say, but it sounds like cross-compilation to me? The article mentions several different GUI libraries that require dynamic linking and complicated build scripts, so even if you setup rustc to cross-compile (which isn’t that hard but is an extra unnecessary step for your run-of-the-mill dev who just wants to get paid), getting the build scripts to cross-compile C++ libraries or testing the cross-compiled binaries with dynamically linked libraries is a pain, assuming your build scripts even let you do that.

All of this is avoidable by building from Windows. Or I guess you can not target Windows. That works too, but most businesses won’t see that as an option.

It’s a GUI framework evaluation. I would imagine most users of a desktop application with a GUI would be Windows users. It would generally be a little weird to develop a professional product that does not work on Windows (or at least Mac). It’s a lot easier to develop that natively than to cross-compile.

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.

Nani the fuck?

I’m not sure I agree with their assessment of Standard, but I think what bothers me the most about it is the explosive powercreep in it over the past few years. Current day standard feels a lot like old (pre-MH1) modern, and I guess that was a fun format as well, but it’s so high power compared to what standard used to be. There are some cards that contribute a lot to the explosiveness (Monsterous Rage for example), but every card that sees play these days does so many things that it’s not even comparable to old standard anymore.

I guess I just wish we could have a lower power format again. It’s wild to think today that Divide by Zero got banned in standard just a few years ago.

I guess this means FLS is the official spec now? Does that mean people can stop complaining about there being no official spec?

(As far as I’m aware, while FLS was developed to mirror rustc, rustc does not guarantee that it follows FLS, though they might change that after adoption)

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.

For personal projects, I don’t really care what you do. If someone who doesn’t know how to write a line of code asks an LLM to generate a simple program for them to use on their own, that doesn’t really bother me. Just don’t ask me to look at the code, and definitely don’t ask me to use the tool.

No.

Although I think it’s a symptom of a larger problem. At the very least, consider Rider (or for non-C# code, VS Code/Codium/your terminal editor of choice).

At work, we have to use VS for C# development though, due to us having VS licenses and not Rider licenses. I guess we could use VS Code for C# dev, but I could also use Morse code to type, and neither of those sound like a good time when you take our work tooling into account.

Ironically, many languages that violate these rules are spoken in the US natively. People in the US just like to forget that there are other natively spoken languages (spoken since before English was introduced to the continent even).

English. I can go to the store and buy a sandwich for $8.99 all in once sentence, but splitting it on periods gives you two sentences.

Another couple missing:

• every language uses gendered nouns/verbs/adjectives/pronouns/etc
• no language uses gendered nouns/verbs/adjectives/pronouns/etc
• pronouns referring to people are always gendered
• pronouns are always singular (1) or plural (2+)

A fun language to learn regarding these is Hawaiian, where the language uses a-class and o-class rather than masculine and feminine, and which you use is largely based on how much control you have over it.

I think linking to the original article in the description is a good compromise if you’re crossposting. That would still save a click for myself and others who aren’t too interested in Phoronix’s commentary.

Save yourself a click. Here’s the original blog post.

A more serious answer would be that Rust can’t be compiled to all targets. There is a lot of work to get Rust to compile with gcc though, which would help with this tremendously.

It was mentioned in the notes for 1.84.0 that they began migrating to it. They might be doing it without an edition change if it’s backwards compatible (or if the incompatibilities are considered bugs).