xtrapoletariat

joined 2 years ago
[–] [email protected] 2 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

This one, I guess.

"The latest generation of 'calculators' (German synonym: computer), 16 colors, on a 'solid plate' (syn: hard drive) including mouse."

"You should wait - it's half the price in six months"

by Uli Stein

[–] [email protected] 2 points 1 month ago

It's all about damn good coffee.

[–] [email protected] 2 points 1 month ago (1 children)

The sequel's plot is somehow weak with a couple of cringe moments. Given the twist is revealed in part one, the movie expresses one of many solutions to what should be free roaming of your own thoughts after the first film.

Sequels can be awful at destroying the 'blew my mind' effect in general by streamlining a great, open idea to a specific plot I guess.

[–] [email protected] 2 points 2 months ago

Apologies for being too cryptic/jargon. Pro tip: a real-life mentor can adapt to your level on-the-fly, if available.

Maybe this introduction helps a bit to get an overview - from the context I expect you are on JavaScript or related.

It's often hard to grasp why packages or techniques exist unless you ran into the problems that motivated the solution yourself.

In this case, it's all about filtering by the severity of log messages (debug level). If the level is high, your app will show tiny bits of information. These do not need to show for every user, except if they want to enable it (via techniques like a switch/flag, environment variable or a config file).

Config files or profiles are often used to enable/disable code parts in production or to configure how often scheduled jobs should be triggered and so on.

Depending on your level of expertise logging stuff via the console may be just fine for the moment. In particular if you are the sole developer. Once you're annoyed by your own logs, incrementally replace the 'prints' with a library that feels comfortable or well-documented.

[–] [email protected] 6 points 2 months ago (2 children)

The question mixes up tests and logging. You are referring to logs.

Use a good logging package. It will allow you to distinguish at least (possibly with verbosity levels)

  • trace
  • debug
  • information
  • warning
  • error

In production, configure the log level to be info-level or above, everything below will be hidden.

Lower levels can be useful for debugging automated tests. Possibly via a flag in production as well.

[–] [email protected] 7 points 2 months ago

I think they spelled anti-diversity disorder wrong.

[–] [email protected] 0 points 2 months ago

Yes, and in fact, the complete jetbrains toolbox works fine on Linux. Setup is commonly done by simply unzipping an archive.

[–] [email protected] 2 points 2 months ago

Remmina is nice to manage remote access, see https://remmina.org/

I heard negative criticism of rustdesk in terms of security, can anyone confirm or refute this?

[–] [email protected] 1 points 3 months ago

Ah, great, I was not aware of that. I typically stick to the defaults, but this may help to convince others.

My impression is that LO criticism is unexpectedly harsh. After all, it's a free and powerful alternative to MO and you are in no way forced to use it.

It's less polished, obviously, but great for a wide range of use cases. Power users relying on specific features: different story.

[–] [email protected] 6 points 3 months ago (2 children)

For some reason I don't fully understand, LibreOffice hides the option to switch the UI in View > User Interface. The option Tabbed seems to resemble MS ribbon-like style.

They should possibly consider to make that a default question on first start-up, like: 'What interface layout feels familiar?'

 

Klima spielte weder im Wahlkampf noch bei den Sondierungsgesprächen eine große Rolle. Das soll sich jetzt ändern – und zwar nicht nur nach dem Willen der Grünen.

 
view more: next ›