If Im not mistaken, they already delivered a payload in one of the previous flights, because they cut the transmission for a while and didn’t show the payload bay like one previous flight.
I’m not sure they are, if only because of the altitude. They only took Starship up to 200km, Starlink are nearly double that so while they do have thrusters that’s quite the distance.
Starship is not really in a true orbit, I forget the exact terminology but the trajectory is designed to re-enter regardless of what happens with the the flight.
It is in an suborbital trajectory but with enough energy to be equivalent to reaching orbit.
Think of it as instead of thrusting perpendicular to gravity for the most optimal energy usage Starship instead points its nose up gaining more altitude but now lacks the speed to miss earth as it comes down.
They actually made use of this this flight again - eq. they still did not perform a deorbit burn this flight & let the trajectory to pull them down to the atmosphere.
I would argue that Go is focused on writing web services and their stdlib is focused on providing those primitives. On the other hand Rust is more general programming language, so it's harder to add something to the stdlib that would not benefit the broader range of users.
TBH with Rust it's easier, because if it compiles, it works. While in the dynamic languages ecosystems is more risky and will require either way manual review, unless you have 100% test coverage that I would assume is very rare.
In manga aren't click bait titles, but because there are so many published, you pick basically a title that explains the premise, otherwise it's harder to get users to read your manga. I suppose that also could work with novels, I'm not a book person, but I suppose you read a review or watched some video that recommended you a book, and if the title is self descriptive, then would easier to go to the book store and buy something that might is your liking.
I suppose that you are not writing your db driver from scratch and you are using a driver that was at least written in the last 10 years, so it will support for sure prepared statements and you will use it, that means no possibility of SQL injections.
I also work on a legacy Ruby/Rails codebase, what I dislike is Ruby as a dynamic language, I'd prefer typed languages, but overall Rails didn't changed too much in the last 14 years that I know it (I didn't used too much in the past), but the concept is still the same to this day, few changes to the API/syntax, but otherwise if you know Rails, if you know Rails, it is most likely that you find very easy to work on any Rails app.
I would recommend to check out feTS[0], it infers the types from the endpoints without the need of generating files, I find this easier to work with because you don't have an extra step when the schema changes. I have to say I didn't used it yet, is on my radar to try it when the opportunity arrives.
One thing I like about the codegen approach is that the generated code provides a snapshot of the changes through time in my Git history, which I refer to quite often.
Thanks for sharing feTS. It looks pretty awesome and I will be checking it out.
When I was younger I was eager to experiment with things, abstractions, etc, now I want to write (in the web development context) as much html, vanilla js and raw sql.
Well a lot of jobs should be automated and more so those jobs that the pay check is low, but also another categories of jobs will be created, it might generate some unemployment but also new opportunities, how many jobs the computer took away and how many it generated?
> Cloud? Why? You can literally do anything on a VPS with Postgres!
In my case I don't want to maintain a server, but a web service, hence I'd prefer cloud most of the time.
> AI? Not on my watch! I can't imagine a tool that does more than VIM two decades ago!
There are a few instances where it's useful, but if you abuse the use of AI (copilot and co), then you will most likely not understand the code the same way if you were the one that wrote it, even if it is a 1:1 match.
> Javascript?! What a shit language.
Indeed Javascript is bad language, but it's hard to avoid if you work on the frontend, WASM is not yet there to be an alternative for most use cases.
> Everything should be written in Java or C++.
I would say at this point in time you will most likely to get away with Go (instead of Java) or Rust (instead of C++).
reply