I believe for many companies, developers work on giant codebases with many hundred thousands or even millions of lines of code.
With such large codebase you have no control over any system. Because control is split between groups of devs.
If you want to refactor a single subsystem it would take coordination of all groups working on that part and will halt development, probably for months. But first you have to convince all the management people, that refactor is needed, that on itself could take eternity.
So instead you patch it on your end and call it a day.
Half of the linux ecosystem is personal projects.
Linux itself started as
just a hobby, won’t be big and professional like gnu
It’s not useless as you can learn from it.
Almost. It doesn’t try to solve all the problems, though. I’d say it’s a passion project like Haiku and TempleOS.
From interview: it started as a research project. The author wanted a distribution that uses the least system resources with maximum performance.
He started with archlinux, moved on to gentoo and to go even deeper - found the infamous “linux from scratch” and started to shape his own distro.
Ok, because of this post - I decided to bite the bullet and try wayland again. And it was much better experience this time:
I’ve installed sway “pattern” on OpenSuse-Tumbleweed and:
waybar absolutely supports clicking tray icons.
I confused it with swaybar, that’s installed with sway by default and should be an i3bar-compatible. Waybar doesn’t seem to support i3bar protocol, but anyway, after I configured it - it’s like 95% there from what I want.
I could switch tomorrow if I could do my current setup:
Last time I tried Wayland in December, I had issues with waybar not supporting clicking tray applet icons. Also I’ve ported my dropdown terminals script to support sway - and it worked half the time, like, literally every second key press was ignored.
On one hand I have X session that currently has no downsides for me, on other - wayland that has no upsides. Tell me, why would I switch?
If it was near the shore - they might’ve stole the section of wire. Copper is really expensive.
Well, then you have to find another name for that kind of software and define it that way. I certainly would support such an effort, i.e. to make software available to everyone at no cost.
There’s no need to come up with new terms or change the existing ones. Free software is inherently free in price. And you can’t enforce paying for software without the restrictions put in place (e.g. drm). Here’s a quote from https://www.gnu.org/philosophy/selling.en.html :
With free software, users don’t have to pay the distribution fee in order to use the software. They can copy the program from a friend who has a copy, or with the help of a friend who has network access. Or several users can join together, split the price of one CD-ROM, then each in turn can install the software. A high CD-ROM price is not a major obstacle when the software is free.
Free software can have a price, but paying it is optional.
I meant that free software is inherently can’t have a price. Even if you provide source code only to your users, they are free to share that source code for free.
Thus there can’t be piracy because piracy of free software is inherently allowed.
And if you try to prevent your users from sharing the source either legally or with drm - you add restrictions to software, making it less free for your users.
The recent situation with RedHat provides good demonstration and example of this.
It’s free as in freedom, not as in free beer.
But you can’t have one without the other. Putting a cost on software is adding a restriction, thus making it less free (as in freedom).
Free software should be available to everyone, even to people who don’t have money to pay for it (poor third world countries, students, kids).
I personally believe, that you should pay for software that helps you earn money. For everything else - it’s everyone’s own decision to donate or not, based on a financial situation, beliefs, political position and what not.
For one - the error handling. Every codebase is filled with messy, hard to type:
if err != nil {
...
}
And it doesn’t even give you a stack trace to debug the problem when an error happens, apparently.
Second reason - it lacks many features that are generally available in most other languages. Generics is the big one, but thankfully they added them in last half a year or so. In general Golang’s design principle is to implement only the required minimum.
And probably most important - Go is owned by Google, aka the “all seeing eye of Sauron”. There was recently a big controversy with them proposing adding an on-by-default telemetry to the compiler. And with the recent trend of enshittification, I wouldn’t trust google or any other mega-corporation.
I have all apps I use daily in the appimage format. Yesterday I decided to try btrfs for my root partition and did my annual Linux reinstall. All my apps were already there and ready for work from the start.
I also have a usb flashdrive always on me with the same appimages. Just in case I’d wipe a hard drive by accident and wouldn’t have an internet connection or something like that (in case of emergencies). You can’t do this with flatpaks or snaps.
IMO, go’s gopher is ugly, not cute. But, anyway, there are better reasons not to learn Go.
There’ve been protests, riots, violent acts of protest at draft centers. This just doesn’t get as much coverage as Putin’s or US propaganda.
It’s not that masses not disgruntled enough. It’s just almost nothing people can do to stop the war. Would you do something stupid and worthless, when even a social media post can and will cost you portion of your life in prison?
I mean, they’re not wrong. But it’s not tiktok, it’s almost all social media and consequently, 99% of the internet.
1 - bloat
2 - click-bait title
Just tell me actual errors like a professional OS would.
Professional OS:
Why I hate snaps/flatpak:
While most of the time, I remember my password, I know I could just snap and forget it right there at any point. Happened to me not once. And I’m in my 20s. Sometimes when I forget a password, I just start typing and muscle memory kicks in, sometimes it doesn’t. I guess our brains are not optimized to store long random strings of characters. You could use a long sentence as your master password or do as I do:
Come up with a way to make up a long seemingly random password from a couple words. Then if/when you forget a password, just remember those words and reconstruct password from them.
Oh, and GBA rom is included with game files.