To be clear, the right of free speech given in the first amendment is the right to express any opinion without fear of repercussions.
There is no inherent right that your opinions must be given a platform, or that any particular platform has the right to exist.
The first amendment is entirely orthogonal to the question of whether or not TikTok should be allowed to operate in the US.
Maybe.
Linux won because it worked. Hurd was stuck in research and development hell. They never were able to catch up.
However, Linus’s kernel was more elaborate than GNU Hurd, so it was incorporated.
Quite the opposite.
GNU Hurd was a microkernel, using lots of cutting edge research, and necessitating a lot of additional complexity in userspace. This complexity also made it very difficult to get good performance.
Linux, on the other hand, was just a bog standard Unix monolithic kernel. Once they got a libc working on it, most existing Unix userspace, including the GNU userspace, was easy to port.
Linux won because it was simple, not elaborate.
After two years of development and some deliberation, AMD decided that there is no business case for running CUDA applications on AMD GPUs. One of the terms of my contract with AMD was that if AMD did not find it fit for further development, I could release it. Which brings us to today.
With pipes/sockets, each program has to coordinate the establishment of the connection with the other program. This is especially problematic if you want to have modular daemons, e.g. to support drop-in replacements with alternative implementations, or if you have multiple programs that you need to communicate with (each with a potentially different protocol).
To solve this problem, you want to standardize the connection establishment and message delivery, which is what dbus does.
With dbus, you just write your message to the bus. Dbus will handle delivering the message to the right program. It can even start the receiving daemon if it is not yet running.
It’s a bit similar to the role of an intermediate representation in compilers.
He could have just paid the £2,150 fine, but instead he chose to appeal…
Engaging in legal action in a foreign country isn’t exactly the brightest idea. Pay the fine and get out.
Like, 3 months is an insane sentence, but it sounds like he just leaned in at every opportunity.
Broken for me.
It displays HOME, but if I tap “reply” to see the underlying markdown, it is definitely $HOME.
Device information
Sync version: v23.11.29-22:27
Sync flavor: googlePlay
Ultra user: true
View type: Smaller cards
Push enabled: false
Device: ASUS_AI2302
Model: asus ASUS_AI2302
Android: 13
Ooo neat. I was not aware of this syscall. TIL!
Billgate
Damn dude. You ok?
To be clear, when I say “corporate support,” I don’t mean the company pays you.
I mean that the company pays someone (like an existing employee) to maintain their internal fork and contribute patches back upstream.
That’s how all of the projects I listed operate.
If you don’t care about interfacing with the industry like this, that’s totally fine, and the AGPL works. But if your goal is to write a piece of software that is used by the industry, then it can’t be AGPL without a strong and exceptional business model.
And I’m not trying to make a statement about whether you should write this kind of software. It’s only a statement about what to expect if you write this kind of software.
FWIW, the stat structure in Linux does not include birth time [1]. It only gives you:
atime: The time of last access.mtime: The time of last modification.ctime: The time of the last change to the inode.I assume the stat command is using a filesystem-specific method to get the birth time.
Anyway, I don’t think any of these stats is guaranteed to be consistent with the rest (or even correct). For example, it is common to disable atime tracking to improve I/O performance.
Assuming the data is accurate, I think the other comment about the file being a copy is the best explanation.
Letting Ukraine join now would immediately trigger war between NATO and Russia. That could easily become nuclear.
In NATO, an attack on one is an attack on all. There’s a good reason nations cannot join NATO with ongoing border disputes.
Linux, coreutils, LLVM, GCC, Chromium, Firefox, V8, Python, Postgres, Java, systemd, kubernetes, Docker, Bazel, Buck, Abseil, Guice, Fedora, Ubuntu, Android, Hadoop, Apache, Nginx, Spark, TensorFlow, PyTorch…
Yeah, companies never contributed to open source.
AGPL is a sure-fire way to steer off corporate support.
GPL is usually fine for corporate use.
For example, Google and Meta actively contribute to Linux (GPL) but neither would ever touch an AGPL project for fear of infecting their other IP.
They didn’t even read the headline.
The headline clearly says that Hasbro (owners of WotC/D&D) did layoffs, not Larian Studios (creators of Balder’s Gate 3).
+1 for Portal 2.
OP, the co-op campaign for Portal 2 is a separate story from the single player campaign.
It’s a puzzle game at it’s heart, wrapped in the control scheme of an FPS.
These are volunteers that work for free, right?
Some are working for free, sure. But mainly GNOME is developed by Red Hat and Canonical, afaict.
Florian Müllner is a Red Hat employee.
Big +1 for MDN.
The Mozilla Developer Network should be considered the standard reference for frontend HTML, CSS, and JavaScript.
(Aside from, you know, the actual standards. But those documents aren’t exactly approachable for new developers.)
deleted by creator