... check out OpenBSD before checking out FreeBSD, and I cannot stress this enough. FreeBSD developers don't use their own operating system; they run it in a Virtual machine on their Macs, and it shows.
Suspend/resume has been broken there since 2008, and drivers for any recent Intel graphics adapter will not run (you cannot switch from Xorg to a console and back) properly.
Yeah, it can suck to run a server-focused OS on a desktop/laptop.
FreeBSD devs do not care about their OS
This is objectively false. Any devs working for free must care, of they'd hack on something else. Any devs being paid must have an employer who cares. The problem is that the people hacking/funding FreeBSD don't care about the same parts of the system that you do.
... the way systemd has turned into something similar to the bloated beast that is the Windows 'svchost.exe'
+1 to the anti-systemd sentiment.
-1 to using svchost.exe to make your case. svchost is just a container process. The real issue is the Windows architecture/philosophy that encourages a proliferation of services.
(I like Unix and I like Windows. Each has their place. Trying to turn one into the other is a big mistake.)
Option #1: Valve has no physical presence in Australia, and tells the Australian government to go fuck themselves. Government responds by banning Valve from doing business in Australia. Good luck enforcing that. To the extent they do manage to enforce it, it will be taking action against Australian citizens, since they have no power over Valve.
Option #2: Valve doubles prices in Australia. Y'all can have all the consumer protection you want, but you're going to pay for it.
The way to fix this is to delete \Windows\System32\FNTCACHE.DAT. The file will automatically be regenerated on the next boot.
(Information found on Microsoft Support Forum and used to successfully fix my own system.)
How do you delete the file if you can't boot?
(1) Press F8 during boot to get to the Windows boot manager advanced options screen.
(2) Select "Repair".
(3) Provide password for a local account that's a member of the Administrator group.
(4) Select "Command Prompt".
(5) Find drive letter assigned to Windows partition (may not be C: in the repair environment!).
(6) Delete \Windows\System32\FNTCACHE.DAT.
(7) Exit command prompt and reboot system.
And now, since this is
This bug demonstrates the danger of running your GUI in kernel mode (win32k.sys). One stray pointer can ruin your whole day. In this case the pointer was sufficiently invalid to cause a bugcheck. A stray pointer that silently scribbles on other kernel data structures is even worse.
"Those who would give up essential Safety, to purchase a little temporary Performance, deserve neither Performance nor Safety."
I think NVidia tied their hands by retaining the ARM architecture. I suspect the result will be a "worst of both worlds" processor that doesn't use less power or provide better performance than competitors.
In order execution, exposed pipelines, and software scheduling are not new ideas. They sound great in theory, but never seem to work out in practice. These architectures are unbeatable for certain tasks (e.g. DSP), but success as general purpose processors has been elusive. History is littered with the corpses of dead architectures that attempted (and failed) to tame the beast.
Personally, I'm very excited about the Mill architecture. If anybody can tame the beast, it will be these guys.
Splits in the circuits are more common than you might imagine, and the Supreme Court doesn't always resolve them. A lot depends on how substantial the split is. Minor differences don't always get resolved.
In any event, this case isn't "ripe" for appeal to the Supreme Court yet. The Supremes rarely get involved until all lower court proceedings have been exhausted, and this case just got sent back for retrial on the issue of fair use. The process can be maddening for the individual litigants, but it makes sense for the legal system overall.
(I actually read the court ruling before posting this)
tl;dr version: The results will likely be awful, but the decision appears legally correct.
Google won at trial because the judge decided that the Java API was not copyrightable. I absolutely believe that API's should not be copyrightable, but that isn't what the law says. Copyrightability has a very low threshold. The trial judge screwed up by applying legal standards related to fair use to the question of copyrightability. The appeals court was correct to reverse.
The case now goes back to the district court. There will be a new trail with a new jury, but the only issue will be whether Googe's copying of the Java API is fair use. The original jury deadlocked on this question. Fair use decisions are very subjective, so it's hard to predict how this will turn out. All I can say is that I hope Google wins.
P.S. None of this decision was related to patents. Oracle lost on their patent claims at trial, and that stands.