Thursday, November 16, 2017

What happened to Intel XDK? Why was it discontinued?

 


.

PaulF_IntelCorp

Employee

‎11-16-2017 02:41 PM

[RETIRED] Intel XDK

Development and support for the Intel XDK has ceased.

The Intel® XDK is no longer being developed or updated for new operating systems and devices. You may continue to use the final version of Intel XDK (version 3987).

https://community.intel.com/t5/Software-Archive/RETIRED-Intel-XDK/td-p/1075483

.

PaulF_IntelCorp

Employee

‎10-26-2016 12:26 PM

An "IoT Companion App" is a mobile Cordova app that's been optimized for use with IoT devices and IoT cloud services. What that means, regarding mobile apps, is that our system will focus on creating Cordova mobile apps that use Cordova plugins that are useful for communicating with apps running on IoT devices and for communicating with cloud services that designed for use with IoT devices.

Mobile apps that you create with the XDK are standard Cordova mobile apps. As the IoT focus of the XDK progresses, if you need to leave the XDK we will provide you with the means to move your mobile app to Cordova CLI. The XDK creates a standard Cordova CLI application, so any app you create with the XDK can be easily built and developed using standard Cordova CLI tools.

Regarding Intel support personnel, none of us works full time on providing support. It has always been this way, we all have other duties we must attend to, beyond support. We are in the process of adding some new support personnel to the forum. Additionally, there are quite a few regular developers who answer questions on this forum. We do try to restrict our support to issues that are specific to the use of the XDK; we are not here to teach people how to write a mobile app or an IoT app. For general help regarding programming problems there are many blogs and forums that provide much better information.

https://community.intel.com/t5/Software-Archive/Future-direction-of-the-XDK/m-p/1066498

.

Read More

Monday, September 18, 2017

What happened to SharpDevelop? Why was it discontinued?

 .

According to dgrunwald , a member of ICSharpCode github icsharpcode/SharpDevelop community:

Yes, it's dead.

It takes a massive amount of effort just to keep up with the changes to the language and build system Microsoft is doing, probably at least 2 man-years to catch up to C# 7 / the .NET Core stuff. That's a bit too much for a hobby project -- we don't have that kind of free time anymore, and even if we did, there are better ways to spend it than playing catch-up with a huge dev team at Microsoft.

Combine that with the free community edition, and there's little space for multiple open-source C# IDEs.

Remember that MonoDevelop is still around; and that VS Code is also open-source! Start with one of those if you need a portable IDE.

https://github.com/icsharpcode/SharpDevelop/issues/799

