Is that Dice? Little Registry Cleaner now installs a ton of crap by default. Look at the latest reviews. You can still get a clean install by reading each of the dialog boxes but the point is it comes bundled with crap in the first place.
Use what makes sense for the application. I'd never try to run my *entire* house on DC. But between my modem, router, access point and VOIP box I have 5 separate 120V -> 12V rectifiers. I would love if I could just plug them into a separate 12V plug.
I have a 8 port USB charger to charge all the different things in my house that run on 5V. I've replaced a few outlets in my house with 4-Port USB outlets. I've seen bars and restaurants put them in because people charge things with 5V these days.
I'd say half of my house could run on DC without a problem. AC Generation->AC->DC->Use is still more efficient than AC Generation->AC->DC->AC->DC-> Use. And for people off grid you can get by with DC Generation-> Use
While you can do neat things with a cheap board programmed by block diagrams, that's not going to cut it in my job, where we control machines that cost in six figures.
I make my living by addressing the hard parts of getting processes automated. I've only been in industry for 10 years and I've already automated away a few internships. I'm learning Python explicitly for the purpose of automating dSpace + Matlab + hardware and reducing the need for 2-3 full time people.
Programming is one of them.
Programming is a tool. Engineers use programming to automate away their engineering. Photographers use programming to automate away their photography. Farmers use programming to automate away their farming.
Your job isn't programming, it is automating what ever task you are trying to complete. What would have taken Hugin a few minutes to complete can now be done in a cell phone.
I've met a few people who had Masters degrees but were terrible coders
It is, and that is where industry is going. I work with PhD and MS Engineers that couldn't code their way out of a wet paper bag. Coding is a tool, not a profession. Engineers use coding to automate something else. Now we're designing entire control systems for vehicles with Simulink.
Cost of entry has come WAY down. Now you can buy a $12 board that interacts with the real world that can be programmed with block diagrams. People that don't or can't learn C can now make their "cool things" that they think of without having to learn C.
"Programming" is not a profession any more than a "hammer" is a profession. It's a tool to get something done faster and more efficiently.
If you asked a normal 5 year old to print out the string "Hello World" 5000 times they might actually type it out 5000 times. If you teach a 5 year old how to program they will make a program to print it and then focus on "something cool".
The cost of entry to program has come down since it required a separate employee to enter your punch cards. Kids that grow up with programming will take that skill set into where ever they go in the future. My wife works with doctors that don't know how to use a keyboard because "You're going to be a doctor, doctors won't type". Now all doctors type. Now doctors enter all of their own notes. In 20 years Doctors will be programming their own disease identification.
And as the cost of entry comes down so does the salary. A job that a 10 year old could do isn't going to garner 6 figures.
I do the same thing with sha256.
echo -n "myseed+username+website" | sha256 | cut -c1-20
echo -n "myseed+0100010001010011+slashdot.org" | sha256 | cut -c1-20
I'm thinking about writing a base65 encode function for websites that require !@#$%^&*().
The only thing that my company will let slide is something that has absolutely nothing to do with their core business.
Say my company makes cars and trucks. If I invent a better breastpump for my wife they really won't care.
But if I start a small startup like Tesla I'm hosed.
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:
A Linux-based system is a modular Unix-like operating system. It derives much of its basic design from principles established in Unix during the 1970s and 1980s. Such a system uses a monolithic kernel, the Linux kernel, which handles process control, networking, and peripheral and file system access. Device drivers are either integrated directly with the kernel or added as modules loaded while the system is running.
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?
Have you tried it on a stable OS release that has systemd?
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).
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
most, if not all of my systemd-units on a dozen of servers using constructs like below to make the whole tree
And what makes debugging even more fun is it does it randomly too:
I can confirm Harald's report at DigitalOcean F21 x86_64. It happens on root login, but *not* every time.
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.
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.