I guess it will make developers who develop the kernel and its components go “hehe fat penguin anyway let’s continue debugging this mess”
I guess it will make developers who develop the kernel and its components go “hehe fat penguin anyway let’s continue debugging this mess”
For starters you don’t have to worry about installing bluetooth stacks, or a network interface to control your wifi (if they somehow don’t end up installing a whole DE package group)
The only thing that could potentially degrade the battery is not cycling it. There should be no direct effect on the battery due to using mains power
I would recommend C for the simplicity. You’ll get familiar with the nitty gritties of a relatively featureless programming language. Which will let you view other languages and their tools with more nuance. But it all depends on what you want to do with it, want to program an MCU like Arduino or learn linux? C is perfect. If you want to build something with graphical interfaces like websites or GUI apps, I would suggest something else but C is still a good place to get started.
Here is something written by AI:
True for all programs
Not officially, you can install it separately but you’ll probably have to tie up some loose ends (haven’t tried)
You can look into Fedora if you want a good gnome experience or Debian if you prefer. The latter will have an old gnome version.
I think I get your explanation but I rarely see people in windows using fullscreen (videos and games don’t count ofc), windowed mode is the default so I don’t get the comment
What’s wrong with fullscreen?
I can’t imagine coding in a small window when you have the whole screen
In professional work space, ubuntu will probably be highest. Second place I would guess Fedora
As personal workstation I would guess arch (even without steam deck) followed by mint or some flavour of Ubuntu
I’ll check out the KDE flavour
I don’t drive but if the engine is off while the clutch is disengaged engaged wouldn’t that produce a braking effect. Maybe not enough to stop the roll on a slope but enough that normal foot braking would stop the vehicle?
I would say he’s arguing in favour of practicality
Similar thing in ubuntu, something required a newer python version than the system installed one. I thought I’ll uninstall the old one bcoz why have two versions. Ended up reinstalling ubuntu.
Linux commands are brutal
It’s got a vim-sized learning curve to really leverage it
As a regular vim user, I have to say. Vim makes sense after you put some effort into learning it. I can’t say the same about latex.
It’s not a standard but still its an interesting software so I’ll post this here:
Joking aside, I love and hate it. Its paradigm is almost like using the C preprocessor to build a really awkward Turing-machine. TeX/LaTeX does a great job of what it was intended to do; it applies high quality typesetting rules to complex material and produces really good results. I love the output I can get with it and I will be eternally grateful that Donald Knuth decided to tackle this problem. And despite my complaints below, that gratitude is genuine. Being able to redefine something in a context-sensitive way, or to be able to rely on semantics to produce spacing appropriate to an operator vs a variable etc; these are beautiful things.
The problem is, at least once a day I’m left wishing I could just write a callable routine in a normal language with variables, types, arrays, loops and so on. You can implement all those things in TeX, but TeX doesn’t have a normal notion of strings, numbers or arrays, so it is rare that you can do a complicated thing in an efficient way, with readable code. So as a language, TeX frequently leads to cargo-cult programming. I’m not aware that you can invoke reflection after a page is output, to see what decisions on glue and breaks were made; but at the same time you can’t conditionally include something that is dependent on those decisions, since the decision will depend on what is included. This leads to some horrible conditionals combined with compiling twice, and the results are not always deterministic. Sometimes I find it’s quicker to work around things like that by writing an external program that modifies the resulting PDF output, but that seems perverse.
At the same time, there’s really nothing else out there that comes close to doing what LaTeX does, and if you have the patience, the quality of documents it can produce is essentially unbounded. The legacy of encodings, category codes, parameter limits, stack limits etc. just makes it very hard for package writers, and consumes a great deal of time for a lot of people. But maybe I am picky about things that a saner person would just live with.
A lot of very talented people have written a lot of very complex packages to save the user from these esoteric details, and as a result LaTeX is alive and well, and 99% of the time you can get the results you want, using off-the-shelf parts. The remaining 1% of the time, getting the result you want requires a level of expertise that is unreasonable to expect of users. (For comparison, I wrote an optimising C compiler and generally found it far easier to make that work as expected, than some of the things I’ve tried, and failed, to do properly in LaTeX. I now have a rule; if getting some weird alignment to work takes me more than an hour, I just fake it with a postscript file, an image, or write an external program to generate it longhand, in order to save my sanity.)
I think (and certainly hope) that LaTeX is here to stay, in much the same way that C and assembly language are. As time moves forward I think we’ll see more and more abstractions and fewer people dealing with the internals. But I will be forever grateful to the people who are experts in TeX, and who keep providing us with incredible packages.
Isn’t Matter supposed to solve this issue?
I completely agree. Still, the interactive graphical visualizations like in the ohmygit game are quite helpful and fun to play around with. I would recommend checking it out after you go through the official git book to consolidate your knowledge.
Looks like something an underpaid school teacher would whip up