Today’s starting programmers mostly directly dive into Jquery / angularjs , Programmers of last decade started with javascript . and Now Angularjs is on hike .
See whenever a WebPage is opened , JS / Jquery / AngularJS Code is on Client Side So Amount of Code is adds to Page will Increase Request Time .
We Use Javascript Before Jquery , Different types of Sliders , Dom Manipulations were done with lot of Javascript code like using But After Jquery We took a Relief for many things as below
Lines of Code Decides Lifeline of App as below -
Javascript -
Function changeBachground(color) {
Document.body.style.background = color;
}
Onload=”changeBackground (‘red’);”
Jquery
$ (‘body’) .css (‘background’, ‘#ccc’);
So Simple if we can achieve something easily with less code why we will not adopt it
Then AngularJS Came that is a complete MVC Framework . It is also Javascript Framework . So whatever you do with AngularJS you can also achieve with Javascript . But Why you need to it start it from scratch you can join angularjs repository to propose some solid changes to it and extend it if you strongly need as doing everything you need to do in a website using javascript doesn’t look good idea .
JAVASCRIPT CODE
Characters: 700
Lines of JavaScript: 13
<!DOCTYPE html>
<html>
<body>
<h1>Hello World with pure JavaScript</h1>
Write some text in textbox:
<inputid="hello-input"type="text" />
<h2id="hello-output">Hello </h2>
<script>var inputField =document.getElementById('hello-input');var label =document.getElementById('hello-output');varhandleKeyup=function() {var value =inputField.value;label.innerHTML='Hello '+ value; }if (document.addEventListener) {document.addEventListener('keyup', handleKeyup); } elseif (document.attachEvent) {document.attachEvent('keyup', handleKeyup); } </script>
</body>
</html>
JQUERY
Characters: 529
Lines of JavaScript: 7
<!DOCTYPE html>
<html>
<body>
<h1>Hello World with jQuery</h1>
Write some text in textbox:
<inputid="hello-input"type="text" />
<h2id="hello-output">Hello </h2>
<scriptsrc="//ajax.googleapis.com/ajax/libs/jquery/2.0.3/jquery.min.js"></script> <script>var inputField =$('#hello-input');var label =$('#hello-output');inputField.on('keyup', function() {var value =inputField.val();label.html('Hello '+ value); }); </script>
</body>
</html>
ANGULARJS
Characters: 325
Lines of JavaScript: 0
<!DOCTYPE html>
<htmlng-app>
<body>
<h1>Hello World with AngularJS</h1>
Write some text in textbox:
<inputtype="text"ng-model="sometext" />
<h2>Hello {{sometext}}</h2>
<scripttype="text/javascript"src="//ajax.googleapis.com/ajax/libs/angularjs/1.0.7/angular.min.js"></script>
</body>
</html>
The Story of Freedom 251 is not so old and Now Again Make In India Came With a New Crappy Thing "Namotel" . We know Namo is rocking these days in Indian Politics But that does not mean its name works everywhere . If you are doing Shit then It will not come in different way if you say NAMO .
Namo + tel = Website Crash
Namotel is another attempt of "Make In India" To Lauch & Offer Chepest SmartPhone . The Crappy game started by Freedom 251 gave to birth to another one . This Time SmartPhone is offered at Price of "Rs 99" It is claimed to be India's Most Affordable Smartphone
In Press Conference Company's Promoter Madhav Reddy Said Smartphone will be available to be booked at Price of Rs99 from 17 May,2016 To 25 may, 2016 On Company's Official Website Namotel . Smart Phone Will Be Available on Cash On Delivery
But I think they Don't Know How To Launch A Product To 1.252 Billion Indians . This Also Doubt About the Quality of Make In India Products That they are planning To launch and also Some That they launched .
Instead of Launching Cheap SmartPhone they should Use Their Talendted People To Make Valuable , Creative and Better Quality Product Atleast Better Than Freedom 251 or Nametel
Message By Comapany That Didn't Stood Up For Even 1 Day
'Joy and freedom represents the logo! The same joy will flourish in billion Indians in the form of smart Connect with (3 different looks and shapes) Android Smart powerful Phone at 99. We make this product to show love for India it is a 'MAKE IN INDIA' Initiative. This model is limited and it is applicable only for India and who holds Aadhar Identity.'
Namotel Rs. 99 SmartPhone Product Specification
4-inch display with 480x800 pixels WVGA resolution.
Android 5.1 Lollipop OS
1GB RAM.
4GB of internal storage which is expandable up to 32GB via microSD card.
One of the Fundamental Principal of Asp.Net MVC Framework is Web is Stateless And AspDotNet MVC is Stateless AspDotnet WebForms is a try to make Stateful Modal But Its difficult to main it as this modal does not exist . Sessions Create lot of load on Cache that was biggest problem .
Using Session in AspDotNet MVC is like Putting APPLE Logo on Asus Laptop and Calling it Apple Laptop . Reality does not change .
What Is Alternative To Session in MVC
You can use TempData in place of Session . Tempdata is limited form of Session . Don’t Use Session in MVC as you are already having Tempdata and one benefit of Using Tempdata is They will automatically deleted no need to clear or remove them as we do with session
How To Use TempData In MVC
When Data is TempData is read it is immediately market for deletion at the end of request . That means you can use Value Tempdata In Tempdata Only at the Next Request . See Example Below -
TempData is Filled With Data
TempData["SomeTemp"]= "Hey! This is MVC" ;
Tempdata Accessed in Second Request
Object value = TempData["SomeTemp"] ;
Value in Tempdata will be Cleared After Above Line of Code . If you access in after that line of code after above line you will not found it there it will be deleted
Keep And Peek Methods
Peek And keep methods are used to read value without marking it for deletion after reading its value . So it is acutally helping us to retain its after its first read instead of deleting tempdata
With Peek Method We get the value of Tempdata Without Marking it For Deletion . In this method we access the Tempdata value using Peek Method That tells it to Hold Value and does not mark it for deletion
With Keep Method we hold the Value of Tempdata that was marked for Deletion after its first read . so it is using two different calls . First one is getting Tempdata Value then Second call is To Save Tempdata From Deletion
Quality Of Work is Valuable in Freelancing , Along with Dedication to work , Punctuality , Quick and Efficient Decision Making & Logical Thinking etc .
If we go for Comparing Designer With Web Developer To know which one is more valuable Then I think the Comparing them makes no sense . Its like comparing Michael Jordan To Lionel Messi . So we Should . They both are from sports but we can’t compare them Both have their own games and requires different view of thinking
Both Skills are Important Part of Project . There was Time When Functionality of Website was thing that was needed in website & Design of Website was not crucial But In Today’s World Along with Functionality of Website Design , User Usability are important aspects of website .
Only Making website to look pretty is not enough In Web Designing . It should be good according to User Usability Rules , It should be Responsive to different available Screens , Performance of Page loading is also included for web designer .
I Know Web Development project lasts long as compared to some of the Web Designing Projects That’s make more person attracted to them for more earning . But Creativity has No Money Bar . If you require a Unique Web Design or Logo etc Then That may cost you more than a Web Development Project . Developing Creative Gif’s for your Business / Ads Purposes are Very Creative & Demanded Things .
There are Number of Online Website including ThemeForest ,Templatemonster , colorlib, freshdesignweb etc . These Websites Contains number of Contributions From Developers .
Web Development is regarding to working / Logical Making of website So that consumes your more time . So Other Person is not hiring you , Client is hiring your Time So More Time is consumed in Web Development That’s Why Web Developers Sometime Earns More and This Thing attract most person to go in web development
All In All We Can both web development & Web Designing Have their own Importance . All That Maters is How good you are in your Skill & Quality of work .
Use Ajax & Jquery To Fetch & Populate News Feed . Make Ajax Call From Page Control Will go to specified PHP page through ajax call then fetch data in that PHP page and send data to callback to Ajax Call
Impact Of Domain Extension On Seo And Business Success
What Do you Think Does Domain Extensions Make Any Effect on SEO of Website . Everybody First tries to get '.COM' Extension and other extension like .info , .in etc are not liked so much .
What Do you think does domain extension put any effect on Optimization of Your Content on Search Engines .
There are neither any penalties Nor any preferences is given for Domain Extensions By google.com . All Domain Extensions are treated equally in agoogle.com web search.
However, Domain Extension do affect your search results for country specific searches. For example, a .co or .in domain will not rank as well as a .us website in a google.us web search. Also, a .co.uk site will rank better then a .us site in a google.co.uk search.
So In Above Cases Domain Extensions have an Impact on Search Result and SEO . But Otherwise there is no inbuilt Algorithm in Search Engines That Filter Or give preference to Some Specific Domain Extension
So if you are targeting a specific country or region, try to use the Domain Extension for that country or region. If not then the TLD does not make a difference
If .COM is Not Available Then What Should We Do ?
I think the best advice in think kind of situation is to search for a different domain name, especially if the .com is owned by a competitor in your space (you can also face some legal issues in future ).
Domain Extension Preferences :
If you are targeting your Product in Specific Country then Go for Domain Extension Specific to That Country Like if you are targeting United States The it good to choose .US Extension
If you are planning a Non-Profit Organisation Then you can choose .ORG
Other wise For All purposes Choose .COM Extension
As Joel Spolsky Said - .COM Extensions are Million Times Better Than Other Extensions
Twitter Bootstrap is very well known CSS framework today . It is easy to Use CSS framework that helps in Creating Responsive Web pages . I am going to give a Brief Overview of How Bootstrap Differentiate between Different Screen Sizes
Bootstrap includes a responsive, mobile first fluid grid system that appropriately scales up to 12 columns as the device or viewport size increases. It includes predefined classes for easy layout options, as well as powerful mixins for generating more semantic layouts.
Media queries
Bootstrap Uses Media Queries To Differentiate Between Screen Sizes . See Below What is code behind these media queries
/*================================================== = Bootstrap 3 Media Queries = ==================================================*/ /*========== Mobile First Method ==========*/ /* Custom, iPhone Retina */ @media only screen and (min-width : 320px){ } /* Extra Small Devices, Phones */ @media only screen and (min-width : 480px){ } /* Small Devices, Tablets */ @media only screen and (min-width : 768px){ } /* Medium Devices, Desktops */ @media only screen and (min-width : 992px){ } /* Large Devices, Wide Screens */ @media only screen and (min-width : 1200px){ } /*========== Non-Mobile First Method ==========*/ /* Large Devices, Wide Screens */ @media only screen and (max-width : 1200px){ } /* Medium Devices, Desktops */ @media only screen and (max-width : 992px){ } /* Small Devices, Tablets */ @media only screen and (max-width : 768px){ } /* Extra Small Devices, Phones */ @media only screen and (max-width : 480px){ } /* Custom, iPhone Retina */ @media only screen and (max-width : 320px){ }
POCO stands for "Plain Old CLR Object" Here CLR means Common Language Rutime that includes dotnet supported languages like C#, VB etc.
A Plain Old CLR Objects (POCO) is a class that doesn't depend on any framework-specific base class. It is like any other normal .Net class; that is why they are called “Plain Old CLR Objects”. These POCO entities support most of the same LINQ queries as Entity Object derived entities.
POCO allows you to write your own entity classes in a persistence ignorant fashion. POCO is also called as Persistence ignorant objects .
Persistence ignorance means that, as much as possible, anything in your code operating at the business logic layer or higher knows nothing about the actual design of the database, what database engine you're running, or how or when objects get retrieved from or persisted to the database. In the case of the EF, persistence ignorance is attained by working on POCO's and using LINQ to perform queries (i.e., not requiring the user to create any SQL queries to retrieve the desired objects).
There is still the need for you to “plug in” persistence and EF so that your POCO entities can be take from the database and updated back to the database. In order to do this, you will still need to either create an Entity Data Model using the Entity Framework Designer
Some programmers are blamed for Using Google and Stack Overflow for accomplishing their tasks and most people A novice coder might feel relying on Google or Stack Overflow is a bad thing But Believe Me Resources Says Opposite is True .
Brain Memory is most Valuable Disk Space and It Cannot Be Wasted For Storing Something That Can be Easily found in some clicks
IMPOSTER SYNDROME : Programmers often suffers from this syndrome . Hey, Don't fear its not a serious disease . Its a feeling one doesn’t deserve the honour they receive, or the doesn't deserve the skills or experience required for the work they are doing . But if they see quality that are providing then is rated as BEST . Being a good programmer they should accept as Computer / Even Super Computers can't kept everything in RAM ( Brain IN Programmers ) and they require HDD / Other Host for storing other info
Resources and Stats Says Experience or good programmers use google a lot , Even Some Surveys say Experienced Programmers Use Google More than Begineers and Google is getting an important place in Programmers Software Development Kit
If Programmers are searching google for optimal solutions of their problem then one suggestion is they should not copy and paste the code samples found they should compare them their own solution and evaluate the optimal solutions If you have any doubts regarding the article Comments are most welcomed Below . Don't Forget to Like Us on Social Media , Subscribe Us For Latest Articles From Us and Share Us With Others
The following optimizations combined are the reason AMP pages are so fast they appear to load instantly: Allow only asynchronous scripts
JavaScript is powerful, it can modify just about every aspect of the page, but it can also block DOM construction and delay page rendering (see also Adding interactivity with JavaScript). To keep JavaScript from delaying page rendering, AMP allows only asynchronous JavaScript.
AMP pages can’t include any author-written JavaScript. Instead of using JavaScript, interactive page features are handled in custom AMP elements. The custom AMP elements may have JavaScript under the hood, but they’re carefully designed to make sure they don’t cause performance degradation.
While third-party JS is allowed in iframes, it cannot block rendering. For example, if third-party JS uses the super-bad-for-performance document.write API, it does not block rendering the main page.
Size all resources statically
External resources such as images, ads or iframes must state their size in the HTML so that AMP can determine each element’s size and position before resources are downloaded. AMP loads the layout of the page without waiting for any resources to download.
AMP uncouples document layout from resource layout. Only one HTTP request is needed to layout the entire doc (+fonts). Since AMP is optimized to avoid expensive style recalculations and layouts in the browser, there won’t be any re-layout when resources load.
Don’t let extension mechanisms block rendering
AMP doesn’t let extension mechanisms block page rendering. AMP supports extensions for things like lightboxes, instagram embeds, tweets, etc. While these require additional HTTP requests, those requests do not block page layout and rendering.
Any page that uses a custom script must tell the AMP system that it will eventually have a custom tag. For example, the amp-iframe script tells the system that there will be an amp-iframe tag. AMP creates the iframe box before it even knows what it will include:
Keep all third-party JavaScript out of the critical path
Third-party JS likes to use synchronous JS loading. They also like to document.write more sync scripts. For example, if you have five ads on your page, and each of them cause three synchronous loads, each with a 1 second latency connection, you’re in 18 seconds of load time just for JS loading.
AMP pages allow third-party JavaScript but only in sandboxed iframes. By restricting them to iframes, they can’t block the execution of the main page. Even if they trigger multiple style re-calculations, their tiny iframes have very little DOM.
The time it takes to do style-recalculations and layouts are restricted by DOM size, so the iframe recalculations are very fast compared to a recalculating styles and layout for the page.
All CSS must be inline and size-bound
CSS blocks all rendering, it blocks page load, and it tends to get bloated. In AMP HTML pages, only inline styles are allowed. This removes 1 or often more HTTP requests from the critical rendering path compared to most web pages.
Also, the inline style sheet has a maximum size of 50 kilobytes. While this size is big enough for very sophisticated pages, it still requires the page author to practice good CSS hygiene.
Font triggering must be efficient
Web fonts are super large, so web font optimization is crucial to performance. On a typical page that has a few sync scripts and a few external style sheets, the browser waits and waits to start downloading these huge fonts until all this happens.
The AMP system declares zero HTTP requests until fonts start downloading. This is only possible because all JS in AMP has the async attribute and only inline style sheets are allowed; there’s no HTTP requests blocking the browser from downloading fonts.
Minimize style recalculations
Each time you measure something, it triggers style recalculations which are expensive because the browser has to layout the entire page. In AMP pages, all DOM reads happen first before all the writes. This ensures there’s the max of one recalc of styles per frame.
Learn more about impact of style and layout recalculations on rendering performance.
Only run GPU-accelerated animations
The only way to have fast optimizations is to run them on the GPU. GPU knows about layers, it knows how to perform some things on these layers, it can move them, it can fade them, but it can’t update the page layout; it will hand that task over to the browser, and that’s not good.
The rules for animation-related CSS ensure that animations can be GPU-accelerated. Specifically, AMP only allows animating and transitioning on transform and opacity so that page layout isn’t required. Learn more about using transform and opacity for animation changes.
Prioritize resource loading
AMP controls all resource downloads: it prioritizes resource loading, loading only what’s needed, and prefetches lazy-loaded resources.
When AMP downloads resources, it optimizes downloads so that the currently most important resources are downloaded first. Images and ads are only downloaded if they are likely to be seen by the user, above the fold, or if the user is likely to quickly scroll to them.
AMP also prefetches lazy-loaded resources. Resources are loaded as late as possible, but prefetched as early as possible. That way things load very fast but CPU is only used when resources are actually shown to users.
Load pages in an instant
The new preconnect API is used heavily to ensure HTTP requests are as fast as possible when they are made. With this, a page can be rendered before the user explicitly states they’d like to navigate to it; the page might already be available by the time the user actually selects it, leading to instant loading.
While prerendering can be applied to all web content, it can also use up a lot of bandwidth and CPU. AMP is optimized to reduce both of these factors. Prerendering only downloads resources above the fold and prerendering doesn’t render things that might be expensive in terms of CPU.
When AMP documents get prerendered for instant loading, only resources above the fold are actually downloaded. When AMP documents get prerendered for instant loading, resources that might use a lot of CPU (like third-party iframes) do not get downloaded.
AMP HTML is a way to build web pages for static content that render with reliable, fast performance. It is our attempt at fixing what many perceive as painfully slow page load times – especially when reading content on the mobile web.
AMP HTML is entirely built on existing web technologies. It achieves reliable performance by restricting some parts of HTML, CSS and JavaScript. These restrictions are enforced with a validator that ships with AMP HTML. To make up for those limitations AMP HTML defines a set of custom elements for rich content beyond basic HTML. Learn more about how AMP speeds up performance.
How does AMP HTML work?
AMP HTML works by including the AMP JS library and adding a bit of boilerplate to a web page, so that it meets the AMP HTML Specification. The simplest AMP HTML file looks like this:
The AMP JS library provides builtin AMP Components, manages the loading of external resources, and ensures a reliably fast time-to-paint.
The AMP Validator
The AMP Validator allows a web developer to easily identify if the web page doesn't meet the AMP HTML specification.
Adding "#development=1" to the URL of the page instructs the AMP Runtime to run a series of assertions confirming the page's markup meets the AMP HTML Specification. Validation errors are logged to the browser's console when the page is rendered, allowing web developers to easily see how complex changes in web code might impact performance and user experience.
It also allows apps that integrate web content to validate the web page against the specification. This allows an app to make sure the page is fast and mobile-friendly, as pages adhering to the AMP HTML specification are reliably fast.
AMP HTML Components are a series of extended custom elements that supplement or replace functionality of core HTML5 elements to allow the runtime to ensure it is solely responsible for loading external assets and to provide for shared best practices in implementation.
We push a new release of AMP to all AMP pages every week on Thursday. The more detailed schedule is as follows:
Every Thursday we cut a green release from our master branch.
This is then pushed to users of AMP who opted into the AMP Dev Channel.
On Monday we check error rates for opt-in users and bug reports and if everything looks fine, we push this new release to 1% of AMP pages.
We then continue to monitor error rates and bug reports throughout the week.
On Thursday the "Dev Channel" release from last Thursday is then pushed to all users.
You can always follow the current release state of AMP on our releases page. The release used by most users is marked asLatest release and the current Dev Channel release is marked as Pre-release.
AMP Dev Channel
AMP Dev Channel is a way to opt a browser into using a newer version of the AMP JS libraries.
This release may be less stable and it may contain features not available to all users. Opt into this option if you'd like to help test new versions of AMP, report bugs or build documents that require a new feature that is not yet available to everyone.
Opting into Dev Channel is great to:
test and play with new features not yet available to all users.
use in Q&A to ensure that your site is compatible with the next version of AMP.
If you find an issue that appears to only occur in the Dev Channel version of AMP, please file an issue with a description of the problem. Please always include a URL to a page that reproduces the issue.
To opt your browser into the AMP Dev Channel, go to the AMP experiments page and activate the "AMP Dev Channel" experiment. Please subscribe to our low-volume announcements mailing list to get notified about important/breaking changes about AMP.
Further Reading
If you are creating AMP pages, check out the docs on ampproject.org.
These docs are public and open-source: https://github.com/ampproject/docs/. See something that's missing from the docs, or that could be worded better? Create an issue and we will do our best to respond quickly.
