Mike Hartington

Recently a Pull Request from Matthieu Riegler came to the Angular repo that wanted to mark the HTTPClientModule and similar modules as deprecated. Overall it seems the idea has received positive traction, though in Matthieu’s tweet about the PR, there was a comment in there that did stand out to me. I think I need an example before I decide whether I need pitchforks or not. So let’s make a quick example to show this person what this PR does and how it can impact non-standalone apps.

It seems that the wider tech community is very prone to having heated arguments regarding a particular piece of technology. Hybrid vs Native, Tailwind vs CSS, Web Components vs Framework Components. They normally start off with a valid piece of criticism, but inevitably become a pissing contest. If some sort of argument doesn’t happen on Twitter, it can feel like a quiet week! Tribalism in Tech People in tech often feel passionate about their tools.

To all the attendees who spent their money on Modern Frontends Live: I’m sorry that you had to experience one of the most unpleasant conferences I’ve been a part of. To the speakers (new and seasoned pros) who were told they’d have their accommodations covered only to have that rug pulled out from under them: you deserve better and I hope there is a way to get something back. To the sponsors who spent their companies’ money to attend an event which promised over 3000 attendees and more virtually: We know better now, but I hope you do not face any push back from your leaders regarding future events.

Something I’ve heard from a few people in the Ionic community is that the miss the updates speed from Ionic App scripts when updating CSS. They often ask “how can I use app scripts with V5?” or “Why is Angular CLI so much slower?”. Well it’s a bit more involved that just those blanketed statements, but it is possible wit the Angular CLI flag --hmr. App Scripts and Styles For those who don’t know, App Scripts was a project we made at Ionic that was essentially the Angular CLI, but before the Angular CLI was built.

I was digging into ESLint tonight to see if there was a Language Service plugin available for TypeScript. In doing so, I realized I had no clue how to setup ESLint, especially considering the changes with regard to @typescript-eslint. Last time I used ESLint, I was still writing AngularJS and ES6 was still far away. So, somethings have changed. Installing First, we’ll want to install the necessary packages, ESLint, the parser, and the plugin itself.

These days it seems like everyone is using VSCode as their main editor, and with good reasons. VScode offers a lot of cool features, and if you’re using TypeScript, you get great support out of the box. But, I’m a vim person, and more specifically, I use Neovim. Since, I write mostly TypeScript, I needed something that offered all the feature of VSCode, but for Noevim. So I created nvim-typescript.

Recently, I’ve been diving into the new tooling setup being worked on for upcoming ionic/[email protected]. Since we’ve moved all of our tooling over to the Angular CLI, we get to take advantage of new features, like Angular’s Schematics. Schematics is a pipeline for building out new files/features in an app. What’s even more impressive, is that schematics itself can be used in a non-angular project. In theory, you could have a Vue or P/React project, and it could also use schematics, though without some utility libs that exist for Angular.

In hybrid apps, when we want to add support for different languages, we tend to rely on JavaScript libraries to make this possible. This is perfect when we need to deploy a PWA, but when it comes to the App Store, we then have a different challenge. How do we tell the App Store that we support different languages as well? How iOS Checks this For native iOS project, the process is actually quite similar to how we manage localization in web-based apps.

If you jumped from Ionic 1 to Ionic 2 when it was first released, a new thing that was added was this concept of $colors. Something that looks like this : $colors: ( primary: #488aff, secondary: #32db64, danger: #f53d3d, light: #f4f4f4, dark: #222 ); This was a big change from how we did styles in Ionic 1, where all of our theme colors were defined upfront: $light: #fff !default; $stable: #f8f8f8 !

Every year Apple releases a new iPhone and a new iOS version to match. For the history of the iPhone, any changes that come with these new devices tend to be very small. Design changes in iOS7? Not a huge deal, as they’re fairly easy to design for, especially in a hybrid app context. This year however, Apple has introduce it’s most drastic change in iPhone history. Introducing… the Notch