Enjoying it, and time.
Vancouver, BC, Canada
Enjoying it, and time.
These comments really speak to me as someone who is comfortable in Arch but mildly interested in NixOS. The concept seems great, and it seems to work very smoothly when it works. Yet there are always these war stories where people have had to fight the system, to debug some misbehaving hack that is nonetheless required to smash a particular package into the NixOS mould. It is discouraging. The idea I get is that NixOS involves more time doing OS curation chores than does Arch, which already hits the limit of my willingness.
Flakes are another issue. The pre-flakes way seems to be de-facto deprecated, yet the new, flaky way is experimental. I don’t want to waste time learning a doomed paradigm, and I don’t want to depend on anything experimental.
For me, configuration files in git plus btrfs snapshots is just so straightforward. I want to see NixOS as a better way, but I can’t.
Every time I hear this word firefish, I cannot help but be reminded of the phrase “turds of the firefish”, which appears quite randomly in one of Orson Scott Card’s novels.
Notice how none of these replies are “AI assistant”?
We’re talking cross-platform depravity these days.
I even explicitly called out my statement as tongue-in-cheek, so it’s not to be taken 100% seriously. And full disclosure: I myself am not a PHP developer, but much worse: a PowerShell developer, among other languages.
This is a bit tongue-in-cheek, but kbin generally requires its users to be either unaware it is written in PHP or OK with using something written in PHP. That has to exert some selective pressure.
I am both a (T-)SQL expert and a language design enthusiast. IMO, SQL the language is mediocre in its grammar and extremely resistant to cleanliness. Once you get past that, the things you can actually do with it are extremely useful.
I’d love for a better syntax to exist, but it’s a Herculean task to make one. Modern SQL dialects have gargantuan, labyrinthine grammars, and they grow with each new product version. It’s a lot easier to keep adding to that than to build a feature-complete replacement. This is also the reason why most ORMs are so frustratingly limiting: it’s too much work to support the advanced features of one SQL dialect, let alone multiple.
Just heard of this service but I am signing up first thing tomorrow.
It could be that we have transitioned into the unforeseeable future.
Arc aims to be more than just a place to view webpages
Personally, that’s all I want a browser to be. Anything more is useless bloat, IMO.
I don’t buy this excuse. Just make it “opt”, meaning neither option is the default. You have to choose “Yes, contribute diagnostic and bug data to Fedora (recommended)” or “No, keep my data private” before you can continue. Put a big “more info” link to documentation on what is collected, when, and who gets it, and how it’s used.
It somewhat under-represents those who value privacy most and over-represents those who want to help Fedora with their usage data, but I argue that’s a good thing.
SSD firmware is baked into the kernel?
I have listened since the time it was the Engadget podcast, then This Is My Next, then the Vergecast. Yes, it’s fluff and not deep technical info, but it’s really useful for keeping up with the overall zeitgeist of the tech industry. Also it’s often funny. It’s a nice, refreshing thing to listen to while making coffee on a Friday.
That fixes the main problem with Clippy, which was not using a blockchain.
They’re similar. Mlem seems to be a slightly more featureful at the moment, but its release cadence seems slower. Mlem’s compact mode is better at being compact. Memmy has an ability to set a default view.
Edit: Mlem now has a setting for default sort order.
C derivatives are similar in terms of things like imperative control flow, lower-case keywords like if
, mostly insignificant whitespace, { }
-delimited blocks, etc., but they can be vastly different in terms of features, semantics, idioms, and typical use cases.
It’s like how non-programming languages can use the same Latin alphabet but be vastly different in terms of grammar and culture.
A relative of mine works in the same room as 911 call-takers in western Canada. They’re having a big problem with this.
Python is easy to learn and marketable. I personally prefer Ruby to Python, but Python is a good place to start. For most AAA games, it’s C++, and yes it’s horrendously complex. I vastly prefer Rust to C++. Good old C is actually a fairly small language, and only moderately difficult.
The reaction is funny too, because in my experience comparing communities of various distros, Fedora’s community is among the the most inviting and professionally-behaving of them.
Personally, I am not running Fedora at the moment, but probably will when my Framework 16 arrives, since Fedora is officially supported on it. And to be honest, I find that I am making the same choices with Arch as Fedora would have made for me (aside from bootloader), so I feel that I’m wasting a bit of effort.