.
Alternative:
(Cross platform IDE for C#, F# and more)
Read More

Sunday, February 21, 2016

Google Apps Script Library Underscore

 


 

.

Underscore

Underscore for Google Apps Script is a library that enables the use of the underscore.js library in Google Apps Script. API docs are available here.


Adding the library to your project

Underscore for Google Apps Script is made available as a script library. This is how you add it to your project:


Select "Resources" > "Libraries..." in the Google Apps Script editor.

Enter the script id (1PcEHcGVC1njZd8SfXtmgQk19djwVd2GrrW1gd7U5hNk033tzi6IUvIAV) in the "Find a Library" field, and choose "Select". (If you have copied the library, enter instead the project key of your copy.)

Select the highest version number, and choose Underscore as the identifier. (Do not turn on Development Mode unless you know what you are doing. The development version may not work.)

Press Save. You can now use the Underscore library in your code.

If you want to combine Underscore with Underscore.string for Google Apps Script, then also add its project key by following these instructions.

.

Reference:

https://github.com/simula-innovation/gas-underscore


Read More

Google Apps Script Library Lodash

.

LodashGS

Lodash for Google Apps Script is a library that enables the use of the lodash.js library in Google Apps Script. API docs are available here.


Adding the library to your project

Lodash for Google Apps Script is made available as a script library. This is how you add it to your project:


Select "Resources" > "Libraries..." in the Google Apps Script editor.

Enter the project key (1SQ0PlSMwndIuOAgtVJdjxsuXueECtY9OGejVDS37ckSVbMll73EXf2PW) in the "Find a Library" field, and choose "Select". (If you have copied the library, enter instead the project key of your copy.)

Select the highest version number, and choose Lodash as the identifier. (Do not turn on Development Mode unless you know what you are doing. The development version may not work.)

Press Save. You can now use the Lodash library in your code.



Reference:

https://github.com/contributorpw/lodashgs

Read More

Wednesday, February 10, 2016

Google Apps Script Library Code Sample









Reference:
Read More

Thursday, October 13, 2011

What happened to MS FoxPro? Why was it discontinued?

.

“Not a Strategic Product”

Enough disclaimers, let’s get to the subject at hand.  Microsoft has stated for some time that FoxPro was not a strategic product for them.  What does that mean?  To my mind, a strategic product is one that Microsoft would invest in heavily and recommend as the primary path for their customers.  MS would build upon the technology and form an entire “strategy” around it.  VB was strategic.  COM was strategic. .NET is strategic.  Fox was not.  Why not?  To answer that, I think you have to look at why Microsoft bought Fox Software in the first place.

Why Buy Fox?

So, why did Microsoft buy Fox Software.  I will quote an article Jordan Powell wrote in FoxTalk when Access 1.0 and FoxPro 2.5 were about to ship:

Microsoft was working on its Access DBMS which uses a modern variant of the BASIC language. It had to have been embarrassing for Microsoft to have such a glaring hole in its product lineup. They had no DBMS, and their partnership with Ashton-Tate failed to get Microsoft SQL Server off the ground. Some of the marketing types at MS realized that FoxPro was the best version of X-Base out there, and had been trying to talk Bill Gates into doing something about it. They knew that the X-Base language commanded a huge segment of the market and that a product which used the X-Base language would get them into the DBMS market in a big way. They had the marketing resources to put behind FoxPro, and Fox had some interesting and useful technology — not to mention some very talented people, the kind Microsoft likes.

.

xBase Market Decline


FoxPro was first and foremost a competitor in the xBase market.  As that market declined, so did the value of FoxPro as a strategic product to Microsoft.  What led to the decline of a technology that had been so popular in the 80’s and early 90’s?  Technology trends are constantly changing, but here are few key things that in my opinion diminished the xBase market:


dBASE IV: 

dBASE IV was a buggy disaster, and it was two years before they released version 1.1.  Borland bought Ashton-Tate, but could not undo the damage.  dBASE for Windows was not released until 1994.  This was good for FoxPro, which became the biggest fish in the xBase pond, but the pond itself began to shrink.


Lawsuit: 

Ashton-Tate sued Fox Software for cloning dBASE.  The suit was dropped when Borland bought Ashton-Tate, but it could not have inspired confidence in the xBase market.


Client-Server: 

By the early 90’s, client-server technology picked up in popularity and developers were beginning to flock towards database servers and client-server development tools like PowerBuilder and VB.  At the same time, Microsoft was trying to enter the server market with Windows NT and SQL Server, so I’m sure there was strong emphasis on this style of development from them.  I believe there was talk of a “FoxServer” product at Fox Software, but it never saw the light of day before the Microsoft acquisition.


Those are reasons that the xBase market declined, but about now you’re thinking that VFP is so much more than an xBase tool.  I couldn’t agree more.  VFP can go toe-to-toe with VB, PowerBuilder, Delphi, .NET, and others.  If FoxPro was supposed to “go quietly into the night”, someone forgot to tell the VFP 3.0 team, because they transformed the Fox into a full-fledged OOP development platform ready for the 32-bit world and beyond.  So, why wasn’t the emphasis there from Microsoft? 


An important point to make about Microsoft is that they are a follower of development trends, not a leader.  With a few exceptions (the VB GUI designer comes to mind), Microsoft has not been the one to create a development trend.  “Embrace and extend” was their motto, and they have done well with that.  Windows was Microsoft’s answer to the Mac.  .NET is Microsoft chasing Java into the enterprise.  They follow current trends and they do so mercilessly.  Even now, Microsoft is emphasizing HTML5, leaving Silverlight developers thinking “Wait, I thought we were on the cutting edge?”  It would be out of character for Microsoft to promote and strategize around a product built for a market that was trending downwards.  It’s nothing personal against the Fox, it’s just not in their DNA. 


FoxPro Market Decline

Even with the xBase decline, if FoxPro revenue had continued upward, I wouldn’t be writing this article.  Sales declined, and there are several reasons for that:

Power Users: 

Going all the way back to dBASE you could question whether it was a platform for power users with development capabilities or a platform for developers that power users could use.  It was both.  Visual FoxPro put it squarely in the developer category, and Access took over as the preferred database for power users.  The result: much fewer licenses sold.


VB, SQL Server, .NET: 

VFP faced a lot of competition from other products within Microsoft.  With the emphasis always on the latest trends, many developers felt compelled to move to other technologies. 


Visual FoxPro: 

That’s right, VFP itself.  While VFP 3.0 was a massive improvement in development capabilities (and most of us are happy with that decision), it was also a big leap from FoxPro 2.x in terms of learning curve.  It took some developers quite a while to make the jump, and some never did. 


Not Invented Here Syndrome:  

Microsoft took a great product and made it even better, which makes their treatment of FoxPro all the more frustrating.  But Fox was still the stepchild and it was never going to supersede other products developed internally.  By the time Microsoft purchased Fox, they had already made significant investments in VB, Access, and SQL Server.  Those would be Microsoft’s strategic products while Fox would continue serving the declining xBase market and otherwise fit between the lines.


Why 2007?

People had been foretelling the death of FoxPro since Microsoft bought it in 1992.  What made 2007 the year when Microsoft finally decided to cancel it?  Had sales declined to the point that Microsoft could no longer justify Fox development?  Did they want to use the Fox Team in other parts of Microsoft?  Did big customers move to something else?  Were the people that cared gone or no longer in a position to do anything about it?  Your guess is as good as mine.  We will never know. 

.

There are a couple of ways to look at this: 1) Microsoft always wanted to cancel Fox and they finally got their way, or 2) in spite of Fox not being a strategic product, Microsoft continue to create new versions for Fox developers.  I tend to think of it as the latter.  While there was always a question of Microsoft’s commitment to FoxPro, by the release of VFP 5, it had become clear that it would not be a strategic product. 

