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.
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?
it’s a marketing stunt not a logic-related problem
He might do like 2-5 deliveries per trip if they align.
it seems to be a variation of “cargospace” meme.
“Part of the couch, Part of the family”
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.
That’s a human weakness, most animals eat poop for breakfast
Well, I was smarter, but, thankfully, still here.
I was maybe 5 years old when one day I decided for some reason that I have to know how the electricity works “first hand”. So I took an electrical plug with a wire from dad’s tool box. It had two exposed copper ends. I plugged it in the outlet and while trying to inspect the “electricity” flow I, most likely accidentaly, have completed the circuit with my hand.
Interesting how the experience wasn’t painful it’s just muscles in your body get tense and you literally can’t drop the wire or move at all. Thank god my Dad was around and maybe 10 seconds after I got shocked he pulled the plug. I had no serious injuries: just burns, a bit of shock and a lifelong lesson.
P.S. It was a 220V outlet too. But I’m not sure if it’s more dangerous than the US ones.