GNOME Text Editor the most polished text editors I ever used for simply doing what a text editor is doing: Simply editing (plain-)text
1,264 karma · joined February 23, 2021
- ~/Programming for my projects I worked recently on
- ~/Programming/obsolete for my projects I didn't work on for a longer time
- ~/Projects for projects I currently work on
- ~/tmp for projects where I just write e.g. a small patch for a MR and then push and forget about it
- ~/Downloads/pdfs for all pdfs I downloaded
- My VM images are wherever GNOME Boxes decided to save them
- Documentation and manuals are not in my home directory, but hosted on a Raspberry PI
- ~/Uni for all things for the "Hochschule".
This is an argument beyond dystopian. Yes, governments did a lot of bad things in the past (and some are still doing this), but a future, where e.g. the government is only a bunch of companies that would probably really dystopian.
You see already a difference between the USA and e.g. Germany. We have decent healthcare, decent public education, a lot of consumer protection, (Hello DSGVO!). If it would even go further, you would have a country where are no unions& employee rights, no consumer protection laws, absolutely nothing, total surveillance.
Saying that a government is less trustworthy than e.g. FAANG is really a hyperbole
At least you can vote governments out
For a thing that shows the licenses you need 5-10 days? Weird estimation.
Add a item to a popover menu called "Licenses", make it open a window with textview in it or a listview of expanders for each component, done. Maybe two hours at worst
> You need to make the source code available either with the product or separately, which means you need to manage a repository where people can inspect and download the open-source code, depending on the open-source license sometimes even your own code. It would be best to create a workflow allowing people to request the open-source software, create and maintain a software repository where the relevant source code is available, and assign somebody responsible for this. [...] The development of the corresponding UI takes some 2 to 3 developer days.
The GPL does not require you to host it as a git repo, so a simple "Download"-Button should be ok, so it would only require adding a button to the website and uploading the file to a server, maybe adding a direct link to this file somewhere in your application. This shouldn't take more than 30 minutes
> No bloatware, no autoupdater and if possible no GUI. Browser with mouse and maybe some typing courses requires GUI, but at least browser may be called from CLI.
I doubt there is a CLI Browser that can play videos (And does Khan Academy use DRM?, if yes that's another problem)
https://trac.webkit.org/wiki/ApplicationsGtk: Epiphany, Yelp, Devhelp, SWT, Evolution, Pidgin, etc....
> It's dubious because it's a huge library that takes 1 hour to build [...]
How often do you build GNOME-Control-Center with all of its dependencies? Sure, if you are using Gentoo/LFS, that is absolutely expected, but then you can afford to do one (maybe minor) patch to do it yourself.
> The fact that you accept that is exactly what I talked about in this other article
Yes, maybe one or two things like the increased memory usage are legit regressions, but GNOME is doing far less breakage/inconsistencies in a major version update than some multi-billion dollar company like Samsung or Microsoft.
> Better believe they do all this on purpose, trying to discourage anyone from changing their masterpiece. (In the article)
This is really the wrong conclusions, if extensions depend on some internals then you can expect them to break. That is like depending on some undocumented kernel feature of Windows 7 and then complaining that it is not there anymore.
But for example blanket looks a lot better now, the button of the slider is far more visible.
kgx is, compared to the old GNOME-Console a lot nicer to use. Already the changing colours to violet for SSH and red for root-access are already a really nice feature.
Sure there are maybe some bugs and/or leftovers from the GTK3-GTK4 transition, but same as above, it will be fixed sometime.
> GNOME is still coupled to dubious libraries, with no way to avoid them unless heavily patching the code:
GDM depends on systemd || And now we also have libadwaita
systemd is standard for linux. And libadwaita is well, an extension to GTK, the Toolkit for GNOME => Absolutely appropriate.
Sure the dependency on WebKitGtk and Evolution is not that good, but at least Webkitgtk is installed on every GNOME-Desktop for other things.
But calling it "dubious" is not that appropriate, as they always have a sense. A dubious dependency would be - imo -, if GNOME depended on Wine or Qt
> ...Nvidia drivers can be problematic,...
That's only the fault of Nvidia. If they would do the same as Intel and AMD, nobody would have problems with those drivers.
> clearly incomplete and, in a nutshell, meaningless
Maybe for the author, but a lot was done, the screenshot tool is soo nice to use, the applications often got better. (In my opinion at least)
The HIG are excellent, without GNOME I would be maybe 40% as productive as with it.
The recommendations are really wild (I don't care about VSCode plugins or list of opensource Discord communities)
But I think this could be a neat thing, if the UI is cleaned up a bit
For GNOME-Builder, if I want to debug LSP-issues, I add "--env=JSONRPC_DEBUG=1" to the commandline and I get nice output. For VSCode? - No idea. In the end I redirected strace for writes to a file and then grepped for "Content-Length", because I was frustrated that there was no straightforward way to do this otherwise.
Another issue I have with VSCode is, that it adds some folders to the project, that's something I absolutely can't stand.
- Video
- Plain-Text
- Images
- Sometimes forms
HTML provides everything you could need in the huge majority of cases.