It's a pretty niche app, but the Slashdot crowd has a pretty large percentage of retro-computer collectors, so I thought it might be worth a mention...
tapDancer is an Android app that encodes
...have been around for years. I know they don't generally share the road (except with hapless interlopers who have to get out of the way) but there's still been much knowledge gleaned there. So the 'science' is already eay more advanced than with autonomous cars, for example.
Famo.us chases another holy grail, namely the 'write once, run anywhere' dream. Instead of having to write different code for different platforms, like iOS and Android, developers can write one application that works and looks as good on all platforms, in theory anyway. This of course saves a huge amount of time and resources. Unfortunately, this idea is not without its problems and has never really worked very well with earlier attempts like Java-applets, Flash and Silverlight. In the end native applications have so far always been faster and slicker and I'm pretty skeptical Famo.us will be able to change this."
...think that was ever going to last? C'mon now... really?
Firefox better watch itself. Trying to "nudge" people into creating apps that only work properly with their browser / OS may not end well for it.
While I agree most digital pianos do not have the greatest sound, VST plugins (particularly Kontakt) can emulate a piano quite closely using libraries that are gigabytes in size. It's not uncommon to see a MacBook chained to a digital piano during a performance.
there are virtually no stop signs, only round-abouts and "give way"s (yields). Never mind cycling, DRIVING is much quicker!
Uber is set to meet with the Directorate next week but it is likely the demands the Directorate will place on Uber drivers, such as mandatory criminal record checks, vehicle inspections and insurance, will make the service in Melbourne unviable.
Meanwhile, the New South Wales government is awaiting a report to determine if Uber drivers operating in that state are doing so illegally, warning that drivers could face substantial fines if they are found to have been operating in breach of the law. In South Australia, it doesn't even appear Uber will get off the ground — the state has made it clear that those who operate as an Uber driver will be driving without being covered by the state's mandatory insurance coverage, essentially de-registering their vehicle and making them liable for fines and license suspension."
Link to Original Source
Unfortunately, while still theoretically possible, installing an alternative init system means doing without a number of useful, even essential system programs. By design, systemd appears to be a full-blown everything-including-the-kitchen-sink solution to the relatively simple problem of starting up a Unix-like system. Systemd, for example, is a hard-coded dependency for installing Network Manager, probably the most user-friendly way for a desktop Linux system to connect to a wireless or wired network. Just this week, I woke up to find out that systemd had become a dependency for running PolicyKit, the suite of programs responsible for user privileges and permissions in a typical Linux desktop.
I was able to replace Network Manager with connman, a lightweight program originally developed for mobile devices. But with systemd infecting even the PolicyKit framework, I find myself faced with a dilemma. Should I just let systemd take over my entire system, or should I retreat to my old terminal-based computing in the hope that the horde of the systemDead don't take over the Linux kernel itself?
What are your plans for working with or working around systemd? Are there any mainstream GNU/Linux distros that haven't adopted and have no plans of migrating to systemd? Or is migrating to one of the bigger BSD systems the better and more future-proof solution?"
Rather than continuing to bitch about how your darling child idea didn't work out, maybe you should just come up with something else and move on?
This is getting a bit old...
I think this comment thread does a great job of proving the point TFA was trying to make.
Of course, chanting "women are no good at IT" often and loud enough will cause women to shy away from IT as a career. Using that mantra as justification to not hire those foolish enough to continue pursuing it solves that problem too.
The reality is different. Plenty of women were programmers in the 1980s. Thousands of girls learned Pascal in the high schools of the late 1980s / early 1990s. That females are capable of being technologically savvy is indisputable.
The truth is, for a number of self-interested male reasons the IT of the last couple decades has drifted toward misogyny rather than away from it, like the rest of corporate culture. Why? Well, brogrammers, aspies and hustlers, for a start, each for their own reasons, don't like collaborating with women, out of fear of conflict, or the risk of feeling humiliated if shown up. They need to man up, but as long as the industry at large permits them to have their little male-only clubhouses they won't make any effiort to change,