- 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

> [...] 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.

Then I happened to become interested in software and become a SWE which forced me to again butt my head against this as the whole Linux world decided to go down this path. Every distribution, some worse than others, decided to choose completely different ways of doing things, Mint uses female names, Debian uses Toy story characters and who knows what Ubuntu is doing. Some are alphabetically ordered, some not, again creating unnecessary friction in understanding which one is older. Some that are in alphabetical order already reached V, what happens then?

You want to download Debian/Ubuntu cloud images? The web directory is indexed by the codename, same for bugs on launchpad. Are you checking a GitHub repo to build a package locally? Be prepared to know that it no longer supports Bookworm. And please, remember the codename of all the VPSs and Linux boxes you have around the house or you'll have to check every time a package doesn't work right.

This then forces me and everyone else to go the extra step of looking up which codename corresponds to which version, which is a complete waste of time. And even if you happen to know them, I would bet few people actually remember the mapping between codename and version after a few releases.

How did you come to terms with this?

TLDR: WTF?

Comments URL: https://news.ycombinator.com/item?id=43844777

Points: 6

# Comments: 5

  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.

  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.

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

There's no concept of "server" or "Change lobby" on Apex or other Battle royales.

You just queue up for a game, which lasts ~20 minutes. As you are in a 3 player team if you disconnect from the game you get a temp ban penalty, since that also degrades other players experience. So there's no disconnecting freely once a game has started. Now imagine you're playing for 10-15 minutes just to die without really having any chance. That gets frustrating, really quickly, since winning is close to the only "reward" you get from playing the game.

It's not like a classic COD or Battlefield game, where you can feely leave or join any game/server. Once you're in you're somewhat committed, and you have no control over where or with whom you're playing against.

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.

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

As seen in other environments, 3D printing lets anyone design and build for their own use case. People are not all about practicality, they want to like their environment too and being able to bring up your house exactly the way you like it is great.

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?

The website looks and feels like it was made by some undergrad that's following django+bootstrap class and has to deliver an entirely made-by-hand project the next day. Not that it would matter much normally, but there's really nothing inspiring confidence on it.

I see you're using Next+Tailwind+Supabase and the main Next instance is being diretly hosted on a bare metal server from Scaleway, https and all, which is a somewhat weird choice for a framework like Next that works very well with standard hosted/serverless options from your usual big providers.

Considering there's not much logic going on, since the DB and auth logic are being handled by a hosted version of supabase, the homepage links redirect to github and the storage request flow is akin to sending an email, this could explain the HN hug of death, since no proxy/cache/scalable option was used.

Furthermore, the email verification link was sent from a simple gmail alias, with no confirmation on the website part.

I wouldn't dox you publicly, but your full name, surname and YOB are visible in the email sender information (along with your private gmail address). This confirms my undergrad project hunch.

All of the above makes me even more concerned about what could happen with any data uploaded here.

Ultimately I don't trust this, and I would advise anyone else not to.

There's nothing wrong with experimenting, learning and building cool stuff, especially while young, but I would have considered a whole lot more things before posting in a community such as HN

I haven't encountered issues with "different versions of Docker." On the contrary, I've faced challenges with various versions of Python, PHP, packages, and system libraries when not using Docker. These are issues that simply don't arise within the Docker environment.

While it's true that some users neglect image hygiene, using the wrong base image or including unnecessary elements in the final image, I've noticed a decreasing trend in such practices.

Regarding configuration files, my understanding is that they remain the same files needed for a vanilla install, simply mapped inside a container.

In my opinion, Docker is not just "yet another thing to learn"; it's a single tool to learn and use universally, both now and in the future.

I'm not well-versed in PHP development. If I were to use a tool for PHP development, I would need PHP installed, but there are numerous versions available. Do I need Apache? Is it compatible with my three-year-old version? Will it work with a nightly build? What about Composer? Does it have dependencies?

And then there's the matter of the database. Now, I'd have to install and configure a complex piece of software with numerous dependencies. SQL is a familiar term to many, but not everyone is comfortable navigating the MySQL CLI, especially when it doesn't come by default on your machine.

But what about more than just experimenting? With Docker, a simple Compose file can be created to spin up a configured database, including all necessary dependencies. If required, it can also handle any migration or initialization needed.

I searched on youtube to ee if anyone made a video explaining it, but i'm back at square 1