As Godot is still very simple from the UX perspective, I'd prefer a set of tools to fully replicate the flash workflow instead of a dedicated app. Why reinvent the wheel? Stuff like keyframe animation editor etc is already there anyway and the engine is powerful enough. Just missing some tools, which could be easily added via the asset store.
Robot slaves is a funny phrase if you consider that the origin of the word robot literally is a term that meant slave or "forced work". Language doing circles.
Not only that, but in Russian, the equivalent word for verb "work" (as in "go work" or "do work"), is "rabotay", which is derived from the word "rab" which is the word "slave". So "to work" is literally "to slave", in Russian (and quite a few slavic languages). An English speaker may categorize this as a linguistic anachronism, but a slavic speaker would categorize this as linguistic honesty.
This is pretty common. In Hebrew aved means both "work" and "slavery" and you have the same in Arabic and other semitic languages. In Ancient Egyptian "bak" is used for both "servant" and "worker". The ambiguity in the Hebrew is why many references to this are translated as "servile labor" in the King James, as they were uncertain of the sense of the term meant, or perhaps correctly guessed that both senses were meant. In many ancient languages, e.g. ancient egyptian "worker" and "slave" were synonyms. In modern parlance "slavery" or "servitude" is viewed as an unspeakable evil and people are shocked that there is linguistic overlap with neutral terms like "work" or "labor", which are just ubiquitous parts of life, but historically this is quite common and it is true all around the world, for example in German "knecht" means both "servant" and "farm hand", and in Latin "minister" meant "servant" or "subordinate" (as opposed to "magister"), just like in english you have "server", "serve", "servant", "servile". In Sanskrit "dasa" originally meant "foreigner" or "enemy" and then later "slave" but over time it has come to be used as a suffix to denote someone who "serves" a diety voluntarily, e.g. "Ramdas". In Ancient Japanese you have "yakko" for a low status worker or servant, and later that evolved to footmen who carried baggage for samurai.
Wait until you find out what the word 'ciao' meant in the original Italian/Latin: 'ORIGIN: Italian dial. alt. of schiavo (I am your) slave from medieval Latin sclavus slave.'
The same thing I wonder when one claims Jupyter notebooks to be literate programming.
I think cue might be close but to be honest, some practical examples would have been helpful to get a better impression of the point the article is trying to make.
I use it for my music files and audio books as it is smaller than mp3. In average it was around 1/3 less space used, I think. I do not hear a difference, but just to make sure I usually convert from the highest available format available, often FLAC, to opus using ffmpegs default settings. No regrets so far. Doing this for a few years now.
I encode parts of my FLAC music collection to 96kbit Opus for the mp3 player that I use in my car, or just walking around. Cars and cities are noisy, and the earbuds I use aren't great, so I'm not concerned too much about the quality I'm leaving on the table, but it's good enough and the space savings are awesome.
You never have only one requirement to satisfy. For example, if you'd welcome a certain amount of contributors, your language should be something people know or people like to learn. And of course it may just be the mood of the initiator, which I find completely fine.
Personally I find rust projects very inviting. Figuring out the amount of unsafe code is easy with grep/rg (to a certain degree), the project structure is pretty standardized, etc. All of this makes even a complex project relatively easy to start with. At the same time, the language is pretty usual (C-like and readable). I understand people like it, and writing "written in rust" is a good call for those people, I guess.
"Written in JS" would communicate something else than "written in D" or "written in C++". It communicates a lot of things implicitly.
First of I think it is nonsense as I never got any NSFW content with filters enabled, and I actually always disable them and still get no NSFW content if I do not search for topics that can at least imply it.
But the main point here is that this is something generated in a chat-like product. The task and expectations and level of control are completely different. I am not saying it is impossible something like this comes up in a model even with good training data, but even in this unlikely case, this would be easy to catch with a filter.
AI is not search. It is a likelyhood-based text generator which can be useful for finding good terms for search and a lot of other uses, and while people use it for search, the mode and UX is completely different. That is why people use it as such!
If a Restaurant cannot provide proper hygiene, it will be forced to improve or be closed if noticed. And for Grok (and others) hygiene is in question due to such incidents. Society needs to discuss metrics for AI chat hygiene so we can have consistent law enforcement to shut down services like these when they are not hygienic enough.
Still not Habecks legacy. This was decided under Merkel.
Besides, CO2eq are often wrongly measured with nuclear energy, ignoring building emissions and effect on the water temperature in rivers (every summer more and more plants need to shut down because of this), etc. Even if this would be done right, there are again and again longer periods where Germany exports energy to France because their reactors are often in maintenance. In the end I would say it is always a bad idea to rely on only one technology to a large degree. Only a well done mix makes you resiliant.
I agree on this point, me not being anti-Nuclear doesn't mean I am anti-wind or solar. Every country has different circumstances, I live in a landlocked country with mild mountains, temperate climate and modest rivers. In our case nuclear energy seems like the most reliable and scalable option. For countries with huge coastline off-shore wind absolutely makes sense, simialrly with solar.
> Besides, CO2eq are often wrongly measured with nuclear energy, ignoring building emissions.
I think this point is overestimated. Based on a brief search, studies show nuclear carbon intensity around 6-12g, and the building emissions just around 13% of total lifetime emissions [1].
> there are again and again longer periods where Germany exports energy to France because their reactors are often in maintenance.
Valid point but the 2022 French nuclear "disaster" hasn't repeated at that scale so far. In recent years France is a net exporter to Germany. I can imagine that as with many problems in renewables having technical solutions the water temperature problem is also solvable technically.
How strong correlation is there with energy exports from Germany and the status of France nuclear reactors? From a casual look, exports seems to be correlated with weather and access to excess energy, rather than demand from neighboring countries. I would like to see some support that "Germany exports energy to France because their reactors are often in maintenance", rather than Germany export energy to France because windy/sunny weather is producing excess energy.
Looking at Denmark, their export and imports have little correlation to neighboring countries demand or supply. They will try exporting if the wind farms produce excess energy, and they will try importing energy when demand exceed supply. Neighboring countries demand will mostly only have impact on export price.
Reading this on my Fairphone 5 and can't reproduce this issue. But I admit that sometimes I just want to see the lock screen and accidentally unlock the phone. Therefore, I still agree. The back is the better position for the fingerprint reader.
It rarely happens right when locking the phone, mosty because I already developed the habit to press the power button not with the tip of my thumb but lower down, where the joint is. But when shoving it back in my pocket it still happens on a regular basis, even when I try to avoid it. The button is just located in such a way that it's very hard to avoid touching it while doing so. Then I pull it out a while later to find I changed 20 settings and made a dozen in-app purchases. ;)
Not sure if there was an option, but I would not want to enable it anyway. I want to avoid baby fingers to enable the screen ;) I remember I enabled it with my previous phone, though, so could work for some.
that also never happened on any of the string of cheap chinese phones I installed lineageos on before deciding the world was sketchy enough to mean grapheneos was the minimum viable level of hardening for my phone. I miss the power button fingerprint scanner dearly.
While I am not so negative, I'd also like to have a demo with a real example. Even if it does not scale, I think this could make debugging interesting at least for beginners and their smaller code bases. Rust is called a language that is hard for beginners, and I think every approach into easing things should be welcomed.
