When we last looked at Google’s Fuchsia operating system , it was very modest. While it was designed for everything from Internet of Things devices to PCs, there wasn’t even a graphical interface to show. Well, things have… evolved. Ars Technica has revisited Fuchsia several months later, and it now touts an interface (nicknamed Armadillo) that makes it clear this isn’t just some after-hours experiment. It’s only a set of placeholders at the moment, but it gives you a good idea as to what to expect. The home screen is a large, vertically scrolling list of cards for “stories, ” or collections of apps and OS components that work together to complete a given task. There’s also a Google Now -style section that has “suggestion” cards for tasks — use them and you’ll either add to an existing story or create a new one. The prototype UI also includes a simple split-screen interface, and scales up to tablet size. Fuchsia isn’t based on Linux, like Android or Chrome OS, but it still uses open source code that would let anyone tinker with the inner workings. Apps, meanwhile, are built using Google’s Flutter kit, which lets developers write both Android and iOS apps. Things are clearly coming along. But there’s one overriding question: just what role will Fuchsia have? Google’s Travis Geiselbrecht stresses that this “isn’t a toy thing, ” but there’s no public strategy. Ars speculates that Google is treating this as a sort of Android re-do: what if the company could design a platform while dumping all the technology it no longer needs or wants, such as Linux or any traces of Java ? The use of Flutter would let you run Android apps until there’s broader software support. It might take years before Fuchsia is ready for public use, assuming that’s the ultimate plan, but there could be a day where Android is no longer the center of Google’s computing universe. Source: Ars Technica
See the original article here:
Google’s mysterious Fuchsia OS looks like an Android re-do
New submitter evolutionary writes: Plutus Payroll, an Australian payroll company, is refusing to pay contractors due to a dispute with companies using their services. Around 1, 000 IT workers are unable to receive payment for services rendered. One may ask, “Where are the companies who actually hired the IT workers?” The Register reports: “This story starts with Australia’s employment laws, which see lots of contractors officially employed by recruitment companies or payroll companies. The company at which the contractor works likes this arrangement as it means they don’t have to put such people on their books. Recruitment companies and payroll companies charge for the service. Contractors generally like the convenience of having one employer even though they hop from gig to gig. The system requires fluid payments. Companies who hire contractors pay the recruiter, which either pays contractors direct or pays the payroll company contractors prefer. If the cash stops flowing, contractors get crunched. That’s what’s happened to around 1, 000 contractors who elected to use Plutus as their paymasters: the company says it is in the midst of a completely unexplained ‘dispute’ that leaves it unable to pay contractors, or receive money from recruitment companies, but is still solvent. The Register has checked with the bank that Plutus clients say sends them their money — the bank says it is aware of no dispute. One possible reason for the mess is that Plutus did not charge for its services. How it made money is therefore a mystery. Another scenario concerns the company’s recent acquisition: perhaps its new owners are being denied access to some service Plutus could access as a standalone company. Plutus is saying nothing of substance about the situation. A spokesperson tells us the company deeply regrets the situation but won’t divulge anything about the dispute and has offered no details about when contractors can expect resolution.” Read more of this story at Slashdot. 