These are valid points, taken to the extreme we will have apps that cannot be supported.

In short term, we already have SQL/reports being automated. Lovable etc is experimenting with generating user interfaces from prompts, soon we will have complete working apps from a prompt. Why not have one core that you can expand via a prompt?

I am currently studying and depending heavily on Anki, its been amazing to use Claude Code to add new functionality on the fly. Its a holy mess of inconsistent/broken UX but it so clearly gives me value over the core version. Sometimes it breaks, but CC can usually fix it within a prompt or two.

Will we stop using web browsers as we understand them today in the next few decades in favor of only interacting with agents? Maybe.

Been building a project in the side to help my studies and it usually implement new complete apps from one prompt, working on the first try

GNOME was started on 15 August 1997 by Miguel de Icaza and Federico Mena as a free software project to develop a desktop environment and applications for it. It was founded in part because the K Desktop Environment, which was growing in popularity, relied on the Qt widget toolkit which used a proprietary software license until version 2.0 (June 1999). In place of Qt, GTK (GNOME Toolkit, at that time called GIMP Toolkit) was chosen as the base of GNOME. GTK is licensed under the GNU Lesser General Public License (LGPL), a free software license that allows software linking to it to use a much wider set of licenses, including proprietary software licenses. GNOME itself is licensed under the LGPL for its libraries and the GNU General Public License (GPL) for its applications.

Taking 100000 IU per day for months/years is not necessarily toxic, especially when reducing calcium intake.

If you're going to do high doses, stay away from anything with significant amount of calcium in your food (dairy, nuts etc)

Come join SparkMeter’s Systems team and help increase electricity access in developing countries. As an Infrastructure Engineer with an automation focus, you’ll build the tools and architecture that will allow us to expand our affordable smart metering systems to new microgrid and central grid utilities.

At SparkMeter, we believe in embracing automation, and our team takes every opportunity to reduce manual work or remove workarounds using tools like Fabric, Chef, and Docker. You’ll officially own automation for the Systems team, creating new tools and taking over the maintenance of existing tools that others across the organization will use every day. This will include improving automation for our software release process, automating the (now largely manual) provisioning of the Linux base stations at the core of our smart metering system, and generally building and maintaining the tools that help make it easy for us to efficiently manage a growing herd of servers and devices.

SparkMeter’s core value is opportunity: the opportunity for underserved communities to achieve great things. That's why our mission is to increase access to electricity in underserved communities - it is electricity and the services derived from it that unlock and create those opportunities. This value is reflected in our hiring ethos: we believe that the strongest teams have diverse backgrounds. Our approach to hiring has been validated by academic and industry studies that show that workforce diversity improves team and business performance. (It has also been validated by the quality of the team we’ve assembled so far!) We encourage applications from members of groups currently underrepresented in software engineering.

You can read the complete description for this role, including requirements and how to apply, at http://www.sparkmeter.io/en/jobs/infrastructureengineeraf/. Thanks!

Three of the major phone operators (Vivo, Claro, TIM) implemented the ban, while the fourth (Oi), did not. The CEO of Vivo, one of the major phone operators, came out a couple of months ago saying that WhatsApp is "piracy", since they are not affected by the same regulations as the normal phone operator.[1]

[1]: http://www1.folha.uol.com.br/mercado/2015/08/1666187-whatsap... (portuguese)

[1]: http://www.ncbi.nlm.nih.gov/pubmed/22213293

Combustion taxes makes sense if it's only used by transportation means, but that is not the case of electric energy. You could tax at the plug/socket level, but that's probably something that will be easy to tamper with.

There could always be something fancy such as remotely tracking the vehicles, but that will open a can of privacy worms.

The only viable option is to do tolls. Not necessarily representative of actual use, but a good enough approximation of use.