.

Read More

Monday, April 06, 2009

Download Sentiment140 dataset with 1.6 million tweets


 

.

Sentiment140 dataset with 1.6 million tweets - Sentiment analysis with tweets

What is Sentiment140?

Sentiment140 allows you to discover the sentiment of a brand, product, or topic on Twitter.

How does this work?

You can read about our approach in our technical report: Twitter Sentiment Classification using Distant Supervision. There are also additional features that are not described in this paper.

How is this different?

Our approach is different from other sentiment analysis sites because:
  • We use classifiers built from machine learning algorithms. Other products use a simpler keyword-based approach which may have higher precision but lower recall.
  • We provide transparency for the classification results of individual tweets. Other sites only surface aggregated metrics, which makes it difficult to assess the accuracy of their classifiers.


Who created this?

Sentiment140 was created by Alec Go, Richa Bhayani, and Lei Huang, who were Computer Science graduate students at Stanford University.
What are the use cases?
Brand management (e.g. windows 10)
Polling (e.g. obama)
Planning a purchase (e.g. kindle)


Kaggle Site

This is the sentiment140 dataset. It contains 1,600,000 tweets extracted using the twitter api . The tweets have been annotated (0 = negative, 4 = positive) and they can be used to detect sentiment .

Content

It contains the following 6 fields:

  1. target: the polarity of the tweet (0 = negative, 2 = neutral, 4 = positive)

  2. ids: The id of the tweet ( 2087)

  3. date: the date of the tweet (Sat May 16 23:58:44 UTC 2009)

  4. flag: The query (lyx). If there is no query, then this value is NO_QUERY.

  5. user: the user that tweeted (robotickilldozr)

  6. text: the text of the tweet (Lyx is cool)

Acknowledgements

The official link regarding the dataset with resources about how it was generated is here
The official paper detailing the approach is here

Citation: Go, A., Bhayani, R. and Huang, L., 2009. Twitter sentiment classification using distant supervision. CS224N Project Report, Stanford, 1(2009), p.12.

Inspiration

To detect severity from tweets. You may have a look at this.

.

DOCLINK:

https://www-cs.stanford.edu/people/alecmgo/papers/TwitterDistantSupervision09.pdf

.

WEBLINK:

https://www.kaggle.com/kazanova/sentiment140

.

WEBLINK:

http://help.sentiment140.com/home

Read More

Saturday, January 01, 2000

What is programming


 

.

Programming is a way to “instruct the computer to perform various tasks”.

.

“Instruct the computer”: this basically means that you provide the computer a set of instructions that are written in a language that the computer can understand. The instructions could be of various types. For example:

  • Adding 2 numbers,
  • Rounding off a number, etc.

Just like we humans can understand a few languages (English, Spanish, Mandarin, French, etc.), so is the case with computers. Computers understand instructions that are written in a specific syntactical form called a programming language.

.

“Perform various tasks”: the tasks could be simple ones like we discussed above (adding 2 numbers, rounding off a number) or complex ones which may involve a sequence of multiple instructions. For example:

  • Calculating simple interest, given principal, rate and time.
  • Calculating the average return on a stock over the last 5 years.

The above 2 tasks require complex calculations. They cannot usually be expressed in simple instructions like adding 2 numbers, etc.

In summary, Programming is a way to tell computers to do a specific task.

.

Why should you bother about coding?

You must be wondering - why does one need a computer for adding or rounding off numbers? Or even for simple interest calculation? After all, even an 8th standard kid can easily do such things even over large numbers. What is programming used for? What benefits do computers offer?

Well, computers offer so many benefits:

Computers are fast: 

computers are amazingly fast. If you know how to properly utilize the power of Computer programming, you can do wonders with it. For a typical computer of today’s time, an addition of 2 numbers which could be as big as a billion each takes hardly a nanosecond. Read again - nanosecond! That means that in 1 second, a computer can perform about a billion additions. Can any human ever do that? Forget a billion additions a second, typical human can’t even do 10 additions per second. So, computers offer great speed.

Computers are cheap: 

if you were a stock market analyst and you had to monitor the data of say 1000 stocks so that you can quickly trade them. Imagine the hassle that would create if you were to do it manually! It is just impractical. While you are performing your calculation on the stock’s performance, the price may change. The other alternative is to hire people so that you can monitor more stocks in parallel. That means your cost goes up significantly. Not to mention the trouble you will face if some of your employees commit a calculation error in the process. You may end up losing money! Contrast that with the case where you use a computer. Computers can process a huge amount of information quickly and reliably. 1000 stocks are nothing for computers in the 21st century.

Computers can work 24x7: 

Computers can work 24x7 without getting exhausted. So, if you have a task that is big enough, you can without worries allocate it to a computer by programming it and sleep peacefully.

.

Extracted from: 

https://hackr.io/blog/what-is-programming



Read More