I successfully helped a woman in a similar situation a few years ago. We thought what would help the most was to become familiar with the parts of a modern framework (controllers, ORMs, etc). She used _Agile_Web_Development_With_Rails to build a sample site, and then built another site with jhipster, studying the generated artifacts. This took about 4 months, and we met every other week so that she could ask questions and we could plot out where she should concentrate her efforts.
After that effort, she was able to get a job with a large stable company.
the gear on the left is the driving gear, moving at a constant rate. When the gear on the left allows the gear on the right to fit closer to the center of that left gear, the gear on the right moves more slowly. Similarly, when the gear on the right fits farther from the center of the left gear, the gear on the right moves more quickly
If you want an example of a project using all the latest technologies together, a good place to look is jhipster. It’s code generation of a spring boot and angular or (coming soon) react app. When you use it, it will ask a series of questions about what you want your app to look like, and then generate that app. It as if you paid some expert to come in for a week and set everything up, including migrations, auth, documentation using swagger, and so on.
It's worth pointing out that both of these sites exist specifically to address my frustration in just getting started with a Java web stack, but it's taken me a couple of weeks to discover them.
I've been teaching my 7 year old using the "Coding Games in Scratch" book, and he loves it. I'm using Chrome on Ubuntu 16.04 to run flash, and it works fine.
Would be interesting to see how this compares to RDS--i.e. perhaps all these optimizations are already in place, or perhaps it makes sense to not use RDS, and optimize mysql for your own workload.
Anyone know of any comparisons between this and Apache Mahout? I've used Mahout's Item-Item recommender in the past, and it's worked well, just wondering if there were advantages to this recommender.
Considering the type of information that would be stored in an application for use by physicians, they might be considering Java due to the number of security issues found in Rails as compared to the number of security issues found in something like Spring over the past several years.
If you don't want to read the whole thing, here's a summary: there's a whole bunch of stuff the compiler does when it transforms SequenceL code into C++. For example, it's numa aware and takes advantage of sse and similar types of things where possible. They've seen that if a dedicated team has been hand tuning a particular algorithm in c++ for years (the sort of thing you might see in certain industries), the sequenceL generated code will probably not beat that--but, it might take a week to develop a version in SequenceL that runs at 80 to 90% of that speed.
The rest of the time (i.e. when compared to code that has not had a dedicated team devoted to hand optimizing the c++), they've found that the SequenceL generated code runs much faster and takes less time to develop than traditionally developed parallel code. This is for a few reasons: generally, most teams won't take the time to parallelize all the parts of their code than can possibly be parallelized. Thus, they run into a sort of self imposed Amdahl's law situation--those parts that they haven't spent time parallelizing eventually become, relative to the entire app, the part of the app that takes longest to run. This problem is seen more with larger core counts, of course. Second, many highly talented engineers who are world class in their own domain are not also world class at writing multithreaded c++, and so may not have written their own multithreaded / numa aware memory allocator, or optimized the sse widths correctly for different chip generations and so on.
In the end of course, it depends on the algorithm, and delving into the paper, or even better, contacting them any trying it out with your particular algorithm, would provide the best answers.
4. I'm not aware not aware of other such languages/systems.
I think the main difference is that Centos strives to be "100% binary compatible." We write software targeted to enterprise users that are generally running Redhat. Our development and test platforms are Centos.
Scientific Linux, while compiled from Redhat sources, does not strive for binary compatibility with Redhat.
They compile the same SRPMS after they strip the logos and Redhat references out. Yes, they add extra optional packages like OpenAFS and others, but you can just disable those repos.
After that effort, she was able to get a job with a large stable company.