I deleted my Linked In after getting endless recruiters and head hunters that didn't even read my resume and just blindly sent out requests.

I have 10 years in industry in a very niche market and I'll get jobs in manufacturing or other random area that just require a Mechanical Engineering degree.

It got to the point where I'd have boilerplate nastygram about actually reading my resume and getting back to me.

It WAS that way:

Other people in this thread have already point out that the direction systemd is headed will leave us with 2 binaries: The kernel and systemd. What next, systemd incorporates a mysql server?

You mean like Fedora/RH which has 4 'urgent' severity bugs with systemd

Including one where systemd breaks Keyboard shortcuts handling in text virtual consoles on Redhat Enterprise Linux.

If you lower the bar to "high" priority you get some fun ones like:

Unable to boot when systemd's LogTarget is set to syslog-or-kmsg or syslog on RHEL7. (The devs left it at "Ok, dropping log messages even just from systemd itself isn't probaly a best way, but wee need more time for investigation." in September 2014).

reboot or shutdown commands unresponsive during systemd-fsck

systemd stuck when auto-mouting volume for NFS

Systemd doesn't unmount all devices before calling reboot/halt and thus corrupts a clean RAID1

These aren't "oops, I can't play MP3" level bugs.

To quote Debian:

How Debian Testing Works

Packages from Debian Unstable enter the next-stable testing distribution automatically, when a list of requirements is fulfilled:

• The package has been in "unstable" at least for 2-10 days (depending on the urgency of the upload).
• The package has been built for all the architectures which the present version in testing was built for.
• Installing the package into testing will not make the distribution more uninstallable.
• The package does not introduce new release critical bugs.

There are definitely some systemd bugs that would be considered 'critical release' bugs, including a new one on Fedora that randomly makes folders RO such that daemons and services can't start.

I would call that a 'critical release bug'.

Wow, I had to go look for myself and you're right RedHat/Fedora has ironed out ALL the bugs with systemd

This one is a few weeks old

And what makes debugging even more fun is it does it randomly too:

There's a difference between This package broke a small test case" and "A large number of users are having problems across the board"

If Debian developers were following their own rules systemd would have never made it out of unstable or experimental. It was certainly not ready for testing.

https://en.wikipedia.org/wiki/...

SystemD is fucked up by design. Do one thing. Do it right.

Now they're taking a separate, barely updated UEFI bootloader and shoehorning it in as well. They would have been a bit better of at least starting from Grub2.

No, it's not "supposed to break". Heck I ran unstable for years and only had 1 serious problem in all that time. If you really want crazy go to experimental.

Testing is for hashing out deep and difficult bugs not "This is a complete POS"

I don't think the true "PowerGlove" successor has come yet.

A smart glove like this could turn any ordinary squeeze ball into a chording keyboard. With Google Glass and other similar technologies chording keyboards and wearable tech would work for rapid next input without voice. Anyone that has played GuitarHero knows how a chording keyboard can work.

It would actually be a perfect device for simulating the EPA test cycle. It would be a perfect way to sell it legally. The EPA cycle is "the" test for cars in the US so there are plenty of professionals that would love a tool. Some simulation software starts at $5k/license. (CANalyzer). No one says you have to sell your device with 'encryption' so that the EPA cycle would be replaced with whatever cycle you wanted.

Or you could just do it with a cheap uC board these days. These guys are building a engine EFI controller with a $14 circuit board as the base. Even having to spoof their own messages With an ODB/CAN simulator you could easily

And maybe someone would then finally make a legitimate cheap CAN/ODBBluetooth reader instead of clones of clones or a chip that is ages old to read data as well. USBCAN cables from good vendors start at $500 even though the functionality is built into a lot of new chips.

When a computational package designed to manipulate massive data sets uses less RAM than facebook I kind of think we're doing something wrong.

Did I say write 3 versions? Just do all of the JIT compiling NOT on my computer.

That's the point. Why are we using the battery power of thousands of tiny little ARM devices to compile something that could have been compiled once?

When you boot your Laptop do you recompile everything just so you can grab the source daily?

So use it like html5 video and have javascript backup.

script x64="uselessWidgetJavascript.x64" x32="uselessWidgetJavascript.x86" javascript="uselessWidgetJavascript.js"

If you lumped 90% of all internet devices on the web they'd probably fall under x86, x64, & ARM.

Additionally Apple has figured out how to do fat binaries.

script type="x64"

I don't want something else that my computer has to interpret. Do all the compiling before it shows up on my computer so that I don't have to deal with this: http://i.imgur.com/b2uUrIL.png

Even "JIT" compilers start to suck when you have a few dozen of them running at the same time.

Agreed. I can't open more than a few javascript heavy pages without this happening: http://i.imgur.com/b2uUrIL.png

All of those tabs have terrible javascript trying to give me a decent Web 2.0 experience.