The implications of a technology like this go far beyond taxi drivers.

In the moment when autonoumous cars go mainstream, half of the car manufacturers will go bancrupt and the other half will have a very good time.

I yet have to see many convincing cases of extensions for browsers (for everyday applications). I am unisg firefox, and the extensions i use are scrapbook, nojs, foxyproxy.

Probably my post was to long to understand for the AC.

And you actually have to share it only with the person you are giving the binary to.

but recently mainly for low-price products. i dont complain, i bought a HP low-cost notebook 3 years ago, and i am happy - despite the obvious drawbacks, since the price was more than ok.

Yes.

Android development started a long time before the iphone was released. Taken into account the first target market for any mobile company back in that day (Japan), it seems indeed likely that there were *many* other devices which influenced the design of samsungs mobile phones. (Most notably the huge amount of PIM devices in japan like the Sony Clie Series).

What indeed was manifested by the Iphone is that even mobile phones should not be designed as PIM devices but as media players (thus the loss of buttons makes sense).

Yeah, i would like to say that these things are probably a great source or creativity and enable next level of machine learning algorithms to understand life, but 20 years of internet made me a realist.

What really worries me about this is that such a thing cant be enforced or checked without decrypting all my storage, how unrelated it may be.

I find that court rulings should have the property of being enforcable without confiscating all of my stuff if i am not guilty (or accused) of any crime.

I mean, thats the elephant in the room, isnt it. I found that everything thich can be automated easily is automated in eclipse.

My advice is: train your analytic skills and understand where thing go right, wrong, or just different. This can only be done by experience. While i learn programming languages slower than with 25, i learned to analyze code. Having seen code written by many very different people (everything from physics professors to psychologists), i understand the idea of most code better than the authors (since i see the limitations the author is placed under). If you apply your analytic experience and skills to the problem, you will be welcome to any team.

you just ask on slashdor for people volunterring for the setting it up, knowing the specific requirements, and thinking about it.

The real question is: is tehre already a MS Access DB?

If yes, then dont touch a running system.

I love the cloud. I have a 24/7 EC2 instance for personal use (vpn, charing files between my computers in the vpn), I use the compute instance whenever i need to number crunch something (FEM, Inductance calclulations).

But there are reasons to keep things in your own responsibility. The most important reason would be that iff you dont want the cloud service provider to write something "if it fails it fails" then the cloud is as expensive as your own serve, and that only if you dont count the lawyer cost which you would need to check if yout fulfilled all obligations for your purpose by making some contract.

inadverted creation of obligations:

-the matlab compiler signs code for execution. no GPL3 is compatible with it (even if they never mention the term "DRM" in the manual).

-what happens if a part of your software sits in controllers owned by your customer (for whom you develop) which logs data as a service offered to his customers? as long as you own the controller they dont need to pass the code on, but at whuch point should that happen?

-assume that you develop software to be delivered to a daughter company. is it enough to create builds and give them access to the repository to enable them to fulfill their obligations?

i have been working in two of theand really big companies (both > 100k employees), one Japanese, one german.

  in the Japanese company there was no strategy regarding software and "whatever works" was fine, which included open source.

the German company had the strategy to explicitly manage the obligations from open source. effectively the rules were:
Apache style, bsd style licenses and LGPL where white listed
GPL 3 was blacklisted
GPL needed special consideration (so kind of blacklisted)

Employers favor people getting things done in a professional way. I have colleagues who stay in office 20% more than i do (10h instead of 8h), yet they produce less code and much less *well working not completely bugged code*. Planning my work and dissecting a problem into small, doable (and commitable) tasks came to me with age and experience. If a release date comes close, it gets even more important to think twice before you type and avoid stupid mistakes - and thus, my experience shows: avoid stupid all-nighters or 100h/week coding marathons. A missing feature usually can be explained and added later. But if a fucking show-stopper bug causes an undetected gross miscalulation, then things escalate quickly and nastily, up to loosing the customer.

I had the case that some moronic project leader did not honour the feature freeze, but forced a junior colleague of mine (he knew I would not follow his order in that) to patch something in the middle of the code on the last afternoon before the review meeting (wihtout telling the rest of the team). He did not even put the time into looking into the new pdf report generated by the program and sent it directly to the customer as a demonstration. I can tell you, the customer was impressed that we presented software the output of which were not inspected by a human a single time (Reported cost error was by a factor of 10^12).