Sad. A great idea ruined by poor business practices.

I think it had more to do with the reality of the market. Solar panels have become incredibly cheap and that's because they are mass produced and standardized. Everything in the manufacturing process has been optimized. Now it is technically of course possible to make them other form factors, but artisinal solar panels are simply so much more expensive and cannot compete in any meaningful way with regular panels.

It was a bad idea from the beginning, technically and economically it sucked, the only possible utility was areas with strict heritage constraints which forbade normal rooftop PV.

A bad idea ruined by poor business practices. Like, it's very hard to see how it could ever compete economically with normal solar panels.

What a ridiculous statement. People get all sorts of roofs with all sorts of trade offs. Looks is absolutely one of them. Also, any product that gets popular eventually gets highly optimized manufacturing pipelines bringing the cost down.

It doesn't need to compete with normal panels on only one metric. People will accept longer payoff times for aesthetics or durability if the ratio is right. Also, who really cares about Tesla at this point? Other companies are now producing these panels.

Like everything Musk, it died because of his poor business practices and his politics. The only thing he seems to excel at these days is extracting government money.

The GOAT.

I am a little confused. Is this still JSON? Is it “binary“ JSON?

It’s neither!

Sample output:

'fdiscovered,aextreme,7danger,6+1A+16;6level_range,b:QThe Heap ,d'th

Human unreadable, ascii output. Line up and get yours today!

it's not really possible to stay human readable and get the compression levels and random access properties I was going for. But it is as human tooling friendly as possible given the constraints.

>it's not really possible

I find it obvious that your first attempt failed. Try again, you have not even remotely failed enough if you are making the argument that this is kinda readable. Yes, ascii words are easy to pick out, you didn’t do that, you did the part that makes it all harder.

Holy Deep Dive, Batman. This has to be the most mathematically heavy design for creating TUIs ever conceived. The name makes sense.

But does it blend? (Actually useable?)

CLI is an API, so I decided to treat it as such and created Jargon (for Crystal). Define CLI in JSON Schema, get argument parsing, validation, help text, and shell completions for free. Supports nested options with dot notation, subcommands, config file loading and merging, env vars, XDG base dir compliant, and JSON to stdin.

Honestly if it were not for my extensive Ruby background that I have now been able to carry over to Crystal, I probably would have dived into Guile.

(I have been enjoying Elixir too, but at the end of the day it doesn’t quite sit right with me — just feels a bit clunky. Gleam seems an attractive alternative though. The BEAM rocks, but it is a heavy dependency that doesn’t fit all distribution needs.)

FOR loops?

YAML has a merge key <<:, which might be helpful.

The merge key is a clever little trick, but it depends of the special hash key, so lists can’t be merged.

Syntax does matter, which is why YAML matters — even if imperfect.

Merges and anchors are some of the least maintaineable and most error-prone config i've seen.

Doesn't help every yaml parser has their own opinion on what a merge or an anchor should do, exactly.

So brilliant that we’re all still using ASCII!†

† With an occasional UNICODE flourish.

I agree. Separate keys would be better.

I wonder if hat word processors would have used a separate Enter (or Go!) for?

I hope there are no major problems to commercialization. This will be huge!