This is not a supply chain attack, it is sudden extreme enshitification. according to the article, the attacker also bought the GitHub repo

I don’t see how buying the GitHub repo as well makes it not a supply chain attack but enshitification.

They bought into the supply chain. It’s a supply chain attack.

In my Firefox I get a NS_BINDING_ABORTED error on the Google Fonts font request.

And they didn’t specify a font fallback, only their external web font. It would have worked if they had added monospace as a fallback.

Ignoring secondary email addresses, what was my primary [onlineaccount] E-Mail address has changed four times.

Nested CSS obscures complexity

An interesting point. Something I will take with me for observation and consideration.

Maybe sometimes it’s worth despite it and other times not.

extending the list

• You don’t need JavaScript to build web pages
• You don’t need JavaScript to publish web pages

Seems like a valid formalization.

I think a or a few counter-examples would go a long way though.

The “rectangle” probably isn’t supposed to be this messy?

Are you saying “don’t use a synthetic key, you ain’t gonna need it”?

People regularly change email addresses. Listing that as an example is a particularly bad example in my opinion.

many2one: so in this relationship you will have more than one record in one table which matches to only one record in another table. something like A <-- B. where (<–) is foreign key relationship. so B will have a column which will be mapped to more than one record of A.

no, the other way around

When B has a foreign key to A, many B records may relate to one A record. That’s the many2one part.

The fact that different B records can point to different A records is irrelevant to that.

one2many: same as many2one but instead now the foreign key constrain will look something like A --> B.

It’s the same, mirrored. Or mirrored interpretation / representation to be more specific. (No logical change.)

If you had B --> A for many2one, then the foreign key relationship is still B --> A. But if you want to represent it from A perspective, you can say one2many - even though A does not hold the foreign keys.

In relational database schemata, using foreign keys on a column means the definition order is always one to one, and only through querying for the shared id will you identify the many.

many2many: this one is interesting because this relationship doesn’t make use of foreign key directly. to have this relationship between A and B you have to make a third database something like AB_rel. AB_rel will hold values of primary key of A and also primary key of B. so that way we can map those two using AB_rel table.

Notably, we still make use of foreign keys. But because one record does not necessarily have only one FK value we don’t store it in a column but have to save it in a separate table.

This association table AB_rel will then hold the foreign keys to both sides.

Ask your profs or other applicable personnel for offered final year projects, suggestions, and previous years projects. You can also check software dev companies which may offer such projects as job openings. That’ll give you more of an overview of current common projects, and some ideas of what you could do.

Did you stop programming altogether? /s

I think you can potentially get stuck with worse when you stop Java.

For a desktop app I would go with none of those.

If cross platform is the goal, the more important question, and independent of the programming language, is which GUI framework you will use.

Your best bet, at least if you are looking for a stable GUI framework, the best candidate may be C++ and Qt. But that’s a hassle in its own right - both C++ and Qt.

TypeScript will have some solutions for you, with web rendering as a desktop app. Golang will have Qt bindings or other more experimental/not thoroughly established+popular GUI frameworks.

My personal favorite ecosystem is .NET. It has an official cross-platform UI project MAUI, but without an official Linux target. Community extensions probably exist. Personally, I dislike the way the UI is declared and bound though (XAML).

My current interest, which I have not explored or validate yet, is using .NET but then host a web or Blazor app in it with Webview2. .NET supports cross-boundary programming, crossing web+managed/native development, and crossing web(HTML+JS)+managed.

Most of the time GUI and the framework technology is a hassle. Your question is too broad and unspecific, so there’s not a good answer.

If it’s not a “serious” project that you depend on [for your livelihood], pick and start with whatever [looks good or interesting] and go from there. If it is a “serious project” do a bit more GUI framework exploration and assessment, and pick and commit to something. If it’s a big commitment or risk, do prototyping with your candidates for verification and assessment - beyond the most simple examples, and for your specific usage.

deleted by creator

Sounds to me like the AI was programming using you instead of the other way around.

Did you copy and paste back and forth without learning or understanding anything? Or did you read and assess the results, and try to understand errors and issues?

I know Julia. I used Julia. I moved away from Julia.

I’m on Nushell now for scripts, or C# for utils.

Mojo? Mojo games?

Mozilla has good introduction guides into web development https://developer.mozilla.org/en-US/docs/Learn

I would learn on the project, and use the official documentation to look up what it is, how it works, and how to solve what you want to do.

I’m surprised my not one of the biggest German cities is in there too. Very cool.

First half is a general introduction, second half is an introduction to their product Digma, which is limited to Java and IntelliJ.

Currently, Digma fully supports Java and IntelliJ, along with related frameworks such as Spring, Spring Boot, Dropwizard, and Micronaut. If you’re interested in other languages, you can find more information here.

Overall it feels shallow to me.

From what I see they didn’t even support the claims they set out to present. They show a few screens of their tool, but never how that would “avoid breaking changes”. The conclusion is incredibly generic. Feels like publicity/promotion and keywords content was the goal rather than actually sharing information. OP only posting their Digma content fits the impression of PR too.