How is this the first time I hear about mangoWC?

What are the advantages compared to searxng?

Vou escrever em português já que não falo espanhol e assim para uma pessoa que fale espanhol deve ser fácil de perceber.

Mesmo textos japoneses normais, especialmente aqueles escritos um bocado mal como o meu, têm muito hiragana, mas maioria das palavras que se conseguem ler normalmente não dizem muito. Por exemplo, na primeira frase, se só se lesse o hiragana:

“_” “mais ou menos” “desde” “_” “<- especificar objeto” “_” “<- fazendo a ação anterior no objeto especificado” “_” “sou”

Por outro lado, só lendo os kanji:

“3 anos atrás” “japonês” “estudo” “pessoa”

Juntando tudo:

“3 anos atrás” “mais ou menos” “desde” “japonês” “<-” “estudo” “a fazer” “pessoa” “sou”

Ou seja:

“Estudo japonês há cerca de 3 anos”

Por isso mesmo que se saiba ler hiragana, muitas vezes (maioria das vezes) as partes mais importantes das frases são as que não se conseguem ler! Mesmo quando maioria da frase é composta por hiragana ou katakana!

Mais, existem kanjis que parecem-se com katakana. Por exemplo:

口　ロ 夕　タ

Por isso sem contexto pode-se pensar que se está a ler uma coisa quando na verdade é outra.

Mesmo assim, acredito que só conseguir ler hiragana e katakana já é impressionante o suficiente ;)

三年前ぐらいから日本語を勉強している人です。あなたのメッセージを翻訳した。

英語はどこにでもある存在。故に、英語とコンタクトすることを世界中のどこでも逃さない。

が、他の言語を練習することが難しいとは言えない。

電子書籍を読む、動画や映画を観る、音楽を聴く、それにインターネットでネイティブに会うこともできます。

よって、目標の国を旅行しなくても、言語を覚えることができると思う。例え英語だけを話せても。

後、あなたはおそらく英語を覚えることが楽しいや簡単や有用だと思うだろうが、それは甘いだと思う。

人は時間がなかったりモチベがなかったり、私の思う日本人の場合、日本語との違いは大きすぎて、継続的に触れても覚えることがとても難しいのです。

上に、この頃大体の人々は強制的な英語授業を受ける。それでも授業を受けなかった人々もある。最初の一歩をしないと何も始まらないかもしれない。

英語を覚えなくても、自動的に文化交流をしたくないと考えるのが甘い。

悪い日本語でスマン。

I have no idea why I wrote this tbh

Usually yes, but afaik not in this case.

The argument would be:

“You are amab therefore not a woman”

Which implies:

“You are either amab either a woman”

But a question remains:

¿Por qué no los dos?

…but how should I interpret your passive aggressiveness if I should interpret your use of punctuation as no more than an effort to communicate clearly?

You can ask for no ice and get the 1L of soda experience just as it was meant to be

I believe it’s AI slop. I checked until 2012 and unless I missed something, there isn’t a single year where the list goes “France, Turkey, Canada, Indonesia.” In proper AI fashion, it looks correct at first glance but the further you go the worse it tends to get. The information could be from another source, but the hammer in china tells me otherwise.

I believe vimium does this with T

Edit: Wait, you don’t even need that. It’s already built-in https://support.mozilla.org/en-US/kb/search-open-tabs-firefox

go to swiftkey > language > add language and it looks like simply adding a german keyboard should do the trick.

It says:

Multilingual: You can type in any installed language that is supported by your current keyboard layout without the need to switch keyboards.

in gboard, at least, you can set two dictionaries for the same keyboard, which I think should theoretically prevent that from happening. If you’re using an iphone or another keyboard an equivalent feature might exist.

I know you’re probably just ranting but I’m going to say this anyway because I, too, had the same issue before discovering this

yet to see hand people going at it

I don’t use forgejo actions. This bug doesn’t affect me, right?

This article gives me vibes that someone wrote a few lines outlining the situation and asked the AI to write the article itself. Interestingly though, I think most people would just rather read the outline, less time wasted and less llm.

A part that screams AI would be:

This wasn’t subtle venue security—your biometric data became part of the artistic statement, whether you consented or not.

“This isn’t this–it’s that” is an extremely common AI sentence structure, further exposed by the fact that the part before the em-dash doesn’t even make sense to begin with. No one was asking themselves whether it was part of subtle venue security.

As a sidenote, sometimes I read sentences like this and I wonder “could this ever even have been written by a human?” I think that there’s a very low chance that this article didn’t have at least some amount of AI involved, but I know that somewhere out there there must be some people who actually write like this. And that’s kind of sad.

tbh I don’t even know why I even wrote this, the entire article appears to be one big example of generic AI writing

Resume: Either get married and be made to watch on a man’s phone Either don’t get married

The meaning of either or

used to refer to a situation in which there is a choice between two different plans of action, but both together are not possible

Thus, if you want to truly feel that pedanticness, getting married or not getting married is, by definition, an either-or situation, since you can’t be married and not married at the same time.

Questionable though my reasoning my be taking the context into account, get outpedantic-ed!

I probably have forgotten more programming languages than you can list, and if there are constants in programming, then a) while compilers get better at catching bugs, they never got over the basics, and b) a good programmer will alyways be better at preventing and catching bugs than a compiler.

I agree with this

Once you have aquired a good mindset about disciplined programming, those buglets a compiler (or even code review systems) can find usually don’t happen.

I also agree with this.

I would like to put a lot of emphasis in the usually. It doesn’t mean that they don’t happen, no human being makes no mistakes. Rust simply gives people a little more peace of mind knowing that unless they use unsafe they’re probably fine in terms of memory issues.

As a side note, there was this once I was making an ecs engine in rust, and kept fighting the compiler on this issue. Specifically, the game engine bevy uses Query in the World to retrieve information about the game state, and I wanted to do the same. For instance, in the following function (or something similar, I honestly don’t remember all that well):

fn getplayer(player: Query<Player>) {}

Would get player from the world and assign it to player (more or less). However rust was adamant in not letting me do this. After some thinking I finally realized why

fn getplayer(player: Query<Player>, player_too: Query<Player>) {}

Would give two mutable references to the same Player in the same function, which can be very easily mishandled, and thus is not allowed in rust.

I don’t know about the MISRA standard, but I don’t think that using it would have changed the way I coded my inherently flawed approach. This is a small example, one that didn’t even matter that much in the grand scheme of things and could be even hard to understand why it’s bad without knowing rust, but it is the one that came to mind. I think that if I had more experience I would he able to give you one that actually had security implications.

I’m no seasoned programmer, however

It’s the bugs that even evade a seasoned programmer that poses the problems, and there, Rust won’t help either

What do you mean these are not the ones that rust tries to fix? Even huge projects like the linux kernel get memory bugs. I don’t know anything about ADA and nor do I want to “evangelize rust” but what you’re saying sounds boggers.

Obviously rust cannot prevent all bugs or even most of them. It can only prevent a small subset of bugs, but saying that that “small subset of bugs” wouldn’t happen to seasoned programmers is just wrong, especially when you have tons of programmers working on the same big project.

I don’t mean to say that rust is always the correct choice, but that you’re waving off its greatest offering as bicycle training wheels (i.e. something no seasoned programmer would need)

Yep! What I wanted was for a “just works” experience as much as possible. Having to manually install lsps and treesitter parsers manually with nix felt like a bummer, honestly. It does work though

I don’t get why using an unsigned value is bad in this context. Like you’ve said yourself, why would you add support for dates that happened before the creation of the network?

“Guess what it is not processed locally anymore”?