Hacker News new | past | comments | ask | show | jobs | submit | a1o's comments login

Why do results need a license?

That's a misparse, I think:

"We are very proud of the results of this work and want to share it"

They want to share the work, not the results (otherwise the sentence would be "we want to share THEM").

The results of the research and development effort, e.g. the code and resources like documentation is how I was reading that sentence.

Can I use plausible in a desktop application? I would like to have an idea of exactly which versions of an open source desktop app I maintain are being actively used so I know what to pay attention and invest efforts as I would like my users to be constantly migrating forward - we do have like 20 years of backwards compatibility so we push things forward very slowly.

I don't see any reason why not: https://plausible.io/docs/events-api although you'd have to come up with your own user-agent

I was able to do it pretty easily with a mobile app, should be just as easy on desktop. You could even register custom “pages” for various parts of the desktop app.


I have the same experience.

Windows has a new terminal as default that is pretty cool - I install MSYS2 and set it in the new Windows Terminal and it's all good. Gnome Terminal and other terminals on Linux are also pretty cool too.

If you want the worst default terminal experience just boot macOS.

Can you explain what's the big appeal of other terminal apps? I have been using Terminal for 21 years without any issue -- but I'm open to trying something else.

Actually I've only this year switched to an "AI enabled" terminal app called Warp.

I’m curious to know what your experience of changing to Warp has been like? Sounds like terminal was working fine for you - was the switch worth the time?

I signed up for the waitlist ages ago and finally got the announcement of Linux support in February but am still yet to try it. Mainly because I’ve had a particularly busy year and I can’t justify fiddling around with my stack just for fun. I have no appetite for the risk I may lose hours to fixing something that goes wrong.

On Warp: After adjusting a couple of minor settings, I found Warp to be worth it. In fact, I at first trialed it 'side by side,' meaning keeping Terminal.app and Warp both open -- and found myself going for the Warp window more often. So it was an easy call for me.

I chose to not use its custom prompt because I wanted things to be more 'stock' in the terminal and not to rely on an app external to the shell for the features -- the only really fancy prompt feature I have is git branch display, and that's already working fine with my existing zsh prompt.

So, anyway, I can vouch that it didn't try to make changes to my environment (other than that offering to override the prompt, which I think it does in a way that doesn't update your .zshrc/.bashrc file anyway).

And for what it does do, I think it's great. Having command outputs separated and in little scrolling panes, really great. And mouse-able, standard text field to edit commands in, also amazing. Say you have a long URL on the clipboard with a {object_id} variable in the middle. You can paste it in, and use the mouse to select "{object_id}" and replace it instead of using arrow keys etc. to manually delete and replace the variable. So with the above efficiency gains it is already pretty cool compared to any kind of terminal app I knew of.

The AI stuff has been great to have as well. It's really convenient to have free access, right in the terminal, to an LLM that I assume has been well prompted to produce shell or scripting code as requested.

One thing I turned off is their recent "Detect natural language automatically" feature. Before, if you wanted to invoke AI, you just did a #comment. So for instance "# docker command to remove exited containers" -- well, they updated it so that even without that "#" it should "just know" from inspecting the command. But I had a problem with it getting confused by a shell command that was also parseable as 2 English words. I think I prefer actually knowing whether I'm commanding a shell or operating an LLM, anyway.

BTW - it occurs to me that there are also big categories of features that it has which I don't even use, such as like, runbooks that can automate frequently-done tasks, things like that. Those may also factor into your decision.

I use MSYS2 too, can't stand WSL. Foe my terminal choice, I find wezterm to be awesome for my daily 3 OS use.

I must be doing something wrong because I can just use Home to go to the beginning of the line and End to go to the end and I am pretty sure all the things that are easy to type as just as easy to type be in Gnome Terminal on Ubuntu or Windows Terminal on Windows.

The only place I need to know a bunch of weird shortcuts to figure things out is in the macOS terminal where everything is the less intuitive as possible.

These graphics have a lot that reminds me of Rock and Roll Racing for some reason


> clown

That's the best typo ever, I had an extension for chrome many years ago that allowed to replace "cloud" with a different word for funsies because it was used everywhere, might ressurect it using clown.

I'm not sure it is a typo. I have been calling it 'the clown' or 'the clod' for years. So I suspect others have been too.

This is like the nerd version of rule 34.

Deliberate. I’m working on a comic set in a dystopia run by AIs that have decided that “cartoon clowns” are the best way to tell humans what to do.

Do post links, previews, etc. :)

Gosh. "Clown Devices" :)

PS. Actually, it might be a good word for "self hosted cloud" setups, where you "[c]loud [own] (as in, 'ownership')" your data and infra is under user control ...

I don't get the dismissal of C++, to me constexpr is exactly that! And now if we get reflection in C++26 it will be possible to do even more incredible things using it, but constexpr is already pretty good.

Er- kinda? Maybe? Not really?

constexpr does not mean that you can evaluate arbitrary C++ code at compile time. It allows you to evaluate a _very specific subset_ of C++ at compile time that is not at all easy to wrap your head around: look no further than https://en.cppreference.com/w/cpp/language/constexpr to understand the limitations.

If you do this by hobby, if you ever have free time and want to play with c++11, here is an interpreter that is dear to my heart that I am curious if someone can figure how to speed it up - the tricky parts are the function calls.


The implementation that exists for clang is fast but we will see how it goes with MSVC and GCC.

At least is a proof existence that it can be done.

That doesn't mean much unfortunately, Clang had a fully working C99 designated initialization in C++ for many years, but the designated initialization that ended up in C++20 is only a butchered version of the full feature set despite Clang clearly demonstrating that it's possible to integrate the full C99 designated init feature set into C++.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact