Stories
Slash Boxes
Comments

SoylentNews is people

Log In

Log In

Create Account  |  Retrieve Password


First Divorce

Posted by takyon on Monday February 26 2018, @05:05PM (#3029)
18 Comments
Career & Education

Melania Trump re-emerges amid marriage scrutiny

Can Trump succeed where FDR and Bill Clinton failed?

No Guns for Cyberstalkers in FL

Posted by takyon on Friday February 23 2018, @06:04PM (#3020)
9 Comments
Digital Liberty

Florida governor Rick Scott's three-point plan requires gun buyers to be 21 and up

Scott's plan also includes prohibiting a person from having or buying a firearm if he or she is subject to an injunction for protection against stalking, cyberstalking or domestic violence.

Cyberstalking is serious business.

Reality TV Star Wipes Out $1 Billion+ of Snap's "Value"

Posted by takyon on Friday February 23 2018, @02:14AM (#3018)
6 Comments

Ryzen 5 2600 Benchmark: 7-15% Faster Single, 22-31% Multi

Posted by takyon on Tuesday February 20 2018, @07:18PM (#3012)
21 Comments
Hardware

This is about a 12nm "Zen+" chip coming out this year, not "Zen 2".

AMD Ryzen 5 2600 Pinnacle Ridge Processor Single And Multi-Core Benchmarks Leak

The Ryzen 5 2600 is a 6-core/12-thread processor with a 3.4GHz base clock and 3.8GHz boost clock. It also has 3MB of L2 cache, 16MB of L3 cache, and a 65W TDP.

In Geekbench, the chip scored 4,269 in the single-thread testing and 20,102 in multi-threaded testing. Compared to the Ryzen 5 1600, which is a 6-core/12-thread processor clodcked at 3.2GHz to 3.6GHz with the same cache arrangement and TDP, the Ryzen 5 2600 is anywhere from 7-15 percent faster in single-threaded performance, and 22-31 percent faster in multi-threaded performance. The ranges in percentages take into account different scores in Geekbench's database.

Even if going by the low end numbers a 7 percent jump in single-threaded performance and 22 percent gain in multi-threaded work chores is a nice upgrade. Part of the difference is obviously attributable to faster clockspeeds, but performance optimizations underneath the hood also play a role. The gap could be even wider when Pinnacle Ridge ships too, as AMD and its partners will have had more time to polish up drivers.

AMD Ryzen 5 2600 spotted in Geekbench database

Previously:

AMD Expected to Release Ryzen CPUs on a 12nm Process in Q1 2018
AMD at CES 2018

Conservatives React to Peter Thiel's Los Angeles Move

Posted by takyon on Sunday February 18 2018, @10:10PM (#3007)
33 Comments
/dev/random

As Peter Thiel ditches Silicon Valley for LA, locals tout 'conservative renaissance'

If the billionaire tech investor and noted libertarian Peter Thiel really does leave Silicon Valley for Los Angeles to escape what he views as an increasing intolerance for conservatives, the city’s growing community of conservatives will be there to welcome him.

Among LA’s right-leaning residents are the Daily Wire’s Ben Shapiro, the political commentator Dave Rubin and the blogger Bill Whittle. There’s also the former members of the defunct Friends of Abe, a secretive group of Hollywood conservatives that fractured in 2016 over the candidacy of Donald Trump.

“Silicon Valley has long despised the American right and it’s beginning to flex its muscles against us,” said Michael Knowles, an LA-based podcaster for The Daily Wire, referring to a lawsuit filed by conservative media site PragerU against YouTube for allegedly “censoring” conservative videos.

“It’s a sign of the time that Peter Thiel is heading down here because there’s been a conservative renaissance in Los Angeles,” Knowles said.

PragerU’s chief marketing officer, Craig Strazzeri, added: “It’s both astounding and sad – but unfortunately not surprising – that there are parts of this country where you are socially and professionally shunned if you support the duly elected president of our country. That might be changing in Los Angeles.”

Previously: Peter Thiel Migrating From Silicon Valley to Los Angeles

Foutanga Babani Sissoko

Posted by takyon on Friday February 16 2018, @01:18PM (#3002)
3 Comments

You Up? College in the Age of Tinder

Posted by takyon on Thursday February 15 2018, @01:01PM (#2997)
12 Comments
/dev/random

You Up? College in the Age of Tinder

Frankly, dating apps can also just make things incredibly awkward. My freshman year I swiped through hundreds of people. At one of the last tailgates of the year, a random man walked by me and yelled: “Hey! We matched on Tinder! You are Tinder girl!”

I was mortified. Suddenly everyone around me knew that I was on Tinder. And I had swiped through so many people, I had no idea who this guy was. He was just another nameless “match” that I would never get to know. Because, needless to say, I walked away and never spoke to that guy again.

[...] The same Snap asking to “hang out” sent at 2 p.m. can have a completely different meaning when sent at 2 a.m.

[...] You don’t want to be mid-makeout while the jewel-encrusted crab from “Moana” is singing about how shiny he is.

I am in love with Linux again thanks to Void

Posted by Azuma Hazuki on Wednesday February 14 2018, @10:58PM (#2996)
34 Comments
OS

So, most people know I've been using Linux since mid-2004, and that I started with Gentoo...which, yes, is the equivalent of learning to swim by donning a bacon bikini, rubbing yourself in A1 Steak Sauce, and jumping in the Amazon in the middle of piranha season.

Over the last 13+ years, Linux has...changed. A lot. I am sorry to say that I don't believe most of the changes have been good ones: GTK 3.x, the fiasco that was the KDE 4 series, RedHat aiming to become the next Microsoft, and the crux of the former, SystemD. Yes, I am a SystemD hater, and I make no apologies for it. It does things wrong, it does not even pretend to follow the Unix philosophy, and its syntax and "feel" remind me more than anything of PowerShell, which has to be the most bloated, flabby, weak, user-hostile CLI environment in history.

I also don't have a lot of money for hardware; this post is being typed on a used Thinkpad T440s I was lucky enough to acquire for $200 on EBay from a trusted source. And, being that i work 55+ hours a week *and* do anti-human-trafficking stuff, I don't have endless time to piddle around with Gentoo any longer. Much as I love the near-insane levels of control and configurability it offers, my poor ULV mobile i5 CPU just can't take that level of abuse for long.

So...I'd been distro-hopping for a while, playing with Devuan, Slackware, Artix, Obarun (unsuccessfully; the fucker just wouldn't install and I have no idea why), even FreeBSD.

And then a friend from college, the one who got me into Linux all those years ago, suggested Void.

Now, I'd heard of Void before, but had never even visited the homepage. Doing so left me somewhat underwhelmed, but intrigued; it was very businesslike. There wasn't the patronizing aura of the *buntu family, the slightly notionally-cabbage-smelling, half-baked feeling around Debian, or the complete unprofessionalism of umpteen hojillion other flavor-of-the-week distros.

If anything, it felt like FreeBSD, which I had limited success with and mostly enjoyed, but which didn't let me do a few things I really had gotten used to on Linux. So with Matt's encouragement, I downloaded the Xfce installer, backed up my stuff, cleared out my HDD, and booted it up.

It was a revelation. I don't know how else to describe this. Aside from the slightly WTF choice of using CFDisk, the installer was a no-nonsense NCurses-based affair that reminded me in all the good ways of the Slackware and FreeBSD bootstrappers. It was one of the most painless and ye-gods-FAST installs I had ever seen. Rebooting worked immediately; I was presented with a vanilla Xfce desktop and a very minimal set of programs, which is how I like it.

Two things immediately stood out: the first is the package manager, the XBPS suite (xbps-* commands). I can't say enough good about this; it's like Arch's Pacman for adults. it feels like the lovechild of Apt and Pacman in all the best ways, and it is *blazing* quick. It also has an xbps-src build system, which is to xbps something like the *BSD ports tree is to FreeBSD's pkg utility. It even acts a lot like the ports tree.

The second, and the thing that has made me a Void fangirl for life, is the Runit init system.

OpenRC isn't bad, and I'll take just about anything over Gawdawful SystemD, but Runit feels like alien technology. It is incredibly fast, it's very simple to administrate--just symlink stuff from /etc/sv to /var/services--and it will even, something like the Minix reincarnation server for its drivers, automagically restart crashed services for you!

Did I mention fast? Because this thing goes from "pushing Enter on the GRUB prompt" to "SDDM login screen ready for my credentials" in 10 seconds. 10. I counted. 9-and-a-bit, actually, but close enough to 10 to say 10.

If you run Linux, if you *love* Linux, try Void. You won't regret it. It will change the way you think about Linux. It sweeps away all the bad decisions of the last half a decade. Stuff Just Works. It's the most stable Linux I have ever used, and this despite being nearly as bleeding-edge as Arch. Runit is the star of the show and I wish it were standard on every distro. Do it. You won't b disappointed. Enter The Void.

New York Times Hires and Fires Writer Within 6 Hours

Posted by takyon on Wednesday February 14 2018, @05:19PM (#2993)
8 Comments

Thoughts on init systems, Epoch, the future

Posted by Subsentient on Monday February 12 2018, @06:08PM (#2989)
5 Comments
Code
Oh boy, has it been a while. A lot has changed, much of it not at all for the better.
Life's been hard, but I suppose that's a story for another time.
I've spent the last year or so using Fedora exclusively, as it always has been my favorite distro, other than the systemd quagmire. I've stopped using SubLinux 2, because it's too outdated and I don't have the time or the energy to build another complete system myself with everything that's been going on, much less maintain it.
I used Epoch with it for a while, stumbling through the incompatibility that intermixing systemd and Epoch components caused, before I gave up and essentially said "fuck it". So, I've been using systemd for around a year now.
Here's what I learned from that experience:

* systemd is still terrible. It's unstable, slower than it should be, buggy in critically important places (like unmounting filesystems on shutdown), and still assimilating technologies that it really shouldn't be. (systemd-boot, aka gummiboot, anyone? Now introducing systemd the bootloader.)

* systemd does have some important things that Epoch does not, most importantly a more packager-friendly configuration system as compared to Epoch.

* Epoch is still substantially superior in some ways. Among them is stability, fault tolerance, overall program size, and service management, not to mention the lack of external library dependencies, e.g. dbus. It also has a better feature set for recovering from certain issues, e.g. ctrl-alt-del to kill a stuck service.

* Epoch's codebase is absolutely nauseatingly terrible. It's incredibly hideous. It's "tried and convicted for war crimes" bad. It's unwise for me to attempt to further this codebase as-is, without at least a substantial partial rewrite.

I've had time to do some introspection, and I've realized where Epoch succeeded, and where it failed.

Where Epoch succeeded
* Service management
* Footprint size
* Configuration syntax
* Logging system

Where Epoch failed
* Codebase quality. Like seriously, so disgusting.
* Packager-friendly configuration/service files (A very big one)
* Single threaded design, which created opportunities for lockups and broken applets with misconfigured services, though this was always recoverable.


So, what now? Well, I haven't given up, but I don't have a lot of time right now, due to crippling financial problems.

I do have a plan.

Enter "Monolith"
The new design concept for Epoch's replacement.
The paradigm for it is as follows:

* No dependencies other than the standard library, just like Epoch.

* Multi-threaded, can start multiple services in parallel.

* FIFO file-based interprocess communication, phasing out the incredibly disgusting "MemBus" used by Epoch currently.

* Similar service file keys as to what Epoch uses currently.

* Far better support for multiple configuration files than Epoch

* Minimalist C-based module system and API, for further functionality.

* The biggest thing of all: An optional module for systemd service file compatibility, to make it a true drop-in replacement for systemd. Some things that deal with, eh, stupid stuff from systemd, like its own version of getty etc, will not be supported for obvious reasons.

* GPLv3 license. I've spent considerable time lately being exposed to the proprietary, Tivo-ized Linux systems of today. I've been absolutely disgusted at what I've found. I have no intention of giving them any further resources to lock users in. The GPLv3 should force all modifications to the base code to be published openly, as well as prevent Tivo-ization on those that do use it. With any luck, someone will put it in a set-top box without paying attention and I'll be able to force them to open it up to user code.

I'm thinking I'll write it in C++14, so I can have an easier time eliminating issues like segfaults caused by buggy homebrew linked lists etc.

It'll be a while before I can do this.
Unless someone wants to pay me a livable wage to work on this project, it's going to have to wait until my life stabilizes a bit, which doesn't seem to be coming soon. hint hint.

That's it for now.

Any thoughts?