thanzex

This was really fun to play with, I have a few suggestions: - As the airspace gets more congested, it becomes difficult to click the airplanes as you can also grab an existing path, messing everything up.

- The big stats table on the top left completely obscures a good portion of the map, making it harder than necessary. A togglable or semi-transparent option would be nice.

-The possibility of zooming or moving around could be nice

> [...] two years of carefully structured academic work disappeared [...]

> [...] but large parts of my work were lost forever [...]

I wouldn't really say parts of his work were lost. At most the output of an AI agent, nothing more.

If somehow e-mails, course descriptions, lectures, grant applications, exams and other tools, over the period of two years disappeared in an instant, they did not really exist to begin with.

For once, the actual important stuff is the deliverable of these chats, meaning these documents should exist somewhere. If we're being honest everything should be able to be recreated in an instant, given the outputs and if the actual intellectual work was being done by Mr. Bucher.

Does it suck to lose data? Even if just some AI tokens we developed an attachment to? Sure.

Would I have outed myself and my work shamelessly, to the point that clicking a "don't retain my data" option undermines your work like this? Not really.

I really don't understand this take. A script that installs all required dependencies is fine if and only if you are dedicating a machine to immich. It probably requires some version of node, with possibly hidden dependencies on some python, it uses ffmpeg, so all related libraries and executables need to be there. You then have a couple separate DBs, all communicating together. Let's not talk about updates! What if you're skipping versions? Now your "simple install script" becomes a fragile behemoth. I would NOT consider this if it was non docker-native. Plus, I don't have a server with enough resources for a lot of VMs, with all of their overhead and complications, just to have one per service. Nowadays there are many ways to run a container not just the original docker.com software, and you can do that on pretty much any platform. Even Android now!

I truly want to try it, but these lines give me the heeby jeebies:

  You hereby grant to us, our affiliates and our third party partners (“SPRING Parties”) an unconditional, irrevocable, non-exclusive, royalty-free, sublicensable, transferable, perpetual and worldwide license, to reproduce, use, and modify Your Content in connection with the provision and improvement of the Services and its underlying technologies, as well as for the SPRING Parties' respective business operations, in each case, to the extent permitted by applicable laws.

Which means they own everything that happens on trae and will use it for training, and then:

  You represent and warrant that any names, slogans, trademarks, logos and other designations you use in association with Your Content are owned by or duly licensed to you. You hereby grant SPRING Parties a non-exclusive, royalty-free, perpetual, transferable, sub-licensable, worldwide license to use, modify, reproduce, display, and distribute your relevant names, slogans, trademarks, logos and other designations on the Services for the purposes of operating and providing the Services to you.

Which means that anything you don't own and put on trae will automagically grant them a licence to use it.

Me too, when reading "open source" I was expecting some design docs or the like. Aside from the general confusion of the website, I haven't been able to find some of the most important information. For example, there's no diagram or immediate explanation of the general working principle and airflow path. The heat exchanger itself is published only as-is for those designs, while the author writes that he uses a custom python script tuned for the design size and his 3d printer to generate it.

When i saw this I immediately thought of studying it and reuse some of its designs for my custom use case, which does not appear to be currently possible.

At first glance it appears to be "open source" in the sense that you can buy it, but if and when something breaks you can print/reorder it easily.

Correct me if i'm wrong

I have to disagree, k8s is extensively documented and the reference docs and APIs are easily accessible. K8s at its core is a customizable, extensible, dynamic API server, with a focus on containerization. It's built with scale and customization in mind, you're not supposed to use it only for running a few containers. I've worked for people that use it to manage VMs with custom controllers. You can change pretty much anything and fit it to your needs. All this with defined, somewhat opinionated sane defaults and conventions

Edge does that

Not really. In my country, at least, it is explicitly stated in driving theory manuals to maintain at least one reaction distance between the car in front of you.

For a car traveling at 100Km/h the stopping+reaction distance would mean more than 130m, which is a quite large and possibly impractical for higher traffic scenarios.

I think that's not something that can be avoided, unfortunately. Any number of things could cause a train to suddenly stop. A mechanical failure, derailment, collision, a wagon could get detached... On roads we have millions of vehicles, carrying on average a very small amount of people, around 1.5. For efficiency sake we have accepted the risk of staying within reaction distance instead of stopping distance between vehicles.

It is a tradeoff between the safety of lives on board and traffic requirements that is relatively easier to accept when the average number of people involved is low against massive speed and efficiency gains.

The same cannot be said for trains though. Modern trains carry upwards of 1000 passengers, often at high speeds and without all of the safety and retention systems built into modern cars.

Having one or multiple trains with this large amount of people onboard be involved in a sudden catastrophic accident is possibly not worth the efficiency gained by thess than one minute separation.

Unfortunately we cannot just think about a normal scenario of simple deceleration

Seeing the fin still moving and keeping attitude despite being chewed trough was amazing

Many people before me have already pointed out many of the pain points of this project, but I'd like to ask you a few more things.

I'd like to start by congratulating though, this is no small feat!

As I understand it, this project requires an online connection to a hosted service. Said service is complex/heavy enough that it requires a k8s cluster or similar to run on, with databases, object storage, queues ecc.. Many already pointed out the unnecessary complexity, but the first thing i think of is: > I'm never going to use this for my projects.

As in: My laptop is full of dozens, maybe hundreds of started/ongoing/stalled/failed/abandoned projects, Only a fraction of those ever leave my machine.

I can start a project with a local git repo as easily as one folder and one command, and have peace of mind knowing that i can still record any change i make and archive the important stuff if it ever takes off.

What about checking out other people's work? To contribute now i either need my own compute, or have access to someone else's compute.

This all screams expensive , and we haven't even mentioned AI.

As a few already said, uploading every keystroke seems madness to me. I may be not as good a developer as others, but I constantly do things that I would not want uploaded anywhere, sometimes use dirty hacks like hardcoding secrets for testing. Let's not kid ourselves, we've all been in a position where the code was not well structured and we had to put in a magic string to make things work. Now the peace of mind that comes from the `watch` command made you upload everything, and maybe someone else's repo has already been auto-rebased onto it.

I get that you can not use the auto `watch` command, but it seems to me the whole project is centered around it.

Git is portable, I can share a folder/tarball and be done with it, this seems like google docs for coding, could I change provider if I wanted to? Backups now seem a fairly complicated ordeal.

As a side note, I've worked for one large national telco, I couldn't believe the amount of times servers broke or the VPN/Firewall/Wifi/network fairies had a bad day. Having the entire VCS be online only leaves me with an unshakeable scary feeling.

The only environment in which I see this being a possibly reasonable choice is an enterprise one. Unless someone makes a bet and starts offering a hosted version this looks to me simply not it for one developer, too expensive/complicated for a small group, yet too new for a large organization. And without the drive that comes from single developers that know how to use and trust it, the adoptions comes down to a bet made by some manager.

If i had to make one question, what is the future that you forsee for Grace? How would you spread its adoption without individual developers using it?