My computer programming teacher had always told me that 10% of our time is spent developing 90% of our application, and the other 90% of our time finishing the last 10% of our project. Even with a good project plan and a concept that makes logical sense, most of our time will be consumed with fixing errors. Moreover, with JavaScript, our application can run without obvious errors preventing it from being run, so we have to employ several techniques to make sure everything is running smoothly.
With the upgrade to React Native 61 came the prospect of substantially improving performance of our Android app. How? Through the use of Hermes, Facebook’s new JavaScript engine. To say that we were excited is an understatement. And with that excitement came curiosity: How is this new JavaScript engine achieving performance boosts?
The TrackJS team is hard at work polishing the product to make it even better at tracking JavaScript Errors. Here’s what we shipped in January.
It’s a new year and TrackJS has a new look. It’s smaller, it’s simpler, and it feels friendly–just like TrackJS. These minor refinements to our brand do a better job at emphasizing what were best at: easy to use and user-focused. The colors are brighter and clearer, the fonts are more refined, and there is just less noise.
My computer programming teacher had always told me that 10% of our time is spent developing 90% of our application, and the other 90% of our time finishing the last 10% of our project. Even with a good project plan and a concept that makes logical sense, most of our time will be consumed with fixing errors. Moreover, with JavaScript, our application can run without obvious errors preventing it from being run, so we have to employ several techniques to make sure everything is running smoothly.
It's Friday afternoon and you decide to check on your web logs one last time before you go out for the weekend. Since you've deployed recently, you want to make sure everything is going smoothly. You open your tool and suddenly you find your screen flooded with TypeErrors. Does this sound familiar? JavaScript TypeError is one of the most common browser errors because it wraps a number of different situations, each of which needs to be handled separately.
Hi there stroopwafel fans As we’re looking forward to publishing more Ruby, Elixir, and JavaScript posts in the coming 2020, we decided to take a look back at the blog posts that you gave the most hearts on Twitter, reads on the blog, and that we got the most appreciation for in 2019.
Ignoring noisy and external errors is important to understanding the health of your client-side applications. Third-party scripts, user extensions, content crawlers, and non-impactful errors create lots of noise in web operations. With TrackJS Ignore Rules, you can filter out this noise and and have a clear view of your web application quality.
Hello again! Welcome to the finalé of a two-part series of posts on errors in JavaScript. Last time, we took a look into the history of errors in JavaScript — how JavaScript shipped without runtime exceptions, how error handling mechanisms were later added both to the fledgeling web browsers of the day and to the ECMAScript spec, and how they future efforts to standardise these features would be connected to the politics of the browser wars of the late 90’s and 2000’s.
