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!

Even the statuspage is dead https://www.stackstatus.net/

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.

  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.

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

That's not a thing you can do on many games nowadays. I assume this comment is also related to this thread https://www.theverge.com/2024/10/31/24284644/apex-legends-lo...

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.

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

Maybe one of the few upsides of this tech is the customizability. Sure, you can get a prefab house built in a week or less if you try, but it's going to be constrained by the prefab shape and layout, even with modular blocks there are still design constraints, like with https://www.wikihouse.cc.

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.

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?

I don't know man, the website was first online on 2023-11-19, as reported by the first known https certificate, no information about who you are and what you're doing. I'm supposed to give you my data and my money/payment information, but as others like @bluehatbrit pointed out i know nothing else about your infrastructure, my data safety or the process behind the scenes. It takes time to save to LTO, how often is this done? Is my data going to be at risk for days?

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 seem to have a different perspective on this. My understanding of Docker and containerization, in general, is that their primary goal is to encapsulate all the necessary components to run a piece of software within a single, universally portable package.

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 want to say that graphically I like what i see, but having scrolled around your website and downloaded the ebook, i still have no idea what i'm looking at.

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

As they state, the demo only contains fake pricing data, presumably random-generated

I kind of hate the way they handle write calls, they tell you to just try it and if it fails with a readonly error your app has to respond with a specific header that lets fly redirect the whole request to the main region. On one hand it's fairly trivial, on the other it adds quite a bit of latency and now you need to customize your application code to the service(s) you're using, breaking portability. Since in their pg stack already includes proxies, I'd love for them to have the proxy simply redirect write queries to the correct location instead.

As aerzen pointed out, your homepage pegged my Ryzen 9 5900HS iGPU at 100%, you should consider frame limiting your spinning globe, or render it using some other technology or even rasterize it. It is completely unnecessary to have it consume so much computing

Except for the fact that usually there is not just one single typescript agent working within itself, for which you don't need validation. There are many cases in which you need to verify some object, anything that does not come from your code i would argue is untrusted, I come across this almost daily, it would be absolutely fantastic to just have a way to check does this object conform to this type? Instead, i need to use some external dependency, effectively duplicate my type definitions and add yet another place to introduce bugs.

I've read "AI", "superior", "exciting" and "qualcomm" about a dozen times, yet there is absolutely _zero_ information on what this thing is or what its capabilities/limitations/intended purposes are.

This comment makes no sense.

1- If the airline industry really had a problem about paying for a low bandwidth satellite data link for a 100MM $ aircraft, they could optimize things, such as using ground data links 90% of the time while switching to satellite only in the middle of the ocean.

2- If a pilot is suicidal, black boxes don't help either. It's like saying we don't a better car safety systems, if someone really wants to die they will smash their car to a tree. That's not why BBs exist. Even knowing that a pilot was the cause of a crash helps immensely in analysing their mental state prior to the event, you know, to prevent it from happening again.

That's realy the key there, you have a 100+Tons of metal and fuel with 100:300 people on board going close to the speed of sound. It NEEDS to be safe, but unfortunately, accidents happen. In such an event you HAVE TO know what happened, know if it was an accident or a voluntary action, the fault of equipment, software, procedure, pilot, ATC , anything really. Every procedure/safety system/training/design specification/ecc.. is literally written in blood from past mistakes.

If i know I shouldn't have left that pilot in the cockpit, great! I'll make sure no other pilot gets in that same mental condition.

As others have already said, you can get millions of executions of serverless functions for literal pennies on other platforms.

These serverless platforms already tend to cost A LOT more than running traditional servers, but your offering is 200,000 times pricier than an already costly option.

One thing to note here is that those traditional providers charge per request, while your product is priced on actions, which are blocks in the request flow. Realistically, any non-basic API will have several blocks for each request, thus considerably inflating your numbers.

To put things in perspective here, 1 Req/s is 2.5M Req/Mo which is already over your highest plan, and while it may be a considerable amount of volume for a medium app, it’s still something you could run on a $5 VPS and have 99% of your CPU sitting idle. For your proposed pricing, you could literally deploy tens or hundreds of dedicated servers around the world for each client that signs up and still end up being ridiculously overpriced.

As another example, given the current Reddit debacle, we know that an average user of theirs makes ~380 API Req/day. This means that 175 users would saturate the 2M actions in your highest Team plan. How would you justify 30.000$ for 175 MAU?

If these prices are somehow based on your costs for hosting the API you seriously need to rethink your internal efficiency

