Not sure why this was downvoted/flagged, I do use Drone CI myself currently and it's quite pleasant: https://www.drone.io/
There's also the Woodpecker CI fork, which has a very similar user experience: https://woodpecker-ci.org/
When combined with Docker images, it's quite pleasant to use - you define what environment you want for the CI/CD steps, what configuration/secrets you need and define the steps (which can also just be a collection of scripts that you can run locally if need be), that's it.
Standalone, so you can integrate it with Gogs, Gitea or similar solutions for source control and perhaps a bit simpler than GitLab CI (which I also think is lovely, though maintaining on-prem GitLab isn't quite a nice experience all the time, not that you have to do that).
The stock may have suffered but Cisco as a company has been consistently profitable and dependable partly due to its financial management. They have a crap ton of cash, and they are very good at buying and integrating companies. I would consider them more reliable than IBM, partly because they do make "real things", and partly because they're just damn good at business. They are a great example of why you don't need an engineer to lead a very successful engineering company.
I adopted the fortunes-it package on debian, after I think over 20 years of neglect.
Debian ships the offensive fortunes in a separate .deb so it needs to be installed on purpose, and it's not recommended by the regular one. But it's there.
I actually moved a bunch of stuff into the offensive section, or just removed them. Humour has changed a lot since the last time that package had been touched. Political jokes made little sense, talking about stuff that happened when I was a child and didn't really follow politics.
I was sad that some offensive cowsay ascii arts were removed, but I won't pick that fight so I just got them from the archive and made a .deb that I manually install on my own machines.
The jobs are available for citizens. But they don't do them. And it's not because
of immigration. Think about it for more than 5 seconds. They could just stop immigration for migrant workers and suddenly give citizens jobs. Every politician wants to be known as a job creator. But they don't. Why? There is not enough workers here. Proof? COVID. They stopped letting migrant workers in and farms failed left and right from lack of workers.
We weren't lacking teenagers. We were lacking a dirt cheap seasonal exploitable massive workforce. There are not enough teens even if we conscripted them all. And if you don't, teens don't like doing work. Most teens don't live in the sticks anymore. And (for teens) we care about these stupid things like safety, a minimum wage, and labor laws.
It's not 1950 anymore. The world has changed. The reason we need migrant workers is WalMart. Their demand for ever lower prices creates the need for the lowest priced highest supply scalable labor due to a global supply chain and pricing pressure. You can't put the genie back in the bottle. Want cheap shit? Then you hire migrant workers. Or give up on farms and buy from overseas. Or make robots that can pick fruit. There's no free lunch.
US ag labour has rarely functioned in a free-market fashion.
Through 1864, roughly half of the ag states used slave labour.
California, nominally a free state, had developed (under Spanish and Mexican rule) using what was effectively slave native labour. Following statehood, ag labour was largely imported: from China in the 19th century, from Mexico and Japan in the 20th, with the Bracero programme (established in WWII), and of course Oakies during the dustbowl as immortalised in Steinbeck's Grapes of Wrath, all of whom were at best severely politically marginalised. Conditions in the antebellum former Confederacy long disadvantaged labour as well.
The US National Labour Relations Act (NLRA, 1935) explicitly excluded farm labor from its protections (wages, hours, conditions, unions). California eventually pased the Agricultural Labour Relations Act (ALRA) forty years later, which provided for the right to unionise (Cesar Chavez and the National Farm Workers Association features strongly in promoting this), and ... even it is fairly weak sauce despite being the only significant ag labour law in the US.
Farming itself is a marginal business, and farm labour gets the short side of that stick. The underlying economic reasons are complex, and not readily solved. It's not that the present situation is fair to farm workers at all, but a sudden shift would likely be catastrophic across the board. I'd like to see a far fairer system, but it would take significant governance and management to roll out smoothly.
Cars now have cell modems that you can hook up to select telecom providers to turn your car into a hotspot, so those cell modems/SIMs do have an APN for internet data
This will not amount to anything, but it's nice to know we aren't all crazy or anti-semitic for thinking the Israeli state has been acting very poorly in regards to the State of Palestine. Feels a little bit like trying to get organized crime on tax evasion.
What they've been able to accomplish in such a short time is nothing short of amazing, and I applaud them for their efforts.
That said, I've been using Asahi for a month, and I'm ditching it. Maybe in a year or two it'll be stable, but for now it's got too many bugs and unsupported features. A lot of the problems come down to Wayland and KDE/Gnome, as you literally have to use Wayland. But there's plenty of other buggy or challenging parts that all add up to a very difficult working experience.
One of the biggest challenges I see is support for hardware and 3rd party apps. Not only do all the apps need to support this slightly odd Arm system, but so do hardware driver developers. I never realized before just how much of a Linux system works because most people had an incredibly common platform (x86_64). Even if Linux on Mac became incredibly popular, it would actually take away development focus on x86_64, and we'd see less getting done.
(This kind of problem is totally common among Linux laptops, btw; there's a ton of hardware out there and Linux bugs may exist in each one. Adding a new model doesn't add to the number of developers supporting them all. If anything, the Mac is probably benefited by the fact that it has so few models compared to the x86_64 world. But it's still only got so many devs, and 3rd party devs aren't all going to join the party overnight)
Yeah, I can definitely see this being an issue going forward for quite some time. The existence of non-Apple ARM devices should hopefully lead to general interest in addressing these issues, but there's so much hardware and software out there, and only so many devs with the time, interest and access to fix them.
On the other hand, I suspect people will start making choices for their hardware/software that maximise compatibility, as they already do for Linux x86. ("Don't buy NVIDIA if you want functioning Wayland", etc.) It'll be tough, but things will hopefully get better over time.
I don't get why you were downvoted to oblivion. A perspective from someone who actually used Asahi is very valuable, so thanks for sharing.
You're definitely right that having a usable system is not just about supporting first-party hardware. Linux on its own is a huge mess of different components that all somehow need to work together, and it's a miracle of engineering that it works as well as it does, even on well-supported hardware. I can't imagine how difficult it must be getting all of this to work on hardware that requires reverse engineering. It seems practically impossible to me.
On HN downvotes are usually because of disagreement. OP's experience doesn't match mine: I have used Asahi for quite a bit longer than OP and I have experienced no serious bugs.
But then again I only use those software that's available in the distribution or those that can be compiled by me. So naturally I don't deal with incompatible third party software.
That's great. Is your experience somehow more valid then?
Downvoting because of disagreement is asinine to begin with. Burying opinions that contribute to the discussion does nothing but perpetuate the hive mind.
Most of the software that ships works, but actually I've run into a number of bugs on stock. A bunch of seg faults and other crashes I couldn't trace.
For some reason a lot of apps have bugs in Wayland, like mousing over menus, only the first menu item shows up; move to a different item, then back to the first, and suddenly all the menu items show up. Persistently happens in several apps.
Some of the Flatpak apps also have serious performance issues and bugs that native ones don't. A big app I need to use is FreeCAD, which there was no ARM build for until the recent 1.0pre releases. Their FreeCAD build has some issues that their AppImage doesn't. But even the AppImage release has some weird bugs, and I wasn't able to figure out if they're FreeCAD bugs, Wayland bugs, Fedora bugs, or what.
And then there's DisplayLink drivers+userland, which amazingly kind-of works (after a bunch of tries), but then hard crashes or prevents the machine from resumung from suspend.
I also get weird giant green flashes on straight HDMI. And because the laptop resolution is fixed, when I attach a monitor, the laptop screen "invades" the monitor screen. Fullscreen doesn't work, the panels conflict, it's kind of a mess. I'm almost certain the latter is some kind of KDE/Wayland bug, but the green flashes must be the video driver.
There's a bunch of other issues I don't remember at the moment. But all of this adds up, sadly, to something I just can't make work. Really wanted it to.
FYI it seems that your account is perma-dead, or however HN calls this. Your comments are automatically flagged and not seen by anyone who doesn't choose to enable seeing them in their settings.
