AI
A couple of days ago, I stumbled upon an interesting article on TechDirt about how many websites have started to wall themselves off from the open internet in order to prevent AI bots from scraping their content. I have thoughts about it.
It seems like every browser is currently jumping on the band wagon and trying to “enhance” the browsing experience with AI. Vivaldi isn’t and that’s refreshing.
Such a lawsuit has the potential to shape the future of online publishing as well as search. It will be interesting to see how it develops.
Executives have started boasting about how AI is going to take a lot of jobs and leave people jobless. It seems they have lost their humanity.
A couple of days ago, I had a conversation with my programmer dad and we thought it would be fun to make fun of old C++ code.
AI note-takers are starting to become a regular fixture in a lot of online meetings allowing people to focus on their work instead of attending meetings.
Fortunately, I’m not the only one worried about AI leading to the collapse of the online publishing industry. The CEO of Cloudflare has just introduced a new feature that should help prevent that.
If I had to rely on any of my blogs for income, I would be panicking about now.
AI replacing traditional search engines promises efficiency, but concerns about reliability and content creators’ impacts loom large.
Yet another major tech company using AI as an excuse to significantly increase the price of their subscription services…
A few days ago, an article was published on Ars Technica that, as a creative person, I thought I should share here. As the title implies, it is about protecting human creativity from the onslaught of AI.
Since Angular’s new signals API became stable with the release of version 17, I have been a little confused about when to use them versus standard class variables in components and services. So I asked AI and this is what it told me.
