clement_b

Sad to see Windows has no more moat

Ah. Another 3 months delay for gemini-3.5-pro.

What's quite annoying is how agressive most products are into forcing this method over regular email+pw / Social Logins. Let me use my 100 chars password!

Amazing

Very interesting take and definitely an article I will come back to, but in the end, the size of tasks is relative, and the author counts them. How's that better than counting story points? Feels like a lot of folklore for a similar result. In the end, like with story points, what matters is the effort put into splitting a problem to better understand it and plan accordingly.

I have a git feeling this comment was written on mobile.

are you vraiment sure?

I actually did a one time backup using Take Out, then what I do is:

- Cloud Sync to keep a copy of my Google Drive. - Synology Photo on my phone to backup every new photo/video I take.

That way I benefit from Google software and storage + backup of my stuff without worrying about it.

I recently purchased a Synology with 2 disks in raid 1 to backup all my Google Drive, all my Google Photos files continuously.

I feel much better since doing this (apart, of course, for the fact I now need to back up my Synology too to really feel good!)

And for those who think Google Takeout is there to save you, just bear in mind it can be very erratic with large volumes (I had the biggest pain to get my Google Photo despite taking out less than 200 gb, it took several tries to have all the files)

No one is safe against account issue, or as it seems to be the case in the help thread, pure data loss. Just back things up and rely on cloud for flexibility rather than storage.

Incredible! On my end I see a year as:

- Jan to June on one row - July, August September in a column under June - October to December on one row, which is on the same row or next year's Jan.

All that left to right.

Have I just described a (weird) wall calendar?

I see a couple of things.

1) Some front end needs and/or frameworks were developped by companies having a scale and pool of talent justifying the needs for new tools tailored to their use cases (extreme audience = need to address many user specificities + pool of talents means the best brains on this planet invent something: doesn't help in coming up with a trivial solution). React, Flutter, AMP.

2) During the zirp, coming up with some great tech was also a way to attract talents. Using such tech was (is) a way to be part of that group too. There is a trend effect. I am wondering whether complex front end tech stacks are justified when you can't hire the best talents and when you need to work faster to keep in business.

3) Micro service all the things leads to using API's everywhere which leads to have consumers everywhere including your front end. Coming back from this could mean using simpler apps and dropping some of the front end complexity.

Probably more :)

Okay but what's the alternative that still involves fiddling with computers?

Feels like a problem that will be solved as soon as incentives will be here, and cost of fresh water from other sources depleted or protected. The costs mentioned in this 15 years old article aren't that high in a world where we have to be careful with water.

I wonder what is the reality now.