In a move that caught everyone by surprise, Google recently announced the sale of Google Domains to Squarespace. To many, this strategic realignment came out of left field, providing a glaring clue about the shape of Google’s new vision. The seismic shift to prioritise artificial intelligence (AI) has raised questions about the fate of Firebase, a Google-owned platform popular among developers.
What will come of Firebase?
Under Sundar Pichai’s leadership, Google has transformed from a mobile-first to an AI-first company. If Google Domains, a more traditional web offering, no longer fits within the framework of this AI-focused vision, where does Firebase fit in?
In Aurelia 1, you could access the controller and ViewModel of an element using au.controller and in Aurelia 2, it’s more of the same (except the properties are different). Here is how you get the controller and ViewModel of an element in Aurelia 2.
import { Controller, ICustomElementViewModel } from "aurelia"; // Define an interface for Aurelia element export interface AuElement extends Element { $au: { "au:resource:custom-element": Controller; }; } /\*\* \* This function receives an element and extracts the Aurelia controller associated with it. \* @param {Element} element - The target element \* @returns {Controller|null} - The controller or null if it does not exist \*/ export function getElementController(element: Element): Controller | null { const auElement = element as AuElement; if (!auElement.$au) { return null; } return auElement.$au['au:resource:custom-element']; } /\*\* \* This function gets the View Model associated with a given element. \* @param {Element} element - The target element \* @returns {T|null} - The View Model or null if it does not exist \*/ export function getElementViewModel(element: Element): T | null { const controller = getElementController(element); return controller ? controller.viewModel as T : null; }
Recently while using the Material Components Web components in an Aurelia 2 application with Sass, I encountered an annoying issue where a warning would appear in my app. The warning appears to be harmless, but it’s annoying.
The error appears as:
Module Warning (from ./node_modules/sass-loader/dist/cjs.js): both $level and $color are required; received $level: ‘0’, $color: "
To fix it in Webpack, you can use the warningsFilter argument for stats to filter it out:
One of the most annoying things as a developer setting up a Mac is that files with a dot are hidden by default. Here is how to set them always to be visible:
Open Terminal (Command + Shift and type Terminal) Run defaults write http://com.apple.Finder AppleShowAllFiles true You can toggle them in Finder by using Command + Shift + . but having them show by default is a lot nicer.
Well, well, well, what do we have here? The guardians of Stack Overflow, those volunteer moderators who’ve turned the site into their personal fiefdom, are having a tantrum. As of June 5th, 2023, they’ve gone on a historic general moderation strike, joined by over 850 contributors and users.
Their beef? Stack Overflow, Inc. isn’t giving them the attention they feel they deserve regarding being able to police AI-generated answers. To which I say, “Welcome to the club, mates.”
Hold the phone, everyone. Martha Stewart, yes, that Martha Stewart has decided to grace us with her hot take on remote work. Spoiler alert: she’s not a fan. Apparently, she believes you can’t possibly get everything done working part-time in the office and part-time from home. Martha, I hate to break it to you, but the rest of us aren’t trying to juggle a cooking show, a magazine, and a bedding line — we’re just trying to pay our mortgages and buy the occasional carton of eggs (thanks, inflation).
It’s been a while since we’ve seen something completely new from Apple, and after years of speculation that Apple would launch a headset of some kind, it has finally been announced (one of the worst kept secrets ever because we knew it was coming).
The Vision Pro is undeniably impressive. With 4K displays, infrared cameras, and LED illuminators, not to mention it runs on Apple’s M2 chip and a new mixed-reality-specific R1 chip, the specs are nothing short of impressive (as expected).
The Metaverse, a term coined from Neal Stephenson’s 1992 techno-dystopian novel “Snow Crash,” has been a topic of discussion in the tech industry for years. It was envisioned as a new frontier, a virtual reality space where users could interact in a simulated universe. Meta, formerly known as Facebook, aimed to lead this virtual revolution by building a future where work and social interactions could be conducted from anywhere in an immersive 3D world.
It’s 2023, and a war rages on. On one side are businesses and mega-corporations, and on the other are the workers. While everyone argues about the future of work and the benefits of having employees back in the office (even in a hybrid capacity), the world around us is figuratively burning.
Despite inflation peaking in most countries, it remains quite high. In Australia, the CPI rose to 6.8 per cent in March. While this is not as high as the 30-year record set at the end of 2022, when it hit 8.4 per cent, it is still stubbornly high. To put this into context, the Reserve Bank of Australia has a target of 2 to 3 per cent, which we are far from achieving. The current cash rate is 3.8%, combined with a rental crisis and inflated house prices.
Reading the latest update from StackOverflow’s CEO, I can’t help but feel a sense of disconnect. StackOverflow and the broader StackExchange network are facing a tidal wave of change with the rise of AI, and it seems like they’re just treading water.
For many of us, AI tools like ChatGPT have become go-to resources. They’re efficient, user-friendly, and, most importantly, not judgemental. On the other hand, StackOverflow has become notorious for its hostile environment, particularly towards newcomers. It’s as if you need to pass a test of fire to ask a question, and that’s if you’re brave enough to ask in the first place.