What makes you so sure that AI coding price will drop ? There are many reasons to think otherwise.

People do not generally want to build software to impress at parties, that is a very weird flex, even if you are trolling.

There is a huge difference between pushing your kids to overcome their current limits and forcing them to do something they do not enjoy at all.

There is indeed a difference between giving a slight push and "forcing" which is what TFA is talking about.

This is all fun and games until your kid has school assignments with deadlines

In the Netherlands we didn't get homework until 12 and lots of play time. Curious how that stacks up to other places.

Then you have a mediocre developer not willing to align his interests with those of the company. Cannot end well.

Totally agree there, the article makes complete confusion between the execution model and the tech used to execute. Especially since it says « not CGI as the protocol but as the model ».

As far as model goes, the serverless one is not a different model. It is still a flavor of the CGI concept. But the underlying tech is different. And not that much. It is only serverless for you as a customer. Technically speaking, it runs on servers in micro-VMs.

Those are orthogonal matters, and even if such tech as the middleware mentioned get some wind, the execution model is still the same and is not new.

Any tig users here ? I’m happy with it since then, looks like the feature set is pretty similar

tig rules.

gitui does not support vim keybinding for me, or I did not find out how.

rust's size always surprise me:

tig -- 600KB, gitui: 11MB

similar size pattern for other utilties, in general, rust executable is about 200x larger than its c/c++ peers, and, they all linked to similar c/c++ libraries, looks like rust stdlib is pretty big in size to me.

looks like there's a key binding file to enable vim bindings.

Having said that, I'm also a tig user and at least at first glance, I prefer its simplicity. Gitui presents a huge amount of info on the default screen and spends quite a lot of real estate drawing borders around everything. Tig just takes me straight to the commit history, full screen and then I have single key actions to get to other views.

The only thing I don't like with Tig is how little it binds to keys with the expectation that you set up your own mappings to git commands. I would prefer it baked more of them in so they would be standard and documented ... but that is a minor complaint.

+1 for opinionated-tig.

IIRC rust statically links crates used by the application, so it might not just be the stdlib that is causing this.

rust binaries are statically linked, that's the big difference. If you included all the libc code statically in most c programs they'd probably also be pretty big

Go programs are also statically linked and Go based CLI tools generally only come in at 3-4 MB IIRC. I've used static linking in binaries in Nim and C programs too with similar (or smaller) sizes.

Rust binaries are just impressively large. I'd guess part of it must be how Rust monomorphizes generics: https://rustc-dev-guide.rust-lang.org/backend/monomorph.html

if you strip them you tend to lose a lot of the fat.

Nice, any tips on how to do that? Is there a Cargo thing or just run regular ole strip?

strip will help to some extent, like 20% downsize, just not enough

when i have an embedded board with say 64mb storage,a few rust executable will fill them up fast. problem is that rust does not give me option to do dynamic link to its stdlib.

Not that this is based on some Googleing and experimentation; I could not find official docs.

It actually is possible to dynamically link to the standard library. Add this to your project's .cargo/config.toml file:

    [build]
    rustflags = ["-C", "prefer-dynamic"]

And add a reference to this crate, which copies the stdlib's shared library to your output directory:

https://github.com/WilliamVenner/prefer-dynamic

After you do `cargo build --release`, you will notice you hello world EXE is much smaller than a typical rust binary. Like 10~20KB small. On Windows it runs just fine. On Linux, I has to change the exe's RPATH to look for the standard library in the current directory:

    patchelf --set-rpath '$ORIGIN' ./exe_name

Anyways, it is possible. The rustc compiler itself is shipped in this way.

as far as i know,this is not officially supported.rust links to its stdlib statically by design. when you have to share this stdlib with a few dynamically linked rust crates it's hard to do in practice.

tried all size reduction tricks,still the size is much large,like 15x large than c,c++. even the stdlib is a 3x larger than to libstdc++

by default rust doesn't statically link to libc.

I bet that size could be brought down with link time optimization, at the cost of longer build times, and potentially slower performance.

The gitui has lto enabled.

gitui has much bigger feature set than tig. Rust binaries might be larger because Rust makes creating complex software possible.

"With friends like these who needs enemies?" All these glowing recommendations and no one shares the URL?

https://jonas.github.io/tig/

Tig combined with this vim plugin is big part of my workflow: https://github.com/iberianpig/tig-explorer.vim

Tig is just awesome. So well thought out, with sensible shortcuts for every relevant action in each context. Must have gone a lot of thought into it.

I use tig daily. I've never used anything I like as much for quickly browsing through commits in a repository or staging individual hunks.

how does tig compare to something like magit?

It only does a fraction of what magit does. I just use it for scrolling though the commit history, occasionally searching messages, and it's my tool of choice for staging/unstaging hunks.

It's the only tool I use to compliment the git cli.

I see. have you tried magit as a comparison? while magit can do everything it's got a very easy interface for most tasks. I don't use emacs for anything but magit to the point where i have a magit command on the command line to open up emacs in the current directory and then a spc-g-g opens up magit. it's that good.

So I use neovim as my editor, I'm familiar with fugitive but only use it for blaming.

I just prefer switching to my git tab in tmux and using the cli or tig deepening on what I'm doing.

Happy tig user. Viewing git history without it is painful.

I used tig way back in the day, but I have found `magit` to be superior and one of the most useful emacs packages that I use daily.

Yep tig is my world.

Nothing wrong with tig. It just works.

tig is perfection

This clearly is an ECS. I don't get why the author argues otherwise. It is fine to be an ECS.

Agreed. Entt is a popular ECS library that does all the things the author states separates his library from a traditional ECS ¯\_(ツ)_/¯