Is that per person or for the 5 people? No if per person if the minimum commit is 30 days (300/Night is not too bad, but for a week to 10 days at a time, not the month). If for all 5 then yes, it might make sense for retreats.

I DO wish there a business focused resort with meeting rooms, workspaces, good connectivity and AV, etc. Suites with meeting space for smaller groups/after hours meetings and some amenities for after hours (eg pool, golf, gym, etc).

EDIT: My house is paid for, so I am not really the target demographic :)

Price is for one people. But I have formulas for week-ends or per week which is cheaper. Week-end is €990 and week is €2900.

Thanks anyway for the comment. Do not hesitate to email me for further enquiries.

It could be that Gen 3 shipping late 2026 is a concession that R2 might be delayed until then.

Personally I think they will ship R2 Gen 2 vehicles to the early adopters that are less concerned with ADAS.

My R2 reservation is very late (I had to redo it for reasons) so I probably won't be able to order one until it's available anyways.

sqlite is just a library (in C)

A few projects:

  * https://github.com/rqlite/rqlite Distributed, fault tolerant cluster
  * https://litestream.io/ Replication to S3 (or compatible) - more disaster recovery than fail over
  * https://fly.io/docs/litefs/ Same Author as litestream).  Distributed replication.  Requires writes to be redirected to the primary.

I am debating Postgres vs sqlite (probably with litestream) for a project right now.

And other than HW redundancy, I can get pretty far by scaling vertically on a single box. And for my app, I could probably (and my users!) live with some occasional downtime (as long as the data is replicated/backed up).

If I get 20-50K users, it'll be a successful venture so I don't need much these days and it will be cheaper and easier to run as well.

rqlite creator here, happy to answer any questions.

Yeah if you're comfortable scaling vertically and potentially a little downtime. Sqlite massively simplifies your ops, backups litestream is fantastic.

It's also as you mentioned dirt cheap (VPS or a hetzner box).

When we were at Spirit Halloween last week I saw some building blocks like drops and swinging mechanisms for DIY.

Just think of it as evolution in action.

Did they mean route as in path to a solution? Or root as the source? Seems odd.

“The root of the problem” is a more usual usage, but is just as readily applied (ha get it) as “the root of the solution”, especially when a dental pun can be bonded (puns are swell) to the headline (I can’t think of a way to pun on gumline here).

I found the phrasing really difficult to read and understand, even though I got the pun, so you’re not alone in that.

Root as in seed [crystal], as in nucleation point is what I would surmise.

Dentistry pun? Root as in the root of a tooth?

According to the Programming Guide, it supports aliases for imports

"In case of conflict or convenience, you can give modules an alias as well."

This isn't about conflict, it's about how humans read it.

Let's say I have two modules, "telnet" and "ssh", and both have a "connect" function. When I read "import connect, (long list of other imports here)" I don't know which connect it is, and I might form the wrong mental connection, which I then have to revise when I start to read the module name.

There's a youtube video from one of the paper's authors and interstellar is probably a stretch but 1000+ AU is far beyond what we can achieve today so not bad.

If you have to ask.... :)

(other people's) previous guesstimates were 500k - 1M. It does look like you can order it partially provisioned (compute wise I'm guessing) and expand later.

I don't know about anyone else, but I pronounce midget and widget exactly the same. eg... soft I sound for the 'i' and a j sound for the 'g'.

So for me, the clarification on the name makes it less understandable :)

Hey, thanks for the comment - you're right.

It’s pronounced /ˈmɪgɛt/ – like it’s spelled, with a hard “g”. No relation to “midget”, no offense intended.

Thanks again for pointing it out!