martinskou

Go fork with new throw operator error handling.

Idea: - Local data so I can access my CL without network. - Templates. Start CL from predefined template. - History. Which templates completed when. - Hierarchical items. - Share or export/import. - Logic engine. Some items might not be relevant in some scenarios.

Getting support for something like this at Microsoft is impossible. They don't care at all. They will reply with standard responses from some supporter without any access or knowledge of the inner working of the system.

I do understand the ideer of letting a large IT organisation handle you email. Working email is a high priority, if not Microsoft or Google can make it work, who can?

But as soon as there are any problems a little out of the ordinary, its clear that choosing something like Microsoft or Google is a really bad idear. It's not possible communicate with anyone who know anything.

As more and more are moving their solutions to Microsoft and Google, they will be in a position to strangle any smaller providers.

They are a thread to the free internet!

Yes, lost opportunity. Like COVID which should have been named KungFlu.

If only <frame> was'nt depricated. /s

I don’t get it. IKEA is much scarier than that game!

All Ripe assigned AS, IP and routing in Russia should be disabled until Russia has removed its forces from Ukraine.

Statis is nice. But what about intra-site search? And form to email? Is there a best practice for this?

Didn’t JWST use some kind of grivitational breaking to stop at the LGPoint? A manned mission would require much more fuel to shorten the time of the trip and fuel for returning.

I host quite a lot and the size is around 40-80 MB for presentation sites. Shops are around 100-300 MB. So a nice fit for SQLite. Would be a really nice options, but it should be part of the normal WP distribution.

By far the easiest way to quit : Close you credit card, and order a new...

Looks nice.

Now if we just had a good Markup Language for webdesign...

My bet is that you only chance is making it a family history site. And by that I mean that each generation of your future family must contribute their story and at the same time update the site to a modern solution.

The base layer could be text files and image, even though jpeg might not exists in 200 year some other format does.

But you must leave it up to you grandchildren to update the solution to modern formats. Maybe set some inheritance up to support this.