I hope they're using IPv6. If it's IPv4 I'm going to exhaust the address space.

From first hand experience, I can state that FUD like "the infrastructure will never be ready for mass adoption of EVs" is blatantly false.

For 5 years I charged my first EV at home using the charger it came with, which plugged directly into a standard US 120V socket. No significant increase to my electric bill. No need to install a special ("Level 2") charger. I logged tens of thousands of miles driving to and from work, stores, etc.

Some more modern EVs can even store power and return it to the grid when needed, drawing power when it is plentiful and returning it to the grid when it is scarce. This helps _increase_ grid stability, not threaten it.

If you see statements about infrastructure not being ready for EVs, you should immediately dismiss the author as either gaslighting or hallucinating.

Could they have chosen a more (in)appropriate name, given this action? Sigh.

For a (near) production 2-person vehicle, it has several notable accomplishments. Hats off to the engineering team.
* Record(?) Coefficient of Drag of 0.15
* 10 miles / kWh efficiency, a dramatic increase from the current EV efficiency leaders (in the US, at least)
* Self-powered for 30-40 miles per day

I think the onboard solar panels are compelling since they can power the average commute without plugging in. Not everyone has convenient access to a charger, so this opens up a new market of EV buyers.

It will have a NACS charging port, so if you have your own solar array you can keep it inside and still power it cleanly.

Otherwise it looks like a compelling, unique vehicle for daily use, and even road trips based on the video.

The estimated Cd is supposed to be in the 0.13 to 0.15 range, better than any other production vehicle. The enclosed wheels are supposed to be a significant contributing factor, according to this article: https://electrek.co/2023/07/12...

I believe Aptera folks are predicting 30-40 miles per day of added range if left in the sun (thanks to the vehicle's predicted efficiency). Since for many people that covers their daily commuting needs, some buyers might almost never need to plug in for a charge.

Aptera (https://aptera.us/) is nearly in production with an efficient EV. The vehicle includes solar panel options, but they don't completely cover it. I wonder if this paint technology could further increase the daily range added from the sun beyond the 40 miles they're currently quoting?

Info and videos: https://aptera.us/

It is always great to see new libraries and frameworks to keep Java relevant in a world where web-based applications are the norm.

I think some other interesting options in this space are Flavour and TeaVM, which let you code your front-end in Java too. To me, that is full-stack Java development, when you can code the front-end and back-end in Java, and still deploy a lightweight, modern web app.

Flavour: https://frequal.com/FlavourPlu...

Flavourcast podcast (created using a Flavour app): https://castini.frequal.com/ca...

TeaVM/Flavour introduction article from Java magazine: https://blogs.oracle.com/javam...

Clean-room alternatives (like Wordii https://frequal.com/wordii/ ) seem to be "the sincerest form of flattery", as they say.

What really seems to bother Wardle are people who simply downloaded and repackaged his code to turn a profit. That would be frustrating. Especially since fighting it would take money, which he didn't have since Wordle was free.

For the millions of developers still using Java and maven to develop services, TeaVM fills a vital need -- a Java-friendly front-end tool for developing modern browser apps.

* Share models (POJOs) between front- and back-ends.
* Refactorings apply top-to-bottom. No more having to remind the front-end team you just changed the service interface Refactor the POJO, and the references client-side get updated too, automatically!
* TeaVM's Flavour toolkit includes automatic marshaling and unmarshaling to/from JSON, so invoking RESTful services is as easy as calling a method.

TeaVM does away with the need for a JVM in the browser, so it neatly avoids the problems with startup time and "gray rectangles" that caused pobelms back in the applet days.

It compiles Java bytecode into compact, quick-downloading JavaScript. No JRE, JVM, or Java Plugin required. Just a standard browser with JavaScript enabled.

The fact that developing with the official Java UI technologies is becoming more challenging is one of the exciting things about TeaVM. It compiles to HTML and JS, which deploy like any other website. Any web API is available. And it checks all of the boxes you want from a web development tool:

* fast
* produces compact JS
* produces great Lighthouse scores
* works great with the latest web tech (Flexbox, SPA, PWA, etc.)

Definitely give it a shot, the "Getting Started" instructions will have you up and running with 2 easy steps:

http://teavm.org/docs/intro/ge...

TeaVM works with web technologies, it doesn't attempt to create an alternate UI.
* HTML for content
* Styling via CSS
* DOM access
* Web API access

Just the logic is implemented in Java. Or another JVM langauge, if that is your preference. The force multiplier is coding front-end and back-end logic in the same langauge. IDE refactorings apply to the entire project. And SAST/DAST tools can be applied everywhere, a big when for larger projects.

Before you knock it, be sure to try it. It is just 2 quick steps: http://teavm.org/docs/intro/ge...

TeaVM doesn't require Java to be installed on any user's system. It turns Java into JavaScript so it runs in browsers without any Java plugin or JRE!

Even better, the JavaScript it produces is often smaller that that produced by other tools (like GWT or React). So it's even faster to start up and execute -- an improved experience for users over most web technologies.

So if you want to avoid Java deployment headaches, and make fast-starting, user-pleasing apps, definitely switch from legacy Java tech to TeaVM! ( http://teavm.org/ )