enzolovesbacon

"dead in the water" is incorrect. SUSE's SLES (I believe OpenSUSE as well) uses btrfs on root and XFS on home for default install. And SUSE systems are very far from "dead in the water" as it's employed in lots of big servers around the globe.

Just because Red Hat marked btrfs deprecated on their systems, doesn't mean the technology itself is deprecated.

Also, from what I've read, they deprecated it because of resources issues rather than tech issues (seems like they had 0 btrfs devs and lots of XFS specialists on the team).

Besides the obvious, I'd also like to see:

  - Salary range for that specific position (not for the whole department (I've seen that))
  - Remote work policy
  - Visa sponsorship policy
  - Vacation policy
  - Interview process
  - Link to future manager's technical background

Also, please avoid using cute/hipster phrasing shit that's full of puns, hearts and whatnot. Just get straight to the point.

This is how a review is done. Thorough and covers the details that matters for a distro review.

Although I could experience the advantages it's offering over 16.04, I tried it yesterday and it's incredibly slow. Like 5-seconds-to-activate-focus-on-any-window slow.

Has anyone had similar issue? The last time I experienced something laggy like this was with crappy hardware.

It doesn't happen on RHEL 7.5 (with GNOME Classic), Fedora (with GNOME), Ubuntu 16.04 (with Unity). I have a beefy computer (HP Z600, 2x Xeon, 48GB RAM ECC), so I'm pretty sure it's not a hardware issue. Windows 10 also runs fine.

I have the same issues/annoyances as you.

Also, for the past few weeks, I set up a few Linux desktops. When you install Firefox Quantum alongside with the pre-installed Firefox ESR (most of mainstream distros has it) and enable sync, your bookmarks will have a higher chance of being incorrectly synced and your history (if you chose to sync it) will probably be at FIREFOX_PROFILE_DIR/places.sqlite.corrupt

A simple fix is to close Firefox and

  $ cd ~/.mozilla/firefox/YOUR_PROFILE
  $ mv places.sqlite.corrupt places.sqlite

I'm still trying to find the time to prepare a proper bug report.

I would have asked this too (aka shadow profiles).

It's sad that it looks like the senators weren't even aware of this, or maybe some were but couldn't phrase in layman's terms.

Just found out about your site. It's great! Will be using it for my next projects for sure.

> eul is a registered company, and all binaries are signed. Your data is safe.

I see a lot of companies drawing that conclusion from such premise (and you're using C, which really decreases the odds that my data is really safe).

Using that sentence on your main page makes it look shady. Specially if you're not a security company.

IMHO, if you remove "Your data is safe" it will look much more professional.

I don't think they have a "compatibility" slide anywhere at all at Google.

I was about to buy a Ryzen workstation, but ended buying an (used) HP Z600 (2x E5620, 48GB ECC RAM, 2TB HD) because it was the best bang for the buck; just the Ryzen 1800x + motherboard would cost me what I paid for the Z600 (I live in Brazil, prices here are crazy).

That said, I'm really rooting for AMD here. It's very nice to have this kind of competition and customers will benefit a lot from this.

I recommend you try Fedora.

Even though Ubuntu is beginner-friendly at first sight, in very short time you'll see that all the benefit you're supposed to get from a community are actually hacks to solve things like: GUI issues with Unity, some services not starting, services crashing randomly, and so on.

Fedora is often taken as somewhat unstable because of its fast release cycle and lack of a long-term support release, but, in my experience, it has proven itself to be very reliable and stable for my workflow.

Yes, I understand that. I mean, why don't these censors block the whole wikipedia.org access then?

If they don't want their population to access a Wikipedia topic/article and can't block/determine if someone is accessing it, the easiest thing to do would be just block it right away. So why they won't do it?

(PS: I'm in no way in favor of censorship, I'm just trying to understand such mindset)

  Critics of this plan argued that this move would just result in more 
  total censorship of Wikipedia and that access to some information 
  was better than no information at all

I'm no critic of this plan but I still don't understand why this wouldn't result in more total censorship. Someone explain please?

Logged in just to upvote.