That said, I like the style and concept of the product, but there are still too many missing features, especially to justify a price that’s many orders of magnitude higher than anyone else.

The problem is that many, many 3P app users are some of the most active and engaged on the platform. For example, mods of literally thousand of the top subreddits use 3P apps for moderation.

Any new user would just use the official client, but the fact that so many alternative ones exist and so many people use them is telling of the unusable state of their app.

I use reddit every day, only because I don't use the official app, because of that it's become my go-to site to look for things, even on a computer.

If I lose access to my 3P client, which is tens of times faster, not clunky, customized to my liking, has all the shit sub filtering set-up and is generally a joy to use ( mind you, it has ads too) I will simply not bother anymore.

So, people that use 3P apps usually engage more because otherwise they wouldn't bother, this change is going to royally piss off every single one of them. In the short term maybe some users are going to switch, but in the long run I think the platform is going to lose lots of people that actually engage in the community.

Ah, yes! Of course! How couldn't anyone think of just increasing the price, no, double it and make it a subscription just to be sure we're making tons of money! Surely people will flock to our app now, a 60$/Y subscription to browse a social media platform where people tell each other off and meme.

This isn't the problem, if you're willing to just shed 95+% of you userbase, then sure, make everyone pay and have a first seat view of your app slowly dying.

I mean, GPT3 requires some 800GB of memory to run, do we all have gazillion dollars supercomputers at home? I think, unless there's some real breaktrough in the field or in the hw acceleration, this kind of model is going to stay locked behind a pricy API for quite some time.

This was incredibly impressive, I just wonder how expensive it is to save everything like this, for every frame they save the code, the compiled result, the game data, the changes, and code stepping.

Please, "The design is very harsh on the eyes." is an understatement, I really had a hard time navigating the pages and reading the text.

Just out of curiosity, did you code the pages by hand, not using any frontend/style framework? It sure does look like it.

I don't mean to be mean or just point and laugh at someone that is starting out, but I'll be blunt on what I found

I have no idea of what I'm looking at:

- There is little to no actionable information from the home page.

- The /algorithms page reports almost the same data as the homepage, still barely comprehensible. There I see the one and only suggestion that this may be some kind of paid service.

- Documentation: There is an empty square for some reason. The big empty squares overflow on the footer.

  - API Code in the same font as the text without highlighting? No actual information of the format of passed/returned data?

  - The user guide leaves me with even more questions than what I had before entering it.

  - The /available_assets page is flat out useless, No asset has a type or exchange, why have that table? The pagination is  aligned to the left, and I just have a regurgitation of some 20.000 symbols and names. I had to click the search button to see that the weird box on the top was a text field and not another UI glitch.

- The about us page has pretty much the same information present in the homepage, but with your face on it, still i know little about the website, or you for that matter.

- At the time of writing this, the CSS of register form is completely broken, and I mean completely. If you're posting to HN at least have something usable. Do you want me to give out all of my personally identifiable data, including a scan of my documents, to an entity that is so incredibly shady, on a website that is barely readable and has "terms of use created using Termly's Terms and Conditions Generator."? That's not going to happen. This saddens me a little since I won't be able to peek at the tools and pages once you're logged in.

- The footer and other elements changes size, shape and position in almost all the pages, do you just have HTML templates for the pages with copy-pasted elements?

- The homepage has 3 random canvas elements that are going to suck up all the GPU you can give them, I assume to look cool.

Please, let's not talk about mobile.

Again, I don't mean to be harsh or unnecessarily mean, but this is a bad execution. I did one Web project together with 2 other people that never touched frontend code before for a University project, working MAX 8 h/week for a month and I'm sorry to say that we did a better job at building a usable website.

I know that a pretty website is not the goal of this, and probably there's much more under the hood / in the reserved areas that I could not access but, especially when we're talking about money and investments, you simply cannot afford to look this bad.

Seeing as you're a one-man team, I would suggest working a little more on the presentation, maybe find someone willing to do it for you, or at least help you out.

There's much much more I'd like to ask, but for this comment I'm just going to focus on what I can visually see.

seems like a promising project! I'll definitely give this a spin, however, I landed on the page and I wasn't immediately sure about what i had in front of me, same goes for the github page.

If this is a software meant for developing with powerful collaboration tools, where is even just one screenshot of what it looks like? I don't want to sound like a tiktok kid that only cares about form over function, but there's absolutely nothing visual ( or written for that matter ) to illustrate this project.

Do I really have to pull the image, execute it and find out about the looks, features, and how to configure it? No introductory video? No Docs? Heck, not even a screenshot of the main page